Maniphest T1728

Draft guidelines for archiving scientific software artefacts for ASE conference use case
Closed, MigratedEdits Locked
Actions

Description

On this google docs: https://docs.google.com/document/d/1P5G1fLvRZNi_oslwk0-jyapgMOAhA1Q3koCkYRwN2xY/edit?usp=sharing

How do we archive software artefacts associated to conference publications?

Option A: save code now of a an existing repository
Option B: software deposit with a new deposit client for each conference

Artefact evaluation examples:

The first conference for which we are addressing the guidelines:

https://2019.ase-conferences.org/committee/ase-2019-organizing-committee

Related Objects
Search...

		Status	Assigned	Task
				Unknown Object (Maniphest Task)
		Migrated	gitlab-migration	T1728 Draft guidelines for archiving scientific software artefacts for ASE conference use case

Event Timeline

moranegg changed the task status from Open to Work in Progress.May 21 2019, 2:22 PM

moranegg triaged this task as High priority.

moranegg created this task.

moranegg moved this task from Backlog to High priority on the SWORD deposit board.May 21 2019, 2:24 PM

moranegg moved this task from Backlog to Specifications on the Metadata workflow board.May 21 2019, 2:30 PM

moranegg added a project: Scientific Community Building.May 22 2019, 5:04 PM

moranegg moved this task from Backlog to High priority on the Scientific Community Building board.May 24 2019, 4:53 PM

moranegg renamed this task from Draft guidelines for archiving scientifict software artefacts for ASE conference use case to Draft guidelines for archiving scientific software artefacts for ASE conference use case.Jun 4 2019, 10:46 AM

Draft is done and was sent to Inria GT for feedback.

In https://gitlab.inria.fr/gt-sw-citation/artifact-archival-swh.git

moranegg closed this task as Resolved.Jun 18 2019, 4:14 PM

moranegg added a parent task: Unknown Object (Maniphest Task).

This task has been migrated to GitLab.