emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Gitlab Migration


From: Arthur Miller
Subject: Re: Gitlab Migration
Date: Sat, 28 Aug 2021 03:51:40 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Arthur Miller <arthur.miller@live.com>
>> Date: Thu, 26 Aug 2021 22:51:41 +0200
>> Cc: philipk@posteo.net, Eli Zaretskii <eliz@gnu.org>, danflscr@gmail.com,
>>  larsi@gnus.org, emacs-devel@gnu.org
>> 
>> Maybe Emacs project should be better at informing users about Emacs bug 
>> tracker:
>> 
>> https://debbugs.gnu.org/cgi/pkgreport.cgi?package=emacs
>> 
>> and this one:
>> 
>> https://debbugs.gnu.org/
>
> It's mentioned on line 45 of CONTRIBUTE, near the beginning of the
> "Getting involved with development" section.
>
>> and debbugs package for browsing bugs directly from Emacs?
>
> The debbugs package has several non-trivial dependencies, like email,
> and is probably not the first or the second thing newcomers should be
> messing with.

Maybe, but if somoeone is developer who would like to send in patch to Emacs
than they can probably setup email? Newcomer to Emacs dev, does not mean
newcomer to computing.

What about automating it for them?

Is this too wild: when someone signs FSF copyrights assignement, create
automatic "development mail account", which will work only to send and recieve
emails between certain addresses, the person and those used for Emacs
devs? We could then write a small pacakge to auto-setup persons account in
his/her Emacs that would work for bug repporting, debbugs, sending patches etc.

Limitiation because I guess FSF/GNU does not have resources to host free email
accounts for everyone.

We could then abstract parts of PR based worklfow on top of email.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]