Getting started with Noosfero development
Mailing lists
(English is the official language used in the lists)
Getting the source code
There are three ways to get the source code.
Tarballs
On topic
MilestoneItems look to Achieved milestones and click on the tarball version wanted.
Directly from the official git repository
This way is useful only for who don't want to be a code contributor, but want the last
under development code.
git clone git://gitorious.org/noosfero/noosfero.git
or if you are in a network managed by fascists, you can use
git clone http://git.gitorious.org/noosfero/noosfero.git
(this is slower, and worse in several aspects)
Well, right, you still can
contribute by the old fashion way.
Forking at Gitorious
This is the
best way for who want to contribute with Noosfero.
First of all you must to
register/login to Gitorious.org
then visit the
http://gitorious.org/noosfero and fork the noosfero repository, by clicking at "clone repository":
Give it a name:
Wait a little...
Now you can clone it (locally) in your machine and work on:
You can use something like this:
git clone git://gitorious.org/~username/noosfero/cloned-noosfero.git
or this:
git clone git@gitorious.org:~username/noosfero/cloned-noosfero.git
You will need to receive the updates from the official Noosfero repository, so register the remote repository:
git remote add official http://git.gitorious.org/noosfero/noosfero.git
...Then whenever you want you can get updates from the official Noosfero repository:
git pull official master
Installation, Running, Developing
After getting the source code, please follow the instructions on the files
HACKING and
INSTALL. Alternatively, you can read the instructions on-line directly from the
source code repository.
If you are a
Debian user, simply run
script/quick-start-debian at the Noosfero root. This will
automagically prepare your environment to
Hack and
Run.
You will need some users, communities and data to interact while developing, so run
script/sample-data and a fake social network will be created.
Sending patches
Please see
patch guidelines.