Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

requirements recommendations #64

Closed
wants to merge 1 commit into from

Conversation

@marqh
Copy link
Contributor

commented Jan 13, 2016

I have added the conformance page (as html) to this repository

I think the conformance document and the conventions document are aimed to be managed in step, so this makes sense to me.

I have added the 1.6 snapshot to be consistent with the conventions content version.
If this is adopted, we can bring in the 1.7 draft, and thus track changes

If a different format is preferred, please may content in this form be provided? The html form
was all I could find.

thank you
mark

@rhattersley rhattersley referenced this pull request Jan 20, 2016
1 of 2 tasks complete
@painter1

This comment has been minimized.

Copy link
Contributor

commented Apr 10, 2017

I have to apologize for not noticing this pull request. Last week I took the html version of the draft 1.7 conformance document and converted it to AsciiDoc (mostly; lots of variable names still have to be highlighted). I put it in a separate repository, named cf-convention/Conformance.

I don't have any strong opinions about whether the conformance document should be in the same repository as the main CF Conventions document, or its own repository.

One thing which I am concerned about relates to a feature we have for the main document. We have a nice system for automatically converting the master branch's AsciiDoc files into an html file, which is immediately visible to the community. Recently this worked as it should for Ticket 145. I would like to see the same sort of system for the conformance document, but I don't know how it works or who originally set it up.

@rsignell-usgs

This comment has been minimized.

Copy link
Member

commented Apr 11, 2017

I know that everything that happens automatically upon PR or merge is controlled by
https://github.com/cf-convention/cf-conventions/blob/master/.travis.yml
but I don't know much more than that.

I think unfortunately @rhattersley is no longer involved with CF, but perhaps someone else from the @SciTools group or @ocefpaf would be willing to help us out?

@rsignell-usgs

This comment has been minimized.

Copy link
Member

commented Apr 11, 2017

Maybe it's as simple as adding a few lines here?
https://github.com/cf-convention/cf-conventions/blob/master/.travis.yml#L17-L18
@painter1 , what would those lines be?

@ocefpaf

This comment has been minimized.

Copy link

commented Apr 11, 2017

https://github.com/cf-convention/cf-conventions/blob/master/.travis.yml#L21

I did not check the details but I do see all the parts necessary for an automatic update of the page every time a PR is merged in https://github.com/cf-convention/cf-conventions/blob/master/.travis.yml#L21

(Although nowadays I would re-write that to use doctr and simplify it a lot.)

@rsignell-usgs

This comment has been minimized.

Copy link
Member

commented Apr 11, 2017

@painter1, ah, okay, I see you put the conformance doc in it's own repo. So you would need to add a .travis file similar to https://github.com/cf-convention/cf-conventions/blob/master/.travis.yml and get the tokens set up there.

@dblodgett-usgs

This comment has been minimized.

Copy link
Contributor

commented Jun 22, 2019

This PR is getting very long in the tooth. Can we agree to merge or close it for later?

@dblodgett-usgs

This comment has been minimized.

Copy link
Contributor

commented Jul 17, 2019

Going to close and not merge. We need to figure out how to get these builds working properly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants
You can’t perform that action at this time.