@alefattorini, I can propose some things that I’ve picked from my work.
1 Have a dedicated page for how-to’s (wiki)
2 create categories of how-to’s (network, base, SMB, update etc)
3 Documents must have at least 3 attributes beside them as label (Dificulty level, Version of software to what it applies, and Date)
We also must create a How-to on how to create a how-to.
To explain the steps to take care when you create a guide.
Create a standard template for a document that will be used to format the how-to. This way we make sure that all the documents will be the same and will follow a certain pattern.
Include a header with required information (Version of the how-to / revision , author, date of publishing, to what versions of NS applies, difficulty Level and category).
I’ll try to compile a small guide (when I’ll have a bit of time) on what an author should look out for, when they decide to create a How-to.
We have an usage at contribs, HowTo are not signed, because someone after you can modify what you wrote…it is the rule of games with a wiki.
In fact I do love to make documentation, it is one way to retrieve informations several months after…I’m one of those who write the developer category.
Maybe and it is just an opinion, the wiki edit account should be subject to authorization…one good (bad) example is the french ubuntu wiki…it is a mess since everybody can write, specially those who are asking…can someone help me
@alefattorini : However I do feel flattered by the suggestion to join the howto/docs team, I don’t feel I am qualified to be part of that team (yet). My knowledge of NethServer is very limited (now that is an understatement). Maybe in time I can join, but for now I think it is much to premature to do that. I think it is a must to have at least some knowledge of the project to join something like a howto/docs team.
Talking about joining teams, I’d rather (again in time) get more involved with general community issues. Although I come from a tech background, my interests are much more with community management.
Especially community tasks should be done by those that have the support of the community. So (in time), IF the community agrees, I see a role there for me.
@robb I have as well only little knowledge of Netserver and that is the reason to work on the Wiki. I would like to contribute to that part of the documentation/Howto/Wiki that cover the basics in an easy way with the necessary background information. If you work a long time with server and networks you know all this staff but if you are a nuwbi you questions everything if it right, what does it mean, what I have to setup in this field, etc.
Frankly speaking I have trouble to setp a basic server with the existing documentation (network, firewall, email, UPS). In many parts are too little information and this I would like to change.
It’s right, people who have a little knowledge of NethServer are the best people for that job because they are more likely to write getting started tutorials, starting from the basics.
So, we have these NEW team now @Ctek@stephdl@WillZen@Jim@sitz right? Anyone else would like to jump in? @AbsyntH would you like to stick around?
Like in other teams we have to choose a coordinator, who?
and pick him late