The SNEP Development Team would like to rely on you! There are many ways to contribute:

	Documentation Many people are trying to use SNEP and the lack of information can cause difficulties. You can contribute with your knowledge providing useful info to update the documentation.
	Translation If you’re fluent on any language, contribute, so more people around the world could use it on their native language. Available Priority Status File Portugues - BR - Finished pt_BR.po English - US - Finished Messages.po How to Translate a .po File .po 1. Download your preferred .po file. 2. To edit a file, you need to , download POedit, a free software available for Linux, Mac and Windows. 3. You need to load the SNEP’s standard message file to generate to a new language file. 4. Open the translation file. With the file loaded, click File > New Catalog. 5. After the translation, two files will be generated, the .mo file must be copied into the directory langs/. 6. and sent through the Link
	Bugs Identification Sign up SNEP’s Bug Tracker and report found bugs: bugs.sneplivre.com.br
	Plugins Submission You can develop your own plugins and share them with the community!

Click here and obtain more info about how to participate on each team.

This code of conduct cover your behavior as a member of the SNEP Community, in any forum, discussion list, wiki, site, Mirc Channel, public meetings and private mail. The SNEP Community Counsil will judge any discussion about the behavior of a community member.

Consider. Your work will be used by other people, and you, by other hand, will rely on the work of others. Any decision taken by you will affect users and colleagues, and we hope you consider those consequences in consideration when taking decisions. For example, when we’re “freeze to feature addition”, please, don’t send excessive new version for critical components, because other people will be testing the “frozen system” and they won’t be expecting great changes.

Respect. The SNEP Community and its members treat each other with respect. Everybody can make worth contributions to SNEP . We can’t agree always, but this disagreement can’t be an excuse to bad behavior and bad habits. We can all experience some frustration sometimes, but we can’t allow those frustrations to become personal attacks. It’s important to remember that a community where the people feel uncomfortable or threaten isn’t a productive one. We hope that all the members of the SNEP Livre community are respectful dealing with other contributors, as dealing with people outsite the SNEP project or its users.

Collaborate. SNEP and Free Software are signs of collaboration and teamwork. The collaboration reduces the redundant work on the world of Free Software, and improves the quality of the produced software. You must aim to collaborate with others SNEP  maintainers, as well with the community rightly involved interested on the work you do. Your work must be done in a transparent way e the corrections to the SNEP  must be sent back to the community when done, and not only in the distribution’s launch. If you want to work on a new code to an existing project, at least keep those projects informed about your ideas and progress. Maybe won’t be possible to reach an agreement with the project or even with your partners about the correct implementation of an idea, so don’t feel obliged to have this agreement before start. At least keep everyone around informed about your work, and publish it in a way that permits outside people to test it, discuss it and contribute to your efforts.

If disagree, consult others. Divergence, politics or technical, happens on all teams and the SNEP community is no exception. The crucial point is not to avoid divergences or different viewpoints, but solve them constructively. You rely on the community e its process for consulting and to solve disagreements. We have the Technical Board and the Community Council, and both you help deciding SNEP’s path.

When unsure, ask for help. Nobody knows everything and the SNEP community don’t expect anybody to be perfect. Asking for help avoid many problems along the way, so questions are encouraged. Those questioned must be understandable and helpful. Although, when asking a question, you must be careful to do it in the appropriate forum. Off topic questions, as asking for help in an email discussion list about development, harm productive discussions.

Resign with consideration. In all projects developers come and go, and SNEP is not different. When you leave or resign the project, totally or partially, we ask you to do it in a way to minimize project discontinuity. This mean you have to warn all people involved that you’re leaving and do all the appropriate process to ensure other can continue your work.