From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Erik K." To: documentation@lists.ipfire.org Subject: Re: IPFire Wiki Workflow Date: Sat, 27 Jul 2013 18:00:48 +0200 Message-ID: In-Reply-To: <1373640925.16036.16.camel@rice-oxley.tremer.info> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4792611553556773530==" List-Id: --===============4792611553556773530== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Michael, so for the first i think your workflow looks pretty good, but i have some pos= sible enhancements how to extend this workflow.=20 - The developers and their new developments should become also a part of Poin= t (A) i think. Stevee shows a good way how a short developer hand out could l= ooks like, take a look in here --> http://wiki.ipfire.org/en/configuration/ne= twork/dnsforward . So the coordinator needs to know about this changes too th= at he can define a priority in the topics. - In point (B) shouldn=C2=B4t 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 i= s not enough to understand what this software should do, the software needs t= o 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 develo= pment or addons where a GUI was also developed by the IPFire team.. --> Addons with foreign documentations can also become a short docu, but the= y 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 ? O= r 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 fo= und until now 2 different guidelines for the IPFire wiki.=20 - http://wiki.ipfire.org/nonpublic/en/guidelines - http://wiki.ipfire.org/en/edit So some questions to you all regarding to this theme:=20 - What kind of layout and content structure we should use ?=20 - 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 >=20 > Maybe we need to define some things more precisely, but I think this is > a point were we can start from. >=20 > Please post suggestions and critics. --===============4792611553556773530==--