Method for Updating Training Materials Under New Curriculum

[wonderchook]

Request for Comment: Method for Updating training materials under new Curriculum

Below are the steps that we are proposing for updating training materials under the new curriculum. The idea is there is a process from new feature being developed all the way through to being used in a training.

Steps:

1. Regular scheduled meeting between Developer/Trainers/AIFDR
2. Developer presents New Features to AIFDR/Training team in regular meeting - demo
3. Training team test New Feature and users docs
4. Training team provide feedback back to developer through inasafe issue
5. Repeat steps 1-3 until everyone is happy
6. Training team to document in inasafe-doc issue where the new feature will feature in the curriculum as well as page of training material and which milestone
7. Training team to develop training material in doc format
8. Native speaker of English to review training material (in terms of grammar/writing, not supposed to change the content) - Kate
9. AIFDR to review (Charlotte co-working with HOT) - content may change
10. HOT to review AIFDR comments - until everyone is happy
11. Transforming doc into rst (Emir, Wulan, Dewi)
12. Pushing rst into inasafe-doc github and let Linfiniti check the rst (in terms of technical, to make sure there is no problem)
13. Pushing the rst into Transifex (once it goes to Transifex, it should be no more change)
14. Training team to translate training material with Transifex
15. Test of training materials
16. Feedback to be addressed
17. Be committed to continuous improvements

[timlinux]

+1 All sounds good from our point of view!

On Tue, Mar 18, 2014 at 12:37 PM, Kate Chapman [email protected]:

Request for Comment: Method for Updating training materials under new
Curriculum

Below are the steps that we are proposing for updating training materials
under the new curriculum. The idea is there is a process from new feature
being developed all the way through to being used in a training.

Steps:

1. Regular scheduled meeting between Developer/Trainers/AIFDR
2. Developer presents New Features to AIFDR/Training team in regular
   meeting - demo
3. Training team test New Feature and users docs
4. Training team provide feedback back to developer through inasafe issue
5. Repeat steps 1-3 until everyone is happy
6. Training team to document in inasafe-doc issue where the new feature
   will feature in the curriculum as well as page of training material and
   which milestone
7. Training team to develop training material in doc format
8. Native speaker of English to review training material (in terms of
   grammar/writing, not supposed to change the content) - Kate
9. AIFDR to review (Charlotte co-working with HOT) - content may change
10. HOT to review AIFDR comments - until everyone is happy
11. Transforming doc into rst (Emir, Wulan, Dewi)
12. Pushing rst into inasafe-doc github and let Linfiniti check the rst
    (in terms of technical, to make sure there is no problem)
13. Pushing the rst into Transifex (once it goes to Transifex, it should
    be no more change)
14. Training team to translate training material with Transifex
15. Test of training materials
16. Feedback to be addressed
17. Be committed to continuous improvements

Reply to this email directly or view it on GitHubhttps://github.com//issues/166
.

Tim Sutton

Visit http://linfiniti.com to find out about:

• QGIS programming services
• GeoDjango web development
• QGIS Training

• FOSS Consulting Services
  Skype: timlinux Irc: timlinux on #qgis at freenode.net
  Tim is a member of the QGIS Project Steering Committee