On 12/11/2013 11:17 PM, Rajko wrote:
Again, what is wrong with a wiki? Pages can be even blocked, so only author can change them ... there can be even a template and fancy boxes for a state. And it is not that hard to get the text form to send it to ML. If it is used <pre> OSEP Text </pre> then even text format will be preserved with copy-paste to email.
wikis are only as good as the commitment to use them. I have seen them fail just as often as I have seen them work. They are a great tool for this job, if we groups and structure the information in a way that fits into the development process. A good example of one of the best Linux distro wikis is wiki.archlinux.org. (mediawiki) Of all the distros I've tried, their wiki is by far the best. For an example and ideas of how this could be implemented and benefit the factory effort, I encourage all to take a look. Between the package query (with full historic development changes for each package) to implementation and use informational pages for each, they have a slick way of capturing and managing critical development information. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org