Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PTC Recommendation : Software Citation in a project #24

Open
rinkug opened this issue Dec 18, 2019 · 2 comments
Open

PTC Recommendation : Software Citation in a project #24

rinkug opened this issue Dec 18, 2019 · 2 comments
Assignees
Labels
new ptc This issue contains a new PTC which eventually needs to be PR'd

Comments

@rinkug
Copy link
Contributor

rinkug commented Dec 18, 2019

Name and Description

SoftwareCitation: Getting a software citation for your project

User Story: As a team lead , I want to provide citations for our software, so that our software is easily discoverable, creators on my team get due credit and reproducibility with my software becomes easier

Card(s)

  1. Project does not incorporate citations for their software
  2. Investigate the different venues that provide software citations and chooses one that meets your needs
  3. Complete requirements for software citation and get a citation for the software
  4. Use the citation at outreach venues (presentations, publications)
  5. Team documents are updated to educate all team members on how to get and use citations
  6. Team evaluates trends/success of chosen citation method and make a decision to continue or seek newer methods.

Comments

Guidelines for above steps
For Step 1 (Investigate the different venues that provide software citations and chooses one that meets your needs), some of the links on bssw.io may be useful

For Step 3 (Use the citation at outreach venues (presentations, publications))

  • This may be a long term step. What needs to be evaluated in this step, is how easy it is to use the particular citation method in your outreach materials, if other publications are using citations to cite your work. It may be too early to determine if a software citation is being useful to your project.

For Step 4 (Team documents)

  • Team documents here refers to any portals/documents that are used by the team to disseminate information among themselves. Examples of such documents can be software release policies, checklists, guides etc.

Related Cards

None for now

Other Remarks

Please feel free to make each of the bullets more broader.

@rinkug rinkug added the new ptc This issue contains a new PTC which eventually needs to be PR'd label Dec 18, 2019
@elaineraybourn
Copy link
Member

elaineraybourn commented Dec 18, 2019

This is a good start at a task list that can be associated with a progress tracking card. PTCs articulate the behaviors that are evident at the stages of the activity, and what constitutes completeness at each stage. Try writing the PTC in past or past perfect tense, and focus on answering the question, "at this stage, given the associated steps have been performed, what artifacts will we have that signal that at this stage the activity is complete? For instance, your step 1 "Investigate the different venues that provide software citations and chooses one that meets your needs" could be rewritten as "Team has made decision on software citation protocol after investigation and documentation of needs." Reach out if you have more questions.

@elaineraybourn elaineraybourn self-assigned this Dec 18, 2019
@elaineraybourn
Copy link
Member

@rinkug please see my comment on December 18. Would you like to modify your PTC?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new ptc This issue contains a new PTC which eventually needs to be PR'd
Projects
None yet
Development

No branches or pull requests

2 participants