W3C home > Mailing lists > Public > public-css-archive@w3.org > July 2018

Re: [csswg-drafts] Move overscroll-behavior spec from WICG to csswg-drafts

From: Majid Valipour via GitHub <sysbot+gh@w3.org>
Date: Tue, 31 Jul 2018 20:40:55 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-409360395-1533069655-sysbot+gh@w3.org>
I will handle the move logistics. Here is my plan so far, please make suggestions and corrections as you see fit.

## Merging repos without losing history

I did a test run based on @birtles  [suggested path](https://github.com/w3c/csswg-drafts/issues/2179#issuecomment-357089856) and the history remains intact.

Basically, it is a merging two unrelated git histories but git is happy to do so none the less and things seems to be working as expected.

Here is the series of command I used:

``` shell
$ cd csswg-drafts
$ git remote add wicg git@github.com:WICG/scroll-boundary-behavior.git
$ git fetch wicg
$ git checkout -b wicg wicg/master
$ mkdir css-overscroll-behavior
$ mv * css-overscroll-behavior/
$ git add .
$ git commit -m "Move to sub-directory in preparation to move the repository"
$ git checkout master 
$ git merge wicg
$ git merge --allow-unrelated-histories wicg
```

I pushed the result to my GH fork and all the history is intact. See [here](https://github.com/majido/csswg-drafts/blame/merge-ob-repo/css-overscroll-behavior/index.bs) for example.

I suspect then it is just a matter of sending a PR for the above repr and making sure the PR is merged without squashing and rebasing. 

## Migrating open issues
There are three [open issues](https://github.com/WICG/overscroll-behavior/issues). I will manually re-create these in csswg-drafts with proper labels etc.

## Post move

1. Update index.bs fix
    - shortname to `css-overscroll-behavior`
    - URL to `https://drafts.csswg.org/css-overscroll-behavior/`
    - Status to `ED` 
    - Repository to `https://github.com/w3c/csswg-drafts/tree/master/css-overscroll-behavior css-overscroll-behavior`
    - Add myself as an editor
2. Remove LICENSE.md, CONTRIBUTING.md, security-privacy-questionnaire.md

The spec is already in Bikeshed and builds without any warnings so hopefully that means it will not create any issues for csswg-draft tools.
So my plan is to merge the repo as is (with the exception of moving to subdirectory) and make necessary changes to deal with any issues after the merge. Let me know if there is anything I am missing or should try to fix before merging the repo.





-- 
GitHub Notification of comment by majido
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2179#issuecomment-409360395 using your GitHub account
Received on Tuesday, 31 July 2018 20:41:03 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 19 October 2021 01:30:54 UTC