Hi David,
On 09/07/2019 12:20, David Hassell wrote:
> I'm not sure about this - I thought that the "<name>.github.io
> <http://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.
Alison already gave some information, but from the cited help page [1] I
get the following information. There are two kinds of pages, project
pages and user/organization pages. Project pages live in the respective
project repository; orga pages live in the special repository
<orga>.github.io. Orga pages are availabe at https://<orga>.github.io,
project pages are always available from
https://<orga>.github.io/projectname.
Based on this information it seems best to me to keep the
cf-convention.github.io name for this repository.
> 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.
It might be worth pointing out that all forks will retain the link to
the original repository as highlighted in the attached screenshot so
that even with the simplified name the CF connection should be clear.
Having said that, I personally am in favor of keeping the prefix.
Cheers
Klaus
[1]
https://help.github.com/en/articles/user-organization-and-project-pages
>
>
>
> On Mon, 8 Jul 2019 at 11:07, Alison Pamment - UKRI STFC
> <alison.pamment at stfc.ac.uk <mailto: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*____
>
> __?__
>
> 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 <http://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
> <http://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 <mailto: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
> <mailto: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
> <mailto: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
> <mailto:git at github.com:castelao/cf-conventions.git> (fetch)
> origin git at github.com:castelao/cf-conventions.git
> <mailto:git at github.com:castelao/cf-conventions.git> (push)
> upstream git at github.com
> <mailto:git at github.com>:cf-convention/cf-conventions.git (fetch)
> upstream git at github.com
> <mailto: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
> <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 <mailto: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/cf-convention.github.io will
> become: *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/
>
> _______________________________________________
> CF-metadata mailing list
> CF-metadata at cgd.ucar.edu
> http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: github_fork.png
Type: image/png
Size: 78269 bytes
Desc: not available
URL: <
http://mailman.cgd.ucar.edu/pipermail/cf-metadata/attachments/20190709/0f0a96a9/attachment-0001.png>
Received on Tue Jul 09 2019 - 05:25:33 BST
