Re: Unclear where ob-spice.el is being maintained

2023-09-01 Thread Ihor Radchenko
Bastien Guerry  writes:

>> We may consider tagging a new release.
>
> Yes, please go ahead as you see fit.

I made a minor release, because apparently org-contrib 0.4 supposed to
remove ob-spice.el already:
https://git.sr.ht/~bzg/org-contrib/commit/c6aef31ccfc7c4418c3b51e98f7c3bd8e255f5e6

https://git.sr.ht/~bzg/org-contrib/commit/dce101b4612e6deef814516779ce216e8eace569

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 



Re: Unclear where ob-spice.el is being maintained

2023-08-31 Thread Bastien Guerry
Ihor Radchenko  writes:

> Committed. Note that ob-spice was _not_ listed in the README.
> https://git.sr.ht/~bzg/org-contrib/commit/be51e9833b4f3393f4003c88131ba0a0a172c10d

Indeed!

> We may consider tagging a new release.

Yes, please go ahead as you see fit.

-- 
 Bastien Guerry



Re: Unclear where ob-spice.el is being maintained

2023-08-31 Thread Ihor Radchenko
Bastien Guerry  writes:

>> Bastien, it looks like we can now remove ob-spice from org-contrib.
>> Please, confirm.
>
> I do, thanks.

Committed. Note that ob-spice was _not_ listed in the README.
https://git.sr.ht/~bzg/org-contrib/commit/be51e9833b4f3393f4003c88131ba0a0a172c10d

We may consider tagging a new release.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 



Re: Unclear where ob-spice.el is being maintained

2023-08-30 Thread Jonas Bernoulli
Bastien Guerry  writes:

> Ihor Radchenko  writes:
>
>> "Christopher M. Miles"  writes:
>>
>>> Thanks, Updated now.
 ...
> Jonas Bernoulli  writes:
>
>> In 2022 I changed Melpa to get ob-spice.el from
>> https://repo.or.cz/ob-spice.git in response to
>> https://github.com/melpa/melpa/issues/7872#issuecomment-1034945112.
>>
>> But org-contrib still contains that file and the README at the new
>> location still contains
>>
>> Bastien, it looks like we can now remove ob-spice from org-contrib.
>> Please, confirm.
>
> I do, thanks.
>
> -- 
>  Bastien Guerry

 Thanks to all!
 Jonas



Re: Unclear where ob-spice.el is being maintained

2023-08-30 Thread Bastien Guerry
Ihor Radchenko  writes:

> "Christopher M. Miles"  writes:
>
>> Thanks, Updated now.
>>> ...
 Jonas Bernoulli  writes:

> In 2022 I changed Melpa to get ob-spice.el from
> https://repo.or.cz/ob-spice.git in response to
> https://github.com/melpa/melpa/issues/7872#issuecomment-1034945112.
>
> But org-contrib still contains that file and the README at the new
> location still contains
>
> Bastien, it looks like we can now remove ob-spice from org-contrib.
> Please, confirm.

I do, thanks.

-- 
 Bastien Guerry



Re: Unclear where ob-spice.el is being maintained

2023-08-30 Thread Ihor Radchenko
"Christopher M. Miles"  writes:

> Thanks, Updated now.
>> ...
>>> Jonas Bernoulli  writes:
>>>
 In 2022 I changed Melpa to get ob-spice.el from
 https://repo.or.cz/ob-spice.git in response to
 https://github.com/melpa/melpa/issues/7872#issuecomment-1034945112.

 But org-contrib still contains that file and the README at the new
 location still contains

Bastien, it looks like we can now remove ob-spice from org-contrib.
Please, confirm.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 



Re: Unclear where ob-spice.el is being maintained

2023-08-29 Thread Christopher M. Miles

Thanks, Updated now.

Jonas Bernoulli  writes:

> "Christopher M. Miles"  writes:
>
>> Jonas Bernoulli  writes:
>>
>>> In 2022 I changed Melpa to get ob-spice.el from
>>> https://repo.or.cz/ob-spice.git in response to
>>> https://github.com/melpa/melpa/issues/7872#issuecomment-1034945112.
>>>
>>> But org-contrib still contains that file and the README at the new
>>> location still contains
>>>
 This source code is from [[https://github.com/tiagoweber][tiagoweber]].
>>>
>>> and
>>>
 * Project status

 I put it in Org-mode contrib/ now.
>>>
>>> So... is this now being maintained by Stardiviner, at repo.or.cz,
>>> or not?
>>>
>>> If so, please update the README at the new location and remove the
>>> library from org-contrib.
>>>
>>>  Cheers,
>>>  Jonas
>>
>> The new repo https://repo.or.cz/ob-spice.git is maintained by me
>> (stardiviner).
>
> Yes, I know you are the maintainer now and that you maintain the
> package at https://repo.or.cz/ob-spice.git.
>
> However https://repo.or.cz/ob-spice.git/blob/HEAD:/README says:
>
> ,
> | * Project status
> | 
> | I put it in Org-mode contrib/ now.
> `
>
> I read this as "this package is being maintained in the "contrib/"
> directory of Org-mode."  It seems to me, this should just be removed.
>
> Further up in the same file it says:
>
> ,
> | * History
> | 
> | This source code is from [[https://github.com/tiagoweber][tiagoweber]].
> |  
> | - The first version is from 
> [[http://tiagoweber.github.io/blog/entry1.html][here]].
> | - The second version is from 
> [[http://tiagoweber.github.io/blog/entry4.html][here]].
> `
>
> This reads to me like "this is my personal fork of
> https://github.com/tiagoweber;.
>
> How about replacing all that with?:
>
> ,
> | ob-spice is now being maintained at https://repo.or.cz/ob-spice.
> | 
> | This package was originally written by 
> [[https://github.com/tiagoweber][Tiago Weber]].
> | You can find more (potentially outdated) information by him about
> | this package [[http://tiagoweber.github.io/blog/entry1.html][here]]
> | and [[http://tiagoweber.github.io/blog/entry4.html][here]].
> `


-- 

[ stardiviner ]
I try to make every word tell the meaning that I want to express without 
misunderstanding.

Blog: https://stardiviner.github.io/
IRC(libera.chat, freenode): stardiviner, Matrix: stardiviner
GPG: F09F650D7D674819892591401B5DF1C95AE89AC3


signature.asc
Description: PGP signature


Re: Unclear where ob-spice.el is being maintained

2023-08-29 Thread Jonas Bernoulli
>> Stardiviner, the readme in your repository still claims that the package
>> is being maintained in two other locations.  Please remove that outdated
>> information.
>>
>
> I have not found claimed two other locations in my README. Maybe I
> missed out. Can you point out?

See my other message from a few minutes ago.



Re: Unclear where ob-spice.el is being maintained

2023-08-29 Thread Jonas Bernoulli
"Christopher M. Miles"  writes:

> Jonas Bernoulli  writes:
>
>> In 2022 I changed Melpa to get ob-spice.el from
>> https://repo.or.cz/ob-spice.git in response to
>> https://github.com/melpa/melpa/issues/7872#issuecomment-1034945112.
>>
>> But org-contrib still contains that file and the README at the new
>> location still contains
>>
>>> This source code is from [[https://github.com/tiagoweber][tiagoweber]].
>>
>> and
>>
>>> * Project status
>>>
>>> I put it in Org-mode contrib/ now.
>>
>> So... is this now being maintained by Stardiviner, at repo.or.cz,
>> or not?
>>
>> If so, please update the README at the new location and remove the
>> library from org-contrib.
>>
>>  Cheers,
>>  Jonas
>
> The new repo https://repo.or.cz/ob-spice.git is maintained by me
> (stardiviner).

Yes, I know you are the maintainer now and that you maintain the
package at https://repo.or.cz/ob-spice.git.

However https://repo.or.cz/ob-spice.git/blob/HEAD:/README says:

,
| * Project status
| 
| I put it in Org-mode contrib/ now.
`

I read this as "this package is being maintained in the "contrib/"
directory of Org-mode."  It seems to me, this should just be removed.

Further up in the same file it says:

,
| * History
| 
| This source code is from [[https://github.com/tiagoweber][tiagoweber]].
|  
| - The first version is from 
[[http://tiagoweber.github.io/blog/entry1.html][here]].
| - The second version is from 
[[http://tiagoweber.github.io/blog/entry4.html][here]].
`

This reads to me like "this is my personal fork of
https://github.com/tiagoweber;.

How about replacing all that with?:

,
| ob-spice is now being maintained at https://repo.or.cz/ob-spice.
| 
| This package was originally written by [[https://github.com/tiagoweber][Tiago 
Weber]].
| You can find more (potentially outdated) information by him about
| this package [[http://tiagoweber.github.io/blog/entry1.html][here]]
| and [[http://tiagoweber.github.io/blog/entry4.html][here]].
`



Re: Unclear where ob-spice.el is being maintained

2023-08-27 Thread Christopher M. Miles

Jonas Bernoulli  writes:

> In 2022 I changed Melpa to get ob-spice.el from
> https://repo.or.cz/ob-spice.git in response to
> https://github.com/melpa/melpa/issues/7872#issuecomment-1034945112.
>
> But org-contrib still contains that file and the README at the new
> location still contains
>
>> This source code is from [[https://github.com/tiagoweber][tiagoweber]].
>
> and
>
>> * Project status
>>
>> I put it in Org-mode contrib/ now.
>
> So... is this now being maintained by Stardiviner, at repo.or.cz,
> or not?
>
> If so, please update the README at the new location and remove the
> library from org-contrib.
>
>  Cheers,
>  Jonas

The new repo https://repo.or.cz/ob-spice.git is maintained by me (stardiviner).

-- 

[ stardiviner ]
I try to make every word tell the meaning that I want to express without 
misunderstanding.

Blog: https://stardiviner.github.io/
IRC(libera.chat, freenode): stardiviner, Matrix: stardiviner
GPG: F09F650D7D674819892591401B5DF1C95AE89AC3


signature.asc
Description: PGP signature


Re: Unclear where ob-spice.el is being maintained

2023-08-27 Thread Christopher M. Miles

Jonas Bernoulli  writes:

> Ihor Radchenko  writes:
>
>> Jonas Bernoulli  writes:
>>
>>> In 2022 I changed Melpa to get ob-spice.el from
>>> https://repo.or.cz/ob-spice.git in response to
>>> https://github.com/melpa/melpa/issues/7872#issuecomment-1034945112.
>>
>> The last discussion was back in 2020 
>> https://list.orgmode.org/orgmode/cal1eyul8zzg-fdeedovbvm1cfc8w6ajwfr7cthvgs8owdwj...@mail.gmail.com/
>
> Bastien replied to that mentioning only one of the listed packages,
> which left me wondering "what about the others?".
>
>> However, your reference is 2022.
>> So, unless Christopher has something to say,
>> https://repo.or.cz/ob-spice.git is the last known active maintenance
>> location. The last commit is 2022
>> https://repo.or.cz/ob-spice.git/shortlog, and includes more changes
>> compared to ob-spice version in org-contrib.
>
> I came to the same conclusion but because ob-spice had not been removed
> from org-contrib, I wasn't sure.  Ihor, could you please remove it from
> org-contrib now?

I have already forget whether I taken the ob-spice maintaining task like
other libraries. So I'm not sure about it. I'm not work on this library
currently. From git log history, I'm the last maintainer. If you want to
maintain it or avoid duplicate, you can ask Bastien to remove it.

> Stardiviner, the readme in your repository still claims that the package
> is being maintained in two other locations.  Please remove that outdated
> information.
>

I have not found claimed two other locations in my README. Maybe I
missed out. Can you point out?

-- 

[ stardiviner ]
I try to make every word tell the meaning that I want to express without 
misunderstanding.

Blog: https://stardiviner.github.io/
IRC(libera.chat, freenode): stardiviner, Matrix: stardiviner
GPG: F09F650D7D674819892591401B5DF1C95AE89AC3


signature.asc
Description: PGP signature


Re: Unclear where ob-spice.el is being maintained

2023-08-27 Thread Jonas Bernoulli
Ihor Radchenko  writes:

> Jonas Bernoulli  writes:
>
>> In 2022 I changed Melpa to get ob-spice.el from
>> https://repo.or.cz/ob-spice.git in response to
>> https://github.com/melpa/melpa/issues/7872#issuecomment-1034945112.
>
> The last discussion was back in 2020 
> https://list.orgmode.org/orgmode/cal1eyul8zzg-fdeedovbvm1cfc8w6ajwfr7cthvgs8owdwj...@mail.gmail.com/

Bastien replied to that mentioning only one of the listed packages,
which left me wondering "what about the others?".

> However, your reference is 2022.
> So, unless Christopher has something to say,
> https://repo.or.cz/ob-spice.git is the last known active maintenance
> location. The last commit is 2022
> https://repo.or.cz/ob-spice.git/shortlog, and includes more changes
> compared to ob-spice version in org-contrib.

I came to the same conclusion but because ob-spice had not been removed
from org-contrib, I wasn't sure.  Ihor, could you please remove it from
org-contrib now?

Stardiviner, the readme in your repository still claims that the package
is being maintained in two other locations.  Please remove that outdated
information.

 Cheers,
 Jonas



Re: Unclear where ob-spice.el is being maintained

2023-08-25 Thread Ihor Radchenko
Jonas Bernoulli  writes:

> In 2022 I changed Melpa to get ob-spice.el from
> https://repo.or.cz/ob-spice.git in response to
> https://github.com/melpa/melpa/issues/7872#issuecomment-1034945112.

The last discussion was back in 2020 
https://list.orgmode.org/orgmode/cal1eyul8zzg-fdeedovbvm1cfc8w6ajwfr7cthvgs8owdwj...@mail.gmail.com/

However, your reference is 2022.
So, unless Christopher has something to say,
https://repo.or.cz/ob-spice.git is the last known active maintenance
location. The last commit is 2022
https://repo.or.cz/ob-spice.git/shortlog, and includes more changes
compared to ob-spice version in org-contrib.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 



Unclear where ob-spice.el is being maintained

2023-08-24 Thread Jonas Bernoulli
In 2022 I changed Melpa to get ob-spice.el from
https://repo.or.cz/ob-spice.git in response to
https://github.com/melpa/melpa/issues/7872#issuecomment-1034945112.

But org-contrib still contains that file and the README at the new
location still contains

> This source code is from [[https://github.com/tiagoweber][tiagoweber]].

and

> * Project status
>
> I put it in Org-mode contrib/ now.

So... is this now being maintained by Stardiviner, at repo.or.cz,
or not?

If so, please update the README at the new location and remove the
library from org-contrib.

 Cheers,
 Jonas