It seems fine to me the way it is, but if it's really bothering some people
then I think it'd be better to move Symfony 1.4 to a symfony-legacy mailing
list, so that discussion of the latest always happens on symfony-users. Then
when 3.0 comes out in the age of jet-packs and food pills, we
On 5/16/11 7:15 PM, keymaster wrote:
Having all the symfony 1.x releases mixed in with Symfony 2 posts can
sometimes make it difficult to discern which Symfony people are talking
about in their posts.
Not everyone is explicit on whether they are referring to Symfony1 or
Symfony2.
This is not
I don't think this is a good idea. I often have a few minutes spare in my
busy day and can quickly browse my inbox to see if there are any people I
can help. Pushing everything to the forums will mean less people that can
just quickly pop in a reply to a problem someone is having.
I, personally,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
i am also afraid that the forums could have less replies.
unless people are so kind as to subscribe to get emails for the areas
they are interested in, and take the pain to go to the forum to type an
answer.
on the other hand, this list sees more
On Tue, May 17, 2011 at 2:45 AM, Gareth McCumskey gmccums...@gmail.comwrote:
I don't think this is a good idea. I often have a few minutes spare in my
busy day and can quickly browse my inbox to see if there are any people I
can help. Pushing everything to the forums will mean less people that
+1
I would be happy with either different mailing lists, or shutting these down
in favor of the forums. But it's definitely not working the way it is now.
I do agree that forums will see less traffic though.
I think splitting the community can also be seen as organizing the
community or helping
+1 for splitting mailing lists. If someone wants to see Symfony 1 and 2
messages, he/she could just join both groups. I don't really like forums so
I don't have an opinion about that. I don't really mind if there's a forum
or not. Having these mailing lists is really enough for me, so splitting
+1
Am 16.05.2011 19:15, schrieb keymaster:
Having all the symfony 1.x releases mixed in with Symfony 2 posts can
sometimes make it difficult to discern which Symfony people are talking
about in their posts.
Not everyone is explicit on whether they are referring to Symfony1 or
Symfony2.
Having all the symfony 1.x releases mixed in with Symfony 2 posts can
sometimes make it difficult to discern which Symfony people are talking
about in their posts.
Not everyone is explicit on whether they are referring to Symfony1 or
Symfony2.
This is not only a problem for those working on
On Mon, May 16, 2011 at 1:15 PM, keymaster ad...@optionosophy.com wrote:
Having all the symfony 1.x releases mixed in with Symfony 2 posts can
sometimes make it difficult to discern which Symfony people are talking
about in their posts.
Not everyone is explicit on whether they are referring
Legacy sounds a little bit like les misérables hahaha. I'm pretty sure
that S1 people will feel like the forgotten ones with this title.
But the point is that we think that this list is becoming inmantainable.
Symfony 1 y so different to Symfony 2, that this can be compared to having a
CakePHP
11 matches
Mail list logo
