Stream: JIRA/Confluence
Topic: Backlog of PRs
Mark Kramer (Nov 18 2021 at 18:01):
There is a backlog of pull requests on https://github.com/HL7/JIRA-Spec-Artifacts. Can one of two things happen? (1) Someone with write privilege does the merges, or (2) Someone with power extends write privilege to folks like me developing IGs (at least to the /xml directory, if that is possible to limit). @Lloyd McKenzie @Joshua Procious ?
Lloyd McKenzie (Nov 18 2021 at 21:42):
@Mark Kramer. Apologies. Somehow I accidentally 'ignored' the project and wasn't receiving pull request notifications. Now rectified and working my way through the backlog.
Mark Kramer (Nov 18 2021 at 21:44):
Hi Lloyd, you don't have to apologize, but you should learn to delegate.
Lloyd McKenzie (Nov 18 2021 at 21:48):
Right now, @Joshua Procious and @Grahame Grieve can both do it. But I'm most familiar so they usually leave it to me unless someone complains or I tell them I'm gonna be gone.
Mark Kramer (Nov 19 2021 at 14:23):
It looks like it is possible to allow wider access to /xml folder without opening up the entire repo, using modules: https://stackoverflow.com/questions/40567468/give-permissions-on-project-folder-in-github
Josh Mandel (Nov 19 2021 at 14:28):
Codeowners file should work for us too, for this open source project (working with git submodules is challenging for folks who need to come up to speed -- and I say that said somebody who thinks that working with git is generally pretty straightforward)
Josh Mandel (Nov 19 2021 at 14:28):
I guess the question is what does the intended policy look like, who can change what with what review?
Lloyd McKenzie (Nov 19 2021 at 15:48):
Current process has two objectives:
- make sure we don't break Jira (duplicate names, changing keys)
- secondary review to make sure that on a quick glance, what's in the file makes sense/seems reasonable (e.g. that we're keeping keys the same during a rename)
Last updated: Apr 12 2022 at 19:14 UTC
