Project Hosting Application: Simple Digital Library Index
1. Project name :Simple Digital Library Index
2. Existing website, if any :none
3. One-line description :Makes it simple and easy to generate a
library index of resources stored on a school server for example.
4. Longer description :Simple Digital Library Index (SDLI) is
designed to make it quick and easy to assemble digital libraries for
schools in a format that is accessible, fast and easy to add content
in bulk, and can be easily replicated to make it accessible in
multiple locations even if there are asynchronous or very slow
connections.
The system is programmed using Java and XSL - just assemble a folder
with the contents however one wishes to organize them and the meta
data will be extracted from the files according to the format type
(e.g. using meta tags in HTML files, tags from audio files, document
properties info from word documents, etc).
The appearance and interface can be very simply customized by editing
the HTML in XSL sheets.
5. URLs of similar projects : http://www.greenstone.org/
6. Committer list
Please list the maintainer (lead developer) as the first entry. Only list
developers who need to be given accounts so that they can commit to your
project's code repository, or push their own. There is no need to list
non-committer developers.
Username Full name SSH2 key URLE-mail
- --
#1 mikedawson Mike Dawson attached
m...@paiwastoon.com.af
If any developers don't have their SSH2 keys on the web, please attach them
to the application e-mail.
7. Preferred development model
[] Central tree. Every developer can push his changes directly to the
project's git tree. This is the standard model that will be familiar to
CVS and Subversion users, and that tends to work well for most projects.
[X] Maintainer-owned tree. Every developer creates his own git tree, or
multiple git trees. He periodically asks the maintainer to look at one
or more of these trees, and merge changes into the maintainer-owned,
main tree. This is the model used by the Linux kernel, and is
well-suited to projects wishing to maintain a tighter control on code
entering the main tree.
If you choose the maintainer-owned tree model, but wish to set up some
shared trees where all of your project's committers can commit directly,
as might be the case with a discussion tree, or a tree for an individual
feature, you may send us such a request by e-mail, and we will set up the
tree for you.
8. Set up a project mailing list:
[ ] Yes, named after our project name
[ ] Yes, named __
[X] No
When your project is just getting off the ground, we suggest you eschew
a separate mailing list and instead keep discussion about your project
on the main OLPC development list. This will give you more input and
potentially attract more developers to your project; when the volume of
messages related to your project reaches some critical mass, we can
trivially create a separate mailing list for you.
If you need multiple lists, let us know. We discourage having many
mailing lists for smaller projects, as this tends to
stunt the growth of your project community. You can always add more lists
later.
9. Commit notifications
[ ] Notification of commits to the main tree should be e-mailed to the list
we chose to create above
[ ] A separate mailing list, projectname-git, should be created for commit
notifications
[X] No commit notifications, please
10. Shell accounts
As a general rule, we don't provide shell accounts to developers unless
there's a demonstrated need. If you have one, please explain here, and
list the usernames of the committers above needing shell access.
11. Translation
[X] Set up the laptop.org Pootle server to allow translation
commits to be made
[ ] Translation arrangements have already been made at ___
12. Notes/comments:
identity.pub
Description: Binary data
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: Project Hosting Application: Simple Digital Library Index
Hi Mike, Thanks, you should be able to push here now: git+ssh://mdaw...@dev.laptop.org/git/projects/sdli http://wiki.laptop.org/go/Importing_your_project - Chris. -- Chris Ball c...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
project hosting application: Larry
1. Project name :Language Learning with Larry
2. Existing website, if any :http://wiki.laptop.org/go/Larry
3. One-line description :RPG that teaches foreign language vocabulary.
4. Longer description :RPG that teaches foreign language vocabulary.
:
:
:
5. URLs of similar projects :
6. Committer list
Please list the maintainer (lead developer) as the first entry. Only list
developers who need to be given accounts so that they can commit to your
project's code repository, or push their own. There is no need to list
non-committer developers.
Username Full name SSH2 key URL
E-mail
-
--
#1 My21heartsMelanie Kim[EMAIL PROTECTED](attached)
#2 MchuaMel Chua[EMAIL PROTECTED](you should already have my
ssh2 key)
#3
...
If any developers don't have their SSH2 keys on the web, please attach
them
to the application e-mail.
7. Preferred development model
[X] Central tree. Every developer can push his changes directly to the
project's git tree. This is the standard model that will be familiar
to
CVS and Subversion users, and that tends to work well for most
projects.
[ ] Maintainer-owned tree. Every developer creates his own git tree, or
multiple git trees. He periodically asks the maintainer to look at
one
or more of these trees, and merge changes into the maintainer-owned,
main tree. This is the model used by the Linux kernel, and is
well-suited to projects wishing to maintain a tighter control on code
entering the main tree.
If you choose the maintainer-owned tree model, but wish to set up some
shared trees where all of your project's committers can commit directly,
as might be the case with a discussion tree, or a tree for an
individual
feature, you may send us such a request by e-mail, and we will set up the
tree for you.
8. Set up a project mailing list:
[ ] Yes, named after our project name
[ ] Yes, named __
[X] No
When your project is just getting off the ground, we suggest you eschew
a separate mailing list and instead keep discussion about your project
on the main OLPC development list. This will give you more input and
potentially attract more developers to your project; when the volume of
messages related to your project reaches some critical mass, we can
trivially create a separate mailing list for you.
If you need multiple lists, let us know. We discourage having many
mailing lists for smaller projects, as this tends to
stunt the growth of your project community. You can always add more lists
later.
9. Commit notifications
[ ] Notification of commits to the main tree should be e-mailed to the
list
we chose to create above
[ ] A separate mailing list, projectname-git, should be created for
commit
notifications
[X] No commit notifications, please
10. Shell accounts
As a general rule, we don't provide shell accounts to developers unless
there's a demonstrated need. If you have one, please explain here, and
list the usernames of the committers above needing shell access.
11. Translation
[X] Set up the laptop.org Pootle server to allow translation commits to
be made
[ ] Translation arrangements have already been made at ___
12. Notes/comments:
I'm a newbie at coding. I started early this July as a project for ILXO. If
you're familiar to their blog (http://ilxo.org/blog/?p=34), I did post some
information about what Larry currently does. The paragraph I wrote is the
second giant paragrapgh on the post.
Current code is at http://svn.melchua.com/larry
id_rsa.pub
Description: Binary data
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Project hosting application: xomail
1. Project name : xomail
2. Existing website, if any : http://wiki.laptop.org/go/Projects/xomail
3. One-line description : Email activity
4. Longer description : An email activity that provides a usable
interface for sending and receiving email, tags for organizing email,
easy configuration
5. URLs of similar projects : none that I know of (for the XO)
6. Committer list
Please list the maintainer (lead developer) as the first entry. Only
list
developers who need to be given accounts so that they can commit to your
project's code repository, or push their own. There is no need to list
non-committer developers.
Username Full name SSH2 key URL
E-mail
-
--
#1 shikharShikhar Bhushan http://www.schmizz.net/id_rsa.pub
[EMAIL PROTECTED]
If any developers don't have their SSH2 keys on the web, please
attach them
to the application e-mail.
7. Preferred development model
[X] Central tree. Every developer can push his changes directly to the
project's git tree. This is the standard model that will be
familiar to
CVS and Subversion users, and that tends to work well for most
projects.
[ ] Maintainer-owned tree. Every developer creates his own git tree, or
multiple git trees. He periodically asks the maintainer to look
at one
or more of these trees, and merge changes into the maintainer-owned,
main tree. This is the model used by the Linux kernel, and is
well-suited to projects wishing to maintain a tighter control on
code
entering the main tree.
If you choose the maintainer-owned tree model, but wish to set up some
shared trees where all of your project's committers can commit directly,
as might be the case with a discussion tree, or a tree for an
individual
feature, you may send us such a request by e-mail, and we will set up
the
tree for you.
8. Set up a project mailing list:
[ ] Yes, named after our project name
[ ] Yes, named __
[X] No
When your project is just getting off the ground, we suggest you eschew
a separate mailing list and instead keep discussion about your project
on the main OLPC development list. This will give you more input and
potentially attract more developers to your project; when the volume of
messages related to your project reaches some critical mass, we can
trivially create a separate mailing list for you.
If you need multiple lists, let us know. We discourage having many
mailing lists for smaller projects, as this tends to
stunt the growth of your project community. You can always add more
lists
later.
9. Commit notifications
[ ] Notification of commits to the main tree should be e-mailed to
the list
we chose to create above
[ ] A separate mailing list, projectname-git, should be created for
commit
notifications
[X] No commit notifications, please
10. Shell accounts
As a general rule, we don't provide shell accounts to developers unless
there's a demonstrated need. If you have one, please explain here, and
list the usernames of the committers above needing shell access.
11. Translation
[X] Set up the laptop.org Pootle server to allow translation commits
to be made
[ ] Translation arrangements have already been made at ___
12. Notes/comments:
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Project Hosting Application: SocialCalc
1. Project name : SocialCalc
2. Existing website, if any : http://wiki.laptop.org/go/SocialCalc and
http://www.socialtext.net/socialcalcxo/index.cgi?sweet_socialcalc
3. One-line description : The spreadsheet activity.
4. Longer description : SocialCalc is a JavaScript-based spreadsheet
being developed as a sugar activity using XOCom, a
package build for JS-Python
communication. :
:
:
5. URLs of similar projects :
6. Committer list
Username Full name SSH2 key URL
E-mail
- --
#1 manusheel Manusheel Guptamanu.pub
(attached)manuatlaptopdotorg
#2 Dan Bricklindan.pub
(attached) danbatbricklindotcom
#3 Luke Closs luke.pub (attached)
lukedotclossatsocialtextdotcom
#4 K.S. Preeti preeti.pub
(attached)kspreetidot13atgmaildotcom
...
If any developers don't have their SSH2 keys on the web, please attach
them
to the application e-mail.
7. Preferred development model
[X] Central tree. Every developer can push his changes directly to the
project's git tree. This is the standard model that will be familiar
to
CVS and Subversion users, and that tends to work well for most
projects.
[ ] Maintainer-owned tree. Every developer creates his own git tree, or
multiple git trees. He periodically asks the maintainer to look at one
or more of these trees, and merge changes into the maintainer-owned,
main tree. This is the model used by the Linux kernel, and is
well-suited to projects wishing to maintain a tighter control on code
entering the main tree.
If you choose the maintainer-owned tree model, but wish to set up some
shared trees where all of your project's committers can commit directly,
as might be the case with a discussion tree, or a tree for an individual
feature, you may send us such a request by e-mail, and we will set up the
tree for you.
8. Set up a project mailing list:
[ X] Yes, named after our project name
[ ] Yes, named __
[] No
When your project is just getting off the ground, we suggest you eschew
a separate mailing list and instead keep discussion about your project
on the main OLPC development list. This will give you more input and
potentially attract more developers to your project; when the volume of
messages related to your project reaches some critical mass, we can
trivially create a separate mailing list for you.
If you need multiple lists, let us know. We discourage having many
mailing lists for smaller projects, as this tends to
stunt the growth of your project community. You can always add more lists
later.
9. Commit notifications
[X ] Notification of commits to the main tree should be e-mailed to the
list
we chose to create above
[ ] A separate mailing list, projectname-git, should be created for
commit
notifications
[] No commit notifications, please
10. Shell accounts
As a general rule, we don't provide shell accounts to developers unless
there's a demonstrated need. If you have one, please explain here, and
list the usernames of the committers above needing shell access.
11. Translation
[X] Set up the laptop.org Pootle server to allow translation commits to be
made
[ ] Translation arrangements have already been made at ___
12. Notes/Comments
The first version of the activity is available to download from
http://www.socialtext.net/socialcalcxo/index.cgi?sweet_socialcalc .
XOCom will help us in our efforts to motivate the JS developers'
community to develop activities for the XO.
Regards,
Manu
manu.pub
Description: application/vnd.ms-publisher
dan.pub
Description: application/vnd.ms-publisher
luke.pub
Description: application/vnd.ms-publisher
preeti.pub
Description: application/vnd.ms-publisher
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: EduBlog Project hosting application
Any updates on this please ? We are already started on the project and would like to use the git. Marcel On Mon, May 26, 2008 at 11:23 PM, marcel r [EMAIL PROTECTED] wrote: I attached the hosting application and 2 public key files. I read the discussion on rsa vs dsa, but are both methods supported ? If not I will attach de correct key. Thanks in advance! Marcel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Project Hosting Application: olpc-netscripts
2008/6/4 Ixo X oxI [EMAIL PROTECTED]: Great idea! I have some scripts, thoughts, and code I might be interested with contributing myself. Is there a start to a list of tools, what they do, and maybe even a 'request/want' list ? AFAIK this is the wiki page: http://wiki.laptop.org/go/Network_Resources ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Project hosting application: Bundlemaker
1. Project name : Bundlemaker
2. Existing website, if any : http://wiki.laptop.org/go/Bundlemaker
3. One-line description : A shell script that takes an index page on
the web and pulls it, and all the pages it references, into a .xol
library bundle.
4. Longer description :Bundlemaker is a script that takes an index
page on the web and pulls it, and all the pages it references, into a
library bundle. It is useful for things like Wikislices. At the end of
running the script (it is quiet and may take several minutes as it
downloads files) you should have a bundlename.xol file in the directory
you ran the script on, ready to go on the XO.
5. URLs of similar projects :
http://wiki.laptop.org/go/Creating_a_content_bundle (but it's not a script)
6. Committer list
Username Full name SSH2 key URL
E-mail
-
--
#1 mchua Mel Chuahttp://melchua.com/tmp/id_dsa.pub
7. Preferred development model
[X] Central tree.
8. Set up a project mailing list:
[X] No
9. Commit notifications
[X] No commit notifications, please
10. Shell accounts
already have one - mchua
11. Translation
[X] Set up the laptop.org Pootle server to allow translation commits
to be made (once the script matures somewhat, the instructions to use
the script should definitely be localized.)
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: Project hosting application: Bundlemaker
Cool! I would call this bookbinder if it were an activity. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Project Hosting Application: olpc-netscripts
1. Project name : olpc-netutils 2. Existing website, if any : None 3. One-line description : OLPC-specific user-land network software. 4. Longer description : Yani's collection of network status displays. 5. URLs of similar projects : Unknown. 6. Committer list Please let anyone with a dev account commit. Yani and I will be the contact people. 7. Preferred development model Please set up projects/olpc-netutils 8. Set up a project mailing list: [X] No 9. Commit notifications [EMAIL PROTECTED] 11. Translation [X] Set up the laptop.org Pootle server to allow translation commits to be made ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Project Hosting Application: olpc-netscripts
Great idea! I have some scripts, thoughts, and code I might be interested with contributing myself. Is there a start to a list of tools, what they do, and maybe even a 'request/want' list ? :) -iXo On Tue, Jun 3, 2008 at 3:01 PM, Michael Stone [EMAIL PROTECTED] wrote: 1. Project name : olpc-netutils 2. Existing website, if any : None 3. One-line description : OLPC-specific user-land network software. 4. Longer description : Yani's collection of network status displays. 5. URLs of similar projects : Unknown. 6. Committer list Please let anyone with a dev account commit. Yani and I will be the contact people. 7. Preferred development model Please set up projects/olpc-netutils 8. Set up a project mailing list: [X] No 9. Commit notifications [EMAIL PROTECTED] 11. Translation [X] Set up the laptop.org Pootle server to allow translation commits to be made ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Project Hosting Application: olpc-netscripts
On Tue, Jun 03, 2008 at 07:54:13PM -0700, Ixo X oxI wrote: Great idea! I have some scripts, thoughts, and code I might be interested with contributing myself. Then please show off your patches! Is there a start to a list of tools, what they do, and maybe even a 'request/want' list ? Nope. Feel free to write one! Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Project hosting application: SimpleRPG
1. Project name : SimpleRPG 2. Existing website, if any : http://wiki.laptop.org/go/SimpleRPG 3. One-line description : a simple 2D game with overly-commented code intended to be used as a tutorial/base for building a client-server RPG-style game with Pygame for the XO. 4. Longer description : This is a very simple 2D game intended to be used as a tutorial on building a client-server RPG-style game with Pygame, and will be more generally usable as a programming, game development, and Activity development tutorial as development progresses. The target audience is new developers 12 and up. 5. URLs of similar projects : http://hamsterrepublic.com/ohrrpgce/index.php/Main_Page.html http://aegisknight.org/sphere http://sourceforge.net/projects/fife/ 6. Committer list Please list the maintainer (lead developer) as the first entry. Only list developers who need to be given accounts so that they can commit to your project's code repository, or push their own. There is no need to list non-committer developers. Username Full name SSH2 key URL E-mail - -- robertofaga Roberto Faga (attached) [EMAIL PROTECTED] mchuaMel Chua http://melchua.com/tmp/id_dsa.pub [EMAIL PROTECTED] 7. Preferred development model X] Central tree. Every developer can push his changes directly to the project's git tree. This is the standard model that will be familiar to CVS and Subversion users, and that tends to work well for most projects. 8. Set up a project mailing list: [X] No 9. Commit notifications [X] No commit notifications, please 10. Shell accounts None required. 11. Translation [X] Set up the laptop.org Pootle server to allow translation commits to be made 12. Notes/comments: Both Roberto and Mel may already have accounts on the devel machine with those ssh2 keys. Note that we already have two language versions of the codebase - Portuguese and English. (They're not *quite* identical yet; getting there.) Existing code (written by Roberto and licensed under the LGPL) is on the wiki page, linked above. It's playable right now, if by playable you mean 'the program rums as per the instructions provided, and you can see your character walk around the world. ssh_host_rsa_key.pub Description: Binary data ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Project hosting application for Funny Talk
1. Project name : Funny Talk 2. Existing website, if any : http://www.thumbuki.com/xo/funnytalk.activity.zip 3. One-line description : Record your voice with the built-in microphone, and alter the sound using effects such as chorus, reverb, echo, etc. 4. Longer description : A Csound-based activity that children can use to record their voices with the built-in microphone, and process them with effects such as reverb, echo, chorus, etc. Funny Talk allows users to save their manipulated voices as soundfiles so that they can be used in other musical activities. This activity uses the csndsugui toolkit. 5. URLs of similar projects : http://wiki.laptop.org/go/Csound#Activities 6. Committer list UsernameFull name SSH2 key URL E-mail - -- #1 Jacob Joaquin Jacob Joaquin Attached as file [EMAIL PROTECTED] 7. Preferred development model [X] Central tree. Every developer can push his changes directly to the project's git tree. This is the standard model that will be familiar to CVS and Subversion users, and that tends to work well for most projects. [ ] Maintainer-owned tree. Every developer creates his own git tree, or multiple git trees. He periodically asks the maintainer to look at one or more of these trees, and merge changes into the maintainer-owned, main tree. This is the model used by the Linux kernel, and is well-suited to projects wishing to maintain a tighter control on code entering the main tree. If you choose the maintainer-owned tree model, but wish to set up some shared trees where all of your project's committers can commit directly, as might be the case with a discussion tree, or a tree for an individual feature, you may send us such a request by e-mail, and we will set up the tree for you. 8. Set up a project mailing list: [ ] Yes, named after our project name [ ] Yes, named __ [X] No When your project is just getting off the ground, we suggest you eschew a separate mailing list and instead keep discussion about your project on the main OLPC development list. This will give you more input and potentially attract more developers to your project; when the volume of messages related to your project reaches some critical mass, we can trivially create a separate mailing list for you. If you need multiple lists, let us know. We discourage having many mailing lists for smaller projects, as this tends to stunt the growth of your project community. You can always add more lists later. 9. Commit notifications [ ] Notification of commits to the main tree should be e-mailed to the list we chose to create above [ ] A separate mailing list, projectname-git, should be created for commit notifications [X] No commit notifications, please 10. Shell accounts As a general rule, we don't provide shell accounts to developers unless there's a demonstrated need. If you have one, please explain here, and list the usernames of the committers above needing shell access. 11. Translation [X] Set up the laptop.org Pootle server to allow translation commits to be made [ ] Translation arrangements have already been made at ___ 12. Notes/comments: none id_dsa.pub Description: Binary data ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Project Hosting Application: ImageToSound
1. Project name : ImageToSound
2. Existing website, if any : http://wiki.laptop.org/go/ImageToSound
3. One-line description : ImageToSound is an Activity to sonify images.
4. Longer description : ImageToSound is an Activity to sonify images.
Currently, images should
be created with another Activity (e.g. Paint or Record) and then opened from
the Journal with ImageToSound.
Requires csound = 5.08.
:
:
:
5. URLs of similar projects :
6. Committer list
Please list the maintainer (lead developer) as the first entry. Only list
developers who need to be given accounts so that they can commit to your
project's code repository, or push their own. There is no need to list
non-committer developers.
Username Full name SSH2 key URLE-mail
- --
#1 cesare Cesare Marilungo
#2
#3
...
If any developers don't have their SSH2 keys on the web, please attach them
to the application e-mail.
7. Preferred development model
[X] Central tree. Every developer can push his changes directly to the
project's git tree. This is the standard model that will be familiar to
CVS and Subversion users, and that tends to work well for most projects.
[ ] Maintainer-owned tree. Every developer creates his own git tree, or
multiple git trees. He periodically asks the maintainer to look at one
or more of these trees, and merge changes into the maintainer-owned,
main tree. This is the model used by the Linux kernel, and is
well-suited to projects wishing to maintain a tighter control on code
entering the main tree.
If you choose the maintainer-owned tree model, but wish to set up some
shared trees where all of your project's committers can commit directly,
as might be the case with a discussion tree, or a tree for an individual
feature, you may send us such a request by e-mail, and we will set up the
tree for you.
8. Set up a project mailing list:
[ ] Yes, named after our project name
[ ] Yes, named __
[X] No
When your project is just getting off the ground, we suggest you eschew
a separate mailing list and instead keep discussion about your project
on the main OLPC development list. This will give you more input and
potentially attract more developers to your project; when the volume of
messages related to your project reaches some critical mass, we can
trivially create a separate mailing list for you.
If you need multiple lists, let us know. We discourage having many
mailing lists for smaller projects, as this tends to
stunt the growth of your project community. You can always add more lists
later.
9. Commit notifications
[ ] Notification of commits to the main tree should be e-mailed to the list
we chose to create above
[ ] A separate mailing list, projectname-git, should be created for commit
notifications
[X] No commit notifications, please
10. Shell accounts
As a general rule, we don't provide shell accounts to developers unless
there's a demonstrated need. If you have one, please explain here, and
list the usernames of the committers above needing shell access.
11. Translation
[X] Set up the laptop.org Pootle server to allow translation commits to be
made
[ ] Translation arrangements have already been made at ___
12. Notes/comments:
ssh-rsa
B3NzaC1yc2EBIwAAAQEAp8AcZjjwVI7UbldocoB6NPp4pBmRpHUtPvLEx4K+zQwpqfbSXERxXaQuXij17q8rAdTVYO1cB8KyEsxcMnvPCIyd7YPBfRF5BYdWGabc5sPM/IE5e8KUPbLAFMdjtwjhYW9SAwGU2G00zVid6mWK3mRfZkQSVICqMatz4nCx1iuGpGk5U4gXaiChoBg5JrfK90VkDnz5cmS6HcSAJr9Lfy713SxeOiKdFdnVNZ+9dMALk58VQCsKsMHqoyjnv4gmX/h5bg0zd4QdjunR4GX0N/Y0PDzK88W2xFhKfdsaw9pC8YhWVTxGLKQHZ1NUZcJYxHdKdQP3M9K0qY4CK+YJ4Q==
[EMAIL PROTECTED]
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
project hosting application: Colors!
1. Project name : Colors!
2. Existing website, if any : http://wiki.laptop.org/go/Colors!
3. One-line description : Colors! is a simple natural media
painting activity for the XO laptop.
4. Longer description : Rather than constructing images from
geometric shapes, the user is
: encouraged to start with rough strokes
and then add layers of detail
: The activity features soft brushes,
collaborative painting, the
: ability to watch tutorial paintings, and
a variety of input methods.
5. URLs of similar projects : http://www.collectingsmiles.com/colors/
6. Committer list
Please list the maintainer (lead developer) as the first entry. Only list
developers who need to be given accounts so that they can commit to your
project's code repository, or push their own. There is no need to list
non-committer developers.
Username Full name SSH2 key URLE-mail
- --
#1 wadeb Wade Brainerd http://www.wadeb.com/wadeb.pub
[EMAIL PROTECTED]
If any developers don't have their SSH2 keys on the web, please attach them
to the application e-mail.
7. Preferred development model
[X] Central tree. Every developer can push his changes directly to the
project's git tree. This is the standard model that will be familiar to
CVS and Subversion users, and that tends to work well for most projects.
[ ] Maintainer-owned tree. Every developer creates his own git tree, or
multiple git trees. He periodically asks the maintainer to look at one
or more of these trees, and merge changes into the maintainer-owned,
main tree. This is the model used by the Linux kernel, and is
well-suited to projects wishing to maintain a tighter control on code
entering the main tree.
If you choose the maintainer-owned tree model, but wish to set up some
shared trees where all of your project's committers can commit directly,
as might be the case with a discussion tree, or a tree for an individual
feature, you may send us such a request by e-mail, and we will set up the
tree for you.
8. Set up a project mailing list:
[ ] Yes, named after our project name
[ ] Yes, named __
[X] No
When your project is just getting off the ground, we suggest you eschew
a separate mailing list and instead keep discussion about your project
on the main OLPC development list. This will give you more input and
potentially attract more developers to your project; when the volume of
messages related to your project reaches some critical mass, we can
trivially create a separate mailing list for you.
If you need multiple lists, let us know. We discourage having many
mailing lists for smaller projects, as this tends to
stunt the growth of your project community. You can always add more lists
later.
9. Commit notifications
[ ] Notification of commits to the main tree should be e-mailed to the list
we chose to create above
[ ] A separate mailing list, projectname-git, should be created for commit
notifications
[X] No commit notifications, please
10. Shell accounts
As a general rule, we don't provide shell accounts to developers unless
there's a demonstrated need. If you have one, please explain here, and
list the usernames of the committers above needing shell access.
11. Translation
[X] Set up the laptop.org Pootle server to allow translation
commits to be made
[ ] Translation arrangements have already been made at ___
12. Notes/comments:
You can see some art that has been created with the DS version of Colors! here:
http://colors.brombra.net/
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Project Hosting Application
1. Project name :Educational Toolkit 2. Existing website, if any : http://wiki.laptop.org/go/Educational_toolkit 3. One-line description :The educational toolkit aims at facilitating discussion of problems among students and class and allow for an automated way of conducting tests. 4. Longer description : The educational toolkit is a software to facilitate discussion in classroom with the help of technology. It aims at providing teachers and students with a tool to pose problems, compare and discuss solutions by revolving the discussion around it in something known as Demo Mode. It can provide flash cards and other objective and subjective tests that can be used as a formal testing tool for class tests and quizzes to provide a better gauge of a student's progress to the teacher. 5. URLs of similar projects : (HyperCard) http://en.wikipedia.org/wiki/HyperCard (Many custom Windows Based Free Software) http://www.sheppardsoftware.com/teachers.htm 6. Committer list Please list the maintainer (lead developer) as the first entry. Only list developers who need to be given accounts so that they can commit to your project's code repository, or push their own. There is no need to list non-committer developers. Username Full name SSH2 key URL E-mail --- --- -- --- #1 deepankDeepank Gupta http://www.nsitonline.in/it/students/2005/deepank/deepank.pub [EMAIL PROTECTED] #2 david David Goulet Attached along with mail [EMAIL PROTECTED] #3 ross Ross Light http://rlight2.googlepages.com/id_rsa.pub [EMAIL PROTECTED] If any developers don't have their SSH2 keys on the web, please attach them to the application e-mail. 7. Preferred development model [X] Central tree. Every developer can push his changes directly to the project's git tree. This is the standard model that will be familiar to CVS and Subversion users, and that tends to work well for most projects. [ ] Maintainer-owned tree. Every developer creates his own git tree, or multiple git trees. He periodically asks the maintainer to look at one or more of these trees, and merge changes into the maintainer-owned, main tree. This is the model used by the Linux kernel, and is well-suited to projects wishing to maintain a tighter control on code entering the main tree. If you choose the maintainer-owned tree model, but wish to set up some shared trees where all of your project's committers can commit directly, as might be the case with a discussion tree, or a tree for an individual feature, you may send us such a request by e-mail, and we will set up the tree for you. 8. Set up a project mailing list: [ ] Yes, named after our project name [ ] Yes, named __ [X] No When your project is just getting off the ground, we suggest you eschew a separate mailing list and instead keep discussion about your project on the main OLPC development list. This will give you more input and potentially attract more developers to your project; when the volume of messages related to your project reaches some critical mass, we can trivially create a separate mailing list for you. If you need multiple lists, let us know. We discourage having many mailing lists for smaller projects, as this tends to stunt the growth of your project community. You can always add more lists later. 9. Commit notifications [ ] Notification of commits to the main tree should be e-mailed to the list we chose to create above [ ] A separate mailing list, projectname-git, should be created for commit notifications [X] No commit notifications, please 10. Shell accounts As a general rule, we don't provide shell accounts to developers unless there's a demonstrated need. If you have one, please explain here, and list the usernames of the committers above needing shell access. 11. Translation [X] Set up the laptop.org Pootle server to allow translation commits to be made [ ] Translation arrangements have already been made at ___ 12. Notes/comments: Find more information at : http://wiki.laptop.org/go/Educational_toolkit and at http://www.nsitonline.in/it/students/2005/deepank/projects.html david.pub Description: Binary data ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Project Hosting Application: Snakes and Ladders
1. Project name : Snakes and Ladders 2. Existing website, if any : http://olpc-dev.fuelindustries.com/ 3. One-line description : Counting game for multiple players 4. Longer description : An adaptation of the classic Snakes : and Ladders (Chutes and Ladders) game, : designed to help younger children : master counting in their native language. 5. URLs of similar projects : 6. Committer list #1 Username: OpenSpark Full name:James Newton SSH2 key URL: http://olpc-dev.fuelindustries.com/JN_public.ppk Email:[EMAIL PROTECTED] 7. Preferred development model [X] Central tree. Every developer can push his changes directly to the project's git tree. This is the standard model that will be familiar to CVS and Subversion users, and that tends to work well for most projects. 8. Set up a project mailing list: [X] No 9. Commit notifications [X] No commit notifications, please 10. Shell accounts None required 11. Translation [X] Set up the laptop.org Pootle server to allow translation commits to be made 12. Notes/comments: None ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Project Hosting Application: Poetry Jam
On Mon Jan 7 11:57:57 EST 2008, Thomas Tuttle wrote: 1. Project name : Poetry Jam Done. Your tree is here: git+ssh://[EMAIL PROTECTED]/git/activities/poetryjam Please follow instructions here for importing your project: http://wiki.laptop.org/go/Importing_your_project Let us know if you have any problems with your tree. Happy hacking. Cheers, -- Henry Edward Hardy [EMAIL PROTECTED] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Project hosting application - quake-terminal
On Mon Jan 7 12:31:31 EST 2008, Rupa Deadwyler wrote: 1. Project name : quake-terminal Done. Your tree is here: git+ssh://[EMAIL PROTECTED]/git/activities/quake-terminal Please follow instructions here for importing your project: http://wiki.laptop.org/go/Importing_your_project Let us know if you have any problems with your tree. Happy hacking. Cheers, -- Henry Edward Hardy [EMAIL PROTECTED] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Project Hosting Application: Treenimation
1. Project name : Treenimation
2. Existing website, if any : www.treenimation.net
3. One-line description : Make your own multiplayer board games
4. Longer description : Use Treenimation and its built-in scripting
language,
: Treescript (or Python), to create multiplayer
: board games. Subsequent versions will add
support for
: animated games. Even non-programmers can create
: all sorts of board games.
5. URLs of similar projects :
6. Committer list
Please list the maintainer (lead developer) as the first entry. Only list
developers who need to be given accounts so that they can commit to your
project's code repository, or push their own. There is no need to list
non-committer developers.
Username Full name SSH2 key URLE-mail
- --
#1 mikehahn Mike Hahn www.treenimation.net/id_rsa.pub [EMAIL
PROTECTED]
#2
#3
...
If any developers don't have their SSH2 keys on the web, please attach them
to the application e-mail.
7. Preferred development model
[X] Central tree. Every developer can push his changes directly to the
project's git tree. This is the standard model that will be familiar to
CVS and Subversion users, and that tends to work well for most projects.
[ ] Maintainer-owned tree. Every developer creates his own git tree, or
multiple git trees. He periodically asks the maintainer to look at one
or more of these trees, and merge changes into the maintainer-owned,
main tree. This is the model used by the Linux kernel, and is
well-suited to projects wishing to maintain a tighter control on code
entering the main tree.
If you choose the maintainer-owned tree model, but wish to set up some
shared trees where all of your project's committers can commit directly,
as might be the case with a discussion tree, or a tree for an individual
feature, you may send us such a request by e-mail, and we will set up the
tree for you.
8. Set up a project mailing list:
[ ] Yes, named after our project name
[ ] Yes, named __
[X] No
When your project is just getting off the ground, we suggest you eschew
a separate mailing list and instead keep discussion about your project
on the main OLPC development list. This will give you more input and
potentially attract more developers to your project; when the volume of
messages related to your project reaches some critical mass, we can
trivially create a separate mailing list for you.
If you need multiple lists, let us know. We discourage having many
mailing lists for smaller projects, as this tends to
stunt the growth of your project community. You can always add more lists
later.
9. Commit notifications
[ ] Notification of commits to the main tree should be e-mailed to the list
we chose to create above
[ ] A separate mailing list, projectname-git, should be created for commit
notifications
[X] No commit notifications, please
10. Shell accounts
As a general rule, we don't provide shell accounts to developers unless
there's a demonstrated need. If you have one, please explain here, and
list the usernames of the committers above needing shell access.
11. Translation
[X] Set up the laptop.org Pootle server to allow translation commits to be
made
[ ] Translation arrangements have already been made at ___
12. Notes/comments:
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Project hosting application
1. Project name : Mastergoal
2. Existing website, if any :
3. One-line description : Board strategy game inspired on soccer and chess
4. Longer description : The mastergoal board represents the
field and the pieces represent the players and the ball. Each
: team have one or more players (depending
on the level) and the objective is to score a goal to the
: opposite team. This project involves the
implementation of the board game including rules, AI,
: multi-player feature, etc.
5. URLs of similar projects : http://www.mastergoal.com
6. Committer list
Please list the maintainer (lead developer) as the first entry. Only list
developers who need to be given accounts so that they can commit to your
project's code repository, or push their own. There is no need to list
non-committer developers.
Username Full name SSH2 key URLE-mail
- --
#1 nescobarj Nicolas Escobar (below)
[EMAIL PROTECTED]
#2
#3
...
If any developers don't have their SSH2 keys on the web, please attach them
to the application e-mail.
7. Preferred development model
[X] Central tree. Every developer can push his changes directly to the
project's git tree. This is the standard model that will be familiar to
CVS and Subversion users, and that tends to work well for most projects.
[ ] Maintainer-owned tree. Every developer creates his own git tree, or
multiple git trees. He periodically asks the maintainer to look at one
or more of these trees, and merge changes into the maintainer-owned,
main tree. This is the model used by the Linux kernel, and is
well-suited to projects wishing to maintain a tighter control on code
entering the main tree.
If you choose the maintainer-owned tree model, but wish to set up some
shared trees where all of your project's committers can commit directly,
as might be the case with a discussion tree, or a tree for an individual
feature, you may send us such a request by e-mail, and we will set up the
tree for you.
8. Set up a project mailing list:
[ ] Yes, named after our project name
[ ] Yes, named __
[X] No
When your project is just getting off the ground, we suggest you eschew
a separate mailing list and instead keep discussion about your project
on the main OLPC development list. This will give you more input and
potentially attract more developers to your project; when the volume of
messages related to your project reaches some critical mass, we can
trivially create a separate mailing list for you.
If you need multiple lists, let us know. We discourage having many
mailing lists for smaller projects, as this tends to
stunt the growth of your project community. You can always add more lists
later.
9. Commit notifications
[ ] Notification of commits to the main tree should be e-mailed to the list
we chose to create above
[ ] A separate mailing list, projectname-git, should be created for commit
notifications
[X] No commit notifications, please
10. Shell accounts
As a general rule, we don't provide shell accounts to developers unless
there's a demonstrated need. If you have one, please explain here, and
list the usernames of the committers above needing shell access.
11. Translation
[X] Set up the laptop.org Pootle server to allow translation
commits to be made
[ ] Translation arrangements have already been made at ___
12. Notes/comments:
ssh-dss B3NzaC1kc3MAAACBAKA8UeRiQmSK/zavI8oFri1+QKfYM0E01AuYMhVLqHoT
0eBBFNnJKbGdK2SBu4npokPF8P5grDRlJ6cOeMhfG5ABR84emSeLuGhhZGimazgJ
KzM4DLxU5ggxhzjoWU0eYU0l3pBmsLUNxB896ccd59ckPU47tUF3taFoLK9+W2u/
FQCjbbuoXrknW080O0m5NGcgCnQvSwAAAIAbLK5vecX626jiwx0b/42UkJxr
StYohcWiXFes2ujw11k7WbDcvwbCFFF5FiVUY7DLnru4BSgwH3I4TTS4qWN4yA5T
61Ea8cNppnD8UXsAswzU/SJRoxu1O3FtU5+eb/y6R6d4y7AjA/WdgjLuQnAFUhqB
T3v7FnE6NaMkA6UfjQAAAIAzEuIMbVYHAjUgtC+gK047PFyhEnpn6LG6+o1khxpZ
NOj2HvGy15WQSrHBD/ZCxrFoOEK/EiL4l681kFYHOk2nqRdnUZyEm83HXVBSnWKi
9v5IDh2HRH9wTS1RDyqLNJefhJj1pW9fC974bL5OFQO+LD7pzrIig0GtVrBXNFV2
dg==
--
Nicolás.-
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: ssh key for project hosting application
Hi, attach id_rsa.pub from that directory. Yes, that's correct. id_rsa is your secret key, id_rsa.pub is public. I bet some folks use strong pass phrases the can't remember or type, some folks use weak pass phrases, and some folks don't use any pass phrases at all. It's true. We encourage you to use a passphrase. You can use ssh-add to avoid typing your passphrase more than once per session. - Chris. -- Chris Ball [EMAIL PROTECTED] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
ssh key for project hosting application
I do a: ssh-keygen -C [EMAIL PROTECTED] cd .ssh and attach id_rsa.pub from that directory. Is that correct? I bet some folks use strong pass phrases the can't remember or type, some folks use weak pass phrases, and some folks don't use any pass phrases at all. I bet some folks use other command line arguments with ssh-keygen -- Drew Einhorn ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Project Hosting Application: World VistA
1. Project name : WorldVistA
2. Existing website, if any : http://wiki.laptop.org/go/WorldVistA
3. One-line description : Billion Dollar Health Care System from
the US Veterans Administration
4. Longer description : WorldVistA is a complete Electronic
Medical System released by the VA
: in response to a FOIA Freedom Of
Information Act request
: implemented as an open source project by
the WorldVistA non-profit.
:
5. URLs of similar projects :
6. Committer list
Please list the maintainer (lead developer) as the first entry. Only list
developers who need to be given accounts so that they can commit to your
project's code repository, or push their own. There is no need to list
non-committer developers.
Username Full name SSH2 key URLE-mail
- --
#1drew.einhorn Drew Einhorn attached [EMAIL PROTECTED]
#2
#3
...
If any developers don't have their SSH2 keys on the web, please attach them
to the application e-mail.
7. Preferred development model
[X] Central tree. Every developer can push his changes directly to the
project's git tree. This is the standard model that will be familiar to
CVS and Subversion users, and that tends to work well for most projects.
[ ] Maintainer-owned tree. Every developer creates his own git tree, or
multiple git trees. He periodically asks the maintainer to look at one
or more of these trees, and merge changes into the maintainer-owned,
main tree. This is the model used by the Linux kernel, and is
well-suited to projects wishing to maintain a tighter control on code
entering the main tree.
If you choose the maintainer-owned tree model, but wish to set up some
shared trees where all of your project's committers can commit directly,
as might be the case with a discussion tree, or a tree for an individual
feature, you may send us such a request by e-mail, and we will set up the
tree for you.
8. Set up a project mailing list:
[ ] Yes, named after our project name
[ ] Yes, named __
[X] No
When your project is just getting off the ground, we suggest you eschew
a separate mailing list and instead keep discussion about your project
on the main OLPC development list. This will give you more input and
potentially attract more developers to your project; when the volume of
messages related to your project reaches some critical mass, we can
trivially create a separate mailing list for you.
If you need multiple lists, let us know. We discourage having many
mailing lists for smaller projects, as this tends to
stunt the growth of your project community. You can always add more lists
later.
9. Commit notifications
[ ] Notification of commits to the main tree should be e-mailed to the list
we chose to create above
[ ] A separate mailing list, projectname-git, should be created for commit
notifications
[X] No commit notifications, please
10. Shell accounts
As a general rule, we don't provide shell accounts to developers unless
there's a demonstrated need. If you have one, please explain here, and
list the usernames of the committers above needing shell access.
11. Translation
[X] Set up the laptop.org Pootle server to allow translation
commits to be made
[ ] Translation arrangements have already been made at ___
--
Drew Einhorn
id_rsa.pub
Description: Binary data
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: Project Hosting Application: Candy
On Jan 23, 2008, at 6:47 AM, anthony taranto wrote: 1. Project name : Candy Done, your tree is: git+ssh://dev.laptop.org/git/activities/candy Instructions: http://wiki.laptop.org/go/Importing_your_project I note that, instead of continuing to develop Candy independently, you might wish to consider working with Chris Ball in perhaps developing the functionality as part of Pippy. You two should certainly speak and see to what extent your plans might overlap. -- Ivan Krstić [EMAIL PROTECTED] | http://radian.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Project hosting application: Implode
On Jan 21, 2008, at 7:27 PM, [EMAIL PROTECTED] wrote: Falling-block puzzle game Done, your tree is: git+ssh://dev.laptop.org/git/activities/implode Instructions: http://wiki.laptop.org/go/Importing_your_project -- Ivan Krstić [EMAIL PROTECTED] | http://radian.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Project hosting application: Implode
I figure now that people are playing this, using it as an activity-loading
test case, and filing trac tickets for it, it's probably overdue for source
control. :)
1. Project name : Implode
2. Existing website, if any : http://wiki.laptop.org/go/Implode
3. One-line description : Falling-block puzzle game
4. Longer description :
The game starts with a grid partially filled with blocks. The player
makes a move by removing adjacent blocks of the same color in groups of
three or more. When blocks are removed, higher blocks fall to fill their
space, and when a column is cleared, the blocks on either side close to
fill the gap. The object of the game is to remove all the blocks. Since
the patterns of blocks above changes when lower blocks are removed, the
player must carefully decide what order in which to remove the blocks so
that there are no isolated blocks left at the end of the game. (The
levels are generated in such a way that there is always a sequence of
removals that clears the board.)
5. URLs of similar projects :
http://www.chiark.greenend.org.uk/~sgtatham/puzzles/doc/samegame.html
http://live.gnome.org/Same_Gnome
6. Committer list
Please list the maintainer (lead developer) as the first entry. Only list
developers who need to be given accounts so that they can commit to your
project's code repository, or push their own. There is no need to list
non-committer developers.
Username Full name SSH2 key URLE-mail
- --
#1 leejc Joseph C. Lee http://jotaro.com/olpc/key.pub joe
at jotaro.com
If any developers don't have their SSH2 keys on the web, please attach
them
to the application e-mail.
7. Preferred development model
[X] Central tree. Every developer can push his changes directly to the
project's git tree. This is the standard model that will be
familiar to
CVS and Subversion users, and that tends to work well for most
projects.
[ ] Maintainer-owned tree. Every developer creates his own git tree, or
multiple git trees. He periodically asks the maintainer to look at one
or more of these trees, and merge changes into the maintainer-owned,
main tree. This is the model used by the Linux kernel, and is
well-suited to projects wishing to maintain a tighter control on code
entering the main tree.
If you choose the maintainer-owned tree model, but wish to set up some
shared trees where all of your project's committers can commit directly,
as might be the case with a discussion tree, or a tree for an individual
feature, you may send us such a request by e-mail, and we will set up the
tree for you.
8. Set up a project mailing list:
[ ] Yes, named after our project name
[ ] Yes, named __
[X] No
When your project is just getting off the ground, we suggest you eschew
a separate mailing list and instead keep discussion about your project
on the main OLPC development list. This will give you more input and
potentially attract more developers to your project; when the volume of
messages related to your project reaches some critical mass, we can
trivially create a separate mailing list for you.
If you need multiple lists, let us know. We discourage having many
mailing lists for smaller projects, as this tends to
stunt the growth of your project community. You can always add more lists
later.
9. Commit notifications
[ ] Notification of commits to the main tree should be e-mailed to the
list
we chose to create above
[ ] A separate mailing list, projectname-git, should be created for
commit
notifications
[X] No commit notifications, please
10. Shell accounts
As a general rule, we don't provide shell accounts to developers unless
there's a demonstrated need. If you have one, please explain here, and
list the usernames of the committers above needing shell access.
11. Translation
[X] Set up the laptop.org Pootle server to allow translation commits to
be made
[ ] Translation arrangements have already been made at ___
12. Notes/comments:
-- Joe
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Project Hosting Application: Lab
I have a significant majority of the base code written for Lab and plan to
get at least a working standalone version within the next few weeks.
1. Project name : Lab Activity
2. Existing website, if any : None as of yet
3. One-line description : A scientific analysis and interface activity
4. Longer description : This activity is designed to allow full-featured
: analysis of data collected from the XO Mic in
port,
: networked XOs, Measure log files, and numerous
: other sources. It aims to integrate _analysis_ of
: the data with the actual data collection.
5. URLs of similar projects : http://wiki.laptop.org/go/Measure
6. Committer list
Please list the maintainer (lead developer) as the first entry. Only list
developers who need to be given accounts so that they can commit to your
project's code repository, or push their own. There is no need to list
non-committer developers.
Username Full name SSH2 key URL
-
#1 nasa Nicholas Sinnott-Armstrong
https://www.cs.dartmouth.edu/~nasa/ssh2key.pub
Email: [EMAIL PROTECTED]
If any developers don't have their SSH2 keys on the web, please attach them
to the application e-mail.
7. Preferred development model
[X] Central tree. Every developer can push his changes directly to the
project's git tree. This is the standard model that will be familiar to
CVS and Subversion users, and that tends to work well for most projects.
[ ] Maintainer-owned tree. Every developer creates his own git tree, or
multiple git trees. He periodically asks the maintainer to look at one
or more of these trees, and merge changes into the maintainer-owned,
main tree. This is the model used by the Linux kernel, and is
well-suited to projects wishing to maintain a tighter control on code
entering the main tree.
If you choose the maintainer-owned tree model, but wish to set up some
shared trees where all of your project's committers can commit directly,
as might be the case with a discussion tree, or a tree for an individual
feature, you may send us such a request by e-mail, and we will set up the
tree for you.
8. Set up a project mailing list:
[ ] Yes, named after our project name
[ ] Yes, named __
[X] No
When your project is just getting off the ground, we suggest you eschew
a separate mailing list and instead keep discussion about your project
on the main OLPC development list. This will give you more input and
potentially attract more developers to your project; when the volume of
messages related to your project reaches some critical mass, we can
trivially create a separate mailing list for you.
If you need multiple lists, let us know. We discourage having many
mailing lists for smaller projects, as this tends to
stunt the growth of your project community. You can always add more lists
later.
9. Commit notifications
[ ] Notification of commits to the main tree should be e-mailed to the list
we chose to create above
[ ] A separate mailing list, projectname-git, should be created for commit
notifications
[X] No commit notifications, please
10. Shell accounts
As a general rule, we don't provide shell accounts to developers unless
there's a demonstrated need. If you have one, please explain here, and
list the usernames of the committers above needing shell access.
11. Translation
[X] Set up the laptop.org Pootle server to allow translation commits to be
made
[ ] Translation arrangements have already been made at ___
12. Notes/comments:
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: Project hosting application - TalknType
On Jan 3, 2008, at 10:16 AM, Tom Hannen wrote: 1. Project name : TalknType Done. Your tree is here: git+ssh://[EMAIL PROTECTED]/git/activities/talkntype Please follow instructions here for importing your project: http://wiki.laptop.org/go/Importing_your_project Let us know if you have any problems with your tree. Happy hacking. Cheers, -- Ivan Krstić [EMAIL PROTECTED] | http://radian.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Project hosting application - TalknType
1. Project name : TalknType
2. Existing website, if any : http://wiki.laptop.org/go/TalknType
3. One-line description : A spelling game using speech synthesis,
in the style of the SpeakSpell toy.
4. Longer description :
* Currently only a terminal
python program - needs sugarising...
* User opens the activity,
and is presented with a skill level (1 to 4).
* The activity speaks, using
the eSpeak Speech Synthesis software, which will soon be included in
OLPC builds.
* The activity asks the user
to spell a word from the dictionary (one of four, based on the skill
level).
* As the user types each
letter, the activity reads the letters out loud.
* When the user presses Enter,
the activity reads the entered letters as a word.
* The activity compares the
entered letters with the real word, and informs the user whether the
word was spelt correctly or not.
* Another random word is
offered for the user, etc, etc.
* In future, a more
collaborative version will allow you to test your spelling against a
friend, and compete on points.
* This activity would lend
itself well to Pootle translations, although multiple dictionary files
would be required.
5. URLs of similar projects :
http://wiki.laptop.org/go/Screen_Reader
http://wiki.laptop.org/go/Speech_synthesis
6. Committer list
Please list the maintainer (lead developer) as the first entry. Only list
developers who need to be given accounts so that they can commit to your
project's code repository, or push their own. There is no need to list
non-committer developers.
Username Full name SSH2 key URLE-mail
- --
#1 tomhannen Thomas Hannenattached to email
[EMAIL PROTECTED]
#2
#3
...
If any developers don't have their SSH2 keys on the web, please attach them
to the application e-mail.
7. Preferred development model
[X] Central tree. Every developer can push his changes directly to the
project's git tree. This is the standard model that will be familiar to
CVS and Subversion users, and that tends to work well for most projects.
[ ] Maintainer-owned tree. Every developer creates his own git tree, or
multiple git trees. He periodically asks the maintainer to look at one
or more of these trees, and merge changes into the maintainer-owned,
main tree. This is the model used by the Linux kernel, and is
well-suited to projects wishing to maintain a tighter control on code
entering the main tree.
If you choose the maintainer-owned tree model, but wish to set up some
shared trees where all of your project's committers can commit directly,
as might be the case with a discussion tree, or a tree for an individual
feature, you may send us such a request by e-mail, and we will set up the
tree for you.
8. Set up a project mailing list:
[ ] Yes, named after our project name
[ ] Yes, named __
[X] No
When your project is just getting off the ground, we suggest you eschew
a separate mailing list and instead keep discussion about your project
on the main OLPC development list. This will give you more input and
potentially attract more developers to your project; when the volume of
messages related to your project reaches some critical mass, we can
trivially create a separate mailing list for you.
If you need multiple lists, let us know. We discourage having many
mailing lists for smaller projects, as this tends to
stunt the growth of your project community. You can always add more lists
later.
9. Commit notifications
[ ] Notification of commits to the main tree should be e-mailed to the list
we chose to create above
[ ] A separate mailing list, projectname-git, should be created for commit
notifications
[X] No commit notifications, please
10. Shell accounts
As a general rule, we don't provide shell accounts to developers unless
there's a demonstrated need. If you have one, please explain here, and
list the usernames of the committers above needing shell access.
11. Translation
[X] Set up the laptop.org Pootle server to allow translation
commits to be made
[ ] Translation arrangements have already been made at ___
12. Notes/comments:
I have very knowledge of programming - I'm just starting out, but
would like to learn more, and I think this would be a good project to
work on. Several of the programmers working on the ScreenReader
activity
Re: Project hosting application - TalknType
Agree that this is a worthy project. Two suggestions: 1. Chunking -- It would be awesome if the word pronouncer could pronounce using chunking as well, the method literacy teachers use to help emergent readers learn phonics decoding skills. See links on the Phonics page for some resources about this, especially the Canadian phonics site that provides word lists with specific sound combos. 2. Like some other activities for young children (gcompris comes to mind) it would be very beneficial to have an underlying python word bank library that would return word lists and (optionally) images according to a tagging scheme. This would allow an integrated focus on vocabulary lists and learning progression in a classroom setting. It should be accompanied by a means for teachers to easily supply the lists and the tagging. I admit that I don't know the applicability of this to the teaching of reading in languages other than English, however I have discussed this idea on #olpc-content with MartinMai of omegawiki, and he thinks it would be possible to add phonetic spelling as a field in the data and associated machine-friendly access interface there. Thanks for your creativity. On Jan 3, 2008 9:30 AM, Joshua Minor [EMAIL PROTECTED] wrote: On Jan 3, 2008, at 7:16 AM, Tom Hannen wrote: 1. Project name : TalknType 2. Existing website, if any : http://wiki.laptop.org/go/TalknType Tom, this is very cool. I might be able to help out also. I made this toy that might go well with your spelling game. It is a front end to espeak that looks like a face. You can type and it will speak back to you. The mouth is the audio waveform (borrowed from Measure). http://wiki.laptop.org/images/7/7e/Speak-1.xo -josh ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel -- Always do right, said Mark Twain. This will gratify some people and astonish the rest. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Project hosting application - TalknType
On Jan 3, 2008, at 7:16 AM, Tom Hannen wrote: 1. Project name : TalknType 2. Existing website, if any : http://wiki.laptop.org/go/TalknType Tom, this is very cool. I might be able to help out also. I made this toy that might go well with your spelling game. It is a front end to espeak that looks like a face. You can type and it will speak back to you. The mouth is the audio waveform (borrowed from Measure). http://wiki.laptop.org/images/7/7e/Speak-1.xo -josh ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [laptop.org #2034] AutoReply: DOSEmu Project Hosting application/request (fwd)
so i sent this to the devel list... then waited a couple days... then followed the directions posted on the wiki and sent it to [EMAIL PROTECTED] and haven't heard anything from anyone at any time in the interim. what's up, and what can i do to push things along? are the admin types really that swamped? thanks, --elijah On Mon, 3 Dec 2007, Access and Account Requests via RT wrote: Date: Mon, 03 Dec 2007 10:58:14 -0500 From: Access and Account Requests via RT [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: [laptop.org #2034] AutoReply: DOSEmu Project Hosting application/request (fwd) Greetings, If you have submitted a general question, please make sure that it is not answered in the Official OLPC FAQ: http://wiki.laptop.org/go/Official_OLPC_FAQ This message has been automatically generated in response to the creation of a trouble ticket regarding: DOSEmu Project Hosting application/request (fwd), a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [laptop.org #2034]. Please include the string: [laptop.org #2034] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, [EMAIL PROTECTED] - -- Forwarded message -- Date: Thu, 29 Nov 2007 12:49:04 -0600 (CST) From: [EMAIL PROTECTED] To: devel@lists.laptop.org Subject: DOSEmu Project Hosting application/request 1. Project name : DOS Emulator 2. Existing website, if any : none yet 3. One-line description : DOS Emulation support for XO. 4. Longer description : This project's aim is to provide DOS : compatibility support in a Sugar- and : Journal-friendly fashion. : 5. URLs of similar projects : n/a 6. Committer list Please list the maintainer (lead developer) as the first entry. Only list developers who need to be given accounts so that they can commit to your project's code repository, or push their own. There is no need to list non-committer developers. Username Full name SSH2 key URLE-mail - -- #1 elijah Elijah Wright http://stderr.org/~elw/id_dsa.pub [EMAIL PROTECTED] ... If any developers don't have their SSH2 keys on the web, please attach them to the application e-mail. 7. Preferred development model [X] Central tree. Every developer can push his changes directly to the project's git tree. This is the standard model that will be familiar to CVS and Subversion users, and that tends to work well for most projects. [ ] Maintainer-owned tree. Every developer creates his own git tree, or multiple git trees. He periodically asks the maintainer to look at one or more of these trees, and merge changes into the maintainer-owned, main tree. This is the model used by the Linux kernel, and is well-suited to projects wishing to maintain a tighter control on code entering the main tree. If you choose the maintainer-owned tree model, but wish to set up some shared trees where all of your project's committers can commit directly, as might be the case with a discussion tree, or a tree for an individual feature, you may send us such a request by e-mail, and we will set up the tree for you. 8. Set up a project mailing list: [X] Yes, named after our project name [ ] Yes, named __ [ ] No When your project is just getting off the ground, we suggest you eschew a separate mailing list and instead keep discussion about your project on the main OLPC development list. This will give you more input and potentially attract more developers to your project; when the volume of messages related to your project reaches some critical mass, we can trivially create a separate mailing list for you. If you need multiple lists, let us know. We discourage having many mailing lists for smaller projects, as this tends to stunt the growth of your project community. You can always add more lists later. 9. Commit notifications [X] Notification of commits to the main tree should be e-mailed to the list we chose to create above [ ] A separate mailing list, projectname-git, should be created for commit notifications [ ] No commit notifications, please 10. Shell accounts As a general rule, we don't provide shell accounts to developers unless there's a demonstrated need. If you have one, please explain here, and list the usernames
Project hosting application: Gambiarra
1. Project name : Gambiarra 2. Existing website, if any : http://wiki.laptop.org/go/Gambiarra 3. One-line description : Incredible Machine-like game 4. Longer description : Gambiarra (means workaround in portuguese) is a game developed during GameJam Brasil. You got many objects in the screen and must arrange them to interact in a certain way to reach an objective. 5. URLs of similar projects : http://www.crazy-machines.com/ http://www.armadillorun.com/ 6. Committer list Please list the maintainer (lead developer) as the first entry. Only list developers who need to be given accounts so that they can commit to your project's code repository, or push their own. There is no need to list non-committer developers. #1 Username:luizirber Full name: Luiz Carlos Irber Júnior SSH2 key URL: http://www.comp.ufscar.br/~luizcarlos/key.pub E-mail: [EMAIL PROTECTED] #2 Username:ayharano Full name: Alexandre Yukio Harano SSH2 key URL: http://www.comp.ufscar.br/~ayharano/key.pub E-mail: [EMAIL PROTECTED] #3 Username:fabiocpn Full name: Fábio Cassarotti Parronchi Navarro SSH2 key URL: http://www.comp.ufscar.br/~fcpn/id_rsa.pub E-mail: [EMAIL PROTECTED] #4 Username:gabrielgeraldo Full name: Gabriel Geraldo França Marcondes SSH2 key URL: http://www.comp.ufscar.br/~gabrielgeraldo/key.pub E-mail: [EMAIL PROTECTED] If any developers don't have their SSH2 keys on the web, please attach them to the application e-mail. 7. Preferred development model [X] Central tree. Every developer can push his changes directly to the project's git tree. This is the standard model that will be familiar to CVS and Subversion users, and that tends to work well for most projects. [ ] Maintainer-owned tree. Every developer creates his own git tree, or multiple git trees. He periodically asks the maintainer to look at one or more of these trees, and merge changes into the maintainer-owned, main tree. This is the model used by the Linux kernel, and is well-suited to projects wishing to maintain a tighter control on code entering the main tree. If you choose the maintainer-owned tree model, but wish to set up some shared trees where all of your project's committers can commit directly, as might be the case with a discussion tree, or a tree for an individual feature, you may send us such a request by e-mail, and we will set up the tree for you. 8. Set up a project mailing list: [ ] Yes, named after our project name [ ] Yes, named __ [X] No When your project is just getting off the ground, we suggest you eschew a separate mailing list and instead keep discussion about your project on the main OLPC development list. This will give you more input and potentially attract more developers to your project; when the volume of messages related to your project reaches some critical mass, we can trivially create a separate mailing list for you. If you need multiple lists, let us know. We discourage having many mailing lists for smaller projects, as this tends to stunt the growth of your project community. You can always add more lists later. 9. Commit notifications [ ] Notification of commits to the main tree should be e-mailed to the list we chose to create above [ ] A separate mailing list, projectname-git, should be created for commit notifications [X] No commit notifications, please 10. Shell accounts As a general rule, we don't provide shell accounts to developers unless there's a demonstrated need. If you have one, please explain here, and list the usernames of the committers above needing shell access. 11. Notes/comments: ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Project Hosting Application
Danny, don't bother making a git tree for them. I was going to set them
up with a Subversion account on olpc.coderanger.net. Their team is
largely windows based so git will just be a headache (no that that isn't
normal ;-).
--Noah
Jason J. Kong wrote:
1. Project name : OnLine Processing of Content
2. Existing website, if any :
3. One-line description : A online content processing and
management system for OLPC.
4. Longer description : OnLine Processing of Content (codename:
sara) is
a content management system that accepts and catalogs media and makes it
accessible to users of the OLPC Project laptops in an organized
manner. The
system will be simple and easy to use, store relationship information
between
content, and be language-portable. Content submitters can log in using
OpenID
to submit a wide variety of media such as images, videos, audio clips,
articles,
or translated versions of existing content, which will then be made
available
to users. All content is tagged to make it easy for users to browse
related
items, or find the same item in an alternate language.
5. URLs of similar projects :
6. Committer list
Please list the maintainer (lead developer) as the first entry. Only
list
developers who need to be given accounts so that they can commit to
your
project's code repository, or push their own. There is no need to list
non-committer developers.
Username Full name SSH2 key URL
E-mail
-
--
#1 debsj John Debsdebsj-publickey
[EMAIL PROTECTED]
#2hurlop Paul Hurlock-Dickhurlop-publickey
[EMAIL PROTECTED]
#3kongj Jason Kongkongj-publickey
[EMAIL PROTECTED]
#4zandem Michael Zanderzandem-publickey
[EMAIL PROTECTED]
If any developers don't have their SSH2 keys on the web, please
attach them
to the application e-mail.
7. Preferred development model
[X] Central tree. Every developer can push his changes directly to the
project's git tree. This is the standard model that will be
familiar to
CVS and Subversion users, and that tends to work well for most
projects.
[ ] Maintainer-owned tree. Every developer creates his own git tree, or
multiple git trees. He periodically asks the maintainer to look
at one
or more of these trees, and merge changes into the
maintainer-owned,
main tree. This is the model used by the Linux kernel, and is
well-suited to projects wishing to maintain a tighter control on
code
entering the main tree.
If you choose the maintainer-owned tree model, but wish to set up some
shared trees where all of your project's committers can commit
directly,
as might be the case with a discussion tree, or a tree for an
individual
feature, you may send us such a request by e-mail, and we will set
up the
tree for you.
8. Set up a project mailing list:
[X] Yes, named after our project name
[ ] Yes, named __
[ ] No
When your project is just getting off the ground, we suggest you eschew
a separate mailing list and instead keep discussion about your project
on the main OLPC development list. This will give you more input and
potentially attract more developers to your project; when the volume of
messages related to your project reaches some critical mass, we can
trivially create a separate mailing list for you.
If you need multiple lists, let us know. We discourage having many
mailing lists for smaller projects, as this tends to
stunt the growth of your project community. You can always add more
lists
later.
9. Commit notifications
[ ] Notification of commits to the main tree should be e-mailed to
the list
we chose to create above
[ ] A separate mailing list, projectname-git, should be created
for commit
notifications
[X] No commit notifications, please
10. Shell accounts
As a general rule, we don't provide shell accounts to developers unless
there's a demonstrated need. If you have one, please explain here, and
list the usernames of the committers above needing shell access.
11. Notes/comments:
The project is been working on with the help of Noah Kantrowitz.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
signature.asc
Description: OpenPGP digital signature
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Project Hosting Application
1. Project name : OnLine Processing of Content
2. Existing website, if any :
3. One-line description : A online content processing and management
system for OLPC.
4. Longer description : OnLine Processing of Content (codename:
sara) is
a content management system that accepts and catalogs media and makes it
accessible to users of the OLPC Project laptops in an organized manner. The
system will be simple and easy to use, store relationship information
between
content, and be language-portable. Content submitters can log in using
OpenID
to submit a wide variety of media such as images, videos, audio clips,
articles,
or translated versions of existing content, which will then be made
available
to users. All content is tagged to make it easy for users to browse related
items, or find the same item in an alternate language.
5. URLs of similar projects :
6. Committer list
Please list the maintainer (lead developer) as the first entry. Only
list
developers who need to be given accounts so that they can commit to your
project's code repository, or push their own. There is no need to list
non-committer developers.
Username Full name SSH2 key URL
E-mail
-
--
#1 debsj John Debsdebsj-publickey
[EMAIL PROTECTED]
#2hurlop Paul Hurlock-Dickhurlop-publickey
[EMAIL PROTECTED]
#3kongj Jason Kongkongj-publickey
[EMAIL PROTECTED]
#4zandem Michael Zanderzandem-publickey
[EMAIL PROTECTED]
If any developers don't have their SSH2 keys on the web, please
attach them
to the application e-mail.
7. Preferred development model
[X] Central tree. Every developer can push his changes directly to the
project's git tree. This is the standard model that will be
familiar to
CVS and Subversion users, and that tends to work well for most
projects.
[ ] Maintainer-owned tree. Every developer creates his own git tree, or
multiple git trees. He periodically asks the maintainer to look
at one
or more of these trees, and merge changes into the maintainer-owned,
main tree. This is the model used by the Linux kernel, and is
well-suited to projects wishing to maintain a tighter control on code
entering the main tree.
If you choose the maintainer-owned tree model, but wish to set up some
shared trees where all of your project's committers can commit directly,
as might be the case with a discussion tree, or a tree for an
individual
feature, you may send us such a request by e-mail, and we will set up
the
tree for you.
8. Set up a project mailing list:
[X] Yes, named after our project name
[ ] Yes, named __
[ ] No
When your project is just getting off the ground, we suggest you eschew
a separate mailing list and instead keep discussion about your project
on the main OLPC development list. This will give you more input and
potentially attract more developers to your project; when the volume of
messages related to your project reaches some critical mass, we can
trivially create a separate mailing list for you.
If you need multiple lists, let us know. We discourage having many
mailing lists for smaller projects, as this tends to
stunt the growth of your project community. You can always add more lists
later.
9. Commit notifications
[ ] Notification of commits to the main tree should be e-mailed to
the list
we chose to create above
[ ] A separate mailing list, projectname-git, should be created for
commit
notifications
[X] No commit notifications, please
10. Shell accounts
As a general rule, we don't provide shell accounts to developers unless
there's a demonstrated need. If you have one, please explain here, and
list the usernames of the committers above needing shell access.
11. Notes/comments:
The project is been working on with the help of Noah Kantrowitz.
BEGIN SSH2 PUBLIC KEY
Comment:
B3NzaC1kc3MAAACBAPYtI92XdqUpzF8qrlV1+IyPonREB1L5OU7+NvfZignT
mMTVMmO+HUXXqSsFOSPSpqzayBMBDkZQUcUMRCaqqoKivNe545vLy63wg2J3QAnc
yfe0Cp+1Qp6Mo92E3Mj03shAB34lF1vAurL+n5A4XYtqRDfW8y4RIxcLwo8wreAT
FQD7FnEFoTwMVcMNJa9PZ8dsLPkJ/QAAAIEA5le9w1F2zE1pp68oNyUMqcVP
wajvAntwurx09XTjnmISl1MgJuzQLFwjgMvu5vRVy98jZI70vKGfEP0aCBkim9RQ
hYEUy/k5REdHM2p/U3Ra6vxs/dsth6XlcXIK0NAfx0rj31x0pG6sfdot3dJbhgt4
Q0VAR9kWAnSCLhVH1AgAAACBANnGV7dGQUvN6I93xG3jcKkKmXHB6ReDQi1oJGI8
BIsL+eY+WE8lrRYdw9pibz2K9RNLcnn3Xrrq9E1gaPbog5kML0xkxkQe+6iBi7+G
6FVTqaGi+iG5WxzWnfVIaK57gqBDMDGpxTM3sfZME3FdZu2SK1tFt2MJ/UGfNYra
NQj6
END SSH2 PUBLIC KEY
ssh-dss
Project Hosting Application
1. Project name : XOIRC
2. Existing website, if any : ---
3. One-line description : Sugar Internet Relay chat.
4. Longer description : A sugar IRC client based on URK/PURK
:
:
:
5. URLs of similar projects :
6. Committer list
Please list the maintainer (lead developer) as the first entry. Only list
developers who need to be given accounts so that they can commit to your
project's code repository, or push their own. There is no need to list
non-committer developers.
Username Full name SSH2 key URLE-mail
- --
#1 edsiper Eduardo Silva Pereira already on d.l.o
[EMAIL PROTECTED]
...
If any developers don't have their SSH2 keys on the web, please attach them
to the application e-mail.
7. Preferred development model
[X] Central tree. Every developer can push his changes directly to the
project's git tree. This is the standard model that will be familiar to
CVS and Subversion users, and that tends to work well for most projects.
[ ] Maintainer-owned tree. Every developer creates his own git tree, or
multiple git trees. He periodically asks the maintainer to look at one
or more of these trees, and merge changes into the maintainer-owned,
main tree. This is the model used by the Linux kernel, and is
well-suited to projects wishing to maintain a tighter control on code
entering the main tree.
If you choose the maintainer-owned tree model, but wish to set up some
shared trees where all of your project's committers can commit directly,
as might be the case with a discussion tree, or a tree for an individual
feature, you may send us such a request by e-mail, and we will set up the
tree for you.
8. Set up a project mailing list:
[ ] Yes, named after our project name
[ ] Yes, named __
[X] No
When your project is just getting off the ground, we suggest you eschew
a separate mailing list and instead keep discussion about your project
on the main OLPC development list. This will give you more input and
potentially attract more developers to your project; when the volume of
messages related to your project reaches some critical mass, we can
trivially create a separate mailing list for you.
If you need multiple lists, let us know. We discourage having many
mailing lists for smaller projects, as this tends to
stunt the growth of your project community. You can always add more lists
later.
9. Commit notifications
[ ] Notification of commits to the main tree should be e-mailed to the list
we chose to create above
[ ] A separate mailing list, projectname-git, should be created for commit
notifications
[X] No commit notifications, please
10. Shell accounts
As a general rule, we don't provide shell accounts to developers unless
there's a demonstrated need. If you have one, please explain here, and
list the usernames of the committers above needing shell access.
11. Notes/comments:
thanks.
Eduardo Silva.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
project hosting application
project hosting application
Rowen Remis R. Iral
Fundamental IT Engineer
http://wenmi01.bravehost.com
Moody friends. Drama queens. Your life? Nope! - their life, your story. Play
Sims Stories at Yahoo! Games.
http://sims.yahoo.com/ 
1. Project name :Project Malaya
2. Existing website, if any : http://wiki.laptop.org/go/OLPC_Philippines
3. One-line description : Linux kernel Sugar development
4. Longer description  :
We are currently improving the build and would need a repository for
the source code. We are also improving performance of build. Creation of
content and content-bundles plus the creation of activity bundles need some
space for project hosting. We are creating Philippine / Filipino or Tagalog
contents and activities.
5. URLs of similar projects :
http://dev.laptop.org/~arael/
6. Committer list
Please list the maintainer (lead developer) as the first entry. Only list
developers who need to be given accounts so that they can commit to your
project's code repository, or push their own. There is no need to list
non-committer developers.
Username Full name SSH2 key URLE-mail
- --
#1 wenmi01Rowen Remis R. Iral no_ssh2_key
http://wenmi01.bravehost.com[EMAIL PROTECTED]
#2 timhack007Timothy Paul B. Martinez no_ssh2_key no_url [EMAIL
PROTECTED]
#3
...
If any developers don't have their SSH2 keys on the web, please attach them
to the application e-mail.
7. Preferred development model
[X] Central tree. Every developer can push his changes directly to the
project's git tree. This is the standard model that will be familiar to
CVS and Subversion users, and that tends to work well for most projects.
[ ] Maintainer-owned tree. Every developer creates his own git tree, or
multiple git trees. He periodically asks the maintainer to look at one
or more of these trees, and merge changes into the maintainer-owned,
main tree. This is the model used by the Linux kernel, and is
well-suited to projects wishing to maintain a tighter control on code
entering the main tree.
If you choose the maintainer-owned tree model, but wish to set up some
shared trees where all of your project's committers can commit directly,
as might be the case with a discussion tree, or a tree for an individual
feature, you may send us such a request by e-mail, and we will set up the
tree for you.
8. Set up a project mailing list:
[ ] Yes, named after our project name
[ ] Yes, named __
[X] No
When your project is just getting off the ground, we suggest you eschew
a separate mailing list and instead keep discussion about your project
on the main OLPC development list. This will give you more input and
potentially attract more developers to your project; when the volume of
messages related to your project reaches some critical mass, we can
trivially create a separate mailing list for you.
If you need multiple lists, let us know. We discourage having many
mailing lists for smaller projects, as this tends to
stunt the growth of your project community. You can always add more lists
later.
9. Commit notifications
[ ] Notification of commits to the main tree should be e-mailed to the list
we chose to create above
[ ] A separate mailing list, projectname-git, should be created for commit
notifications
[X] No commit notifications, please
10. Shell accounts
As a general rule, we don't provide shell accounts to developers unless
there's a demonstrated need. If you have one, please explain here, and
list the usernames of the committers above needing shell access.
11. Notes/comments:
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
