Hello all,

Some more thoughts on how it might be possible to improve documentation 
for extensions:

With a colleague of mine, I had the idea to build up a "basic review 
team". This team would review every new uploaded extension manually on:
* Weather it has a manual
* If the manual is useful
* If the source code is compliant with the T3 coding guidelines

Based on that review there could be a new flag in TER, something like 
"Approved by QA Team". This has nothing to do with the work of the 
security team, which is much harder.

Based on this approval, it would be easier to decide for users, which 
ext is worth considering. Additionally, there could be a second checkbox 
in the EM to only display results that are approved. So we would have 
three steps: "unreviewed/unapproved", "passed basic review" and "passed 
security review".

What do you think?

Regards,
Christopher.


-----Ursprüngliche Nachricht-----
Von: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] Im Auftrag von 
Dmitry Dulepov [typo3]
Gesendet: Dienstag, 11. März 2008 18:04
An: typo3-english@lists.netfielders.de
Betreff: Re: [TYPO3] Documentation nightmare

Hi!

virgil huston wrote:
 > At TCON07 I basically volunteered to be Doc Team lead and what has 
resulted
 > so far is some internal talking with mainly Daniel Brussler. I am 
thinking
 > that Daniel is the de facto Doc Team leader now and that is fine, he 
does a
 > very good job with the wiki. In any case, I plan on trying to get some
 > things going and I know Daniel will be supportive.

Excellent news! Feel free to contact me with questions about core if it 
is for documentation writing. I cannot promise same minute response but 
you will definitely get the answer withing a week (normally withing a 
day). I feel that doc team needs real support from the core people!

-- 
Dmitry Dulepov
TYPO3 core team
Web: http://typo3bloke.net/
Skype: callto:liels_bugs
"Nothing is impossible. There are only limits to our knowledge"
_______________________________________________
TYPO3-english mailing list
TYPO3-english@lists.netfielders.de
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-english
Hello all,

Some more thoughts on how it might be possible to improve documentation 
for extensions:

With a colleague of mine, I had the idea to build up a "basic review 
team". This team would review every new uploaded extension manually on:
* Weather it has a manual
* If the manual is useful
* If the source code is compliant with the T3 coding guidelines

Based on that review there could be a new flag in TER, something like 
"Approved by QA Team". This has nothing to do with the work of the 
security team, which is much harder.

Based on this approval, it would be easier to decide for users, which 
ext is worth considering. Additionally, there could be a second checkbox 
in the EM to only display results that are approved. So we would have 
three steps: "unreviewed/unapproved", "passed basic review" and "passed 
security review".

What do you think?

Regards,
Christopher.


-----Ursprüngliche Nachricht-----
Von: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] Im Auftrag von 
Dmitry Dulepov [typo3]
Gesendet: Dienstag, 11. März 2008 18:04
An: typo3-english@lists.netfielders.de
Betreff: Re: [TYPO3] Documentation nightmare

Hi!

virgil huston wrote:
 > At TCON07 I basically volunteered to be Doc Team lead and what has 
resulted
 > so far is some internal talking with mainly Daniel Brussler. I am 
thinking
 > that Daniel is the de facto Doc Team leader now and that is fine, he 
does a
 > very good job with the wiki. In any case, I plan on trying to get some
 > things going and I know Daniel will be supportive.

Excellent news! Feel free to contact me with questions about core if it 
is for documentation writing. I cannot promise same minute response but 
you will definitely get the answer withing a week (normally withing a 
day). I feel that doc team needs real support from the core people!

-- 
Dmitry Dulepov
TYPO3 core team
Web: http://typo3bloke.net/
Skype: callto:liels_bugs
"Nothing is impossible. There are only limits to our knowledge"
_______________________________________________
TYPO3-english mailing list
TYPO3-english@lists.netfielders.de
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-english

_______________________________________________
TYPO3-english mailing list
TYPO3-english@lists.netfielders.de
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-english

Reply via email to