On 5/18/07, ar1000@xxxxxxx <ar1000@xxxxxxx> wrote:
Communication Design encompasses tasks related to communication (visual) materials for Haiku. Website is for the website, and CD is for brochures, logos, letterhead, logos, badges, etc. For example, after the content for a quarterly report's data and body is compiled, a ticket would be created under CD to have it formatted and styled for the optimum presentation of data - both aesthetically and considering usability. For a widely known example, graphic design is a component of CD. This would let people in the community familiar with CD collaborate on relevant issues just as web or OS developers/ designers do.
I think there should be a good reason before one uses the ticket system. The ticket system is optimized for dev-related work, but it doesn't work very well for a long discussion with lots of comments from many participants and it makes discussions less visible since only those who watch a ticket will be notified of new comments. Are there so many tasks that you need such a ticket system? Will your tickets contain long descriptions or will they be simple one-liners like the admin tasks? In the latter case a simple wiki page with a TODO list (and links to further explanation/data where necessary) would be much more effective than having to create new tickets and using queries to find your tickets. It also only works well when just a few people should be involved with a certain task and others don't need to know about it (as is the case with the website, for example). Emails can be categorized, starred, etc. (more effective) and are able to reach more potential contributors. Another reason why I added a website category is to make it easier to find where to report a website bug (not everyone uses the website's contact form). I just want to make sure that a ticket system would actually make CD more effective. Bye, Waldemar Kornewald