Menu

HowToCollaborate

Tim Band Minaya Serrano
There is a newer version of this page. You can find it here.

How to collaborate on LinuxStopMotion

Specific collaboration

If you found a bug, or if you want to request a new feature, tell us on our bug tracker (url pending). Also, you can post a fix patch. The LinuxStopMotion team will discuss about it and integrate your patch on the project as soon as possible. (*)

Usual collaboration

If you want to be a linuxstopmotion developer, you need a sourceforge account (or another OpenID account to log in SourceForge).

Then, you need 3 steps:


Step 1

Fork the LinuxStopMotion code from https://sourceforge.net/p/linuxstopmotion/code/.


Step 2

Develop your bugfixes or new features on your fork.

We use Git and the SourceForge Git documentation explain how to configure your repository access.

We have some conventions on this development:

You must create a new branch for your feature/bug. Feel free to name your feature branch as you prefers, but we use a specific format for bugfixes branch names:

bug-N where N is the bug number asociated in the bugtracker. Also, you can append a short bug description.

Examples:

If you want to develop a new feature:
git checkout -b undo-system-refactoring

If you want to fix a bug:
git checkout -b bug-991486
or
git checkout -b bug-991486-thumbnail-autoscrolling


Step 3

Send us a merge request from your branch. The team will discuss about it and integrate your branch on the project as soon as possible.


(*) This integration implies that one team member will do all the new-branch/merge-request process.