2022-01-11 Technical WG Agenda and Notes

MP: Texas Conference on Digital Libraries - https://www.tdl.org/tdl-events/tcdl/2022-tcdl/
MP: Had a request to be a part of a panel on PIDs and it might be a great chance to introduce the work of the ARK Alliance and also update on
progress with different things.  MP is involved with this.
JK: Are people still attending virtual conferences?
GJ: I've stopped attending virtual conferences since I just end up working and trying to listen at the same time
CM: why try to work and attend at the same time?
GJ: seems like a good idea to try, but then its hard to avoid the flood of usual activity when it actually happens
KH: my experience is similar; I just attend the panel I'm most interested in; I tried a virtual meeting room for socializing but it was a kind of disaster
KH: there is an iPres (Glasgow) deadline in March

new GH "arka" user, new repo for spec

freshly rebuilt with GH actions working for CI and draft submission/publication

process for contributions (KH)

passwords with keybase?

KH: some processes we follow for collaborative software editing that permits a review step before fulling accepting a change https://docs.google.com/document/d/1ZXASVBocL7H3XjK4MyLfKZ3CTycVKJ4NnYpCy-RnEF4/edit?usp=sharing
ACTION: note which of the many files is the one of interest (eg, just the main xml file
JK: what kind of merge flavor should we use? merge commit, squash merge, or rebase merge?
CM, GJ, AA: no opinion
TC: we generally used to Merge Commit, but we also see rebase and merge
TC, KH: don't do squash merge
ACTION: document consensus on Merge Commit flavor
JK: should we use Keybase to share passwords?
TC: have you tried converting arka into an "organization"?
AA: yes, good idea
KH: here are some instructions https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization
ACTION: try setting this up
TC: Here is a quick in-process list of practices we use that may help us here; it’s pretty terse:

Use proper local and remote branches.
Keep your changes small
Small changes that fail fast are easier to resolve.
Focus on a Single Feature.
Not to large of a PR.  Keep it under xxx lines.
Take advantage of FS CD pipelines.
Keep up to date
Rebase, not merge, with origin master when it changes
Use diffs when needed.
Be aware of a squash.
Pull requests should be short lived
Follow coding practices that allow PRs to merge faster.
Break your PR into small commits that tell a story.
Do not wait to review existing PRs.

TC: in the end we might prefer rebase merge flavor of commit
JK: probably not a big deal to change how we do it in the future

New arkspec (32)
   diffs v30->v32

via GH-pages