I've never been a big fan of forums, I think they split thing up to much (all the boards with subboards, etc). So I've used the mailing-list a lot. Nice immediate updates of everything, plus you only need one client for all lists out there.
So when we're choosing between A and B, I would go with A (mailing-list). I do think Discourse looks very promising. I think it combines many of pros of both a forum and mailing-list. So in favour of "staying up-to-date" and "bringing the community together", I would say ditch both the forum and mailing-list, and replace them with Discourse. I also think a dedicated StackOverflow site would be a good idea. The community (including me) is already using StackOverflow, because it's great for what it solves. I know it's a 3rd party service (so not an option for the problem being addressed), but I do want to mention that I think StackOverflow and Discourse would compliment eachother very nicely (StackOverflow for Q/A, Discourse for other discussions). -- Jasper N. Brouwer On 26-03-2013, at 07:52, Fabien Potencier <[email protected]> wrote: > Hi all, > > Unfortunately and for no reasons, the Symfony2 mailing-list is gone for the > second time in a very short period of time. It happened some weeks ago and I > was not able to contact anyone about the issue. The mailing-list came back > and still not a single email from Google about what happened. > > So, I think it's time to move on. We cannot be hostages of Google for our > support and our knowledge base. There are several options to replace the > Google mailing-lists and I want to get your opinion on the best one to choose > before doing anything (the decision will probably also impact all my other > mailing-lists on Google - Swiftmailer, Silex, Twig, ...): > > * A - Migrate all the discussions on the Symfony forum > (forum.symfony-project.org). > > * Pros: it's online since 2005, it has a massive amount of registered > people, we already have a big archive of knowledge there, it's written with > phpBB (which uses Symfony and several core team members are also part of the > Symfony community), it allows us to unify the community, which is split right > now. > > * Cons: Some people don't like forums because they want everything to happen > in an email client (but it might be possible to use phpBB that way too). > > * B - Host our own mailing-list software and provide the same kind of service > as Google Groups > > * Pros: The disruption won't be big with what we have now. > > * Cons: The community will still be split in two, only because of some > preferences. What kind of software to use? All of them seems old and > outdated. The only one that looks great is Lamson (http://lamsonproject.org/). > > * C - Use a more "modern" approach to discussions like the recently released > Discourse software (http://www.discourse.org/) -- which is Open-Source. > > Of course, relying on a third-party is not an option anymore. So, stack > overflow or any other forum/mailing-list providers are not an option. > > jQuery chose the first option (A) some time ago and they don't seem to regret > it. Drupal also uses a forum and no mailing-list as far as I know. So, that > works. > > Zend Framework and many other Open-Source projects hosts their own > mailing-lists. > > My personal preference is either A or B without a clear winner. A is probably > better for the community, B is probably less disruptive. > > What do you want us to do? > > Cheers, > Fabien -- -- If you want to report a vulnerability issue on Symfony, please read the procedure on http://symfony.com/security You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en --- You received this message because you are subscribed to the Google Groups "Symfony developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
