Join Our Community of Developers

Our Philosophy

Open source is about more than just code. It’s also about the planning that happens before the code is written, the process of how that code is used by others, and fostering a welcoming environment where a community can grow. We want people to work better together. Although we maintain this site, this is a community we build together, and we need your help to make it the best it can be. Project-Lernaean issues the following policy related to the use of, contribution to, and creation and release of Open Source Software in order to support and build upon the efforts of the OpenSource Community.

Definitions

Contribution is a tangible product created by individuals that help advance an Open Source Software project. Examples of contributions include: programming, bug fixes, issue reports, feature suggestions, and documentation. Open Source Software is “software that can be freely used, changed, and shared (in modified or unmodified form) by anyone” (http://opensource.org/) and is distributed under a license approved by the Open Source Initiative, e.g. one of the licenses found here. A Project—specifically, an Open Source Software project—includes the entirety of collaborative activity, such as planning, discussion, design, documentation, and programming, that furthers the development of a piece of Open Source Software. Software refers to computer programs, or any set of instructions intended to be executed by a machine, including (but not limited to) executable files, libraries, and scripts. USE OPEN SOURCE SOFTWARE WHEN APPLICABLE The UNTL supports using Free and Open Source Software for its business operations whenever open source solutions meet business needs.

Being a Good Person

  • Be welcoming and open-minded - Other collaborators may not have the same experience level or background as you, but that doesn’t mean they don’t have good ideas to contribute. We encourage you to be welcoming to new collaborators and those just getting started.
  • Respect each other. Nothing sabotages healthy conversation like rudeness. Be civil and professional, and don’t post anything that a reasonable person would consider offensive, abusive, or hate speech. Don’t harass or grief anyone. Treat each other with dignity and consideration in all interactions.
  • You may wish to respond to something by disagreeing with it. That’s fine. But remember to criticize ideas, not people. Avoid name-calling, ad hominem attacks, responding to a post’s tone instead of its actual content, and knee-jerk contradiction. Instead, provide reasoned counter-arguments that improve the conversation.
  • Communicate with empathy - Disagreements or differences of opinion are a fact of life. Being part of a community means interacting with people from a variety of backgrounds and perspectives, many of which may not be your own. If you disagree with someone, try to understand and share their feelings before you address them. This will promote a respectful and friendly atmosphere where people feel comfortable asking questions, participating in discussions, and making contributions.
  • Be clear and stay on topic - People use GitHub to get work done and to be more productive. Off-topic comments are a distraction (sometimes welcome, but usually not) from getting work done and being productive. Staying on topic helps produce positive and productive discussions.

Contribute to Existing Projects

Suitable projects should have a clearly documented license approved by the Open Source Initiative. Contributors should ensure that the level of contribution made to an external project is adequately credited within the project’s documentation.

Create and Sustain Open Source Projects

Software created in-house may be released under an Open Source License approved by the Open Source Initiative when possible. All software released by the Project-Lernaean will include current contact information for the maintaining person, unit, or other entity, and a license statement. The MIT License (see below) is recommended. Open Source Software projects should use a public version control repository to manage the software when possible. A hosting service such as GitHub or Gitea is recommended.

Abide By Best Practics for Open Source Development

The author of, or contributor to, an Open Source Software project will adhere to common codes of conduct within shared version control repositories and will address issues and other communications with the public in an timely, professional manner. If there are situations that are not covered by this policy or if there are questions about the policy in general, please contact the us on IRC.

SUGGESTED MIT LICENSE TEMPLATE

MIT License

Copyright (c) 2021 Project Lernaean

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.