What about some kind of mod up / down system to keep the comments clean(ish). Let the users do the moderation for you.
One of the main drawbacks of the current documentation is that although there's loads of it it's usually spread over various books / api docs / snippets / blog posts / etc with little in the way of glue to tie them all together - users could see just one part of it and assume that was all there was. On Jul 2, 1:21 am, Jonathan Wage <[email protected]> wrote: > As far as I know the php comment system is heavily moderated. They make sure > that comments aren't questions and each one is individually approved. > > - Jon > > > > > > On Thu, Jul 1, 2010 at 9:59 PM, AMailer <[email protected]> wrote: > > I second a comment system like php.net, it's a great source for usage > > examples like "you can also do this..." or use "this for this" > > scenarios. > > > I don't know weather it would be worth implementing it for the current > > release of Symfony2 but definitely once its in its beta/release > > stages. > > > On Jul 1, 8:51 am, Tom Boutell <[email protected]> wrote: > > > Comments have worked well for php.net over the years. There is always > > > more to be said. Showing newest comments first is a good quick and > > > dirty solution to the problem of things getting out of date. Of course > > > there must be moderation for flat out spam, requests for help rather > > > than information given, etc. > > > > On Wed, Jun 30, 2010 at 3:11 PM, Denis.Gorbachev > > > > <[email protected]> wrote: > > > > As of my experience, tickets get dumped. I agree with the proposal of > > > > forking the docs using git. > > > > > On Jun 30, 10:11 pm, Fabien Potencier <fabien.potenc...@symfony- > > > > project.com> wrote: > > > >> If there is a problem with the documentation, comments are not an > > > >> option. The documentation should be fixed instead. So, the best thing > > to > > > >> do is create a ticket. > > > > >> Fabien > > > > >> -- > > > >> Fabien Potencier > > > >> Sensio CEO - symfony lead developer > > > >> sensiolabs.com | symfony-project.org | fabien.potencier.org > > > >> Tél: +33 1 40 99 80 80 > > > > >> On 6/30/10 7:46 PM, Bernhard Schussek wrote: > > > > >> > So maybe the email address of the maintainer(s) in the docs pages is > > enough? > > > > >> > Bernhard > > > > > -- > > > > 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]<symfony-devs%2bunsubscr...@google > > > > groups.com> > > > > For more options, visit this group at > > > >http://groups.google.com/group/symfony-devs?hl=en > > > > -- > > > Tom Boutell > > > P'unk Avenue > > > 215 755 1330 > > > punkave.com > > > window.punkave.com > > > -- > > 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]<symfony-devs%2bunsubscr...@google > > groups.com> > > For more options, visit this group at > >http://groups.google.com/group/symfony-devs?hl=en > > -- > Jonathan H. Wagehttp://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
