Github for Arctos

Why Use Github for Arctos?

I’d also like to echo the value of the community from a development perspective. A broader perspective seems to make EVERYTHING better. I can often build stuff that just works out of the box because a bunch of people with very different perspectives looked at it before we started writing code. The key to an extremely robust locality model seems to have been getting parasitologists and ethnologists in the same conversation. Rapid digitization of a paleo collection drew heavily from stuff developed for a herbarium. Etc ad nauseum. I don’t think there’s any remote possibility that any “traditional” group of collections or developers could have built anything like Arctos; it’s a synthesis of the community. ~ Dusty McDonald, Arctos Programmer

The tool we use to accomplish what Dusty describes above is Github.

Requirements

Only a GitHub account is necessary; there’s no need to be a member of any particular organization (and Arctos GitHub membership is generally reserved for Officers and developers).

Uses

If is difficult for us to communicate with users without GitHub accounts; we may be forced to restrict access without a path of communication. Users who have manage_records roles must have a GitHub account in their Agent profile.

How To

Instructions for doing specifc tasks in Github related to Arctos

Edit this Documentation

If you see something that needs to be edited in this document, you can create an issue using the link under the search widget at the top left side of this page, or you can edit directly here.