Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to organize Monthly Milestone records #931

Closed
bajtos opened this issue Jan 30, 2018 · 1 comment
Closed

How to organize Monthly Milestone records #931

bajtos opened this issue Jan 30, 2018 · 1 comment

Comments

@bajtos
Copy link
Member

bajtos commented Jan 30, 2018

In #927, @kjdelisle left a side note:

I also think we should abandon the "Monthly Milestone" label, and actually use the milestone feature to track tasks related to the goals instead

IMO, we need to keep in mind the user experience of casual visitors to our project, who don't have ZenHub extension installed. Here are few of the stories/tasks that I'd like to keep easy to do:

  • I would like a quick way of finding all Monthly Milestones
  • As a user wanting to learn about the current plans of LoopBack project, I'd like an easy way how to find the current milestone in progress, possibly also the next few milestones (the next month, etc.)
  • For each milestone, I'd like to read a high-level overview explaining what are the goals.
  • For each milestone, I'd like to see which user stories (GitHub issues, probably pull requests too?) are part of this milestone, and what is their status (planned, in progress, done). I don't want to clutter by browser with any extensions like ZenHub.

A requirement for both us and the community is to have a place where to comment on and discuss each milestone in the asynchronous way. (Right now, we are posting comments to Monthly Milestone issue.)

Another possible limitation to consider: AFAIK, each issue/pull-request can be assigned to a single milestone only on GitHub. This means we cannot assign a single story to both the monthly milestone and the sprint milestone it belongs to.

I agree manual updates of Monthly Milestone issues is time consuming and easy to forget and I am happy to switch to a better solution. However, if we want to keep our open-source project healthy, then we must prioritize user & community experience over the convenience of us, full-time developers.

@bajtos
Copy link
Member Author

bajtos commented Jan 30, 2018

Closing as a duplicate #930.

@bajtos bajtos closed this as completed Jan 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant