Rettningslinjer for bidrag

Advarsel

This documentation refers to an outdated SpongeAPI version and is no longer actively maintained. While the code examples still work for that API version, the policies, guidelines, and some links may have changed. Please refer to the latest version of the documentation for those.

There will always be a need for developers to help us improve SpongeAPI. There is no such thing as a perfect project and things can always be improved. If you are a developer and are interested in helping then please do not hesitate. Just make sure you follow our guidelines.

Obs

Developers who show determination and consistency in their contributions to the project may be invited to join the Sponge Staff by Team Leaders, at their discretion. There is no formal application process. Please don’t ask to be staff, we’ll ask you.

Generelle steg

  1. Setup your workspace as described in Å gjøre seg klar til utvikling.
  2. Make sure you’re familiar with Git and GitHub. If your knowledge needs a refresh, take a look here: Hvordan bruke Git(Hub)
  3. Check for existing issues in the SpongeAPI, SpongeCommon, SpongeForge, SpongeVanilla, and SpongeDocs repositories. There is possibly someone else already working on the same thing. You can also check issues marked with «help wanted» for existing issues we need your help with.

Obs

Please don’t submit pull request for small changes under 20 lines. Instead, join #sponge on IRC (irc.esper.net) or join #spongedev on IRC (irc.esper.net) and we’ll change it together with the other smaller changes.

  1. Dersom problemet krever en større endring kan det hende du vil sende inn problemene uten de nødvendige endringene først, slik at vi kan bekrefte at det er et problem og vet at du jobber med å fikse det. Du burde også lage en WIP (work in progress, i arbeid) pull request med [WIP] i tittelen tidlig, så vi kan begynne å se gjennom koden tidlig.
  2. Forgren prosjektet, klon det og gjør dine endringer i en ny gren.
  3. Test endringene dine (sjekk at det kompilerer!), begå/commit endringen og dytt den til din forgrening.
  4. Send inn PR-en med en kort oppsummering av hva du har endret, samt hvorfor det bør endres på den måten.
  5. Om du gjør andre endringer, dytt nye endringer til din gren. Ikke mos sammen endringene dine, det gjør det ekstremt vanskelig å se hva du har endret sammenlignet med den forrige versjonen av din PR.
  6. Make sure your PR is rebased to the latest changes of the branch you’re intending to merge it into. If you need help rebasing it, just ask!

Tips

If you’re unsure which branch you should base your work on, read about our Versjonssystem og oppsett av grener i kodeoppbevaringsstedet before submitting your PR.