Issues
The traditional project management in Github is done using issue and pull request, which is not the focus of this article, and is not to be described in detail. But there are some features that need to be mentioned:
- Tag: Each issue can add different tags, can be used to mark the type of issue and issue processing progress;
- MileStone: Each issue belongs to only one MileStone, which shows the progress of the issue processing.
Projects Overview
This is a new feature of GitHub September 2016:
Project provides a real ability to manage issue, whereas traditional tag methods can only manage classifications in a manual way (such as q&a,bug,duplicate,feature these tags??). ), or manually manage issue progress (need test, in progress, wait approval, and so on).
Before we start discussing this, however, it is necessary to discuss the Kanban method first.
Kanban (Kanban) what is Kanban?
Kanban management, originating from Toyota's production model, refers to the tools to control on-site production processes in order to achieve a timely production (JIT) approach. The pull-type production system in a timely way can shorten the information flow and make the material flow smoothly in the production process by means of quantitative and fixed loading containers.
For more information, see the wiki.
If you still don't understand, here are a few examples of Kanban:
Kanbanflow & Trello
Kanbanflow
Trello
As can be seen, the so-called Kanban, is a piece of wood into a few columns, and then put a different content on each column card. These columns on the board are generally sequential, and the cards can be moved between different columns to indicate their state.
The above two examples, Kanban is not for software engineering, their market is also a general enterprise (such as Toyota).
Zenhub & Github Projects
The following two examples are optimized for software development and, to be precise, they are all adapted to Github.
Zenhub
Github Projects
Zenhub is a browser plugin that takes Github's issues as a card, Kanban in the form of issue, and offers a less-than-good Epic feature, while also having TODO management for individuals.
And Github's recent Project not only uses issues as a card, but also the note (three on the left), so we don't have to create a new issues to record the possible requirements on the Kanban board or record the problem on a personal TODO list.
Github Projects
A warehouse can contain multiple items; Initially, this setting puzzled me until it was used to understand that a code warehouse usually has a lot of things to do, such as:
- Develop route map
- Add a new feature
- Publish a new version
Therefore, we can create a project for each of these things, because there is no Epic-like mechanism in Github, so it is useful to use different project.
As you can see, some of the features of the original tag, such as tag processing progress, can be replaced by Kanbans after Project Kanban. The Note provided by Github Project can be converted to issue when needed:
At the same time, Kanban can include not only issue and note, but also pull request.
Github finally has a more reliable project management tool, and the open source project has a better tool. Sprinkle O (^▽^) o
Wish me to finish my first Open source project (IMAP Server) myself at an early date.
GitHub New project calendar mode