Re: Making the Sonatype Plexus GitHub Repositories Read Only

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Re: Making the Sonatype Plexus GitHub Repositories Read Only

William L. Thomson Jr.
On Sun, 1 Jul 2018 20:37:10 +0200
Michael Osipov <[hidden email]> wrote:

> Am 2018-07-01 um 20:31 schrieb Plamen Totev:
>
> > Also if nobody objects  I would like to contact GitHub support to
> > check if we can make the codehaus-plexus repositories regular ones
> > (they appear as forks now). That would help with them being more
> > easily identified as the canonical repositories.  
>
> Sounds good to me. Can we remove the "forked from sonatype/..." too?

That is an easy semi routine request. Github will happily un-attach a
forked repo. Just contact them requesting such. Or you can delete the
repo and re-upload a copy. That will do the same.

Just the same with owners permission you can also change the root of
any forks. Like making codehaus-plexus the root, and sonatype a fork of
that. I did that via owners permission for  JTidy. It is now the root,
it was not before.
https://github.com/jtidy

Though I would likely keep it a fork if the other is archived. Other
repos do that for historic purposes.

Example
https://github.com/google/dagger

You can either detach and archive sonatype or update the readme and
point to codehaus-plexus. I think keeping it a fork is better for
historic purposes. It is moot to me either way. Just my 2 cents.

--
William L. Thomson Jr.

attachment0 (201 bytes) Download Attachment