I want the inbound email as well, and I'm sure we can setup the phpbb solution to notify us via email of any new threads
Sent from my iPad On Mar 26, 2013, at 12:15 AM, Marco Pivetta <ocram...@gmail.com> wrote: > Hey Fabien, > > I'd personally want to have new posts and answers in my inbox ASAP, so I'm > not sure if a forum software would do the trick. If it is possible to use a > mailing list, I'd prefer that solution. Yes, it's all old software, but it > works fine! > > Discourse looks really promising, but I think that what the community really > needs right now is just a tool to work with, not something to experiment. > Does anybody know if it can also work as a mailing list? If it ever goes in > the direction of a "forum please", then I'm all for trying this new tool. The > "double-clawed hammer" guy may be wrong at judging PHP, but he's great at > building community management software. > > > Marco Pivetta > > http://twitter.com/Ocramius > > http://ocramius.github.com/ > > > On 26 March 2013 07:52, Fabien Potencier <fabien.potenc...@gmail.com> 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 >> >> -- >> Fabien Potencier >> SensioLabs CEO - Symfony lead developer >> sensiolabs.com | symfony.com | fabien.potencier.org >> +33 1 40 99 80 80 >> >> -- >> -- >> 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 symfony-devs@googlegroups.com >> To unsubscribe from this group, send email to >> symfony-devs+unsubscr...@googlegroups.com >> 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 symfony-devs+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> > > -- > -- > 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 symfony-devs@googlegroups.com > To unsubscribe from this group, send email to > symfony-devs+unsubscr...@googlegroups.com > 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 symfony-devs+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > -- -- 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 symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com 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 symfony-devs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.