Re: [CF-metadata] Proposals for Versioning CF Conventions and Standard Names on Github

On Tue, Sep 23, 2014 at 2:16 PM, Signell, Richard wrote: > I wonder if we might have a webinar to demonstrate/talk about the > concepts we envision here. We've done a lot of typing, but I get with > 30 min together online I bet we could end up with consensus. > or at least know we're all talking

Re: [CF-metadata] Proposals for Versioning CF Conventions and Standard Names on Github

On Tue, Sep 23, 2014 at 11:47 AM, Signell, Richard wrote: > Back in mid-March we had a long discussion on this topic, initiated > when Richard Hattersley presented a model of what CF could look like > on github using restructured text and github style versioning. His > mock-up is still at > htt

Re: [CF-metadata] Proposals for Versioning CF Conventions and Standard Names on Github

On Tue, Sep 23, 2014 at 9:16 AM, Jonathan Gregory wrote: > I think I must not have missed a point somewhere. Version control is not > the > same as branches, is it. well, we have a vocabulary issue here: Applying version numbers to something and what those version numbers mean is one thing. O

Re: [CF-metadata] Proposals for Versioning CF Conventions and Standard Names on Github

Jonathan, I wonder if we might have a webinar to demonstrate/talk about the concepts we envision here. We've done a lot of typing, but I get with 30 min together online I bet we could end up with consensus. -Rich On Tue, Sep 23, 2014 at 12:16 PM, Jonathan Gregory wrote: > Dear all > > I think I

Re: [CF-metadata] Proposals for Versioning CF Conventions and Standard Names on Github

Dear all I think I must not have missed a point somewhere. Version control is not the same as branches, is it. We already have version control and maybe we could add a third digit to it if we corrected defects between versions. I do not see a need for branches in developing the convention. In soft

Re: [CF-metadata] Proposals for Versioning CF Conventions and Standard Names on Github

Back in mid-March we had a long discussion on this topic, initiated when Richard Hattersley presented a model of what CF could look like on github using restructured text and github style versioning. His mock-up is still at https://cf-conventions.readthedocs.org/en/v1.6/ In the conversation that

Re: [CF-metadata] Broken links

I have found further information: it looks like those pages are generated from the repository at https://github.com/cf-convention/cf-convention.github.io which is owned by @mattben. I should probably post an issue there, if you haven't done so already. On Tue, Sep 23, 2014 at 12:56 PM, John Graybe

Re: [CF-metadata] Broken links

I don't have the keys, though it's possible I will get them soon. This is a known problem and that the people who do have the keys have been dealing with higher-priority issues, but intend to get to this soon. I think this list *is* the webmaster mailto link, but I agree a separate one (or at l

Re: [CF-metadata] Proposals for Versioning CF Conventions and Standard Names on Github

On Sep 23, 2014, at 06:26, Hattersley, Richard wrote: >> You _can_ have different documents in different branches, but that's not >> really how branches were designed to be used, and I think would be a big >> confusing. > > Indeed. Given their independent release cycles it would be *much* mo

[CF-metadata] GRIB2 data cutoff

Hi everyone, As a little "light relief" from the versioning discussion... Does anyone have any prior art for representing the GRIB 2 concept of "hours/minutes of observational data cutoff after reference time" (as expressed in product definition template 4.0) within CF-netCDF? Richard Hatters

Re: [CF-metadata] Proposals for Versioning CF Conventions and Standard Names on Github

> You _can_ have different documents in different branches, but that's not > really how branches were designed to be used, and I think would be a big > confusing. Indeed. Given their independent release cycles it would be *much* more natural and convenient to host them in two separate repositor

Re: [CF-metadata] Proposals for Versioning CF Conventions and Standard Names on Github

> I'd be in favor of migrating the trac tickets to github as well. As they say on github... :+1: :wink: -Original Message- From: CF-metadata [mailto:cf-metadata-boun...@cgd.ucar.edu] On Behalf Of Signell, Richard Sent: 22 September 2014 20:54 To: Chris Barker Cc: CF Metadata List; John

[CF-metadata] Broken links

In search of insight into @rsignell's question regarding splitting the CF Standard Name list and CF Conventions document into separate repositories, I went browsing at cfconventions.org and found numerous 404 links. Turns out there are at least 21 found using a broken link checker