Hi Sunny (and all), On Thu, Sep 22, 2011 at 8:42 PM, Saptarshi Purkayastha <[email protected]> wrote: > Documentation should be in its own project and not be a component of TRUNK. > So, a documentation sprint can live in its own project, with its > greenhoppers, issues etc.
I am going to respectfully disagree (in part). I believe that documentation about the core OpenMRS application should definitely be in TRUNK as a sub-component. As we make improvements to OpenMRS through our release process, part of that release should be to update the documentation for the application. Documentation about the project as a whole, on a larger scale, should of course not be in JIRA's TRUNK project. I have spoken in the past about the value of some kind of "community" project where we track community issues that are not technology-related, per se. This project could also track other community needs like research, outreach, partnerships, etc. One could also argue that they might belong as a component of ITSM. However given the unique nature of that project's on-call support notifications, privacy restrictions, etc., I tend to be inclined against that idea. Documentation about modules will of course be up to the various developers of those modules and may be on our modules wiki, or perhaps elsewhere at their discretion. Cheers, Michael _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
