[INFRA-43] Reorganize projects made old scheme Created: 28/Jul/16  Updated: 23/Jun/17  Resolved: 23/Jun/17

Status: Done
Project: Software Development Infrastructure
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Epic Priority: Major
Reporter: shimono Assignee: shimono
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File 201610jira.rst    
Issue Links:
Blocks
blocks INFRA-49 Prepare for request of OSS license fo... Done
Epic Name: REORG1607
Reviewers: swinbank

 Description   

Some of existing projects are created without organizational discussions, and are not used much now.
On migration at 2016/06, we deleted all ICS projects, and made this instance to track DRP,ETS,SPT packages which has closer relationships than to ICS, and are assumed to be developed in a similar development management and strategy. Although some definitions or management are used for each group, most of organizational documentations could be shared among three software packages. Therefore, we could be fine with one JIRA project for management or infrastructural discussions.

I'd propose:

  • merge CDS and IPMU project into INFRA for general project management
  • rename INFRA as "Development Infrastructure" from current "DRP software Infrastructure"
  • rename "SCAM" as "INSTRM" to track all ICS tickets
  • add "SURVEY" for all survey planning/tracking tickets
  • Add(ed) "FIBERALLOC" for ETS (fiber allocation) tickets

PR on documentation is at https://github.com/Subaru-PFS/doc/pull/4

 Comments   
Comment by rhl [ 28/Jul/16 ]

I added some comments to some of the tickets, but they probably really belong here.

While I think that some Jira cleanup makes sense, I'd like a plan for how we are going to manage the software before we restructure things. In particular, how are we tracking work? Are we using Jira only for bug-reports, or are we using it to track work? Is there a WBS, and how does it align with the Jira projects? Is there a list of all the work that we need to track?

Shimono-san: could you point us to the overall management plan that illuminates these points before we start cleaning up Jira (I'm sure I've seen all the pieces, but I can't find a top-level summary)

Comment by shimono [ 28/Jul/16 ]

let me back to the Project office to secure the plan.....
Personally, plan on development (esp. integration b/w JIRA and git repository) is in a sense, and easy to push into partners.

Comment by shimono [ 21/Oct/16 ]

Updated plan as attachment 201610jira.rst.
I'll add some text for existing and add branch to doc repo, shortly.

Comment by shimono [ 23/Jun/17 ]

all referred tickets marked as closed!

Generated at Sat Feb 10 16:48:49 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.