[gnutls-devel] should we deprecate the development ML?
nmav at gnutls.org
Mon Jul 9 16:27:46 CEST 2018
On Tue, Jul 3, 2018 at 7:19 PM Andreas Metzler <ametzler at bebt.de> wrote:
> On 2018-07-03 Nikos Mavrogiannopoulos <nmav at gnutls.org> wrote:
> > The workflow for gnutls at this point is:
> > 1. Issues and patches can be send via the web by registering (or using
> > other side credentials)
> > 2. Issues can be opened by sending a mail to bugs at gnutls.org
> > <bug-gnutls at gnutls.org>
> > 3. Issues can be brought to gnutls-dev ML
> > 4. Issues can be brought to help-gnutls ML
> > What I'd like is to reduce the amount of places where issues can be
> > and discussed to make it easier to keep track of.
> > Both Andreas and you make the point for gitlab discussions being more
> > easily available and searchable. Would a read-only gnutls-dev which
> > receives gitlab traffic, address that?
> A readonly gnutls-dev would improve things a lot.
Ok, I'll try to make this transition this month.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gnutls-devel