Jucato
Differences between revisions 1 and 2
|
⇤ ← Revision 1 as of 2006-09-08 12:53:28
Size: 4602
Comment:
|
Size: 723
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
| == Suggestions raised in the Kubuntu Meeting for KST == | == Suggestion for the first paragraph on the KST wiki == |
| Line 6: | Line 6: |
| === <nixternal> === *wiki and documentation should probably be seperated..as there are already 'main' teams that take care of that, however you are more then welcome to contribute to both *myself, jjesse, trappist, and robotgeek are the main contributors to Kubuntu docs right now, however we could always use more help...i doubt you can get Kubuntu related docs to split from the main project *wiki and documentation should probably be seperated..as there are already 'main' teams that take care of that, however you are more then welcome to contribute to both *but as it stands, i know help.ubuntu.com/community is trying to be fairly generic and DE dependent in the tutorials as well *you don't need to apply or be a member..all you have to do is submit patches to the mailing list *you have to watch out as well, as the whole "seperating" the DE stuff has been beatin' quite a bit as well... imbrandon will tell you how i was when i first came around, as well as Riddell...i was dude Kubuntu FTW, we don't need them ;) *https://help.ubuntu.com/community/WikiTeam <- this is the current Wiki info right there, that is an open team if you needed to join, but you can also add stuff to those pages as well concerning splitting up some of the docs or adding to them for Kubuntu specifics *we all know that w.u.c is argh! and we can use a lot of help to make it better...that is why there was a split to pull main documentation from the wiki and add it to h.u.c/community *but i agree with you, the "favorite text editor" is annoying because someone might not know about kate or kwrite, let alone nano, vi, vim and so forth *Hawkwind, Jucato, and abattoir, i would also recommend you talk to Burgwork / Burgundavia, or mdke when you get a chance as well concerning the wiki and documentation... #ubuntu-doc is their hangout *believe me when i say, you open up the can or worms on the wiki though in the channel, prepare to work for 11 days straight ;) *nixternal notes that i have been there done that, and stepped on some toes...just trying to make sure others don't step on them sore toes i already did ;) === <imbrandon> === *Hawkwind, yea but that can be done as part of the doc team if you become a member, i think the "zero point of entry" though needs to be worked on *So then I guess the 3 of us would need to apply for the doc team or whatever we need to do to become a member of that: Hawkwind, i would say so *i 100% agree BUT that can be done as part of the existing teams if people know where to look, that in lies the problem *ok i still dont see this as a problem as you come accross them fixem ? *sure and i said i 100% agree, go for it, i just urged you do it within the teams already established === <Hobbsee> === *hopefully not to split. i keep discouraging them from doing that :P === <Burgwork> === *the doc team has been every dormant this release. We would love to have more people help us === <Tonio_> === *I would suggest everyone that reads a bit of french to have a look at docs.ubuntu-fr.org since their base is to me the most well organised concerning ubuntu, the problem is nobody took in charge of merging it with global ubuntu docs *that requires defining the bases of a support branch in the wiki, since it went to all directions till now === <gnomefreak> === *make a list of some wikis you see that need it and feel free to email me the list 10 at a time or whatever adn ill fix them === <Riddell> === *make sure you work with or within the existing teams and everyone will be happy == My Own Notes & Suggestions: == *emphasize on our goal to coordinate contents and people rather than being a completely new and independent team that does documentation. *work within the structure: work with/within people and teams already established, use the processes already available. Again, on our goal as coordinators/co-workers rather than an independent team. Be careful not to step on toes. *be careful of "separating" stuff. We do not need to separate stuff. We just need to add in more Kubuntu-related stuff, and make sure that ubotu properly points to them. *distinguish wiki from official docs (h.u.c.) |
== Suggestions (based on the Kubuntu Meeting): == *emphasize on our goal to coordinate contents and people *work within the structure, work with existing groups/people *be careful of "separating" stuff. We do not need to separate stuff. We just need to add in more Kubuntu-related stuff *distinguish wiki from official docs |
Jucato's Temporary Notepad
(or at least until I get something to write)
Suggestion for the first paragraph on the KST wiki
Suggestions (based on the Kubuntu Meeting):
- emphasize on our goal to coordinate contents and people
- work within the structure, work with existing groups/people
- be careful of "separating" stuff. We do not need to separate stuff. We just need to add in more Kubuntu-related stuff
- distinguish wiki from official docs
- Main Kubuntu docs contributors: jjesse, nixternal, robotgeek, trappist
Wiki Team: https://help.ubuntu.com/community/WikiTeam
- talk to Burgwork/Burgundavia or mdke of #ubuntu-doc about the wiki and documentation
- join the documentation team
Jucato (last edited 2008-08-06 17:00:49 by localhost)