Re: IPFire Wiki Workflow

["Erik K." <ummeegge@ipfire.org>]

[-- Attachment #1: Type: text/plain, Size: 2253 bytes --]

Hi Michael,
so for the first i think your workflow looks pretty good, but i have some possible enhancements how to extend this workflow. 
- The developers and their new developments should become also a part of Point (A) i think. Stevee shows a good way how a short developer hand out could looks like, take a look in here --> http://wiki.ipfire.org/en/configuration/network/dnsforward . So the coordinator needs to know about this changes too that he can define a priority in the topics.
- In point (B) shouldn´t be not also the german translations in there as a point (2) ?
- The testing of the written articles should be mentioned i think, cause it is not enough to understand what this software should do, the software needs to be tested in every single function so a quality management will be done too.
	--> I think a new guideline for new and old wikis should be to explain every function which can be seen on the WUI, this means especially the core development or addons where a GUI was also developed by the IPFire team..
	--> Addons with foreign documentations can also become a short docu, but they should be linked to the external wiki/docu. This should also be a part of a guideline too.

A question: Should i start as a coordinator to list some important topics ? Or do we need a little longer ?

------------------------

A guideline of how to structure the content and the layout of the wiki might be important for the workflow i think. This should prevent that people doing very different stuff if they work together in the same sections. So i have found until now 2 different guidelines for the IPFire wiki. 

- http://wiki.ipfire.org/nonpublic/en/guidelines
- http://wiki.ipfire.org/en/edit

So some questions to you all regarding to this theme: 
- What kind of layout and content structure we should use ? 
- What things are missing in those guidelines ?
- To make one good guideline please give some suggestions to them.

Greetings

Erik


> I drew a little image on how I image the workflow:
>  http://wiki.ipfire.org/projects/docs/workflow
> 
> Maybe we need to define some things more precisely, but I think this is
> a point were we can start from.
> 
> Please post suggestions and critics.