Project hosting: Difference between revisions

From OLPC
Jump to navigation Jump to search
(+Sugar note clarification)
 
(9 intermediate revisions by 5 users not shown)
Line 1: Line 1:
: ''Please note that in addition to the hosting provided below, Sugar project hosting is also available at [http://sugarlabs.org SugarLabs]. Anyone working on Sugar efforts such as Activity development are encouraged to host or mirror them there so they can be more readily available to the entire Sugar community (not just the OLPC portion of it)."

{{OLPC}}
{{Translations}}
{{Translations}}
[[Category:Developers]]
[[Category:Developers]]
[[Category:Software]]
[[Category:Software]]


= Consider external hosting first =
If you're looking to start an OLPC-related project, we are happy to host your code. We can also provide related infrastructure services. Projects must be distributed under a license that provides freedom for the users; please stick to the GPL, LGPL or the MIT license for software; and CC-BY, CC-SA, or the GFDL for text and media, unless there's a compelling reason to do otherwise. A more comprehensive guide to [[software licensing]] is available.


OLPC has limited resources and no longer offers a wide-reaching hosting program. In most cases, you are better off getting your project hosted elsewhere, for example:
= OLPC hosting =
== What we host ==
We want to provide hosting for projects that already have a bit of code and a basic roadmap. Generally, you should create a page about the project here on this wiki, and have at least 50 lines of code written, before applying. Conversely, if you have more than 50 lines of code written for a project, you should get it into git. If you feel your project should be hosted right away despite not having much code, please explain in the "Notes" part of the application.


* [http://git.sugarlabs.org Sugar Labs] provides hosting for anything and everything related to [[Sugar]] Note: Most of SugarLabs development has migrated to github. Currently git.sugarlabs.org should be considered read-only for archival purposes.
== What we provide ==
* [http://fedorapeople.org/ Fedora] provides hosting for Fedora-related projects
* [http://gitorious.org/ Gitorious] and [http://github.com/ GitHub] provide free git hosting for open-source projects


= OLPC hosting =
* One or more source code repositories:
** Using [http://git.or.cz git], the version control system used by the Linux kernel
** Visiblity on the [[git#Git#The_OLPC_Git_Repository|The OLPC Git Repository]] for web browsing and sharing with the community.
** Commit notifications by e-mail
* A bug tracker, via [http://projects.edgewall.com/trac Trac]
* Web and file space, either on laptop.org or on a domain you own for the project (but not a developer's personal domain)
* Mailing lists, via [http://www.gnu.org/software/mailman/index.html Mailman]
* Translation services via our [http://dev.laptop.org/translate Pootle installation ]
* Shell accounts, as needed
* Other infrastructure services that you request, within reason, such as a blog or a separate project wiki

Hosting takes place on a fast server with lots of disk space and bandwidth. We have standardized on the git version control system, as it's blazingly fast and reasonably simple to use. If you have a compelling reason to use a different VCS, please note this in the "Notes" section.

== How to apply ==
Copy and paste the following application into an e-mail, fill it out, and '''send it to the [http://mailman.laptop.org/mailman/listinfo/devel devel] mailing list''' and to sysadmin@laptop.org. You should be subscribed to the [[mailing lists|list]] to monitor the thread and address any questions or concerns from other developers and staff.

If you have trouble logging in, or require further privileges, please request these in an e-mail to sysadmin@laptop.org.

=== The application ===
The application form is available at [[Project hosting application]]. Bear with the process; the antiquated email exchange works well with developing countries.

=== Public/Private Key Pairs ===

The application will ask for a public key.

The use of public keys is not optional in OLPC's security system. Without
a private/public keypair, they 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
[http://en.wikipedia.org/wiki/Public-key_cryptography wikipedia]

Please use RSA rather than DSA keys.

In the Unix/Linux/Mac environment, you can use ssh-keygen [http://unixwiz.net/techtips/putty-openssh.html] to create
the public/private key pair.


OLPC provides a shell account on dev.laptop.org for trusted contributors. This offers:
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.


* Shell access, high bandwidth internet connection, plentiful disk space
In the Windows environment, the free program [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html puttygen.exe] can be used to create a public/private key pair. Make sure to [http://unixwiz.net/techtips/putty-openssh.html#keypair create a ssh-compatible key pair]. The program pageant.exe can be used to facilitate connection to your account using your private
* Web hosting as http://dev.laptop.org/~username
key once we have set up your account with the public key you will
* [[Git]] hosting as git://dev.laptop.org/users/username/repo (and the possibility to contribute to 'global' projects hosted in git)
provide to us.
* Access to contribute to [[RPM Dropbox|RPM dropboxes]]


= Apply for an account =
Please send the public key as a mail attachment, or send a link to some publically accessible place where it is hosted. Cutting and pasting it isn't as good an idea as this often introduces extra nonprintable characters such as line breaks into the key text, making it unusable.


Send a mail to the devel [[mailing lists|mailing list]] requesting access. Attach your public RSA2 ssh key. Having already contributed to OLPC, your name and contributions should be already familiar within the community, but include a brief note about your current and future work anyway.
=== Importing your project ===
See [[Importing your project]] to learn how to move your code into your OLPC repository, and read [[Using a central git tree]] to find out how to use git.


= Other providers =
= Maintainer =


Chris Ball runs the show. Queries should be sent to the devel mailing list.
Other providers that have been used for hosting OLPC and Sugar-related projects include:
* [http://launchpad.net Launchpad.net]
* [http://gitorious.com/ Gitorious]
* [http://sugarlabs.org/ SugarLabs], see [http://sugarlabs.org/go/ActivityTeam/How_to_migrate_from_OLPC How to migrate from OLPC]

Latest revision as of 22:08, 10 March 2016

  english | 日本語 | 한국어 HowTo [ID# 298680]  +/-  

Consider external hosting first

OLPC has limited resources and no longer offers a wide-reaching hosting program. In most cases, you are better off getting your project hosted elsewhere, for example:

  • Sugar Labs provides hosting for anything and everything related to Sugar Note: Most of SugarLabs development has migrated to github. Currently git.sugarlabs.org should be considered read-only for archival purposes.
  • Fedora provides hosting for Fedora-related projects
  • Gitorious and GitHub provide free git hosting for open-source projects

OLPC hosting

OLPC provides a shell account on dev.laptop.org for trusted contributors. This offers:

Apply for an account

Send a mail to the devel mailing list requesting access. Attach your public RSA2 ssh key. Having already contributed to OLPC, your name and contributions should be already familiar within the community, but include a brief note about your current and future work anyway.

Maintainer

Chris Ball runs the show. Queries should be sent to the devel mailing list.