search

rlw730 / support-tools

Automatically exported from code.google.com/p/support-tools
Apache License 2.0
0 stars 0 forks source link

Provide a way for project admins to remove the "Export to GitHub" button #21

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Provide a way for project admins to remove the "Export to GitHub" button.

Original issue reported on code.google.com by chrsm...@google.com on 13 Mar 2015 at 10:29

GoogleCodeExporter commented 8 years ago

Original comment by chrsm...@google.com on 24 Apr 2015 at 9:47

GoogleCodeExporter commented 8 years ago 
I was the original requestor for this feature over email -
<snip>
Hi,

I have several active projects on GoogleCode (as listed below in your email) - 
which I will move to GitHub or elsewhere after due diligence on my needs and 
what the services offer. 

However, that "Export to GitHub" button on every project that allows anyone 
(not just the project's administrator) to copy over the project to GitHub I 
feel may create unnecessary forks where none were intended. I agree it is 
useful for abandoned but still useful projects.

I propose that you give project admins the option to remove that button - so 
that when the admin moves the project the new location becomes the canonical 
project. For folks who do really want to fork - they can of course always do 
that. My intention is only to stop unintended forks, not intended forks.

Srivats
</snip>

Is there an ETA for this? I'm aware Google doesn't typically provide ETA - I 
ask because I see many exported repos in github for my project - ostinato. Not 
sure if they are intentional or unintentional forks. Ostinato is an active 
project and will move to another provider at a convenient time for the 
development team. 

Would request to expedite this feature if possible to avoid multiple copies of 
the repo so that the canonical project doesn't get buried in the sea of 
unintended forks.

Original comment by pstav...@gmail.com on 1 May 2015 at 5:16

GoogleCodeExporter commented 8 years ago 
I'ved just finished rolling out a change to Google Code to remove the "Export 
to GitHub" button for your project:
https://code.google.com/p/ostinato/

However, if you manually try to export the project via the 
code.google.com/export-to-github tool, that will still work. The change to 
disable that has been submitted but will not be rolled out until later this 
week. (Could be as soon as tomorrow, depends on how soon I can get to it.)

Adding a new "admin checkbox" to the Google Code UI probably doesn't meet the 
bar, but if future project admins would like to disable GitHub export for their 
project, I can take care of it manually on your behalf.

Original comment by chrsm...@google.com on 4 May 2015 at 6:23

GoogleCodeExporter commented 8 years ago 
Thanks Chris!

However, it looks like the button is not visible to project owners/moderators 
as well - when we do need it, should we contact you for manual intervention 
again to re-enable it?

Srivats

Original comment by pstav...@gmail.com on 5 May 2015 at 3:00

GoogleCodeExporter commented 8 years ago 
@pstavirs, yup.

Original comment by chrsm...@google.com on 5 May 2015 at 6:11

GoogleCodeExporter commented 8 years ago 
@chris: Having made a new release and with the hg repository now fixed after 
the recent problem, the ostinato project is ready to move to github - could you 
please re-enable the "Export to Github" button?

Thanks in advance!

Original comment by pstav...@gmail.com on 27 Jun 2015 at 4:39

GoogleCodeExporter commented 8 years ago 
Re-enabled export for project ostinato using the Google Code-to-GitHub 
exporter, although the button is still disabled in the web UI. That should be 
fixed in the next rollout of the site.

Original comment by chrsm...@google.com on 1 Jul 2015 at 9:00

GoogleCodeExporter commented 8 years ago 
prepare Mercurial As a first step, you should teach your Mercurial name. So you 
open the file ~ / .hgrc (or Mercurial.ini in your home directory for Windows) 
with a text editor and add the ui section (user interaction) with your user 
name: if You are systems that project members checked or validated changes in 
the source code, or by using command-line tools to upload files to the project 
of the "Downloads" tab. Password is: kt2qK3qV5PX4

http://git-scm.com/downloads

http://mercurial.selenic.com/downloads

look more to my blog site here  :  http://mercurial-1.blogspot.com

Original comment by charliel...@gmail.com on 14 Sep 2015 at 12:38

GoogleCodeExporter commented 8 years ago 
prepare Mercurial As a first step, you should teach your Mercurial name. So you 
open the file ~ / .hgrc (or Mercurial.ini in your home directory for Windows) 
with a text editor and add the ui section (user interaction) with your user 
name: if You are systems that project members checked or validated changes in 
the source code, or by using command-line tools to upload files to the project 
of the "Downloads" tab. Password is: kt2qK3qV5PX4

http://git-scm.com/downloads

http://mercurial.selenic.com/downloads

look more to my blog site here  :  http://mercurial-1.blogspot.com

Original comment by charliel...@gmail.com on 14 Sep 2015 at 12:38