Re: [legalcitem] GitHub etc.(long post...sorry)

[Brian Carver <brian.carver@documentengineeringservices.com>]

I would strongly support making the github repo public and renaming it
or otherwise distinguishing it from the OASIS work.

Really, I'd support anything that enables Frank to keep doing the great
work he's been doing since we created the github repo. It's a tool that
is actually allowing us to get things done and to discuss them, so we
shouldn't do anything that would tie our hands behind our backs.

I continue to find the conference call times difficult to make and
asynchronous communication via lists and github issues is just a much
better way for me to follow what's going on and to contribute.

Brian

On 11/19/2014 01:40 PM, John Quentin Heywood wrote:
> Hi Folks,
> 
> Couple of things:
> 
> 1. The GitHub repository was discussed in the main TC meeting this
> morning, as was other off-site tools such as GoogleDocs. Ken pointed us
> to the OASIS Technical Committee (TC) Process document at 
> 
> https://www.oasis-open.org/policies-guidelines/tc-process
> 
> particularly Section 2.8 on TC Visability
> <https://www.oasis-open.org/policies-guidelines/tc-process#visibility>,
> which says:
>> The official copies of all resources of the TC and its associated
>> Subcommittees, including web pages, documents, email lists and any
>> other records of discussions, must be located only on facilities
>> designated by OASIS. TCs and SCs may not conduct official business or
>> technical discussions, store documents, or host web pages on servers
>> or systems not designated by OASIS. All web pages, documents, ballot
>> results and email archives of all TCs and SCs shall be publicly visible.
> Both GitHub and GoogleDocs would seem to be in conflict with this,
> although as it was pointed out in the call, at least GitHub is an open
> standard, which can't be said about GoogleDocs. Many folks on the call
> were less than happy with the OASIS Wiki, which would seem to be the
> only official collaboration tool available. It was suggested that
> getting the work done was important, so perhaps we could use private
> tools such as GitHub as long as we put the official documents on the
> SC's public document repository, which would be here:
> 
> https://www.oasis-open.org/committees/documents.php?wg_abbrev=legalcitem-courts
> 
> and conduct our technical discussions on this listserv. This seems
> reasonable to me.
> 
> Now Frank has been doing some wonderful work on GitHub, merging the
> reporter data from CourtListener and the CSL project with what we have
> been doing and making it truly usable for us and other projects (like
> the Free Law Project). He thinks we should open the repository up so
> that others can collaborate. I agree, and I think this would dovetail
> nicely with the OASIS rules. If the work being done on the GitHub
> repository is no longer officially OASIS work, we don't have to worry
> about their rules. The GitHub repository becomes a tool for the whole
> free law community, that we in the OASIS SC can use as a resource for
> our work. We could rename it to something like the "Court Citation
> Project" or even something less lame than that. How do folks feel about
> this?
> 
> For some examples of what Frank has done, look at:
> 
> http://jqheywood.github.io/CourtsSC/index.html
> 
> and
> 
> http://jqheywood.github.io/CourtsSC/states.html
> 
> 
> 2. In response to the discussion in our last SC meeting, and never being
> afraid to play the fool (or, if you ask my kids, BE the fool, but I
> digress), I asked the assembled TC what exactly a use case was, and what
> are we supposed to be producing. Everybody seemed happy that I had
> asked. Someone (I'm not sure who) described it thusly: HTML5 is the
> standard, a web page demonstrating all the different parts of HTML5 is
> the use case. John J. reminded us all that the SCs should not get lost
> in the weeds of detail, as he has seen other projects flounder because
> of it. We should be looking for the common things in these citations and
> writing them up. I think we may be close to ready for this in the US
> context very soon.
> 
> Well, time to go home and make my eldest his birthday dinner (he turned
> 17 today),
> 
> John
> 
> -- 
> John Quentin Heywood
> heywood@american.edu
>