> However, what if the lead developers pause the code > development for a while and transfer the effort into making a more > complete manual? I believe this will only do good for the project and > the community.
Then many people will start complaining about the lack of progress of the code. There is just much work that needs to be done. If you start focusing on another aspect, something else will suffer. We need to figure out what is most important for the devs to do: a job that only they can do (code) or a job that they, or any volunteer can do (docs) ? > No one other than the developers themselves knows > exactly the ins and outs of the system. By documenting the whole system > deeply, you're actually reviewing the project There are several devs. i'm damned sure that some of them aren't really following what another is doing. not that that's a problem. Also, we have many users that like to spit through the cake code in their free time to learn about both the inner workings as of the api (how to work with it) of the framework, people like this can perfectly do docs. The best practice -imho- would be to let volunteers work on docs, but be guided by the devs, so that they can make some additions, fixes,.. where necessary without using too much time that could be used for the job that only they can do (development) And your logic is correct: people that want to do docs must learn the code.. a win-win indeed. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
