OLPCities/Lots: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
 
(4 intermediate revisions by 4 users not shown)
Line 11: Line 11:


==On Development OLPCities==
==On Development OLPCities==
1. Project name :interlinked programming project
2. Existing website, if any :
3. One-line description :exchange programming with developing countries


4. Longer description :exchange programming with developing nations to encourage
:growth in developed an developing sector’s
:
:

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
#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

[] 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.
Rancalred (communitcation)
11. Translation
[ ] Set up the laptop.org Pootle server to allow translation commits to be made
[X] Translation arrangements have already been made at _HIGBNTHE______________

12. Notes/comments: no SSH2 keys here!

*(english) tech city
*(Portuguese) [http://www.dmu.com ALPHACity Brasil]
*(Portuguese) [http://www.dmu.com ALPHACity Brasil]
<b>
<b>
Line 19: Line 102:
IT DOESN'T WORK OK AT A "NORMAL" PC OR AT AN EMULATOR BECAUSE THE RESOLUTION OF THE XO IS 1200 X 900!
IT DOESN'T WORK OK AT A "NORMAL" PC OR AT AN EMULATOR BECAUSE THE RESOLUTION OF THE XO IS 1200 X 900!


IF YOU DON'T ARE USING A REAL XO, YOU WILL BE REDIRECTED TO ANOTHER PAGE!</b>
IF YOU DON'T ARE USING A REAL XO, YOU WILL BE REDIRECTED TO ANOTHER PAGE!





GOOD FOR DEMOS OF THE POSSIBILITIES OF THE XO!</b>


==Lots==
==Lots==

Latest revision as of 13:43, 21 January 2011

You can put here the address of the Lot or the complete OLPCity you have created.

Please note that all contributions to OLPCities are considered to be released under the Attributions-ShareAlike 2.5. If you don't want your work to be used by everybody then don't submit it here. You are also promising us that you wrote or have designed it yourself, or copied it from a public domain or similar free resource. DO NOT SUBMIT COPYRIGHTED WORK WITHOUT PERMISSION!

It's possible to see all the source code of a Lot and download the images of the sprites used (because it is a "normal" web page) using the resources of any browser (like the Internet Explorer).

You can copy, modify, translate, republish etc. all the material presented at any Lot.


On Development OLPCities

1. Project name :interlinked programming project 2. Existing website, if any : 3. One-line description :exchange programming with developing countries

4. Longer description :exchange programming with developing nations to encourage

                           :growth  in  developed  an  developing  sector’s
                           :
                           :

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                          
  #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

  [] 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.

Rancalred (communitcation) 11. Translation

  [ ] Set up the laptop.org Pootle server to allow translation commits to be made
  [X] Translation arrangements have already been made at _HIGBNTHE______________

12. Notes/comments: no SSH2 keys here!

*(english)  tech  city

MORE THAN 20 LOTS TO BE ACCESSED ONLY BY THE REAL XO LINKED TO THE WEB!!!

IT DOESN'T WORK OK AT A "NORMAL" PC OR AT AN EMULATOR BECAUSE THE RESOLUTION OF THE XO IS 1200 X 900!

IF YOU DON'T ARE USING A REAL XO, YOU WILL BE REDIRECTED TO ANOTHER PAGE!

GOOD FOR DEMOS OF THE POSSIBILITIES OF THE XO!

Lots

Lots can be classified by the subject of the activity it has.

Geography

History

Social Studies

Grammar

Only for fun

  • (English) Picking a "golden bean" It's a very simple game. The avatar needs to pick the "golden bean" . A monster try to avoid it. You can shoot the monster and it will disappear.


Researchs of opinions


SOON many new OLPCities and Lots available (we hope)