Activities relating to building a scientific community around Software Heritage
Fri, Dec 6
Opened this issue to inform Dirk Roorda:
Wed, Dec 4
This is now done
Nov 14 2019
review template with:
- @software for the software concept/project
- @softwareversion for a specific release
- @insoftware for a specific artifact in the software (e.g revision, directory, file)
Nov 7 2019
Oct 28 2019
review template with @software and @softwareversion entries
Oct 10 2019
Aug 26 2019
Jul 8 2019
Jun 26 2019
thanks @twitu for finding this location, if you see any other places dates are documented, feel free to comment here.
Jun 25 2019
This explains some of the fields associated with dates, timestamps and offset.
Jun 22 2019
I too, two noticed the two glossaries. They have varying levels of explanations and merging them is one of the tasks I have considered for my GSoD application. I will be glad to assist in the process, in any way I can.
Jun 21 2019
@zack: Good idea to have only one glossary.
Jun 20 2019
I second the need of properly defining terms related to push archival.
Jun 18 2019
Draft is done and was sent to Inria GT for feedback.
Jun 7 2019
Duplicate of T1657
Jun 6 2019
References to investigate:
- Zotero and the following issues:
I created a seperate branch moranegg on which I'm working and to which I'm pushing.
You can have a look, but I will ask for a merge only next week.
Seems I can't push to master, but it's better this way :-)
Sorry, I was in the midst of just adding quotes for readability and left it open.
Is this committed?
Jun 4 2019
I have talked to Bruno about it for deposits on HAL.
It can't be implemented on HAL's form without an "high level" decision.
I think this will be the same for the actors roles.