I think we mix up 2 (or 3) different things in this topic. Let's say a contributor wants to implement some feature:
First some discussion should probably happen, for example other developers can help with pointers on how said feature can and should be integrated into DT core. I don't see any need for this to be stored anywhere or accessed by everyone else, because a lot of it will be discarded ideas and just thoughts "out loud". Having to formulate them carefully (as it's expected with mailing lists or forums) will just impede communications at this stage. Historically IRC was used and I think it's still the best tool, the only problem here is timezone differences between developers. Another issue is documenting the design of said feature. Right now such documentation is basically absent in DT, but I think it would be very useful. Something like wiki can be used for this purpose and DT actually already had it for a long time: https://redmine.darktable.org/projects/darktable/wiki Of course nobody wants to write documentation, and my suggestions that it should be done were already rejected for a couple of big features recently merged into git master. I don't really see this changing just because we choose some platform that currently is in fashion. Somewhat separate issue are discussions about release planning and so on. These I think concern only a limited number of people (specifically developers with commit rights and package maintainers) and also historically happened in IRC. Probably mailing list can be used also for these, depending on the topic (if there's a lot to discuss it's more efficient to have real-time communication though). But all this of course is just idealisation, real life makes corrections and compromises have to be taken. So I would suggest not to overthink it with "pros" and "cons" of various technologies and just make sure that necessary people are included in the loop of decision making whatever way is actually possible. On Wed, 17 Apr 2019 13:26:08 -0400 William Ferguson <wpfergu...@gmail.com> wrote: > We are facing the same issue, where to discuss things, with the lua-scripts > repository. We've thought about using github issues and discuss.pixls.us, > but we still haven't come up with a solution. I think I'm just going to > try the github issues and see how it goes. > > Bill > > On Wed, Apr 17, 2019 at 1:22 PM Pascal Obry <pas...@obry.net> wrote: > > > Le mercredi 17 avril 2019 à 14:12 -0300, Moritz Moeller a écrit : > > > But I agree with parent that it is not the right tool to discuss big > > > changes. > > > IRC has no history. IRC has no message threads. > > > That's why I mentioned NNTP. > > > > My first best is GitHub Issues. > > > > You create an enhancement request there. It is discussed, we can add > > some design notes... > > > > Then a PR is created for this and the PR can (should) reference the > > issue number for tracking purpose. Then you'll end up with a commit > > with a reference to the design. > > > > We can't do best :) > > > > -- > > Pascal Obry / Magny Les Hameaux (78) > > > > The best way to travel is by means of imagination > > > > http://www.obry.net > > > > gpg --keyserver keys.gnupg.net --recv-key F949BD3B > > > > ___________________________________________________________________________ > > darktable developer mailing list > > to unsubscribe send a mail to > > darktable-dev+unsubscr...@lists.darktable.org > > > > > > ___________________________________________________________________________ > darktable developer mailing list > to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org > ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
