On 24-01-2026 08:26:06 +0100, Rene Kita wrote: > As discussed in [0] feature requests should be discussed on the mailing > list before being added to the issue tracker. Add some notes to make > this more clear to the user.
What are you going to do when people did not post to the ML first, close their requests? Perhaps document that too, so it is clear to anyone being used to using facilities like gitlab and the workflow as encouraged therein. > While at it, copy a NOTE from the web site about the need to be > subscribed in order to post to a ML. > > [0]: https://marc.info/?l=mutt-dev&m=176822608723403&w=2 > --- > > Can/Should we also add a note to the issue tracker itself? I can imagine > most users go straight to the issue tracker after learning that mutt is > hosted on gitlab. At least github has a way to make users go through elaborate instructions before filing an issue (e.g. see openwrt, where new issue even gets you a menu approach with a form to fill in required info), which could include a checkbox for "I have discussed this feature on the ML". I would hope gitlab would have similar functionalities. Apparently there's something like a template https://docs.gitlab.com/user/project/description_templates/ which looks as if that can be used to give instructions while filing an issue to achieve the above. If that works, like I hope it does, could avoid a lot of disappointments for people filing requests while putting a lot of effort into it. Thanks, Fabian > > doc/manual.xml.head | 10 +++++++++- > doc/mutt.man | 3 +++ > 2 files changed, 12 insertions(+), 1 deletion(-) > > diff --git a/doc/manual.xml.head b/doc/manual.xml.head > index 0aff614b..b0c8e056 100644 > --- a/doc/manual.xml.head > +++ b/doc/manual.xml.head > @@ -79,6 +79,14 @@ automatically forwarded to > <emphasis>mutt-users</emphasis>, so you do > not need to be subscribed to both lists. > </para> > > +<para> > +NOTE: You MUST be subscribed to a list in order to post to it. > +This is not to make your life harder, > +but to reduce SPAM and/or UCE. > +The mailing list software being used is GNU Mailman, > +with its implied deficiencies. > +</para> > + > </sect1> > > <sect1 id="distribution"> > @@ -107,7 +115,7 @@ For version control access, please refer to the > <term>Bug Tracking System</term> > <listitem> > <para> > -The official Mutt bug tracking system can be found at > +The official Mutt bug tracking system (not for feature requests) can be > found at > <ulink > url="https://gitlab.com/muttmua/mutt/issues";>https://gitlab.com/muttmua/mutt/issues</ulink> > </para> > </listitem> > diff --git a/doc/mutt.man b/doc/mutt.man > index 12f34bd6..1b19b84d 100644 > --- a/doc/mutt.man > +++ b/doc/mutt.man > @@ -306,6 +306,9 @@ for one of the functions listed while Mutt is running. > .PP > For a more up-to-date list of bugs, errm, fleas, please visit the > mutt project's bug tracking system under > https://gitlab.com/muttmua/mutt/issues. > +NOTE: The bug tracking system is not meant for feature requests. > +These should go to the mutt-users mailing list, > +see section 1.2 Mailing Lists of the manual for details. > .SH NO WARRANTIES > This program is distributed in the hope that it will be useful, > but WITHOUT ANY WARRANTY; without even the implied warranty of > -- > 2.51.0 > -- Fabian Groffen 80C6 A09A 8D33 302C 1D2C Gentoo on a different level 06A9 3DC1 26BC 457C 8490
signature.asc
Description: PGP signature
