Re: [ohdf] Motion to request a GitHub TC repository for Specification Wo

I seconded the motion but I would recommend “this” repo be the “admin” repo (meeting minutes, etc) and that you make separate repo’s for each future work product.

So for example someone could contribute “OHDC Schema” to this repo (maybe in an “incoming” direcgory) with a PR just to get over the CLA requirements, but after looking at the contrib people think “this rates being a CSD”, then I think a new repo should be made just for that CSD. One repo/work product makes the administrivia easier, makes it easier for people to find what then want (albeit I also think the home page of the admin repo should have link to everything with explanation of what is where) and only work on what they want, and ties ‘github releases’ to ‘spec versions’ in a more logical way (you can do it if multiple specs in one repo, but it’s very confusing, at least to me).

Duncan Sparrell

sFractal Consulting

iPhone, iTypo, iApologize

I welcome VSRE emails. Learn more at http://vsre.info/

From: ohdf@lists.oasis-open.org <ohdf@lists.oasis-open.org> on behalf of Stefan Hagen <stefan@hagen.link>
Date: Friday, April 14, 2023 at 3:43 PM
To: ohdf@lists.oasis-open.org <ohdf@lists.oasis-open.org>
Cc: Mike Fraser <Mike.Fraser@sophos.com>, Aaron L Lippold <alippold@mitre.org>
Subject: [ohdf] Motion to request a GitHub TC repository for Specification Work Products

Dear TC members,

I hereby submit the following motion and request that if seconded and no objection received per this list

before one week has passed on 2023-04-21 20:00 UTC to automatically carry.

Note: For seconding this motion it is sufficient to reply to this message on the TC list

and add the word "second" or "seconded".

The Secretary or Co-Chairs usually state the result per mail to this list when the period has passed.

I, Stefan Hagen, hereby move that the TC requests from OASIS administration the creation

of the Github repository https://github.com/oasis-tcs/ohdf to manage spec related work products like

schema files, specification prose, test files, minutes of meeting, issues, peer reviews, IANA requests and others.

I further move, that the initial maintainers shall be Aaron Lippold and Stefan Hagen.

When this motion carries, the secretary will submit the relevant form such that OASIS

administration can create the repository and enable the maintainers access.

PS: We can always add or change maintainers later easily.

All the best,

Stefan.

Stefan Hagen, Emmetten, Nidwalden, Switzerland.

orcid: https://orcid.org/0000-0003-4206-892X

read: https://stefan-hagen.website

write: stefan@hagen.digital

ohdf message