Difference between revisions of "Software Projects"

From SCECpedia
Jump to navigationJump to search
 
(2 intermediate revisions by one other user not shown)
Line 74: Line 74:
 
* Standard git repo organization to support open-source releases and automated testing
 
* Standard git repo organization to support open-source releases and automated testing
 
* Connecting git project to run tests on commit
 
* Connecting git project to run tests on commit
* Process of contributing new releases to pypy, conda (dockerhub, singularity)
+
* Process of contributing new releases to pypi, conda (conda-forge)
  
 
== Related Entries ==
 
== Related Entries ==
Line 80: Line 80:
 
*[[CSEP Working Group]]
 
*[[CSEP Working Group]]
 
* Design codes and distribution as python modules, packages (and libraries if that term is used)
 
* Design codes and distribution as python modules, packages (and libraries if that term is used)
 +
* Potential build and deploy tools (ansible, others?)

Latest revision as of 22:07, 7 April 2020

Collection of links related to creating software distributions

Packaging Python Projects

Developing Effective Python Documentation

Screen Shot 2020-04-06 at 2.55.46 PM.png

Open Source Software Practices

Open Source Software Licenses

USGS Software and Data Acceptance Criteria

Developing a Community

Defining Interfaces

Data Management Systems

Continuous Testing Links

Software Release Practices

Example Projects

Standard Practices

SCEC is standardized software project practices:

  • Standard elements in git repo (readme.md, license.txt, authors etc)
  • Standard git repo organization to support open-source releases and automated testing
  • Connecting git project to run tests on commit
  • Process of contributing new releases to pypi, conda (conda-forge)

Related Entries

  • CME_Project
  • CSEP Working Group
  • Design codes and distribution as python modules, packages (and libraries if that term is used)
  • Potential build and deploy tools (ansible, others?)