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

Migrate "Natural Collections Descriptions (NCD)" #11

Closed
9 of 12 tasks
peterdesmet opened this issue May 30, 2015 · 12 comments
Closed
9 of 12 tasks

Migrate "Natural Collections Descriptions (NCD)" #11

peterdesmet opened this issue May 30, 2015 · 12 comments
Assignees

Comments

@peterdesmet
Copy link
Member

Current URL: http://www.tdwg.org/standards/312/

  • Contact someone from the standard task group
  • Verify the standard is not maintained in another repository already: there is an svn repo, which @mdoering will migrate
  • Decide on shortname ncd
  • Ask for preferred citation
  • Create repository
  • Create a README based on the standard abstract
  • Download the standard and move the content to GitHub.
  • Create managing team
  • Invite all relevant people to the team managing the standard on GitHub.
  • Describe migration in an issue
  • Create a release
  • Document URL redirect
@peterdesmet peterdesmet self-assigned this May 30, 2015
@mdoering mdoering assigned mdoering and unassigned peterdesmet May 30, 2015
@mdoering
Copy link
Contributor

I can take this task, Peter. I have done a lot of the technical work for NCD

@mdoering
Copy link
Contributor

@peterdesmet I cannot create new teams an Owner is needed for that

@tucotuco
Copy link
Member

You realize that NCD never made it to an accepted standard, right?

@mdoering
Copy link
Contributor

Is ratification relevant, @tucotuco? I thought we simply migrate all groups no matter if they have a ratified standard or not.

@tucotuco
Copy link
Member

In terms of migration, no, it is not relevant. It is just that the checklist makes it sound like one. No worries.

@timrobertson100
Copy link
Member

To me it sounds correct to migrate all, perhaps indicating the status at
the top of the README or similar?
Presumably it would be released / tagged too on ratification.

On Sat, May 30, 2015 at 7:00 PM, Markus Döring notifications@github.com
wrote:

Is ratification relevant, @tucotuco https://github.com/tucotuco? I
thought we simply migrate all groups no matter if they have a ratified
standard or not.


Reply to this email directly or view it on GitHub
#11 (comment).

@peterdesmet
Copy link
Member Author

Thanks @mdoering for taking over. I have created a team ncd, with access to this repo and you as member. You can invite more. Ratified or not does not matter for migration, we're moving everything listed on http://www.tdwg.org/standards/. Indication of status is part of #1.

@peterdesmet
Copy link
Member Author

Note, I have removed the prior-standards team from the ncd repo.

@peterdesmet
Copy link
Member Author

@mdoering, where are we in migrating http://www.tdwg.org/standards/312 to https://github.com/tdwg/ncd?

@mdoering
Copy link
Contributor

I havent done much yet, but ill give it another shot this weekend. With finalizing tapir

@peterdesmet
Copy link
Member Author

@mdoering, any update on the migration of NCD?

@peterdesmet
Copy link
Member Author

This issue can be closed. Remaining tasks (invite more collaborators, check citation and create release) will be handled by @tdwg/ncd

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants