1. Project name : Abiword on OLPC<br>2. Existing website, if any :<br>3. One-line description : Abiword port to the OLPC computer.<br><br>4. Longer description : Continuing Erik Pukinskis' work on porting Abiword
<br> : to the Sugar interface and integrating it with the<br> : presence API framework.<br> :<br><br>5. URLs of similar projects :
<a href="http://snowedin.net/ideas/AbiWord+on+OLPC">http://snowedin.net/ideas/AbiWord+on+OLPC</a> (Erik's page, see above)<br><br>6. Committer list <br> Please list the maintainer (lead developer) as the first entry. Only list
<br> developers who need to be given accounts so that they can commit to your<br> project's code repository, or push their own. There is no need to list<br> non-committer developers.<br><br> Username Full name SSH2 key URL E-mail
<br> -------- --------- ------------ ------<br> #1 jirwin Justin Gallardo <a href="http://tinyurl.com/ydqg44">http://tinyurl.com/ydqg44</a> <a href="mailto:justin.gallardo@gmail.com">
justin.gallardo@gmail.com</a><br> #2 mburns Michael Burns <a href="http://tinyurl.com/ydj6dc">http://tinyurl.com/ydj6dc</a> <a href="mailto:maburns@gmail.com">maburns@gmail.com</a><br><br>7. Preferred development model
<br><br> [X] Central tree. Every developer can push his changes directly to the <br> project's git tree. This is the standard model that will be familiar to <br> CVS and Subversion users, and that tends to work well for most projects.
<br><br>8. Set up a project mailing list:<br><br> [X] No<br><br>9. Commit notifications<br><br> [X] No commit notifications, please<br><br>10. Vhost setup<br><br> [X] No, we don't have a project domain, or don't want to use one. We'll
<br> use the <a href="http://laptop.org">laptop.org</a> website address.<br><br>12. Notes/comments: Our initial version is already running and usable.