Re: Complete Re: Moving the Repo

Please file new issues in the wcag repo. I plan to migrate issues and 
archive the wcag21 repository as soon as I have another work block to 
sit down to it. Michael


On 11/06/2018 3:03 PM, Marc Johlic wrote:
> Hi Michael,
>
>         I will work on migrating issues a bit later.
>
>
> Would you prefer that folks open *NEW* issues related to 2.1 in the 
> wcag repo - or continue to use wcag21 repo until you have Issues 
> migrated over?
>
> Thanks,
> Marc
>
> On Fri, Jun 8, 2018 at 4:44 PM Michael Cooper <cooper@w3.org 
> <mailto:cooper@w3.org>> wrote:
>
>     The repository migration is complete. All files that were in the
>     wcag21 repository are now in the wcag repository, and all people
>     who had commit access to the wcag21 repository now have commit
>     access to the wcag repository. See:
>
>     https://github.com/w3c/wcag
>
>     There is a folder there that wasn't in the wcag21 repository,
>     called "wcag20". This contains files that were used for WCAG 2.0,
>     and should no longer be edited, but are retained for archival reasons.
>
>     It's a virtual guarantee something will not work as expected as a
>     result of this migration. If you encounter any problems, let me know.
>
>     I will work on migrating issues a bit later.
>
>     Prior to migrating content, I merged most open pull requests and
>     Understanding branches. It is possible some of that content was
>     not in fact ready to be merged, but it would be harder to sort it
>     out after the migration. It is possible to revert the changes
>     introduced by the merges if needed.
>
>     Because they were all merged, I did not migrate the Understanding
>     branches. I plan to recreate them soon to support further work.
>
>     I migrated all the branches with names starting with "tech-" so
>     work on techniques can pick up in the new locations.
>
>     There were a couple technique branches that had been started
>     before we introduced the new process to work on techniques. If
>     have content in those branches you still want to work on, let me
>     know and I'll help decide the best way forward.
>
>     There are some other branches that seemed to have stale content,
>     which I did not merge or migrate. If there is a branch in the
>     wcag21 repository containing content you think still should be
>     available for development after the migration, let me know. You
>     can look through them at https://github.com/w3c/wcag21/branches.
>
>     There is a branch named "WCAG_2.1" which is a snapshot of the WCAG
>     2.1 Recommendation (modulo the boilerplate) and not for editing.
>     Mostly we will work on future versions of WCAG in the master
>     branch, but if we decide something should be an erratum for WCAG
>     2.1, we will put it in this branch as well, and potentially could
>     eventually publish an Edited or Amended Recommendation to
>     incorporate those into the official version.
>
>     Michael
>
>
>     On 08/06/2018 2:05 PM, Michael Cooper wrote:
>>
>>     I am beginning the process of moving content from the wcag21
>>     repository to the wcag repository. I have disabled write access
>>     to the wcag21 repository. When the transfer is complete, I will
>>     enable write access on the wcag repo and send around a follow-up
>>     message. Michael
>>
>>
>>     On 07/06/2018 10:00 AM, Andrew Kirkpatrick wrote:
>>>
>>>     AGWGer’s,
>>>
>>>     We are moving the repository that we will be working in from the
>>>     w3c/wcag21 to w3c/wcag on Friday. We will be transferring over
>>>     branches, including branches for techniques that are in
>>>     development (although there is only a few of those). Once this
>>>     is done the branches on the WCAG21 repo will be marked as read only.
>>>
>>>     Just a heads up…
>>>
>>>     Thanks,
>>>
>>>     AWK
>>>
>>>     Andrew Kirkpatrick
>>>
>>>     Group Product Manager, Accessibility
>>>
>>>     Adobe
>>>
>>>     akirkpat@adobe.com <mailto:akirkpat@adobe.com>
>>>
>>>     http://twitter.com/awkawk
>>>
>>
>