Re: Separate Mailing Lists for Patches vs General Dev Discussion?

On Fri, Jul 29, 2016 at 01:56:36PM +0200, Vincent Legoll wrote: > There's not silver bullet for this Some blacksmith should forge one ;) I think there is a real demand for a good hybrid mailing list / web page software development interface.

Re: Separate Mailing Lists for Patches vs General Dev Discussion?

>> But resurrection & real use of patchwork (or any other consensus >> web tracker) would be a plus for at least some of us newcomers >> from different horizons. > > The instance at is > not widely used, it seems. > Part of the problem is that

Re: Separate Mailing Lists for Patches vs General Dev Discussion?

Hi, Vincent Legoll skribis: > But resurrection & real use of patchwork (or any other consensus > web tracker) would be a plus for at least some of us newcomers > from different horizons. The instance at is not

Re: Separate Mailing Lists for Patches vs General Dev Discussion?

Hi, On Mon, 25 Jul 2016 22:35:57 +0200 Florian Paul Schmidt wrote: > I'm following the Guix-Project, even if not contributing much because of > time constraints. The one, very simple to implement, thing that would > make following the project more easy IMHO would be a

Re: Separate Mailing Lists for Patches vs General Dev Discussion?

I'm not sure a separate additional ML would enhance the situation, the combined volume is low enough to let them stay together. But resurrection & real use of patchwork (or any other consensus web tracker) would be a plus for at least some of us newcomers from different horizons. I can

Re: Separate Mailing Lists for Patches vs General Dev Discussion?

Hello! Florian Paul Schmidt skribis: > I'm following the Guix-Project, even if not contributing much because > of time constraints. The one, very simple to implement, thing that > would make following the project more easy IMHO would be a separate > list for patches. Or

Re: Separate Mailing Lists for Patches vs General Dev Discussion?

On Tue, Jul 26, 2016 at 10:44:48AM +, ng0 wrote: > I would say we could keep "guix-devel" for patches and > discussions around them and create another list for discussion, > for example "guix-discuss". > No fix, but could help to separate patches and general > discussions. Notice we already

Re: Separate Mailing Lists for Patches vs General Dev Discussion?

Hi, Florian Paul Schmidt writes: > Hi, > > I'm following the Guix-Project, even if not contributing much because > of time constraints. The one, very simple to implement, thing that > would make following the project more easy IMHO would be a separate > list for patches. Or maybe the other way

Separate Mailing Lists for Patches vs General Dev Discussion?

Hi, I'm following the Guix-Project, even if not contributing much because of time constraints. The one, very simple to implement, thing that would make following the project more easy IMHO would be a separate list for patches. Or maybe the other way around: A separate list for more general