opendev/infra-specs
Code Issues Proposed changes

Merge "Enumerate steps and options"

Browse Source
This commit is contained in:
Jenkins 2016-06-07 19:55:22 +00:00 committed by Gerrit Code Review
commit d98fc41e73
1 changed files with 10 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
specs/task-tracker.rst
View File

@ -131,14 +131,14 @@ Options
tracking tools. Combined with our inability to fully customize our own tracking tools. Combined with our inability to fully customize our own
Launchpad deployment that makes for a pretty unlikely option. Launchpad deployment that makes for a pretty unlikely option.
1. The second option is to migrate everyone to StoryBoard. Benefits: 2. The second option is to migrate everyone to StoryBoard. Benefits:
purpose-built tool aligned with OpenStack needs, API-first and static purpose-built tool aligned with OpenStack needs, API-first and static
webclient design, coded in Python in the OpenStack Way. Drawbacks: still webclient design, coded in Python in the OpenStack Way. Drawbacks: still
not mature, inferior UX (compared to other available solutions), missing not mature, inferior UX (compared to other available solutions), missing
key features (like proper ACLs to handle vulnerability work), requires a key features (like proper ACLs to handle vulnerability work), requires a
lot of maintenance/development investment from the OpenStack community. lot of maintenance/development investment from the OpenStack community.
1. The third option is to migrate everyone to Maniphest (Phabricator's 3. The third option is to migrate everyone to Maniphest (Phabricator's
task tracking component). Benefits: excellent UX, lots of features, active task tracking component). Benefits: excellent UX, lots of features, active
external maintenance. Drawbacks: partial API coverage (API-last design), external maintenance. Drawbacks: partial API coverage (API-last design),
model mismatch (no concept of stories affecting multiple projects) requiring model mismatch (no concept of stories affecting multiple projects) requiring
@ -237,11 +237,15 @@ Work Items
Phase 1: Phase 1:
1. Facilitator identifies feature stakeholders from the OpenStack community 1. Facilitator identifies feature stakeholders from the OpenStack community
1. Feature stakeholders identify remaining needed features
1. StoryBoard team and facilitator prioritize feature requests 2. Feature stakeholders identify remaining needed features
1. Technical Committee are asked to confirm the proposed plan sufficiently
3. StoryBoard team and facilitator prioritize feature requests
4. Technical Committee are asked to confirm the proposed plan sufficiently
addresses blockers for migration addresses blockers for migration
1. StoryBoard team (hopefully with new developer assistance from the extended
5. StoryBoard team (hopefully with new developer assistance from the extended
OpenStack community) implement identified features OpenStack community) implement identified features
Repositories Repositories