Transfer ownership about cf-conventions HOT 9 CLOSED

I can transfer the repo or I can fork it

from cf-conventions.

I think a transfer would be best. Now that we've sorted out the asciidoc sources and agreed the outline of a way to take things from here there's very little need for the @cf-metadata organisation to remain.

There are some tweaks that will be needed to the secure tokens & travis-ci build script after the transfer, but they're pretty straightforward.

from cf-conventions.

There are some tweaks that will be needed to the secure tokens & travis-ci build script after the transfer, but they're pretty straightforward.

I've done some of the tweaks in #58, but the secure tokens will still need updating.

from cf-conventions.

I can transfer the repo or I can fork it

@mattben - can I tempt you to do the transfer?

from cf-conventions.

I'm still confused, do you want me to transfer a repo from cf-metadata to cf-conventions or a repo from cf-conventinos to cf-metadata.

from cf-conventions.

The idea is to transfer this repo to the @cf-convention organisation.

cc @JonathanGregory

from cf-conventions.

Yes please, I agree with Richard

from cf-conventions.

@rhattersley @JonathanGregory Done. Maybe change the description, sorry for the delay.

from cf-conventions.

Done.

Thanks @mattben - that's great news! 😄

@JonathanGregory - NB. Now that the repo has moved, the auto-build versions of the conventions are available at:

• http://cfconventions.org/cf-conventions/
• http://cfconventions.org/cf-conventions/v1.6.0/

Maybe change the description

As things stand I don't have GitHub permissions to do that - it's not my repo any more. 😉

I'm not exactly sure who needs to be set up with what permissions, but presumably at least @JonathanGregory should have admin on this repo?

from cf-conventions.