- From: Krzysztof Janowicz <janowicz@ucsb.edu>
- Date: Mon, 20 Feb 2017 11:26:18 -0800
- To: Maxime Lefrançois <maxime.lefrancois@emse.fr>, Kerry Taylor <kerry.taylor@anu.edu.au>, "Simon.Cox@csiro.au" <Simon.Cox@csiro.au>, "danh.lephuoc@tu-berlin.de" <danh.lephuoc@tu-berlin.de>, Armin Haller <armin.haller@anu.edu.au>
- Cc: "public-sdw-wg@w3.org" <public-sdw-wg@w3.org>
- Message-ID: <b812597d-1882-847a-6793-451045f24e96@ucsb.edu>
Hi Maxime, > I guess you are referring to the pull requests I created today. Not only but also :-). > - Each of these PR mention: "Before merging this pull request, please > discuss options in the Wiki <some link to the wiki>" Yes, but then we should create the changes in the code and issue a pull request after the discussion and not before, right? > - I purposely created one PR = one wiki page, hence we can discuss, > vote, modify the related PR branch accordingly, and merge only the > changes that have been voted for. I see. This is why I said that I will ignore those requests for now. I agree that it makes sense to issue small pull requests and do minor updates so that we have something to show during our telcos (in fact, I did so one time as well), but for larger and more substantial changes, I would propose to go step-by-step. Cheers, Krzysztof On 02/20/2017 11:09 AM, Maxime Lefrançois wrote: > Hi Krysztof, all, > > Krysztof, you wrote: > > Yes, but there are many, many new pull requests for features that > have not yet > > been discussed in the group, so I will only look at and accept those > that reflect > > consensus within the group. > > I guess you are referring to the pull requests I created today. > > - Each of these PR mention: "Before merging this pull request, please > discuss options in the Wiki <some link to the wiki>" > > - I purposely created one PR = one wiki page, hence we can discuss, > vote, modify the related PR branch accordingly, and merge only the > changes that have been voted for. > > - the base branch for each of these PR is "maxime-methodology", which > is still not merged with "gh-pages" (see > https://github.com/w3c/sdw/pull/554). Merging any of these should then > be safe anyways. > > Kind regards, > Maxime > > > Best, > Jano > > > > > On 02/19/2017 10:33 PM, Kerry Taylor wrote: >> >> Ok, thks. My PR yesterday does the ssn.ttl /ssn.owl part of the >> fix https://github.com/w3c/sdw/pull/560 – I will do the rest when >> I get a chance. >> >> Krysztof, can you please review and merge? >> >> -Kerry >> >> *From:*Simon.Cox@csiro.au <mailto:Simon.Cox@csiro.au> >> [mailto:Simon.Cox@csiro.au] >> *Sent:* Monday, 20 February 2017 12:15 PM >> *To:* Kerry Taylor <kerry.taylor@anu.edu.au> >> <mailto:kerry.taylor@anu.edu.au>; janowicz@ucsb.edu >> <mailto:janowicz@ucsb.edu>; danh.lephuoc@tu-berlin.de >> <mailto:danh.lephuoc@tu-berlin.de>; Armin Haller >> <armin.haller@anu.edu.au> <mailto:armin.haller@anu.edu.au> >> *Cc:* public-sdw-wg@w3.org <mailto:public-sdw-wg@w3.org> >> *Subject:* RE: ssn and github >> >> Hi Kerry – >> >> We had some issues integrating a pull-request relating to O&M >> alignment. It was originally issued before the re-name, and we >> were trying to retain the commit history on the branch I had been >> working on. The ttl had gotten re-ordered along the way due to me >> having opened it in TopBraid. We tried to reverse that, but >> clearly failed. >> >> >> Would be very helpful if you could reset the ssn artefacts. >> >> Simon >> >> *From:*Kerry Taylor [mailto:kerry.taylor@anu.edu.au] >> *Sent:* Sunday, 19 February, 2017 15:02 >> *To:* janowicz@ucsb.edu <mailto:janowicz@ucsb.edu>; >> danh.lephuoc@tu-berlin.de <mailto:danh.lephuoc@tu-berlin.de>; >> Armin Haller <armin.haller@anu.edu.au >> <mailto:armin.haller@anu.edu.au>> >> *Cc:* public-sdw-wg@w3.org <mailto:public-sdw-wg@w3.org> >> *Subject:* ssn and github >> >> Github appears to have yet another error on it around ssn: >> >> I can see that there is a new file created here >> https://github.com/w3c/sdw/commit/da109c5b1a8758582caf18c8c797887387123aee#diff-95f609f3731bdeb74f41d82be5f0fadc >> called ssn.owl. >> >> 1) didn’t every one want “ssn.ttl” to be used instead of >> “ssn.owl” (.owl suffix)? Or have I misunderstood? >> >> 2) It is out of date--- it appears to be an old copy that does >> not capture changes to ssn.ttl in the past few weeks and is >> inconsistent with ssn.ttl >> >> 3) I strongly suggest we keep only one of them on git – either >> ssn.owl or ssn.ttl but not both for fear of getting out of sync >> (as they are right now) >> >> I will remove ssn.owl in my next PR – I hope that is ok. Please >> let me know ASAP if that should not be done. >> >> There is also something not right going on with >> dul-alignment.owl – but I am going to leave that alone for the >> principle of “first, do no harm.” >> >> --Kerry >> >> Dr Kerry Taylor >> >> Associate Professor (Data Science) >> >> Research School of Computer Science >> >> ANU College of Engineering and Computer Science >> >> Canberra ACT 2601 Australia >> >> +61 2 6125 8560 >> > > > -- > Krzysztof Janowicz > > Geography Department, University of California, Santa Barbara > 4830 Ellison Hall, Santa Barbara, CA 93106-4060 > > Email:jano@geog.ucsb.edu <mailto:jano@geog.ucsb.edu> > Webpage:http://geog.ucsb.edu/~jano/ <http://geog.ucsb.edu/%7Ejano/> > Semantic Web Journal:http://www.semantic-web-journal.net > -- Krzysztof Janowicz Geography Department, University of California, Santa Barbara 4830 Ellison Hall, Santa Barbara, CA 93106-4060 Email: jano@geog.ucsb.edu Webpage: http://geog.ucsb.edu/~jano/ Semantic Web Journal: http://www.semantic-web-journal.net
Received on Monday, 20 February 2017 19:26:58 UTC