OSLC Core and Domains TC meeting notes 20190404

["Jim Amsden" <jamsden@us.ibm.com>]

from
david honey to Everyone:    10:05  AM
https://www.oasis-open.org/apps/org/workgroup/oslc-core/message.php/201903/msg00018.html
from
James Amsden to Everyone:    10:06  AM
TRS
Configuration
Management
OSLC
Query
QM
Open
Project
ReSpec
changes for OP
from
david honey to Everyone:    10:06  AM
David
is scribe.
from
Andrew to Everyone:    10:06  AM
https://hackmd.io/nkBdXCbSTqmFo1Hs7wnMKQ
from
david honey to Everyone:    10:07  AM
Attendees:
Jim, Jad, David, Nick.
from
david honey to Everyone:    10:08  AM
Status
of Config Management and TRS specs.
from
david honey to Everyone:    10:09  AM
Nick:
In next week, separate the TRS spec into 2 documents - a normative spec,
and a use case document.
from
david honey to Everyone:    10:10  AM
Use
case document will be non-normative.
from
david honey to Everyone:    10:14  AM
Nick:
Config management - nothing new in last month or so.
from
david honey to Everyone:    10:18  AM
Bettere
to check in changes to current Github repo. It will be cloned to the open
projects Github in a few weeks time.
from
david honey to Everyone:    10:18  AM
Still
pending: RFC for the Configuration-Context header.
from
david honey to Everyone:    10:19  AM
Respec
for open projects. Some changes will be required.
from
david honey to Everyone:    10:21  AM
Nick
needs the OASIS list of status enum values. Currently, Respec uses a union
of OASIS and W3. The W3 ones need to be removed.
from
david honey to Everyone:    10:23  AM
Jim:
Believes the normative spec will be a Github URL that renders the source
into HTML with Respec.
from
david honey to Everyone:    10:26  AM
<Correction>
The URL that renders the spec is not a Github URL, but rather one that
redirects to Github.
from
Andrew to Everyone:    10:27  AM
https://github.com/oasis-tcs/oslc-core/wiki/!TC-work
from
Andrew to Everyone:    10:27  AM
All
spec draft links point to GitHack
from
david honey to Everyone:    10:28  AM
<Corrected>
Attendees: Jim, Jad, David, Nick, Andrew.
from
david honey to Everyone:    10:30  AM
Jim:
Doesn't see any need for Github (GH) pages.
from
david honey to Everyone:    10:31  AM
Example
of URL for Githack that renders spec: https://raw.githack.com/oasis-tcs/oslc-core/master/specs/oslc-core.html
from
david honey to Everyone:    10:33  AM
OSLC
Query and QM needs some editing for open projects.
from
david honey to Everyone:    10:34  AM
Respec
- links don't need rewriting because filenames will not change on publication.
from
david honey to Everyone:    10:35  AM
Nick:
We should have a well-defined process for labelling baselines in Github.
from
david honey to Everyone:    10:35  AM
Jim:
Suggests QM is done first.
from
david honey to Everyone:    10:38  AM
Would
be good to have a link to latest, latest published, and perhaps previous
published.
from
david honey to Everyone:    10:39  AM
Most
of the changes for Respec are template changes.
from
david honey to Everyone:    10:39  AM
Open
projects status....viable, have governing body and budget.
from
david honey to Everyone:    10:44  AM
IBM
Open source steering committing, meeting on 9th to assess proposal. Dibbie
would probably sign the CLA.
from
david honey to Everyone:    10:45  AM
Nick
to send David and Ian the PDF and contact details so that they give each
approval to sign the Individual CLA.
from
James Amsden to Everyone:    10:45  AM
https://www.oasis-open.org/policies-guidelines/open-projects-process#individual-cla-exhibit
from
david honey to Everyone:    10:47  AM
QM,
once OP established and repos moved, will move spec to new Github repo.
Needs some minor changes and put through new Respec.
from
david honey to Everyone:    10:49  AM
For
existing core specs, Jim thinks that it might be as simple as move the
source, then check it renders ok with updated Respec. If minor edits are
needed for it to render properly, that is permitted without further public
review.
from
david honey to Everyone:    10:49  AM
OSLC
Query - lJim has potential changes arising from review documents.
from
david honey to Everyone:    10:51  AM
In
a future meeting, soon after OP setup, review potential changes and determine
which should be tackled, and prioritize.

Jim Amsden, Senior
Technical Staff Member
OSLC and Linked Lifecycle
Data
919-525-6575