Good Old Mailman is for me the best solution :)

On Tue, Mar 26, 2013 at 12:21 PM, Matt Robinson <[email protected]> wrote:

> As far as I know, PHPbb doesn't do email round-tripping (putting email
> replies back on the site), but something like https://postmarkapp.com or
> http://context.io could help that integration if necessary. I've tried
> doing email integration manually before, and it's one of those things where
> you can get 90% of the way in no time at all, and then (since email
> implementations are so varied and so horrible), the remaining 10% will kill
> you :P.
>
> As Fabien pointed out, we've had the forums since 2005, so I suspect that
> most of the people reading this largely prefer the mailing list (in other
> words, we've had the choice for years, and we've chosen not to use the
> forums). The question is whether to respect that or force the communities
> together. If there's a clear benefit to doing so, then we should probably
> just get it over with. If nothing else, it should be a boost to the phpbb
> development community ;). If on the other hand merging the communities is
> out of nothing more than a desire for neatness (not saying it is), then we
> should probably just set up Mailman or Lamson or whatever and carry on as
> if nothing happened.
>
> I used to run a moderately sized (hundreds of users) mailing list and
> transitioned it to a moderately sized (thousands of users) forum. The
> biggest difference I saw was that with a mailing list, everyone sees
> everything; it's self-limiting (and limited). With a forum, people tend to
> specialise into sub-forums as the amount of traffic grows, becoming less
> cohesive but allowing for a lot more growth. It also seemed that mailing
> list and forum had very different tones - the format and delivery of the
> discussion have an effect on the kind of discussion that's had. This isn't
> necessarily a bad thing - more people get actively involved in discussions
> on forums than they did on mailing lists, where they'd usually just lurk.
> It means more work for moderators to keep everything on topic, but it also
> means that there's more involvement from the wider community.
>
>
> On 26 Mar 2013, at 09:15, David Buchmann <[email protected]> wrote:
>
> > can phpbb also handle answering to emails? sort of like github or jira,
> > where an answer email creates a new comment on the issue...
> >
> > then i think we could take this as a chance to re-unite the forum and
> > mailinglist communities.
> >
> > if it won't be possible to answer by email, we either need somebody to
> > build such a plugin or find something else imho.
> >
> > cheers,david
> >
> >
> > Am 26.03.2013 08:45, schrieb Bob den Otter:
> >> PHPBB supports sending emails "out of the box". Both for threads you've
> >> posted in as well as forums/threads you've subscribed to. Not that i'm
> >> saying it's the best way to go, just to let you know that this isn't a
> >> big reason _not_ to choose it.
> >>
> >> Personally, i'd think a Stack Overflow or Discourse site would work
> great.
> >>
> >> Cheers, Bob.
> >>
> >> Op dinsdag 26 maart 2013 07:52:00 UTC+1 schreef Fabien Potencier het
> >> volgende:
> >>
> >>    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 <http://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 <http://sensiolabs.com> | symfony.com
> >>    <http://symfony.com> | fabien.potencier.org
> >>    <http://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 [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.
> >>
> >>
> >
> > --
> > Liip AG // Agile Web Development // T +41 26 422 25 11
> > CH-1700 Fribourg // PGP 0xA581808B // www.liip.ch
> >
> > --
> > --
> > 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.
> >
> >
>
> --
> --
> 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.
>
>
>

-- 
-- 
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.


Reply via email to