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

Types of software #65

Closed
danielskatz opened this Issue Oct 4, 2018 · 10 comments

Comments

Projects
None yet
3 participants
@danielskatz
Copy link
Collaborator

danielskatz commented Oct 4, 2018

Based on discussion in Section 2 of A&P google doc

  • We need to determine what scheme to use for the various software types. Dan originally proposed a simple listing. Alejandra proposed looking at various dimensions.
  • We need to add other types that are not in the document now, such as services, executables, containers, packages or modules (that only work within a framework).
  • Should this be a table? Showing dimensions and values? A drawing?
@danielskatz

This comment has been minimized.

Copy link
Collaborator

danielskatz commented Nov 20, 2018

The writing group is struggling with how to express this as a drawing - the discussion will continue. Help with a drawing would be welcome

@ljhwang

This comment has been minimized.

Copy link

ljhwang commented Nov 20, 2018

What if software is considered in the context of workflow? Do you wish to consider all of it as in scope? When does it stop being a "tool" and becomes a "creative work"?

@danielskatz

This comment has been minimized.

Copy link
Collaborator

danielskatz commented Nov 27, 2018

@dbouquin will be working on this drawing

@danielskatz

This comment has been minimized.

Copy link
Collaborator

danielskatz commented Nov 27, 2018

@npch will work on the text at the start of section 2 to make it clear how expansive we are being in inputs, and that here, we are describing the narrow part of the hourglass where we treat these things in as few categories as possible.

@danielskatz

This comment has been minimized.

Copy link
Collaborator

danielskatz commented Nov 27, 2018

Also we need to think about if we want to keep the flowchart document separate or merge it together? In either case, it is a somewhat different way of thinking about some of the same issues

@dbouquin

This comment has been minimized.

Copy link
Contributor

dbouquin commented Dec 4, 2018

Draft diagram here. Pretty wordy but it's a start at figuring this out I think.
software_citation_2018

@dbouquin

This comment has been minimized.

Copy link
Contributor

dbouquin commented Dec 4, 2018

Refer to linked version (fixed a few mistakes)

@dbouquin

This comment has been minimized.

Copy link
Contributor

dbouquin commented Dec 4, 2018

Diagram files moved to PR 87.

@dbouquin

This comment has been minimized.

Copy link
Contributor

dbouquin commented Jan 15, 2019

New draft - will insert into A&P doc draft_software_types_011419

@danielskatz

This comment has been minimized.

Copy link
Collaborator

danielskatz commented Feb 7, 2019

this discussion has been mostly resolved within the document now.

@danielskatz danielskatz closed this Feb 7, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment