Re: On Contributing To Emacs

[Óscar Fuentes]

Po Lu <luangruo@yahoo.com> writes:

> Óscar Fuentes <ofv@wanadoo.es> writes:
>
>> And basic things like (un)subscribing to a bug, subcomponents (with
>> subscriptions),
>
> Don't we already have that?  (Where you give debbugs an incantation
> along the lines of "Package: emacs,component-here", and it will DTRT.)
>
> It's just that not many people make use of it.

Maybe that hints at an usability problem?

>> not having to CC every participant which is not already on the CC list
>> of the mail you are responding to, etc.
>
> I never found that to be a problem with debbugs.  I think you only have
> to CC the bug address.

Sadly, no. If I submit a bug and get responses to the original report
from Alice and Bob, then I answer Alice's message, Bob wont see it
unless I add his address to the CC list on my message to Alice.

>> Extra points if the new system does not require to read a manual for
>> closing, reopening or categorizing bugs.
>
> I haven't seen such a system to date, and that includes SourceHut.

Well, just to name an example, bugzilla which is both popular and
ancient, hardly needs any instructions to do those trivial things.

>> For now let's put aside cross-references between commits, bugs, patch
>> submissions and C.I. runs as something too modern to bear.
>
> FWIW, My experience is that stuff always gets in the way.

In my experience is really convenient.

>> It is already possible on debbugs.gnu.org, for some sufficiently broad
>> definition of "possible".
>
> It's not possible on debbugs.gnu.org, which doesn't let you submit
> reports from a web browser.

The mentioned guix debbugs frontend doesn't allow that either. It says
it is disabled, the question is: why?

>> Famous last words.
>
> No.  If you can submit comments, you can send e-mail, which means adding
> an attachment to the email should be a fairly trivial task.

You can attach cat pics too :-) The hard part is not attaching patches,
the hard part is to recognize and handle them so they are automatically
available to the related tools (conflict detection, quick merge, run
C.I. on the patch, etc.)