Re: Trip Report: Provenance Week 2016

Ivan,

> On Jun 20, 2016, at 10:40 AM, Ivan Herman <ivan@w3.org> wrote:
> 
> Tim,
> 
> that is fine with me but, as I said, it is not my decision. 

To be clear, you are deferring to the “community”, right?

I addressed my discussion to you because you raised the concern,
and cc'd the public list so that others may consider my points.

If I need to do it differently, please advise.

Regards,
Tim


> 
> Ivan
> 
> 
> 
>> On 20 Jun 2016, at 16:26, Timothy Lebo <lebot@rpi.edu <mailto:lebot@rpi.edu>> wrote:
>> 
>> Ivan,
>> 
>> 
>>> On Jun 19, 2016, at 10:05 AM, Ivan Herman <ivan@w3.org <mailto:ivan@w3.org>> wrote:
>>> 
>>>> 
>>>> On 17 Jun 2016, at 16:46, Timothy Lebo <lebot@rpi.edu <mailto:lebot@rpi.edu>> wrote:
>>>> 
>>>> Ivan,
>>>> 
>>>> If w3c does set up a prov repo, can you fork https://github.com/timrdf/prov-wg <https://github.com/timrdf/prov-wg> ?
>>>> It derives directly from https://dvcs.w3.org/hg/prov <https://dvcs.w3.org/hg/prov> as documented in [1] and
>>>> includes updates that handled post-WG WG tasks (i.e. I haven’t hijacked the repo to do anything other than what was needed by the WG).
>>> 
>>> Do you mean the new repo should be a copy/clone of that repository?
>> 
>> I mean that https://github.com/w3c/prov <https://github.com/w3c/prov> should be a git clone of https://github.com/timrdf/prov-wg <https://github.com/timrdf/prov-wg>.
>> 
>>> 
>>> Personally I am not sure, but I let the others decide. The reason of my hesitation is that the intention of the new repo would be to look at the future, so to say, whereas your repo (or the hg repo) is, in some sense, the history. 
>> 
>> 
>> I completely agree. We should be looking forward
>>    — that’s why I’m suggesting what I am.
>> 
>> We should avoid cloning https://dvcs.w3.org/hg/prov <https://dvcs.w3.org/hg/prov> because it contains 4,816 files of which only about 103 matter today. 
>> 
>> I’m suggesting that w3c clone https://github.com/timrdf/prov-wg <https://github.com/timrdf/prov-wg> because it contains ONLY the 103 files that actually matter today, 
>> and it also maintains the provenance of those 103 files (98 commits resolving 11 issues [1]) since the WG disbanded in 2013.
>> As you know, this is the provenance of the files that are actually hosted on W3C’s web server (because you copy them to there for me :-).
>> 
>> While https://github.com/timrdf/prov-wg/wiki <https://github.com/timrdf/prov-wg/wiki> currently documents the maintenance of the published documents,
>> https://github.com/w3c/prov/wiki <https://github.com/w3c/prov/wiki> can be used to fulfill the original suggestion to aid “the broader community” by providing a wiki.
>> What both repositories would share is the 103 authoritative copies of the published W3C PROV documents.
>> 
>> 
>>> A history that we should remain intact (except for possible testing bugs, that you already took care of; thanks for those!).
>> 
>> Yes, intact and preferably *actually connected*.
>> By following my suggestion, I am certain that we can support the new need for a GitHub wiki while also preserving the provenance connections with actual PROV instance data.
>> (One can do it with https://github.com/timrdf/pvcs <https://github.com/timrdf/pvcs>, but that is a side consideration)
>> 
>> In the future, when I submit requests to publish new versions (to resolve 11 outstanding issues [2]), I could start just submitting pull requests from https://github.com/timrdf/prov-wg <https://github.com/timrdf/prov-wg> into https://github.com/w3c/prov <https://github.com/w3c/prov>.
>> That way, W3C is taking more control of the publishing process for the PROV documents, instead of my surrogate.
>> 
>>> 
>>> A possibility is that I copy this repository into the new one, but I create a 'product' for the rec to have a frozen version, and the group can take it from there. But, again, I am not sure that is what the group wants.
>> 
>> 
>> I would highly DISCOURAGE you from “copying”, as I’ve already done the work to ensure the 103 files in https://github.com/timrdf/prov-wg <https://github.com/timrdf/prov-wg> are still relevant.
>> 
>> Regards,
>> Tim
>> 
>> [1] https://github.com/timrdf/prov-wg/issues?q=is%3Aissue+is%3Aclosed <https://github.com/timrdf/prov-wg/issues?q=is:issue+is:closed>
>> [2] https://github.com/timrdf/prov-wg/issues <https://github.com/timrdf/prov-wg/issues>
>> 
>> 
>> 
>>> 
>>> Paul, Luc? I do whatever you prefer (if we go the github way, that is…)
>>> 
>>> Ivan
>>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>> 
>>>> 
>>>> For example, see https://github.com/timrdf/prov-wg/issues <https://github.com/timrdf/prov-wg/issues> and https://github.com/timrdf/prov-wg/wiki <https://github.com/timrdf/prov-wg/wiki>
>>>> 
>>>> Thanks,
>>>> Tim
>>>> 
>>>> [1] https://github.com/timrdf/prov-wg/blob/master/COPIED <https://github.com/timrdf/prov-wg/blob/master/COPIED>
>>>> 
>>>> 
>>>>> On Jun 17, 2016, at 9:39 AM, Ivan Herman <ivan@w3.org <mailto:ivan@w3.org>> wrote:
>>>>> 
>>>>> Thanks for this, Paul!
>>>>> 
>>>>> Per
>>>>> 
>>>>> "make sure that the W3c PROV wik <https://www.w3.org/2001/sw/wiki/PROV>i is up-to-date and is a better resource overall."
>>>>> 
>>>>> would it help to set up a github.com/w3c/prov <http://github.com/w3c/prov> repo instead? People may feel more comfortable with github than with wikis these days…
>>>>> 
>>>>> Ivan 
>>>>> 
>>>>> 
>>>>> 
>>>>>> On 17 Jun 2016, at 15:25, Paul Groth <pgroth@gmail.com <mailto:pgroth@gmail.com>> wrote:
>>>>>> 
>>>>>> Hi All,
>>>>>> 
>>>>>> Here's my trip report from last week's Provenance Week 2016
>>>>>> 
>>>>>> https://thinklinks.wordpress.com/2016/06/17/trip-report-provenance-week-2016/ <https://thinklinks.wordpress.com/2016/06/17/trip-report-provenance-week-2016/>
>>>>>> 
>>>>>> Great seeing many of you!
>>>>>> Paul
>>>>>> pgroth.com <http://pgroth.com/>
>>>>> 
>>>>> ----
>>>>> Ivan Herman, W3C 
>>>>> Digital Publishing Lead
>>>>> Home: http://www.w3.org/People/Ivan/ <http://www.w3.org/People/Ivan/>
>>>>> mobile: +31-641044153
>>>>> ORCID ID: http://orcid.org/0000-0003-0782-2704 <http://orcid.org/0000-0003-0782-2704>
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>> 
>>>> Timothy Lebo
>>>> lebot@rpi.edu <mailto:lebot@rpi.edu>
>>>> https://impactstory.org/TimothyLebo <https://impactstory.org/TimothyLebo>
>>>> http://purl.org/twc/id/person/TimLebo <http://purl.org/twc/id/person/TimLebo> a foaf:Person.
>>>> 
>>> 
>>> 
>>> ----
>>> Ivan Herman, W3C 
>>> Digital Publishing Lead
>>> Home: http://www.w3.org/People/Ivan/ <http://www.w3.org/People/Ivan/>
>>> mobile: +31-641044153
>>> ORCID ID: http://orcid.org/0000-0003-0782-2704 <http://orcid.org/0000-0003-0782-2704>
>> Timothy Lebo
>> lebot@rpi.edu <mailto:lebot@rpi.edu>
>> https://impactstory.org/TimothyLebo <https://impactstory.org/TimothyLebo>
>> http://purl.org/twc/id/person/TimLebo <http://purl.org/twc/id/person/TimLebo> a foaf:Person.
> 
> 
> ----
> Ivan Herman, W3C 
> Digital Publishing Lead
> Home: http://www.w3.org/People/Ivan/ <http://www.w3.org/People/Ivan/>
> mobile: +31-641044153
> ORCID ID: http://orcid.org/0000-0003-0782-2704 <http://orcid.org/0000-0003-0782-2704>
> 
> 
> 
> 

Timothy Lebo
lebot@rpi.edu
https://impactstory.org/TimothyLebo <https://impactstory.org/TimothyLebo>
http://purl.org/twc/id/person/TimLebo a foaf:Person.