Attending
Time:12:00PM PDT/03:00PM EDT - 01:00PM PDT/04:00PM EDT
Zoom: https://princeton.zoom.us/j/281265700
Participants
- tamsin woo (UC Santa Barbara)
- Trey Pendragon (Princeton University Library)
- Noah Botimer (U. Michigan)
- bess (Data Curation Experts)
- Mark Bussey (Data Curation Experts)
- James Griffin (Princeton University Library)
Agenda
- ZenHub/HuBoard Review
- Sprint Planning
Notes
ZenHub Review
Has some cool integration with the Chrome Extension
HuBoard and ZenHub are pretty equivalent in terms of functionality
Two factors which were noticed:
Chrome Extension and integration with GitHub Issues
Some concern over security and the interference when working with GitHub
Other aspect with ZenHub: A repository is attached to one board
Difficult to determine if there was some way around this
Example: With enough activity on active-fedora, this WG would need to detach their project from their board
This would be problematic given that there might be ongoing, concurrent work with other repositories
HuBoard
Better security posture
Better permissions management regarding what is requested from GitHub for the app.
Does support multiple repositories for any given board
ZenHub UI was slightly better in terms of experience
Does use labels to synchronize, but these are weird labels
Numbers at the beginning of labels are used to control the flow of the tickets
Have to be comfortable creating labels for the tickets on all of the projects which we have
Three Options
- Use HuBoard and accept the strange labels
- Pros
- One spot to see all of the issues
- Does not stop other parties from working on issues
- Cons
- Weird labels
- Pros
- Use ZenHub
- When we due sprint planning, create mirror issues in the maintenance repository linking to the issues we wish to close
- Pros
- ZenHub has some better PR association functionality (supports blocking)
- Cons
- We need to create and maintain mirror issues
- Create a Github Project board in the Samvera Organization
- Should have access to the repositories we need to add
- Adding a repository alone still requires that one manually add tickets to columns
- Can request Product Owners to add issues to a Project
- Appeared that there was a 5 repository limit for a Project
- We might also avoid linking to repositories, and just populating the Projects with issues
Samvera-Labs
We don't need to be concerned with this as a separate Organization
If we needed to promote a component, we could just create mirror issues
Or, we could simply maintain two separate boards
Testing Promotion
Should try and promote samvera-labs/maintenance to samvera
WG should add a license to this repository just for good measure
We will assert that this is an administrative repository, should express this to the community
Mark: Fine with writing up a justification asserting that the repository meets the promotion criteria
Noah: Part of our role here is to be sensitive to process issues
Tom: Adds an apache2 license to samvera-labs/maintenance
Samvera is not a
Trey: In this case, GitHub Projects to be acceptable for this WG
Trey: Migrating GitHub issues to a Projects
Do we want to preserve the custom columns?
Yes
We're going to need to associate repositories with issues, and scroll through search results for tickets
Can search in Projects for non-linked repositories
What is the purpose of linking a repository?
Automation: creating a pull request which closes an issue in a linked project...does it automatically associate?
No
Also note that, without linking to the project, the issue does not show up
Pull requests do not get automatically linked when the comment specifies the issue it closes
It needs to be manually linked to pull requests
When pull requests are merged, we need to also manually close issues
Action Items:
Tom: Promote samvera-labs/maintenance
Mark: Link Repositories to the Maintenance GitHub Project
Trey: Migrate issues from Waffle to the GitHub Project
May 6th: Sprint Begins
Meeting adjourned at 12:39 PDT/15:39 EDT