Re: Just a tiny thing

> >I'd like to be involved with that as well; I'd love to help with PHP > >development but I don't have enough time to really be helpful (not to > >mention that I'm not exactly the world's largest fan of C). Whereas I do end > >up looking things up in the PHP manual and noticing problems or a regular > >basis. Maybe we could work with the doc team to give some people editorial > >access for comments? > > The developers have expressed doubts about giving out CVS accounts. I agree with them on this; handing them out left and right would make me a bit nervous, too. > I feel that for the annotations in the manual, editing the content by hand > and submitted modified documents to the manual editors should not be too > big of a hassle. > > Or alternately, let the doc team choose/elect/whatever someone as editor - > let the editor assemble, check and commit of the changes. > > Alternately, the annotation system could be modified, but this would take > some time. The annotations are stored a MySQL table. Perhaps the easiest approach might just be to add some sort of "editor reviewed" column to the database and creating a separate page that would display unreviewed notes so that a designated annotation editor (or group) could easily keep on top of new notes. > > I think a quick trip through the php-general archives > >and the FAQ/KB listings would turn up some knowledgeable candidates who > >could be trusted for this sort of thing. > > I would guess that making a letter that invites people to help out on this > project would be the best way to do this? What do you think about working with the doc team to establish either an editor or review group and then sending out a message encouraging people to submit dubious annotations for review? Kind of like what is currently being done with the bugs database where the QA team is helping filter out easy reports to save developer time.