[opensuse-wiki] Organizing Wiki
The http://en.opensuse.org/Tasks list is by now quite large . It is not always easy to find what to do and what is already done. Well defined tasks are important for success of any project. For each participant is easier to pick up some well defined job than to make guesswork from present offer what is the most important, how far article should be developed, what is the best way to structure article. This is specially true for projects in the initial phase like openSUSE wiki. It is time to reorganize Tasks page to list tasks by groups with additional information: * urgency * planned subtasks * proposed article structure * who is working on it * what is already done * ... Some smart template from our template specialists would make this easier, or maybe there is some other way like bugzilla for software, that has all this included, and tasks page should contain only link to this task tracking tool. ==Tasks== ===Wiki=== * structure chart and plans, * maintenance, * standards, * guides, * wish list, * plans, * ... ===Distribution documentation=== * Technical ** specifications, ** standards, ** manuals, ** ... * User ** HowTo, ** tips, ** FAQ, ** SDB, ** ... ===Illustrations=== * Artwork ** article illustrations, ** buttons, ** banners, ** window decoration ** ... ===Technical=== * Diagrams, * Flow charts, * Schematics, * ... ===Programming=== * ... Any ideas how to do this will help to do more with lesser work. -- Regards, Rajko. Visit http://en.opensuse.org/MiniSUSE --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-wiki-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki-help@opensuse.org
Rajko M wrote:
The http://en.opensuse.org/Tasks list is by now quite large . It is not always easy to find what to do and what is already done.
Well defined tasks are important for success of any project. For each participant is easier to pick up some well defined job than to make guesswork from present offer what is the most important, how far article should be developed, what is the best way to structure article. This is specially true for projects in the initial phase like openSUSE wiki.
It is time to reorganize Tasks page to list tasks by groups with additional information: * urgency * planned subtasks * proposed article structure * who is working on it * what is already done * ...
Some smart template from our template specialists would make this easier, or maybe there is some other way like bugzilla for software, that has all this included, and tasks page should contain only link to this task tracking tool.
==Tasks== ===Wiki=== * structure chart and plans, * maintenance, * standards, * guides, * wish list, * plans, * ...
===Distribution documentation=== * Technical ** specifications, ** standards, ** manuals, ** ...
* User ** HowTo, ** tips, ** FAQ, ** SDB, ** ...
===Illustrations=== * Artwork ** article illustrations, ** buttons, ** banners, ** window decoration ** ...
===Technical=== * Diagrams, * Flow charts, * Schematics, * ...
===Programming=== * ...
Any ideas how to do this will help to do more with lesser work.
No ideas? Well, back to old editing by hand and with hope that someone will pick up. -- Regards, Rajko. Visit http://en.opensuse.org/MiniSUSE --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-wiki-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki-help@opensuse.org
Rajko M a écrit :
No ideas?
I put this aside, waiting for the front page redesign acheivement (should be soon, I hope, now) jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-wiki-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki-help@opensuse.org
jdd wrote:
Rajko M a écrit :
No ideas?
I wrote this about tasks to initiate discussion, because I see more users coming in. They can be great reinforcement if they know what to do. The Tasks and Todo pages, are filled with complex tasks that must be crunched in smaller. Why? 1) No one can expect that every user act as project manager, and split tasks in one evening portions, easy to accomplish. 2) It will make possible that everyone can see what is done, and what not, to prevent duplicate efforts. Wiki doesn't seem right form to do it and, besides, there is so much software developed for such purpose. It would be like inventing hot water, to write template, that will help to follow task execution. Or, it is possible and appropriate, to use wiki for all, just I can't see how to do it without crowding wiki with work files, that will be not needed once task is accomplished.
I put this aside, waiting for the front page redesign achievement (should be soon, I hope, now) jdd
It is August, a holiday season. Not time for high speed anywhere :-) -- Regards, Rajko. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-wiki-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki-help@opensuse.org
Hello, Am Sonntag, 6. August 2006 14:26 schrieb Rajko M:
I wrote this about tasks to initiate discussion, because I see more users coming in. They can be great reinforcement if they know what to do. The Tasks and Todo pages, are filled with complex tasks that must be crunched in smaller.
Why? 1) No one can expect that every user act as project manager, and split tasks in one evening portions, easy to accomplish. 2) It will make possible that everyone can see what is done, and what not, to prevent duplicate efforts.
Correct.
Wiki doesn't seem right form to do it and, besides, there is so much software developed for such purpose. It would be like inventing hot water, to write template, that will help to follow task execution.
I still vote for using bugzilla and put the Tasks list in the "Action Items" component. We would need an "everybody@opensuse.org" dummy bugzilla account for this because items on the tasks page are defined as "not assigned to someone" and people (obviously) refuse to have something assigned to them in case it's not their job [1] ;-) BTW: The inclusion of Bugzilla RSS in the wiki (discussed some time ago) is already implemented in the "Bugs this week" section of http://developer.novell.com/wiki/index.php/Novell_Forge (<getrss> tag) - I guess this could be included in *.opensuse.org (more or less) easily. Regards, Christian Boltz [1] "not my job" as in http://tinyurl.com/qdmt3 ;-)) --
[HD mit badblocks] NACK, es kommt immer auf den Anwendungszweck an. Für ein Lern- / Experimentiersystem lohnt sich keine neue HD, solange es zu funktionieren scheint. Experimente auf welchem Sektor? Spanabhebende Storage-Lösungen? [> Al Bogner und Thomas Dreher in suse-linux]
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-wiki-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki-help@opensuse.org
Christian Boltz wrote:
Hello,
Am Sonntag, 6. August 2006 14:26 schrieb Rajko M:
I wrote this about tasks to initiate discussion, because I see more users coming in. They can be great reinforcement if they know what to do. The Tasks and Todo pages, are filled with complex tasks that must be crunched in smaller.
Why? 1) No one can expect that every user act as project manager, and split tasks in one evening portions, easy to accomplish. 2) It will make possible that everyone can see what is done, and what not, to prevent duplicate efforts.
Correct.
Wiki doesn't seem right form to do it and, besides, there is so much software developed for such purpose. It would be like inventing hot water, to write template, that will help to follow task execution.
I still vote for using bugzilla and put the Tasks list in the "Action Items" component.
We would need an "everybody@opensuse.org" dummy bugzilla account for this because items on the tasks page are defined as "not assigned to someone" and people (obviously) refuse to have something assigned to them in case it's not their job [1] ;-)
BTW: The inclusion of Bugzilla RSS in the wiki (discussed some time ago) is already implemented in the "Bugs this week" section of http://developer.novell.com/wiki/index.php/Novell_Forge (<getrss> tag) - I guess this could be included in *.opensuse.org (more or less) easily.
Regards,
Christian Boltz
[1] "not my job" as in http://tinyurl.com/qdmt3 ;-))
:-D I've seen one "not my job" on my street today and drove carefully around. The bugzilla is what came in my mind, but I used it only once, and now when you mentioned it, it looks viable to communicate achievements, problems, time shortage, needs, exchange files, etc, that comes up during the task execution. The other problem who is going to develop project, who is going to manage it, is still kind of secret. At the present time I don't see many (sufficient) people that can dedicate time for large projects, so we need project management that works fine with loose groups like the wiki editors. That looks like I have to reread some chapters in: Producing Open Source Software, by Karl Fogel http://producingoss.com/ to come up with some ideas. -- Regards, Rajko. Visit http://en.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-wiki-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki-help@opensuse.org
participants (3)
-
Christian Boltz -
jdd -
Rajko M