Hi, On Sat, Jul 24, 2010 at 6:20 PM, Richard Bateman <[email protected]> wrote: > > On Jul 24, 2010, at 1:43 PM, Jonathan Wage wrote: > >> You have to remember that Symfony2 is very new so everyone has to get >> familiar with it. The code is still only at preview release stability >> so it will take some time for things to be as active and easy to get >> community support as symfony 1. > > I understand, and I didn't mean that as a criticism; I am highly impressed by > Symfony2, which is why I'm using it. I was merely pointing out a problem > that doubtless others have had, as part of my reasoning for wanting a second > group. >
I think having a 2nd group wouldn't change anything. The problem is not enough people are knowledgeable about Symfony2 yet. The same problem would exist even if we created a 2nd group. I read the group and I filter the e-mails into Symfony1 and Symfony2 e-mails and I try to answer questions that I know the answer to and Fabien does the same. >>> If we could have our own group for sf2, that would be awesome! >>> >> >> I use filters for this to separate the group into symfony1 and >> symfony2 lists. That way we don't divide and split the community which >> I don't think would be a good thing. > > Is there, then, a convention for posting topics for one or the other? I have > seen a few posts with [symfony2 in the subject, etc, but that isn't > documented on the website or anything, so it's not something that newcomers > would be aware of. That would be extremely helpful to put on there. http://www.symfony-project.org/blog/2010/06/24/talk-about-symfony2-not-symfony-2 Basically just use "Symfony2". It can be in the subject or in the body. Most e-mail programs these days have a way to filter and apply labels to e-mails by searching the subject and body. I would recommend doing "[Symfony2] My Subject" as the subject line. > > I don't see having a seperate group as dividing the community so much as I > would see it as allowing a focus of specific interests. I realize that many > people are very interested in the 1.x symfony branches; I am as well, but > merely as a curiosity. I don't have time to read through all of the posts to > try to figure out if they apply to symfony2, and I don't ever plan to use the > old symfony framework. I'm sure that there are some similarities between the > two, but if so, they aren't significant enough that any of the emails I have > read through pertaining to symfony1 gave me any new insight as to how to use > or contribute to symfony2. > > In short, I don't really want to see *any* of the emails that only pertain to > symfony1, but I am currently forced to sift through them in order to find > anything that I *do* want to see. > > On the other hand, it would be very easy for someone interested in both > branches to subscribe to a second group. It would be much easier to find > answers to questions relating to symfony2, as someone could quite easily > search the google group page for symfony2. Currently, when I do a search on > the group page for this group or for symfony-users, I find little or nothing > of use, since close to every item returned pertains to symfony1 and not to > symfony2. > > Anyway, that's my $.02. If you leave it as is, I would appreciate any advice > you have on filtering -- that would work if I don't have other options. Well if we use the "Symfony2" keyword in posts pertaining to Symfony2 then you will be able to see all posts related to Symfony2 and only Symfony2. > > Also, where are the symfony2 docs stored that you can submit a pull request? > Are they in the git repo somewhere that I haven't stumbled across yet? If > so, that would be a great thing to include in the docs! > http://github.com/symfony/symfony-docs I think we probably need to add a section to the docs on how to contribute to the projects code and documentation. > The documentation on the web seems to have a lot of assumptions built in > about what the reader already knows that made it nearly unintelligible to me. > That could just mean that I'm dense, but I would love to go through and make > some small additions in places to clarify things that did not make sense to > me on my first couple reads through, if you'll just point me in the right > direction. > Sure things can always be better. We've just started last month and it will change a lot over the next few months so we'll keep your suggestions in mind and any specific changes would be much appreciated. Thanks, Jon > Thanks for all your hard work; this is the first framework I've found in 10 > years that inspired me to actually use it over the framework I wrote and used > internally 10 years ago. I am really excited to see it grow up, and hope to > be able to contribute. > > - taxilian -- Jonathan H. Wage http://www.twitter.com/jwage -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com 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
