IMHO, even the pharo-users and pharo-dev mailing lists should be together. We're a too small community to have fragmentation when we can avoid it.
Pharo should be documented/self-documented and stable enough to not require newcomers to subscribe to a mailing list to get answers to their normal problems. Mailing lists are old-fashioned for getting answers of "common" problems, usage, etc, for everything else, maybe StackOverflow is a good tool to use, and also a display for Pharo community. Less is more. :) Esteban A. Maringolo 2013/1/29 Esteban Lorenzano <[email protected]>: > well.. I more or less agree with Torsten (even if I already subscribed): > component parts of Pharo should be kept together, otherwise... why not to > create a group for mophic, for zinc, for filesystem, etc.? > jutst to have a nice header? do you know you have some rules that you can > apply to auto-label mails? :) > > > > On Jan 29, 2013, at 9:15 AM, Camillo Bruni <[email protected]> wrote: > >> subscribe and you're done, >> >> the thing you get for Free is a decent title in the message in your mail >> client. >> For me that saves a couple of second on each mail to check about what it is. >> >> >> On 2013-01-29, at 08:40, Torsten Bergmann <[email protected]> wrote: >> >>> I dislike outsourcing it to a google group. NB is now part of the image >>> and the discussion should be here as well. >> >> valid point. but then again, we will anyway allways announce changes made by >> NativeBoost automatically via the update mails. >> >> Besides, the issue tracker is also no longer in the mailinglist, which is >> essentially >> the heart of development? How do you argue in favor of that? >> >>> Otherwise we end up with too many places nobody will be able >>> to follow or find... >> >> invalid point: >> well then the INRIA mailing lists are the worst place since they don't have >> a proper index either. the only thing that get's indexed is the mapped forum >> on http://forum.world.st/ >> >>> Please close the group since it adds more confusion. >> >> nah, my personal opinion outweighs, besides you're always free to not use >> it... > >
