From: "Erik K." <ummeegge@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: IPFire Wiki Workflow
Date: Sat, 27 Jul 2013 18:50:56 +0200 [thread overview]
Message-ID: <E2C1AEB0-6BD7-4BFC-A063-9491F5905C0E@ipfire.org> (raw)
In-Reply-To: <E6D9508B-AB99-48F0-86B1-538458BE985B@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 5038 bytes --]
Have found another possible wiki guideline list :-)
http://wiki.ipfire.org/en/wiki/syntax
Am 27.07.2013 um 18:00 schrieb Erik K.:
> 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
EDIT:
http://wiki.ipfire.org/en/wiki/syntax
>
> 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.
>
Am 27.07.2013 um 18:00 schrieb Erik K.:
> 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.
>
> _______________________________________________
> Documentation mailing list
> Documentation(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/documentation
next prev parent reply other threads:[~2013-07-27 16:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D8D682F2-7C9C-4962-AA0E-9AD00D3D5003@ipfire.org>
2013-07-12 14:55 ` Michael Tremer
2013-07-27 15:25 ` IPFire Wiki Workflow - list of why it can be interesting to be in a documentation group Erik K.
2013-07-27 16:00 ` IPFire Wiki Workflow Erik K.
2013-07-27 16:50 ` Erik K. [this message]
2013-07-28 16:27 ` Michael Tremer
2013-07-12 17:50 ` R. W. Rodolico
[not found] <CBA641A3-39FA-42D7-93D2-240B22AF1F79@ipfire.org>
2013-08-02 12:01 ` Michael Tremer
[not found] <ED6F7E1F-7128-485B-8365-98F6674459B4@ipfire.org>
2013-07-12 12:06 ` embp
2013-07-10 9:46 Michael Tremer
2013-07-11 7:28 ` R. W. Rodolico
2013-07-11 10:01 ` Michael Tremer
2013-07-11 16:18 ` R. W. Rodolico
2013-07-11 17:30 ` Erik K.
2013-07-11 17:54 ` Erik K.
2013-07-11 22:01 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E2C1AEB0-6BD7-4BFC-A063-9491F5905C0E@ipfire.org \
--to=ummeegge@ipfire.org \
--cc=documentation@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox