Ihor Radchenko writes:
>> FWIW, I'd be inclined to leave the task for future action, perhaps
>> changing it to a WAITING keyword with a state-change note explaining the
>> status (that's what I use in my system, anyway). But if you disagree, I
>> won't argue.
>
> I do not mind. I can also
Samuel Wales writes:
> not following this.
>
> but it amused me:
> ...
This is not the final version we settled upon.
https://orgmode.org/worg/org-maintenance.html now has
The assignment process does not always go quickly; occasionally it
may get stuck or overlooked at the FSF. If
Adam Porter writes:
> 1. Having to use separate BEGIN and END macros is less convenient than
> more Lispy constructs, like a macro call with a string argument. But I
> guess, to wrap Org elements, like a TODO heading or inline task, it
> would be necessary. A macro call with the text as an
not following this.
but it amused me:
>> In rare cases, an inquiry from an
>> +Org maintainer gets the process moving again.
>
> may be missing something, but the last sentence now reads like our
>(Org maintainer's) inquiry rarely works.
while it can definitely read that way, to me as a
On 4/2/24 06:20, Ihor Radchenko wrote:
I just looked into changing this TODO into inlinetask and that would
require adding a style for inlinetasks. While looking, I noticed a
commented section in worg-editing.org:
...
Also, the above macros may we one existing way to provide
highlighting we
Adam Porter writes:
>> I am inclined to remove this todo - I already asked gnulib guys and they
>> contacted FSF about the latest version of the form. Until we get a
>> reply, there is nothing we can act upon. See
>> https://lists.gnu.org/archive/html/bug-gnulib/2024-03/msg00060.html
>
> FWIW,
On 3/30/24 06:08, Ihor Radchenko wrote:
This is actually not true that Emacs repository has a separate copyright
assignment form.
CONTRIBUTE file says
In most cases, to start the assignment process you should download
Adam Porter writes:
>> I think that we are not very accurate here.
>> According to
>> https://www.gnu.org/prep/maintain/maintain.html#Copyright-Papers:
>>
>> Once the conversation is under way and the contributor is ready for more
>> details, you should send one of the templates that
Adam Porter writes:
> Sure. I've pushed that, adding a "co-authored-by" line for Bastien.
Thanks!
--
Bastien Guerry
Adam Porter writes:
>> Actually, what Bastien suggested is slightly different.
>> See the attached tentative patch.
>
> Sure. I've pushed that, adding a "co-authored-by" line for Bastien.
Thanks!
On 3/28/24 07:01, Ihor Radchenko wrote:
Adam Porter writes:
On 3/26/24 09:59, Ihor Radchenko wrote:
I agree. My concern was not about dropping the previous wording.
What about
The assignment process does not always go quickly; occasionally it may
get stuck or overlooked at the FSF. If
Adam Porter writes:
> On 3/26/24 09:59, Ihor Radchenko wrote:
>
>> I agree. My concern was not about dropping the previous wording.
>>
>> What about
>>
>> The assignment process does not always go quickly; occasionally it may
>> get stuck or overlooked at the FSF. If there is no response to
On 3/26/24 09:59, Ihor Radchenko wrote:
I agree. My concern was not about dropping the previous wording.
What about
The assignment process does not always go quickly; occasionally it may
get stuck or overlooked at the FSF. If there is no response to the
contributor from FSF, Org mode
Adam Porter writes:
> ...
>> According to
>> https://www.gnu.org/prep/maintain/maintain.html#Copyright-Papers:
>> ...
>> We must use a specific form from a specific URL.
>
> That isn't how the Emacs maintainers handle it. They send a form by
> email when asked, or direct users to use the one
On 3/24/24 07:35, Ihor Radchenko wrote:
+New contributors need to submit the
[[https://orgmode.org/request-assign-future.txt][form]] to the FSF.
+#+begin_center
...
+TODO: Get updated version of form from Emacs maintainers that includes the
line asking the secretary to send confirmation to
Ihor Radchenko writes:
> Sounds reasonable.
OKay -- feel free to go ahead with whatever version you find best.
> It is a longer period compared to 5 business days mentioned in
> https://www.gnu.org/prep/maintain/maintain.html, but the copyright clerk
> is just a single guy taking care about
Bastien Guerry writes:
> Until Org maintainers get an email confirmation for when a copyright
> assignment process is done, we can simply suggest contributors to wait
> a month before pinging the copyright clerk and to CC Org maintainers
> when doing so. WDYT?
Sounds reasonable.
It is a longer
Until Org maintainers get an email confirmation for when a copyright
assignment process is done, we can simply suggest contributors to wait
a month before pinging the copyright clerk and to CC Org maintainers
when doing so. WDYT?
--
Bastien Guerry
Dear Adam, Bastien,
> +New contributors need to submit the
> [[https://orgmode.org/request-assign-future.txt][form]] to the FSF.
> +#+begin_center
> ...
> +TODO: Get updated version of form from Emacs maintainers that includes the
> line asking the secretary to send confirmation to interested
19 matches
Mail list logo
