This Code of Conduct covers your behaviour as a member of the L2J Community, in any forum, mailing list, wiki, web site, IRC channel, issue tracking engine, public meeting or private messaging. L2J Project Inner Circle will arbitrate in any dispute over the conduct of a member of the community.
Your work will be used by other people, and you in turn will depend on the work of others. Any decision you take will affect users and colleagues, and we expect you to take those consequences into account when making decisions. For example, when we are in a feature freeze, please don’t upload dramatically new versions of critical system components, as other people will be testing the frozen system and will not be expecting big changes.
L2J community and its members must treat one another with respect. Everyone can make a valuable contribution to L2J. We may not always agree, but disagreement is no excuse for poor behaviour and poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It’s important to remember that a community where people feel uncomfortable or threatened is not a productive one. We expect members of the L2J community to be respectful when dealing with other contributors as well as with people outside the L2J project and with users of L2J.
L2J and Free Software are about collaboration and working together. Collaboration reduces redundancy of work done in the Free Software world, and improves the quality of the software produced. You should aim to collaborate with other L2J maintainers, as well as with the upstream community that is interested in the work you do. Our work should reach community transparently and patches from L2J should be given back to the community when they are made, not just upon commits/releases. If you wish to work on new code for existing upstream features, you should keep those feature designers/maintainers informed of your ideas and progress. It may not be possible to get consensus from upstream or even from your colleagues about the correct implementation of an idea, so don’t feel obliged to have that agreement before you begin, but at least keep the outside world informed of your work, and publish your work in a way that allows outsiders to test, discuss and contribute to your efforts.
When You Disagree, Consult Others.
Disagreements, both political and technical, happen all the time and the L2J community is no exception. The important goal is not to avoid disagreements or differing views but to resolve them constructively. You should turn to the community and to the community process to seek advice and to resolve disagreements. L2J Project Leaders are in place to help decide the right course for L2J. Other L2J members may be able to help you figure out which direction will be most acceptable. If you really want to go a different way, then we encourage you to make a derivative L2J source code distribution or alternative Datapack trying to keep L2J vanilla source code/datapack as pivot for your development. That way the community can try out your changes and ideas for itself and contribute to the discussion.
When You Are Unsure, Ask For Help.
Nobody knows everything, and nobody is expected to be perfect in the L2J community. Asking questions avoids many problems down the road, and so questions are encouraged. Those who are asked should be responsive and helpful. However, when asking a question, care must be taken to do so in an appropriate forum. Off-topic questions, such as requests for help on a contributions thread, detract from productive discussion.
Engage and Participate.
L2J is a body of code, and contributing to that code is only one way to be a part of the project. Engaging in discussion, helping to maintain L2J’s infrastructure and services, offering support to other community members, even requesting others to engage this code of conduct or contributing artwork, and writing documentation are some of the other ways to contribute to L2J.
Step Down Considerately.
Developers on every project come and go and L2J is no different. When you leave or disengage from the project, in whole or in part, we ask that you do so in a way that minimises disruption to the project. This means you should tell people you are leaving and take the proper steps to ensure that others can pick up where you leave off.
Some of the hardest things to do are recognizing that a problem exists, saying “no”, or admitting to a mistake. Be honest with yourself and each other with regards to the state of L2J, what you say, and your level of commitment.
L2J Code of Conduct has been derived from Ubuntu and Xaraya CoC, which were released under the Creative Commons Attribution-Share alike license.
Another reference documents you should read: