I agree with stof also. That would also open the opportunity for individuals to provide patches along with their suggestions.
On Wed, May 11, 2011 at 11:07 AM, Luis Cordova <cordo...@gmail.com> wrote: > fully agreeing with Stof > > On Wed, May 11, 2011 at 11:06 AM, Christophe COEVOET <s...@notk.org> > wrote: > > Le 11/05/2011 17:45, keymaster a écrit : > >> > >> The documentation is slowly improving, thanks very much to those > involved. > >> > >> Symfony2 is a huge framework, and the documentation undertaking is > >> understandably difficult. The documentation team have really done a > great > >> job so far for software which has only just reached beta1, and I think > >> everyone realizes the documentation team is working hard at continually > >> improving it. > >> > >> As the documentation fills out, it will no doubt become more difficult > for > >> the documentation team to know where the weak points are and where the > >> community's pain points are. > >> > >> One easy suggestion might be to create a sticky thread on this forum > >> called "Documentation Suggestions", and simply put a message in the > "Book" > >> directing people to add a post to this thread whenever they come across > an > >> issue they feel should be documented and isn't, or where the > documentation > >> should be improved,or perhaps even is incorrect. > >> > >> It should be made clear that the documentation team is always free to > >> accept or ignore any or all of the community contributed suggestions, > but it > >> might be an easy way to get fairly practical feedback on where the major > >> pain points are, and thus where documention efforts might best be > further > >> focused. > > > > I think that putting it on the mailing-list is not the best solution as > it > > would be difficult to find the mails to check follow the needs. It would > be > > easier IMO to use the github issue tracker of the symfony-docs repository > > (not enabled currently but my suggestion is to enable it). > > > > -- > > Christophe | Stof > > > > -- > > 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 users" group. > > To post to this group, send email to symfony-users@googlegroups.com > > To unsubscribe from this group, send email to > > symfony-users+unsubscr...@googlegroups.com > > For more options, visit this group at > > http://groups.google.com/group/symfony-users?hl=en > > > > -- > 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 users" group. > To post to this group, send email to symfony-users@googlegroups.com > To unsubscribe from this group, send email to > symfony-users+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/symfony-users?hl=en > -- 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 users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
