Contribution Guide

So you want to get involved with MousePaw Media's open source development? Awesome! We've worked hard to make this process and smooth and simple as possible.

  1. Read through our Terms of Development , which you are agreeing to by contributing code to MousePaw Media. This is to save everyone a few dozen headaches; it assures you that we'll always be open source, and it enables us to re-license the code as necessary.
  2. Sign into our instance of Phabricator on DevNet using your GitHub credentials. This is where all of our development work takes place.
  3. Follow our handy guide to Code Contributions (also hosted on DevNet), which will walk you through the process of setting up your development environment and checking out a repository.
  4. The best way to connect with us is through Phabricator, but depending on the day and time, you may be able to find us on our Freenode IRC chatroom.

FAQs: Contributing

(Click a question to view the answer.)

Why do I need a GitHub account?

GitHub is fairly ubiquitous among programmers; the majority of developers have accounts there. GitHub accounts are also more frequently legitimate - developers rely on them to track and display their code contributions - which helps us ensure that the majority of people signing up for Phabricator are real people.

Why don't you accept GitHub pull requests?

We use Phabricator for all of our development work. We've found that the features of that platform fit our workflow better than GitHub does.

What are those weird ".arc[whatever]" files on your repositories?

Those allow Phabricator to interface with Git and do all sorts of neat code review stuff for us. You can safely ignore those - you will never need them.

What's with the Terms of Development?

That's to save everyone a few dozen headaches. If we realize later that we need to license a project under different terms, we don't want to try and track down a few hundred people.

Besides that, it simply states that your code is licensed to us under the MIT License, unless you select another non-restrictive open source license that is compatible with GPL.

Third, it holds us accountable - as long as we're using your code, the project you contributed to shall have an open-source license.

Why isn't the link to the Code Contributions guide working?

That guide is hosted on DevNet , which is only available during certain hours. See the DevNet page for more information.