Status tagging to github projects
Ernie Hsiung
Public
Seen by 413
Credit where credit is due: @joelquilesbaker brought this up and it deserves attention:
> I also think we should tag our github projects with [unmaintained] and another tag similar to "looking for contributors" or whatever it is the project needs to keep moving forward. The project with most activity and most recently updated is the restaurant inspections one. Besides that, there's a lot of repos/projects that seem to have no activity and I don't have any idea of what those projects are/do.
Poll Created Sat 17 Dec 2016 5:43AM
Let's go through the Code for Miami Github repo and tag our github projects with [unmaintained] and another tag similar to "looking for contributors" Closed Tue 20 Dec 2016 5:03AM
We will add github tag statuses to all CFM repos.
See the thread for more context, but the goal is for folks to have more visibility on what projects are active and which are not.
Results
| Results | Option | % of points | Voters | |
|---|---|---|---|---|
|
|
Agree | 100.0% | 4 |
|
| Abstain | 0.0% | 0 | ||
| Disagree | 0.0% | 0 | ||
| Block | 0.0% | 0 | ||
| Undecided | 0% | 32 |
|
4 of 36 people have participated (11%)
Ernie Hsiung
Sat 17 Dec 2016 5:44AM
I'm all for it. [inactive] and [looking for contributors]? Or maybe [active], since the assumption is that an active project will always look for contributors?
Poll Created Tue 20 Dec 2016 3:58PM
What specific CFM github status tags for projects should we use? Closed Fri 23 Dec 2016 3:09PM
This is a proposal to use status tags from shields.io to give a status to each proposal, to be added to the github repo's README.md file.
- this could also refer to live documentation github repos
If you disagree, an alternative option would be useful. Should we include a separate badge for maintainers?
Results
| Results | Option | % of points | Voters | |
|---|---|---|---|---|
|
|
Agree | 100.0% | 2 |
|
| Abstain | 0.0% | 0 | ||
| Disagree | 0.0% | 0 | ||
| Block | 0.0% | 0 | ||
| Undecided | 0% | 34 |
|
2 of 36 people have participated (5%)
Poll Created Sat 14 Jan 2017 9:14PM
Proposal to add an emoji next to the github repo description to easily indicate status Closed Tue 17 Jan 2017 8:02PM
:zap: :construction: for live projects being worked on (under construction)
:zap: :sleeping: for live projects that have been discontinued (not being worked on)
And how about :on: :construction: for things in progress that aren't up yet?
And :raised_hand: :x: for things that aren't live and aren't being worked on
Per conversation on the #committee-tech slack channel, this is a proposal to add an emoji to each of the Code for Miami project titles to indicate if a project is inactive, not maintained, in development or live.
As an example, take a look at this repo: https://github.com/Code-for-Miami/mia-councilmatic
A "yes" vote indicates we should decide on emojis for all the different statuses, go through each of the github repos on CFM and add statuses for each. A "no" vote indicates to keep things as is.
Results
| Results | Option | % of points | Voters | |
|---|---|---|---|---|
|
|
Agree | 100.0% | 6 |
|
| Abstain | 0.0% | 0 | ||
| Disagree | 0.0% | 0 | ||
| Block | 0.0% | 0 | ||
| Undecided | 0% | 30 |
|
6 of 36 people have participated (16%)
Yami Medina
Mon 16 Jan 2017 7:15PM
Red and green is probably the simplest.
Ernie Hsiung Tue 17 Jan 2017 2:10PM
Hey @yamimedina - there is no green circle (!) but they have the :white-checkmark: emoji. You can see a full list - http://www.webpagefx.com/tools/emoji-cheat-sheet/
Pierre Vincent Cabral Wed 18 Jan 2017 3:35AM
👍
Chris Scott Fri 27 Jan 2017 6:36PM
For things in progress that aren't up yet, it can just be the :construction:.
Things that aren't are live or being worked on are essentially just dead? :skull:
Joel Quiles Baker · Thu 15 Dec 2016 2:05PM
Should be something simple accomplish. I guess main members and some others (Chris, dev lead) would know about the history of a lot of these projects. It's a matter of navigating to the repo and being able to know 1) unmaintained/deprecated? (so others don't go about using something outdated or having it as a dependency and 2) looking for contributors, so a dev knows he can dig deeper, clone/fork, look at the outstanding issues and contribute. 1 and 2 are not mutually exclusive. I know that every project, in theory, is looking for maintainers. But there's some priority to some- the ones that are the most active or on the verge of its maintainer not being able to continue working on it.