- From: Dave Jensen <david@jensen47.com>
- Date: Wed, 29 Apr 2015 09:09:10 -0700
- To: T Guild <ted@w3.org>
- Cc: Paul Boyes <pb@opencar.com>, Kazuyuki Ashimura <ashimura@w3.org>, public-automotive <public-automotive@w3.org>
- Message-ID: <CA+JJkjoSnAn_dg4D1MEMknaMjXatsr5dWOiCrtzC1ERZtM8_8Q@mail.gmail.com>
On Wed, Apr 29, 2015 at 4:59 AM, Ted Guild <ted@w3.org> wrote: > On Tue, 2015-04-28 at 14:46 -0700, Dave Jensen wrote: > > If you want to look at changes to just one file, that is already > > supported in git and github has a good interface for this. > > > > I suspect a git sub-repo would be overkill. Do we even need multiple > > repos? Can you expand on other concerns of having just one repo? > > It depends. If we are successful in getting enough resources to develop > some of the types of deliverables we want then yes. There was > discussion of a conformance test suite for the vehicle and data api > specs for instance. That can be open and allow for contributions from > anyone implementing these specs, reviewed on pull requests. The > individual test cases can amount to a sizable number of files although > that seems less likely for these specs compared to CSS3 for instance. > > A different set of contributors, with some potential overlap, will work > on navigation and media tuning deliverables. They are not going to want > to have to do a unrelated pulls before pushing some minor change to > their work. > If this can be reworked again later and if we face that problem then we > can keep it simple for now. > Agreed, I'd rather keep it simple and have a mitigation plan for if/when we have a multitude of resources working on several projects. Regarding the test suite, since it's a different project, it really should have a different repository. It appears that other working groups have multiple repos on github. Lastly, I apologize if anybody is already a git power user but I have a few comments about git basics. First, for the integrity of the repo, there is no such thing as an unrelated commit/pull and trying to get around that can cause headaches. Second, the downstream user will not even notice the difference if a set of commits are unrelated to their work, it will merge painlessly. Third, there are roughly two camps for git workflow. If the team doesn't want to be bothered with upstream changes until they complete a "feature," then we can use feature branches. One or more people work on a feature branch, when the feature is done, merge back to master. > > > I've seen two good uses of sub-repos: > > > > 1. To include the source of a binary dependency. > > > > A good example is sass/node-sass which includes sass/libsass as a > > subrepo for a specific commit. When node-sass is installed/built, it > > already has the source for libsass from the subrepo, it builds is and > > continues packaging itself for install. This usage doesn't seem > > appropriate for our needs. > > > > > > 2. As a collection of other repos. > > > > I think I've seen this done for a color scheme for code editors. Each > > subrepo was for a different code editor (vim, emacs, intellij, > > sublime, textmate) and the "master" repo simply included each for > > convenience. The only other file included was a README. If we need > > more than two repos for projects, this might be a good use of subrepo. > > This also can be done after the fact. > > > > On Apr 28, 2015 8:50 AM, "Ted Guild" <ted@w3.org> wrote: > > Re-adding the list in case others want to give input. > > > > I can make time Wednesday afternoon ET. > > > > Dave you probably surmised what we intend to do here but will > > elaborate > > as the minutes were scant and a plan wasn't fully formed. > > > > http://www.w3.org/2015/04/23-auto-minutes.html#item06 > > > > The two draft specs the Auto Working Group is chartered to > > bring through > > the standards process are presently in a repo that belonged to > > the > > Business Group. > > > > https://github.com/w3c/automotive-bg/ > > > > As both groups are going to co-exist, collaborate and/or > > transition work > > between them it would make sense in my opinion to have a > > single repo for > > both and to have clearly named sub-repositories (submodules) > > per project > > under. > > > > https://github.com/w3c/automotive > > > > The two specs being worked on should be in one folder since > > they > > > > https://github.com/w3c/automotive/vehicle_data_spec > > > > Significant deliverables for a project such as test cases for > > vehicle > > api can either be a sub-directory or sub-repos under > > vehicle_data_spec. > > We want to avoid having to handle huge merge requests across > > all > > projects but have convenience of being able to recursively > > update all of > > one's local checkouts. > > > > There are a few ways to go about this and to be honest I'm not > > sure of > > the pros and cons. I'll read up and ask advice of some who > > know git and > > better than I. > > > > https://github.com/git-commands/git-subrepo > > > http://stackoverflow.com/questions/20137503/managing-a-git-with-sub-repositories > > > > On Mon, 2015-04-27 at 14:25 -0700, Dave Jensen wrote: > > > I'm free after 12:30pm PDT on Wednesday. > > > > > > On Mon, Apr 27, 2015 at 12:26 PM, Paul Boyes > > <pb@opencar.com> wrote: > > > Ted, > > > > > > > > > Let’s make this happen this week. How about > > touching base > > > Wednesday? > > > > > > Paul J. Boyes > > > -------------------------------- > > > Mobile: 206-276-9675 > > > Skype: pauljboyes > > > > > > > > > > > > > > > > > > > > > On Apr 27, 2015, at 1:16 AM, Kazuyuki Ashimura > > > <ashimura@w3.org> wrote: > > > > > > > Thanks, Dave! > > > > > > > > > > > > Kazuyuki > > > > > > > > On Sat, Apr 25, 2015 at 4:25 AM, Dave Jensen > > > > <david@jensen47.com> wrote: > > > > I'd be interested in helping out on this > > front as > > > > well. > > > > > > > > On Thu, Apr 23, 2015 at 3:33 AM, > > Automotive Working > > > > Group Issue Tracker <sysbot > > +tracker@w3.org> wrote: > > > > auto-ACTION-1: Work with ted and > > kaz on > > > > github repository layout > > > > > > > > > > http://www.w3.org/auto/wg/track/actions/1 > > > > > > > > Assigned to: Paul Boyes > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > Ted Guild <ted@w3.org> > > W3C Systems Team > > http://www.w3.org > > -- > Ted Guild <ted@w3.org> > W3C Systems Team > http://www.w3.org >
Received on Wednesday, 29 April 2015 16:09:39 UTC