Skip to content

Latest commit

 

History

History
33 lines (21 loc) · 1.01 KB

CONTRIBUTING.md

File metadata and controls

33 lines (21 loc) · 1.01 KB

How to contribute

Luvit is Apache 2.0 licensed and accepts contributions via GitHub pull requests. This document outlines some of the conventions on commit message formatting, contact points for developers, and other resources to help get contributions into Luvit.

Email and chat

  • Email: luvit
  • IRC: #luvit IRC channel on freenode.org

Getting started

  • Fork the repository on GitHub
  • Read the README.md for build instructions

Reporting bugs and creating issues

Reporting bugs is one of the best ways to contribute.

Contribution flow

This is a rough outline of what a contributor's workflow looks like:

  • Create a topic branch from where to base the contribution. This is usually master.
  • Make commits of logical units.
  • Push changes in a topic branch to a personal fork of the repository.
  • Submit a pull request to luvit/luvit.
  • The PR must receive a LGTM or +1 from one maintainer.

Thanks for contributing!