Contributing Guidelines We love improvements to our tools! There are a few key ways you can help us improve our projects:
Submitting Feedback, Requests, and Bugs Our process for submitting feedback, feature requests, and reporting bugs usually begins by discussion on our chat and, after initial clarification, through GitHub issues. Each project repository generally maintains its own set of issues:
http://wiki.ttxit.com/display/WIKIFT/questions/onboarding
Some projects have additional templates or sets of questions for each issue, which you will be prompted to fill out when creating one.
Issues that span multiple projects or are about coordinating how we work overall are in the Overview Issue Tracker.
To know how to label an issue, have a look to http://jira.ttxit.com/projects/WIKIFT
Submitting Code and Documentation Changes We still do not have project guidelines for all of the projects hosted in our GitHub Organization, which new repositories should follow during their creation.
Our process for accepting changes operates by Pull Request (PR) and has a few steps:
If you haven't submitted anything before, and you aren't (yet!) a member of our organization, fork and clone the repo:
$ git clone git@github.com:wikift/wikift.git Organization members should clone the upsteam repo, instead of working from a personal fork:
$ git clone git@github.com:wikift/wikift.git Create a new branch for the changes you want to work on. Choose a topic for your branch name that reflects the change:
$ git checkout -b Create or modify the files with your changes. If you want to show other people work that isn't ready to merge in, commit your changes then create a pull request (PR) with WIP or Work In Progress in the title.
https://github.com/wikift/wikift/pull/new/master Once your changes are ready for final review, commit your changes then modify or create your pull request (PR), assign as a reviewer or ping (using "@") a Lieutenant (someone able to merge in PRs) active on the project (all Lieutenants can be pinged via @wikift/wikift)
Allow others sufficient time for review and comments before merging. We make use of GitHub's review feature to comment in-line on PRs when possible. There may be some fixes or adjustments you'll have to make based on feedback.
Once you have integrated comments, or waited for feedback, a Lieutenant should merge your changes in!
These guidelines are based on Tools for Government Data Archiving's.
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。