Skip to content

Latest commit

 

History

History
41 lines (24 loc) · 1.81 KB

contributing.md

File metadata and controls

41 lines (24 loc) · 1.81 KB

Contributing

Workflow

Repository

The project uses the Forking Workflow with Pull Requests. This is experimental for the time being, but is expected to help towards the goal of building a complete documentation and a well-organized repository for future TEDxNTUA websites.

In short:

  1. Fork the upstream repository and clone it to your local machine.
  2. Follow the installation instructions.
  3. Create a branch for the feature you want to work on.
  4. When finished, push the feature branch to your repository.
  5. Create a pull request on the upstream repo and describe the changes you've made.
  6. Participate in discussion between the team members on whether the feature needs improvements or should be merged.
  7. Repeat!

For a more detailed guide on how to stay in sync with the upstream and avoid conflicts, read this.

Development

English should be used for variable names, docstrings, documentation etc for uniformity.

Pylint is used to enforce proper guidelines:

  1. PEP 8 compliance.
  2. Docstrings everywhere :)

RECOMMENDED: To enforce Pylint checking right before each commit, then copy the etc/pre-commit file to .git/hooks/pre-commit. This uses the git-pylint-commit-hook module that is included in the dev-dependencies.

Rules are meant to be broken though, so if you disagree when Pylint complains about something, feel free to edit the pylintrc configuration accordingly.

Testing

raise NotImplemented

Contribute what?

Check the running projects to find things to work on.