<div dir="ltr"><div class="gmail_quote"><br><div dir="ltr">Anne, I have a couple of ideas for using this venue:<div><br></div><div>- Create a single onboarding document (I had to use three or four different sources to set myself up for bug fixing on a Mac, for example)</div>
<div>- Revise the contributor form so it captures more closely the audiences proposing bug fixes so we can get a better feel for their documentation needs</div><div>- Figure out how to archive the old documentation and remove it from the search and write steps for it</div>
<div>- Cement the content interlinking approach for contributors/bug troubleshooters and write steps of it</div><div>- Improve the content search by exploring indexing/tagging options and write the steps for it</div>
<div><br></div><div>This may sound like a totally personal request but it's just something that popped in my head upon the first read of the purpose statement. I may think of something else the more I ponder it.</div>
<div><br></div><div>Thanks! </div><div><br></div><div>Nermina</div></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">On Wed, Jul 24, 2013 at 7:06 PM, Anne Gentle <span dir="ltr"><<a href="mailto:annegentle@gmail.com" target="_blank">annegentle@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">This is a great opportunity to have five people get together on a focused effort. Let's talk about what an application for OpenStack might look like. <div>
<br></div><div>Anne<br><div><br><div class="gmail_quote">
---------- Forwarded message ----------<br>From: <b class="gmail_sendername">adam</b> <span dir="ltr"><<a href="mailto:adam@flossmanuals.net" target="_blank">adam@flossmanuals.net</a>></span><br>Date: Wed, Jul 24, 2013 at 5:37 PM<br>
Subject: [FM Discuss] GSoC Doc Camp 2013 CFP<br>To: <a href="mailto:discuss@lists.flossmanuals.net" target="_blank">discuss@lists.flossmanuals.net</a><br><br><br>Google Summer of Code Doc Camp - a partnership of GSoC, Aspiration and<br>
FLOSS Manuals<br>
<br>
This is a call for proposals for the 2013 GSoC Doc Camp. Individuals and<br>
projects are invited to submit proposals for the GSoC Doc Camp to be<br>
held at Google's Mountain View headquarters in California from October<br>
14 - October 18.<br>
<br>
What is it?<br>
<br>
The GSoC Doc Camp is a place for free software communities to meet, work<br>
on creating a book for their project, attract new people to their<br>
efforts, and share their documentation experiences. The camp aims to<br>
improve free documentation materials and skills in free software<br>
projects and individuals and help form the identity of the emergent free<br>
documentation sector.The Doc Camp will consist of 2 major components -<br>
an unconference and 2-4 short (3 day) Book Sprints to produce books for<br>
the selected projects.<br>
<br>
The unconference will explore topics proposed by the participants. Any<br>
topic on free documentation of free software can be proposed for<br>
discussion during the event.<br>
<br>
Each Book Sprint will bring together 4-5 individuals to produce a book<br>
on a specific free software project. All participants of the Doc Camp<br>
must attend a sprint. The books will be launched online in print and<br>
ebook formats on the final day of the event.<br>
<br>
Who should come?<br>
Individuals and free software projects can apply. All individuals will<br>
be required to work on one of the selected projects to assist their<br>
documentation efforts.<br>
<br>
How to I get involved?<br>
Individuals with a passion for free documentation about free software<br>
may apply to attend by filling out the application form [1] and<br>
submitting before August 7. Those wishing to attend do not need to be<br>
from a GSoC project. Accommodation and food will be covered by the GSoC<br>
Doc Camp. Partial or complete travel costs can also be applied for as<br>
part of the application process.<br>
<br>
Free software projects of any sort can also apply - they do not need to<br>
be GSoC 2013 projects although these may be given preference.<br>
<br>
Projects will be chosen from proposals submitted to the GSoC Doc Camp<br>
before August 7 through the application form [2]. Project applications<br>
can nominate up to 5 individuals to attend and participate in the<br>
proposed sprint. A Project proposal does not have to nominate<br>
individuals to participate - you can also use this as an opportunity to<br>
promote your project to Doc Camp participants and extend your<br>
documentation community. If the proposal is accepted the accommodation<br>
and food costs will be covered by the Doc Camp for any listed<br>
individuals and part or complete travel costs for each can be applied<br>
for (if applicable).<br>
<br>
The 2013 GSoC Doc Camp is co-organized by GSoC, Aspiration and FLOSS<br>
Manuals. Unconference facilitation conducted by Allen Gunn, and Book<br>
Sprint facilitated by Adam Hyde.<br>
<br>
<br>
APPLY HERE:<br>
<br>
<a href="https://docs.google.com/a/google.com/spreadsheet/viewform?formkey=dDl6QWlMbDFjcVF2Z1EyQ1d1b1NyN1E6MQ#gid=0" target="_blank">https://docs.google.com/a/google.com/spreadsheet/viewform?formkey=dDl6QWlMbDFjcVF2Z1EyQ1d1b1NyN1E6MQ#gid=0</a><br>
<br>
<br>
<br>
><br>
><br>
<br>
<br>
_______________________________________________<br>
Discuss mailing list<br>
<a href="mailto:Discuss@lists.flossmanuals.net" target="_blank">Discuss@lists.flossmanuals.net</a><br>
<a href="http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net" target="_blank">http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net</a><br>
</div><br></div></div></div>
<br></div></div>_______________________________________________<br>
Openstack-docs mailing list<br>
<a href="mailto:Openstack-docs@lists.openstack.org" target="_blank">Openstack-docs@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
<br></blockquote></div><br></div>
</div><br></div>