Hi Alison,
I'm not sure about this - I thought that the "<name>.github.io" site was
somehow magically created for you by GitHub, not one that you named
yourself? If this is right, I don't really know the implications of it, so
I would welcome more expert opinions.
That said, I realize that I have made a category mistake in that I thought
that this proposal had been discussed on this CF-metadata forum, when it
hadn't - it was talked about informally off-line and I confused the e-mails
in my eagerness to get this sorted before the CF meeting next week. Many
apologies. It's being discussed now, though!
So, I haven't implemented the proposed changes, which is good because
concerns have already been raised by Alison (see above), and also by Ethan,
who points out that the proposed dropping of the "cf-" prefix from
repository names would detrimentally remove any reference to CF in the
names of forked repositories.
I hope that I haven't made too much confusion, and look forward to talking
about it here.
All the best,
David
On Mon, 8 Jul 2019 at 11:07, Alison Pamment - UKRI STFC <
alison.pamment at stfc.ac.uk> wrote:
> Hi David,
>
>
>
> Sorry to be chiming in late on this but I just saw the emails from last
> week and my attention was drawn to this bit:
>
> https://github.com/cf-convention/cf-convention.github.io will become: *https://github.com/cf-convention/website
> <https://github.com/cf-convention/website>*
>
>
>
> I?m absolutely not an expert on GitHub, but the help pages about
> publishing a website from a repository seem to indicate that it has to be
> called http(s)://<orgname>.github.io (see
> https://help.github.com/en/articles/user-organization-and-project-pages).
> You can then set up a custom domain name to point to that repository, which
> is what we do with the cfconventions.org name. This would seem to suggest
> that if you rename the repository as above, the website might stop working.
> Is this something you?ve already looked into?
>
>
>
> Best wishes,
>
> Alison
>
>
>
>
> -----------------------------------------------------------------------------------------------------------
>
> Alison Pamment
> Tel: +44 1235 778065
>
> NCAS/Centre for Environmental Data Analysis Email:
> alison.pamment at stfc.ac.uk
>
> STFC Rutherford Appleton Laboratory
>
> R25, 2.22
>
> Harwell Oxford, Didcot, OX11 0QX, U.K.
>
>
>
> *From:* CF-metadata <cf-metadata-bounces at cgd.ucar.edu> *On Behalf Of *David
> Hassell
> *Sent:* 05 July 2019 17:00
> *To:* CF Metadata <cf-metadata at cgd.ucar.edu>
> *Subject:* Re: [CF-metadata] Renaming of GitHub repositories
>
>
>
> Hello,
>
>
>
> Many apologies, but this week caught up with me, and I didn't get round to
> changing the repository names. But I *will* do it on Monday 8th July.
>
>
>
>
>
> If you need to update a local repository, Guilherme pointed out that it
> might be a good idea to double check what you have before update the
> origin, with
>
>
>
> $ git remote -v
>
>
>
> For example, if you have a fork of cf-conventions called 'origin',
> then the above command might return ...
>
>
>
> origin git at github.com:castelao/cf-conventions.git (fetch)
> origin git at github.com:castelao/cf-conventions.git (push)
> upstream git at github.com:cf-convention/cf-conventions.git (fetch)
> upstream git at github.com:cf-convention/cf-conventions.git (push)
>
>
>
> ... and you wouldn't update 'origin; rather you would update 'upstream' in
> this case:
>
>
>
> $ git remote set-url upstream https://github.com/cf
> -convention/conventions.git
>
>
>
> (I hope that I have got this right, Guilherme!)
>
>
>
> All the best,
>
> David
>
>
>
> On Wed, 26 Jun 2019 at 18:25, David Hassell <david.hassell at ncas.ac.uk>
> wrote:
>
> Hello,
>
>
>
> Somewhat later than I had intended, and following on from Jonathan's
> well-received suggestions on this list (starting from 2019-03-22), I shall
> be renaming the following CF GitHub repositories:
>
>
>
> https://github.com/cf-convention/cf-conventions will become: *https://github.com/cf-convention/conventions
> <https://github.com/cf-convention/conventions>*
>
>
>
> https://github.com/cf-convention/cf-convention.github.io will become: *https://github.com/cf-convention/website
> <https://github.com/cf-convention/website>*
>
>
>
> I shall do this on Tuesday 2nd July (following the principle of never
> making changes that could affect other people just before the weekend).
>
>
>
> Aside from needing to rename our browser bookmarks, this should have no
> adverse effects on most people.
>
>
>
> However, if you have cloned either of these repositories, the old names
> should still work (according to
> https://help.github.com/en/articles/renaming-a-repository), but it is
> best to rename the remote URL as follows, e.g. for the "conventions" site:
>
>
> > git remote set-url origin
> https://github.com/cf-convention/conventions.git
>
>
>
> (Don't take my word for it! See
> https://help.github.com/en/articles/changing-a-remotes-url for more
> details, for example.)
>
>
>
> Please let us know about any concerns that may still remain on this topic,
> all the best,
>
>
>
> David
>
>
>
> --
>
> David Hassell
> National Centre for Atmospheric Science
> Department of Meteorology, University of Reading,
> Earley Gate, PO Box 243, Reading RG6 6BB
> Tel: +44 118 3785183
> http://www.met.reading.ac.uk/
>
>
>
> --
>
> David Hassell
> National Centre for Atmospheric Science
> Department of Meteorology, University of Reading,
> Earley Gate, PO Box 243, Reading RG6 6BB
> Tel: +44 118 3785183
> http://www.met.reading.ac.uk/
>
--
David Hassell
National Centre for Atmospheric Science
Department of Meteorology, University of Reading,
Earley Gate, PO Box 243, Reading RG6 6BB
Tel: +44 118 3785183
http://www.met.reading.ac.uk/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.cgd.ucar.edu/pipermail/cf-metadata/attachments/20190709/ce37037a/attachment-0001.html>
Received on Tue Jul 09 2019 - 04:20:44 BST
