Project Hosting Request: DObject
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 1. Project name : DObject 2. Existing website, if any :http://download.laptop.org/content/conf/20080403-olpc-mini-conf/Collaboration/ 3. One-line description : Active data structures for automatic coherent collaboration. 4. Longer description : DObject is a collection of data structures and : other code to allow the easy creation of Activities : in Python that fully support versioning, undo, synchronous collaboration, : and asynchronous collaboration. 5. URLs of similar projects : http://www.opencroquet.org/index.php/Main_Page, distantly. 6. Committer list Ben Schwartz (username bemasc on dev.laptop.org) 7. Preferred development model [X] Central tree. Every developer can push his changes directly to the project's git tree. 8. Set up a project mailing list: [X] No 9. Commit notifications [X] No commit notifications, please 10. Shell accounts: None needed. 11. Translation [X] Set up the laptop.org Pootle server to allow translation commits to be made 12. Notes/comments: -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkkfQVQACgkQUJT6e6HFtqTq+QCfTHlu2qBPYQuoRoln/6F5zohe 3hQAn2mZj4PK6ZqB90CR2nQEgsxembTw =6WqM -END PGP SIGNATURE- ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Project hosting request: qa-scripts
1. Project name : qa-scripts
2. Existing website, if any : none
3. One-line description : Testing setup/data-collection scripts.
4. Longer description :
A collection of scripts used by the internal OLPC QA team to ease repetitive
test setup/data collection.
:
:
:
5. URLs of similar projects : none
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 reuben Reuben Caron
http://dev.laptop.org/~reuben/id_rsa.pub [EMAIL PROTECTED]
#2 mchua Mel Chua http://melchua.com/tmp/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.
8. Set up a project mailing list:
[X] No
9. Commit notifications
[X] No commit notifications, please
10. Shell accounts
none needed
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
--
Mel Chua
QA/Support Engineer
[EMAIL PROTECTED]
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
new project hosting request: infoslicer
1. Project name : infoslicer
2. Existing website, if any :
3. One-line description :a tool to enable teachers to
quickly and easily select web-based content to edit, package, and
distribute as teaching materials.
4. Longer description :
: infoslicer is a Sugar Activity that both
allows web content (e.g., the Wikipedia) to be cached locally --
similar to wikislice --
: but also allows the remixing of the
content and incorporation of local content. The remixed content can
then be redistributed
: to other Sugar users.
5. URLs of similar projects : wikislice
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 walter Walter Bender [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:
-walter
--
Walter Bender
Sugar Labs
http://www.sugarlabs.org
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
(Resubmission) Project hosting request: Lambda
1. Project name : Lambda
2. Existing website, if any : http://wiki.laptop.org/go/Lambda
3. One-line description : Lambda is a simple Lisp interpreter for
Sugar.
4. Longer description : Lambda is a simple Lisp interpreter for
Sugar which
: aims to be both fun for the beginning
programmer as
: well as simple enough to yield its
secrets to the
: curious student.
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 antoine Antoine van Gelder
http://dev.laptop.org/~antoine/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
Re: Project hosting request: xo-lambda
On Wed, Sep 24, 2008 at 9:04 PM, Bobby Powers [EMAIL PROTECTED] wrote: very cool! On 25 Sep 2008, at 04:10, Eben Eliason wrote: Agreed! I have been secretly wanting to play around with lisp myself, so I look forward to playing with this a lot. *grin* Tx guys! As a small nitpick, I'd recommend dropping 'XO' from the name. While I just discovered that I omitted this detail while discussing naming in the HIG, it doesn't really provide any useful information in the activity name itself. Moreover, since Sugar is quickly becoming available on various distributions, it's incorrect to tie Sugar activities to the XO itself, which is the name of the OLPC specific hardware. It would still be fine, of course, to refer to activities (especially those that are brethren of applications already found on other OSes) as, perhaps, Sugar Lambda to differentiate them in the public image, but even then it doesn't seem necessary to include it in the activity name itself. =) Good points, thank you Eben. Lambda activity it is! Shall I resubmit a hosting request with the name change ? PS. I'm somewhat unfamiliar with the project hosting process, but would there be a good place to introduce this type of information, so we can make things as simple as possible? Should we just mention this guideline/requirement on the wiki page (http://wiki.laptop.org/go/Project_hosting) or the application? I think the name is the only item on the application which needs to adhere to a guideline. However, we might link to the full HIG from that page anyway, and/or include a link to it in the project hosting response, to get budding developers pointed in the right direction. I would have caught it if it was mentioned on the Project_hosting wiki page. - a ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Project hosting request: xo-lambda
1. Project name : XO-Lambda
2. Existing website, if any : http://wiki.laptop.org/go/XO-Lambda
3. One-line description : XO-Lambda is a simple Lisp interpreter
for the OLPC XO-1
4. Longer description : XO-Lambda is a simple Lisp interpreter
for the OLPC XO-1
: which aims to be both fun for the
beginning programmer as
: well as simple enough to yield it's
secrets to the curious
: student.
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 antoine Antoine van Gelder
http://dev.laptop.org/~antoine/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
Re: Project hosting request: xo-lambda
very cool!
On Wed, Sep 24, 2008 at 7:26 PM, Antoine van Gelder
[EMAIL PROTECTED] wrote:
1. Project name : XO-Lambda
2. Existing website, if any : http://wiki.laptop.org/go/XO-Lambda
3. One-line description : XO-Lambda is a simple Lisp interpreter
for the OLPC XO-1
4. Longer description : XO-Lambda is a simple Lisp interpreter
for the OLPC XO-1
: which aims to be both fun for the
beginning programmer as
: well as simple enough to yield it's
secrets to the curious
: student.
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 antoine Antoine van Gelder
http://dev.laptop.org/~antoine/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
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: Project hosting request: xo-lambda
Agreed! I have been secretly wanting to play around with lisp myself,
so I look forward to playing with this a lot.
As a small nitpick, I'd recommend dropping 'XO' from the name. While
I just discovered that I omitted this detail while discussing naming
in the HIG, it doesn't really provide any useful information in the
activity name itself. Moreover, since Sugar is quickly becoming
available on various distributions, it's incorrect to tie Sugar
activities to the XO itself, which is the name of the OLPC specific
hardware.
It would still be fine, of course, to refer to activities (especially
those that are brethren of applications already found on other OSes)
as, perhaps, Sugar Lambda to differentiate them in the public image,
but even then it doesn't seem necessary to include it in the activity
name itself. =)
- Eben
PS. I'm somewhat unfamiliar with the project hosting process, but
would there be a good place to introduce this type of information, so
we can make things as simple as possible? Should we just mention this
guideline/requirement on the wiki page
(http://wiki.laptop.org/go/Project_hosting) or the application? I
think the name is the only item on the application which needs to
adhere to a guideline. However, we might link to the full HIG from
that page anyway, and/or include a link to it in the project hosting
response, to get budding developers pointed in the right direction.
On Wed, Sep 24, 2008 at 9:04 PM, Bobby Powers [EMAIL PROTECTED] wrote:
very cool!
On Wed, Sep 24, 2008 at 7:26 PM, Antoine van Gelder
[EMAIL PROTECTED] wrote:
1. Project name : XO-Lambda
2. Existing website, if any : http://wiki.laptop.org/go/XO-Lambda
3. One-line description : XO-Lambda is a simple Lisp interpreter
for the OLPC XO-1
4. Longer description : XO-Lambda is a simple Lisp interpreter
for the OLPC XO-1
: which aims to be both fun for the
beginning programmer as
: well as simple enough to yield it's
secrets to the curious
: student.
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 antoine Antoine van Gelder
http://dev.laptop.org/~antoine/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
project hosting request
1. Project name : Conozco Uruguay
2. Existing website, if any :
3. One-line description : Uruguayan geography educational game
4. Longer description : This activity features a map of Uruguay
with different layers for departments,
: cities, rivers, etc. The game involves
helping an alien rebuild a spaceship by indicating
: the location based on clues. The game
also features an explore mode to discover
: different locations and facts related to them.
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 geirea GabrielEirea public key 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 ___
12. Notes/comments:
Thank you!
id_dsa.pub
Description: Binary data
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Project Hosting request: ISIS
1. Project name : Incredibly Simple Interactive Storytelling 2. Existing website, if any : http://wiki.laptop.org/go/ISIS 3. One-line description : ISIS is a platform to develop interactive stories. 4. Longer description : ISIS is a platform to allow children to develop adventure stories or interactive fiction authoring system for the XO. The project uses python and pygame (with olpcgames wrapper) technologies. 5. URLs of similar projects : http://wiki.laptop.org/go/StoryBuilder 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 robertofagaRoberto Faga Jr http://grad.icmc.usp.br/~dyw/robertofaga_rsa_key.pub [EMAIL PROTECTED] #2 avoine Patrick Hétu http://grad.icmc.usp.br/~dyw/patrick_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: [ ] 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: This project is already hosted in projects/games-misc, but as games-misc has about 150MB of files (and many about 2000 files!), we want a git repository only for this as the project has less then 1MB. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Regarding public/private key pairs, was Re: [laptop.org #7741] project hosting request (resend)
Regarding public keys required for hosting applications: The use of public keys is not optional in our security system. Without a private/public keypair, we could set up a repository but you would not ever be able to access it. The ssh key is necessary in order for you to be able to connect to the repository. It serves in place of a password. If you are not familiar with the use of public key infrastructure, you can learn about it at wikipedia: http://en.wikipedia.org/wiki/Public-key_cryptography In the Unix/Linux/Mac environment, you can use ssh-keygen to create the public/private key pair. See http://www.linuxquestions.org/linux/answers/Networking/Public_key_authentication_with_ssh for an example. In our case you need only do step one above and provide us with the public key or a link to it in your application. We will provision the server with it. You must be responsible to keep track of your private key as there is no reasonable way to recover it if lost or compromised. In the Windows environment, the free program puttygen.exe can be used to create a public/private key pair, and the program pageant.exe can be used to facilitate connection to your account using your private key once we have set up your account with the public key you will provide to us. http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html --HH. [EMAIL PROTECTED] On Tue, Mar 11, 2008 at 7:28 AM, [EMAIL PROTECTED] wrote: Tue Mar 11 07:28:24 2008: Request 7741 was acted upon. Transaction: Ticket created by [EMAIL PROTECTED] Queue: sysadmin Subject: project hosting request (resend) Owner: Nobody Requestors: [EMAIL PROTECTED] Status: new Ticket URL: http://rt.laptop.org/Ticket/Display.html?id=7741 1. Project name : csndsugui 2. Existing website, if any : 3. One-line description : a toolkit for the development of custom csound activities 4. Longer description : csndsugui is a Python-based toolkit for the development of : activities based on csound under sugar: lab demos, instruments : and music-related applications. It also aims to provide a simple migration : path for csound code that uses FLTK widgets. 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 Victor Lazzarini [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
Project Hosting request: Mastergoal (a resend)
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 (official website)
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
Project Hosting request: Moon (a resend)
1. Project name : Moon 2. Existing website, if any : http://wiki.laptop.org/go/Moon 3. One-line description : Moon phase activity 4. Longer description : Displays current Moon phase image information 5. URLs of similar projects : None 6. Committer list UsernameFull nameSSH2 key URL E-mail - -- garycmartin Gary C Martinhttp://garycmartin.com/ id_dsa.pubgary at garycmartin dot com 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. 8. Set up a project mailing list: [ ] Yes, named after our project name [ ] Yes, named __ [X] No 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 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: FYI: Sorry for the dupe request, I sent this in a couple of weeks back but can't see it in the online archives. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
project hosting request
1. Project name : csndsugui
2. Existing website, if any :
3. One-line description : a toolkit for the development of custom
csound activities
4. Longer description : csndsugui is a Python-based toolkit for the
development of
: activities based on csound under sugar: lab
demos, instruments
: and music-related applications. It also aims
to provide a simple migration
: path for csound code that uses FLTK widgets.
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 Victor
Lazzarini [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 do not have a username or a SSH2 key
Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: Project Hosting request: Maze
On Dec 12, 2007, at 2:56 AM, Joshua Minor wrote: If any developers don't have their SSH2 keys on the web, please attach them to the application e-mail. I didn't see your SSH2 key attached or linked. Could you mail me a copy so I can create your account? Thanks, -- Ivan Krstić [EMAIL PROTECTED] | http://radian.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Project Hosting Request
On Dec 27, 2007, at 7:44 PM, ffm wrote: 6. Committer list N/A To clarify, you only need a mailing list hosted? That's been arranged; let me know if you need anything else. Thanks, -- Ivan Krstić [EMAIL PROTECTED] | http://radian.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Project Hosting request: LiveBackup_XO-LiveCD
On Dec 16, 2007, at 2:58 PM, [EMAIL PROTECTED] wrote: 1. Project name : LiveBackup_XO-LiveCD 3. One-line description : Live-CD build based on the LiveBackup Framework Done. Your tree is here: git+ssh://dev.laptop.org/git/projects/livebackup-xo-cd Please follow instructions here for importing your project: http://wiki.laptop.org/go/Importing_your_project The primary developer should have received an e-mail about the mailing list whose creation you requested. 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
Re: Project Hosting request
On Dec 3, 2007, at 11:59 AM, Roberto Fagá wrote: 1. Project name : ePals Activity 2. Existing website, if any : www.epals.com , http://wiki.laptop.org/go/EPals 3. One-line description : ePals is a pen pal and project activity Done. Your tree is here: git+ssh://[EMAIL PROTECTED]/git/activities/epals 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
Re: Project Hosting Request
On Dec 27, 2007, at 6:44 PM, ffm wrote: 3. One-line description : GASP provides a simple, procedural graphics API for beginning students using Python. I would use that. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Project Hosting request: LiveBackup_XO-LiveCD
[EMAIL PROTECTED] wrote: 1. Project name : LiveBackup_XO-LiveCD 2. Existing website, if any : 3. One-line description : Live-CD build based on the LiveBackup Framework 4. Longer description : Live-CD's are created from official OLPC builds. : Unmodified images are converted to squashfs : filesystems and embedded into a : framework which provides everything : needed to run a live system. ... please create a shell account, because we want to use dev.laptop.org to distribute the Live-CD This LiveCD should be very helpful going forward and seems likely to be easily maintained. Having it available on the OLPC servers would be a good thing and I'm strongly for having the project created (I suggested applying for the project in order to have that happen). Take care, Mike -- Mike C. Fletcher Designer, VR Plumber, Coder http://www.vrplumber.com http://blog.vrplumber.com ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Project Hosting request: Maze
1. Project name : Maze
2. Existing website, if any : http://lux.vu/blog/2007/12/11/one-maze-per-child/
3. One-line description : A multiplayer maze game.
4. Longer description : A multiplayer maze game that uses the
olpcgames
: module and pygame.
:
:
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 jminor Joshua
Minor [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:
This game might fill the role of a Maze Game Template as mentioned
here: http://wiki.laptop.org/go/Game_templates Also, there is no
text in the game
by design, so only the title of the activity would need to be
translated. I have only
tested it under emulation.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Fwd: Project Hosting Request
This was submitted a week ago and got no replies, so I am submitting it again. 1. Project name : Graphics API for the Students of Python (GASP) 2. Existing website, if any : https://launchpad.net/gasp 3. One-line description : GASP provides a simple, procedural graphics API for beginning students using Python. 4. Longer description :GASP is built on top of pygame, and is designed to lead students into full use of python :and object oriented programming.It is designed to imitate LiveWires, a Tk python GUI :API. 5. URLs of similar projects : Pygame http://pygame.org : LiveWires http://www.livewires.org.uk/python 6. Committer list N/A 7. Preferred development model N/A 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 N/A 11. Translation [ ] Set up the laptop.org Pootle server to allow translation commits to be made 12. Notes/comments: Launchpad will handle code hosting and translations. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Project Hosting Request
1. Project name : Graphics API for the Students of Python (GASP) 2. Existing website, if any : https://launchpad.net/gasp 3. One-line description : GASP provides a simple, procedural graphics API for beginning students using Python. 4. Longer description :GASP is built on top of pygame, and is designed to lead students into full use of python :and object oriented programming.It is designed to imitate LiveWires, a Tk python GUI :API. 5. URLs of similar projects : Pygame http://pygame.org : LiveWires http://www.livewires.org.uk/python 6. Committer list N/A 7. Preferred development model N/A 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 N/A 11. Translation [ ] Set up the laptop.org Pootle server to allow translation commits to be made 12. Notes/comments: Just website hosting, please. Launchpad will handle repos and translations. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Project Hosting request
1. Project name : Boggle
2. Existing website, if any : http://rpiolpc.blogspot.com
3. One-line description : A Simple boggle game
4. Longer description : A simple boggle game to increase student word
: knowledge and spelling ability. Will have
ability to
: easily swap in new dictionaries with varying word
: difficulties and languages.
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 tamoneya Andrew Tamoney [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 request (Key attached)
Andrew Tamoney wrote:
1. Project name : Boggle
2. Existing website, if any : http://rpiolpc.blogspot.com
3. One-line description : A Simple boggle game
4. Longer description : A simple boggle game to increase student
word
: knowledge and spelling ability. Will
have ability to
: easily swap in new dictionaries with
varying word: difficulties and languages.
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 URL
E-mail
-
--
#1 tamoneyaAndrew Tamoneyattached
[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:
BEGIN SSH2 PUBLIC KEY
Comment: rsa-key-20071204
B3NzaC1yc2EBJQAAAIEAiS9OBT8n9TxbPKhdfU3dxy5SA2yloPstxCO2
qSIN/zsXfSjGvW6ZMxtZdMoiL81mshfxfaM5vFwiuE1mCRtOQeKLmnlieTMg4+aw
X1Zp1mqdlZwBW6mpO/8SLME+BWKvMu2TTRwwcC7q3et/htcvc93CAlNI2+pOHqVC
XiuOnrU=
END SSH2 PUBLIC KEY
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: Project Hosting request
Nice. The world's greatest word game. You might consider a handicap
system where players can be restricted from playing short or common
words.
And of course in digital boggle one isn't limiited to 6-sided cubes...
SJ
On Dec 4, 2007 12:31 AM, Andrew Tamoney [EMAIL PROTECTED] wrote:
1. Project name : Boggle
2. Existing website, if any : http://rpiolpc.blogspot.com
3. One-line description : A Simple boggle game
4. Longer description : A simple boggle game to increase student word
: knowledge and spelling ability. Will have
ability to
: easily swap in new dictionaries with varying
word
: difficulties and languages.
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 tamoneya Andrew Tamoney
[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
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
