You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
This ticket should document the things we need to do to get up and running with the new FAO github repo.
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
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?
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?
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)
The text was updated successfully, but these errors were encountered: