(revise page with correct repo links and better text)
m (Adamwill moved page QA:Taskotron contribution guide to Taskotron contribution guide: Taskotron page isn't in QA namespace, so move this out, I guess.)
Revision as of 02:59, 10 February 2017
The repositories for the tasks developed alongside Taskotron itself are in the Fedora QA project on Bitbucket:
If you need team membership, send a message out to qa-devel@ or file a ticket in QA/Phabricator against the infrastructure project.
Issue and code change tracking
Tracking of issues and code changes for all Taskotron projects happens in the Fedora QA instance of Phabricator. Please see this section of the page for general instructions on submitting issues and 'diffs' in Phabricator.
There are some specific considerations for contributing to Taskotron components.
Gitflow is a git branching strategy that has been used successfully in the blocker tracking app and several Fedora infra apps.
Taskotron components usually have test suites built on Pytest. Ensure you have
installed to run the tests.
As we are using code linting, you will also need the flake8 tool - runto install it.
General Thoughts and conventions
- Be smart
- All code going into develop branches MUST be reviewed
- All code should have good unit tests where appropriate
- When in doubt, ask