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

Getting started with editing FAO #1

Open
cmungall opened this issue Aug 25, 2016 · 1 comment
Open

Getting started with editing FAO #1

cmungall opened this issue Aug 25, 2016 · 1 comment
Assignees

Comments

@cmungall
Copy link
Member

This ticket should document the things we need to do to get up and running with the new FAO github repo.

OBO-Edit setup

I'll put some instructions in README-editors.md -- at the moment these are a bit Protege-centric, but it makes sense to keep using OE for now

The main thing to remember is to set up ID ranges - I'll add something on this soon

GitHub

Tickets are easy in github, but getting set up with checkin/checkout can be harder

Some people like the command line, others prefer graphical clients - @dianeoinglis are you on a mac or PC?

Are there GO editors in addition to Val that can follow the issue tracker

There are a variety of options you can tag people like this: @ValWood, @mah11 and they'll see the message. They can also choose whether to follow individual tickets, or the whole repo. I also gave @mah11 rights to edit files directly, do we have representatives for other fungal clades?

If so, I will create a ticket for terms that I think should be added with defs and proposed placement

I think that's a great idea. It doesn't hurt to be too granular (unless we're adding 100s of terms at a time, in which case obviously batch the tickets)

@ValWood
Copy link

ValWood commented Aug 25, 2016

OK< I am now following the tracker.
Val

@dianeoinglis dianeoinglis self-assigned this Aug 30, 2016
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

3 participants