Difference between revisions of "Suggestion box: source code to add"
Jump to navigation
Jump to search
| Line 13: | Line 13: | ||
;Contact | ;Contact | ||
: who to contact for technical collaboration on how to best archive source code hosted on the software origin. You can list yourself if you're the relevant person, or provide the most relevant contact point if you know it | : who to contact for technical collaboration on how to best archive source code hosted on the software origin. You can list yourself if you're the relevant person, or provide the most relevant contact point if you know it | ||
| − | + | ;Conservation status | |
| + | : information about how likely it is that the software origin will disappear; high likelihood will make it more urgent for us to archive software hosted there. We suggest to use the [https://en.wikipedia.org/wiki/Conservation_status species conservation status], i.e., one of: Critically endangered (CR), Endangered (EN), Vulnerable (VU), Near threatened (NT), Least concern (LC). | ||
| + | ;How to mirror | ||
| + | : (pointers to) technical information on how to do a full mirror of ''all'' the source code available at the software origin, ideally one shot and in batch | ||
| + | ;How to keep up | ||
| + | : (pointers to) technical information on how to incrementally retrieve new source code accumulated since the last visit; usually this should be based on some kind of incremental change feed or event API | ||
| + | ;Notes | ||
| + | : anything else you think we should know about this software origin | ||
== Suggestions == | == Suggestions == | ||
| Line 23: | Line 30: | ||
!Conservation status | !Conservation status | ||
!How to mirror | !How to mirror | ||
| − | !How to keep up | + | !How to keep up |
!Notes | !Notes | ||
|- | |- | ||
| Line 29: | Line 36: | ||
|Git hosting | |Git hosting | ||
|John Doe <john@example.com> | |John Doe <john@example.com> | ||
| − | | | + | |LC |
|retrieve full repo list at /api/list, then git clone on each entry | |retrieve full repo list at /api/list, then git clone on each entry | ||
|poll RSS feed at /api/updates?since=YYYY-MM-DD | |poll RSS feed at /api/updates?since=YYYY-MM-DD | ||
Revision as of 16:56, 3 July 2016
Work in progress
The Archive is growing organically. We started "small", tracking 3 software origins (GitHub + Debian + GNU), and we will be adding new origins bit by bit, depending on the urgency of archiving them and available development energies to integrate them into Software Heritage.
Using this page you can add suggestions of software origins that we aren't following yet, but we should. You can include information about who to contact for technical collaboration, the urgency of archival, and other useful information. To that end, just add a row to the table below. Here some information about the meaning of the various columns.
Legend
- Software origin
- any (public accessible) "place" on the Internet that host software in source code form. Please provide a title for it and hyperlink it to the relevant URL
- Type of origin
- information about the kind of hosting, e.g., whether it is a forge, a collection of repositories, an homepage publishing tarball, or a one shot source code repository. For all kind of repositories please specify which VCS system is in use (Git, SVN, CVS, etc.)
- Contact
- who to contact for technical collaboration on how to best archive source code hosted on the software origin. You can list yourself if you're the relevant person, or provide the most relevant contact point if you know it
- Conservation status
- information about how likely it is that the software origin will disappear; high likelihood will make it more urgent for us to archive software hosted there. We suggest to use the species conservation status, i.e., one of: Critically endangered (CR), Endangered (EN), Vulnerable (VU), Near threatened (NT), Least concern (LC).
- How to mirror
- (pointers to) technical information on how to do a full mirror of all the source code available at the software origin, ideally one shot and in batch
- How to keep up
- (pointers to) technical information on how to incrementally retrieve new source code accumulated since the last visit; usually this should be based on some kind of incremental change feed or event API
- Notes
- anything else you think we should know about this software origin
Suggestions
| Software origin | Type of origin | Contact | Conservation status | How to mirror | How to keep up | Notes |
|---|---|---|---|---|---|---|
| (sample entry) GitHubBub forge | Git hosting | John Doe <john@example.com> | LC | retrieve full repo list at /api/list, then git clone on each entry | poll RSS feed at /api/updates?since=YYYY-MM-DD | nothing special to add |