You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
In #927, @kjdelisle left a side note:
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:
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.
The text was updated successfully, but these errors were encountered: