[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: TC repository for non-normative artifacts
Gary provided the attached proposal template for an open repository but, unfortunately, I dropped the ball on the next steps. As a TC, we need to:
Unfortunately, it will now be September before we complete #3. In the interim, please respond to #1 and #2. __ Jim Cabral 502 509-4532 From: James E Cabral Gary, Thanks for drafting this proposal. I’ve suggested a few minor changes in the attached version. I’m also willing to be one of the maintainers and have experience with Github. __ From: Graham, Gary Jim, Attached is a first draft proposal for an open repository. Please feel free to comment, edit, revise, etc. The TC will need to decide which of the six license options to employ. No recommendation at this time. Also, we will need to identify one or more ECF TC members to list as initial maintainers. I am happy to help, but do not have enough GitHub experience at this time. Gary Graham From: legalxml-courtfiling@lists.oasis-open.org <legalxml-courtfiling@lists.oasis-open.org>
On Behalf Of James E Cabral CAUTION: This email originated from outside of the organization. Do not click links or open
attachments unless you recognize the sender and know the content is safe. Thanks Gary. No rush. __ From:
legalxml-courtfiling@lists.oasis-open.org <legalxml-courtfiling@lists.oasis-open.org>
on behalf of Graham, Gary <GGraham@courts.az.gov> Jim,
Yes, I will work on drafting the proposal. I may not have it ready until after Christmas. I would like to first get up to speed on Open Repository. I also think it would be appropriate to give some thought on criteria and procedures for TC endorsement of submittals. Of the two approaches suggested by Chet, I am thinking the second would be preferred, but I need to learn about Open Repository first.
Gary Graham
From:
legalxml-courtfiling@lists.oasis-open.org <legalxml-courtfiling@lists.oasis-open.org>
On Behalf Of James E Cabral
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Thank you Chet. That sounds like a great option for our needs.
To move forward with this approach, we need someone to draft a proposal for creation on an open repository and then vote as a committee to approve the proposal. Since our next meeting is in March, that will likely be an online ballot.
Gary, since it was your idea, would you like to draft the proposal? I’m willing to assist as needed.
__
From: Chet Ensign
Jim, this sounds like a perfect case for an Open Repository. The Open Repo program, as you know, let's TC's sponsor open source projects that anyone can contribute to.
I can see how you could define and set up an ECF Extensions Open Repo where people could fork the repo, add their extensions, then issue pull requests. You could either use the pull request as the filtering point - that is, the TC wouldn't accept it unless it conformed with the provided guidance so that any extensions on the main branch would be deemed usable by others. Or, alternatively, you could set a low bar at that point and have a second repo where you hosted those that passed TC review.
The Open Repo program is described in https://www.oasis-open.org/resources/open-repositories/
Let me know if this helps.
/chet
On Wed, Dec 11, 2019 at 10:58 AM James E Cabral <jec@mtgmc.com> wrote:
--
Chet Ensign Chief Technical Community Steward
|
Attachment:
OASIS ECF TC Repository Proposal - Draft jec.docx
Description: OASIS ECF TC Repository Proposal - Draft jec.docx
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]