github repo organization

Given some hope that we start editing LDOM and ShExC in the near
future, I'm thinking about how we want to organize our git repo.

Anything we commit to a "gh-pages" branch shows up in w3c.github.io,
e.g. <https://w3c.github.io/indie-ui/indie-ui-events>. Also, if we
call our specs "index.html", we can address them by directory. I
propose a directory structure like this:

  data-shapes/data-shapes-ucr/index.html
  data-shapes/data-shapes-ldom/index.html
  data-shapes/data-shapes-shexc/index.html

We currently have a branch called "master" with
  data-shapes/shapes-ucr/spec.html
  data-shapes/README.md

README.md has 7 words in it so I'm not focusing too much on that.
shapes-ucr/spec.html is under active development which we'll need to
pause in order to type this:

git checkout -b gh-pages
git push --set-upstream origin gh-pages
git branch -D master
git push origin :master
git mv shapes-ucr data-shapes-ucr
git mv data-shapes-ucr/spec.html data-shapes-ucr/index.html

and select "gh-pages" as the default branch in
<https://github.com/w3c/data-shapes/settings>

Simon, you're the principle culprit actively editing the UC&R. What's
a good time for you to commit and keep your hands off the keyboard for
a few mins (or do the changes above)? (I figure those changes are non-
controversial, but I may be proven wrong.)

-- 
-ericP

office: +1.617.599.3509
mobile: +33.6.80.80.35.59

(eric@w3.org)
Feel free to forward this message to any list for any purpose other than
email address distribution.

There are subtle nuances encoded in font variation and clever layout
which can only be seen by printing this message on high-clay paper.

Received on Tuesday, 20 January 2015 10:49:59 UTC