TrustedUser
2,147
edits
Difference between revisions of "Doc Sprint/Application/2013"
Jump to navigation
Jump to search
m
Doc Sprint/Application/2013 (view source)
Revision as of 09:40, 9 September 2013
, 09:40, 9 September 2013→Doc Sprint Summit v3.0 Application: add feeback from Google
(/* Projects only: List up to 5 individuals that you would like to attend. Please provide the country (and state if applicable) they would travel from, and one or two lines about why each person is a good candidate. Indicate those who would require fu) |
m (→Doc Sprint Summit v3.0 Application: add feeback from Google) |
||
| (5 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
=Doc Sprint Summit v3.0 Application= | =Doc Sprint Summit v3.0 Application= | ||
'''Update:''' Google sent the result on August 15 and unfortunately we were not selected :( | |||
Let's try again next year. The feedback from Google was that the application was excellent but there were just too many applications. | |||
==Introduction== | ==Introduction== | ||
For the 3rd time, Google is organizing a Doc Camp at Mountain View, the week before the mentor summit. It consists of an unconference and 2-5 Book Sprints to produce books on free software - facilitated by Adam Hyde of FLOSS Manuals. | For the 3rd time, Google is organizing a Doc Camp at Mountain View, the week before the mentor summit. It consists of an unconference and 2-5 Book Sprints to produce books on free software - facilitated by Adam Hyde of FLOSS Manuals. | ||
| Line 21: | Line 25: | ||
==Projects only: Please outline in brief detail how the nominated project would benefit from attending the 2013 GSoC Doc Camp.== | ==Projects only: Please outline in brief detail how the nominated project would benefit from attending the 2013 GSoC Doc Camp.== | ||
Currently the project is badly lacking professional end-user documentation. We have several wiki pages, more or less updated, and we link the users to those based on their questions. But regularly, people are asking for something more formal | Currently the project is badly lacking professional and maintainable end-user documentation. We have several wiki pages, more or less updated, and we link the users to those based on their questions. But regularly, people are asking for something more formal and structured and we are pretty sure some people will have given up using our product because they don't find the required information easily enough. | ||
We already have more than 8.5 million direct downloads of our product and it is easy to see that the benefits of the organization would be great. Allowing us to keep more new users on one hand, and decrease the flow of trivial questions on the other (thus reducing time spent on support)! | |||
We also have some less common documentation problems to overcome such as having issues with aligning good formal documentation to a project that supports such a wide variety of platforms with wildly different characteristics. | |||
==Projects only: List up to 5 individuals that you would like to attend. Please provide the country (and state if applicable) they would travel from, and one or two lines about why each person is a good candidate. Indicate those who would require full or partial travel assistance.== | ==Projects only: List up to 5 individuals that you would like to attend. Please provide the country (and state if applicable) they would travel from, and one or two lines about why each person is a good candidate. Indicate those who would require full or partial travel assistance.== | ||
| Line 32: | Line 38: | ||
[[Arnaud Boutonné, from Belgium]] | [[Arnaud Boutonné, from Belgium]] | ||
Arnaud is an engine developer for 4 years and was promoted co-project admin for the project 2 years ago. He's got a good insight of the project. He also has some experience about writing user guides and documentation, as he wrote some for European Commission (DG Agri, DI, DG Taxud, DG Research) in the '00s. | Arnaud is an engine developer for 4 years and was promoted co-project admin for the project 2 years ago. He's got a good insight of the project. He also has some experience about writing user guides and documentation, as he wrote some for European Commission (DG Agri, DI, DG Taxud, DG Research) in the '00s. GSoC Mentor and Admin for several years. | ||
[[Péter Bozsó, from Hungary]] | [[Péter Bozsó, from Hungary]] | ||
| Line 41: | Line 47: | ||
[[User:DJWillis|John Willis, from United Kingdom]] | [[User:DJWillis|John Willis, from United Kingdom]] | ||
John has been a member of the ScummVM team for 7 years and looks after several ports of the platform. He has helped with documentation and project communication in the past. He is a firm believer in the need for good quality 'living' documentation to support a project (It is a critical requirement for the day job of being an Enterprise Architect). | John has been a member of the ScummVM team for 7 years and looks after several ports of the platform. He has helped with documentation and project communication in the past. He is a firm believer in the need for good quality 'living' documentation to support a project (It is a critical requirement for the day job of being an Enterprise Architect). GSoC Mentor and Admin for several years. | ||
All 5 would need travel assistance. | All 5 would need travel assistance. | ||
==Projects only: Propose a topic of the Book Sprint and outline in a few sentences what you would like to cover.== | ==Projects only: Propose a topic of the Book Sprint and outline in a few sentences what you would like to cover.== | ||
- [[how to write | - [[how to write documentation for a massively cross-platform product]] | ||
Our product runs on more than 30 platforms. What are the best practices and obvious | Our product runs on more than 30 platforms and even more disparate form factors. What are the best practices and obvious pitfalls when you write documentation for massively cross-platform products? | ||
- [[how to write documentation for reimplementations/emulators/etc]] | - [[how to write documentation for reimplementations/emulators/etc]] | ||
| Line 56: | Line 62: | ||
- [[how to keep documentation up to date for a constantly evolving open source project]] | - [[how to keep documentation up to date for a constantly evolving open source project]] | ||
One of the issue we encountered with our previous effort to write a user manual was to keep it updated when releasing a new version of the software with changes in the GUI, new options, support for new games... What are the best practices to ease that effort? | One of the issue we encountered with our previous effort to write a user manual was to keep it updated when releasing a new version of the software with changes in the GUI, new options, support for new games... What are the best practices to ease that effort? How do people overcome the needs for formal documentation against the needs for living documentation. How can the team structure and expectations help with these issues? | ||
==Will you (or anyone you listed before) be attending the 2013 GSoC mentor summit? (Yes/No/Not Sure)== | ==Will you (or anyone you listed before) be attending the 2013 GSoC mentor summit? (Yes/No/Not Sure)== | ||
Not Sure | Not Sure | ||