Difference between revisions of "Software Projects"

From SCECpedia
Jump to navigationJump to search
Line 10: Line 10:
 
* https://realpython.com/documenting-python-code/
 
* https://realpython.com/documenting-python-code/
 
* https://divio.com/blog/documentation
 
* https://divio.com/blog/documentation
 +
* https://www.writethedocs.org/guide/
  
 
[[Image:Screen Shot 2020-04-06 at 2.55.46 PM.png|right|150px]]
 
[[Image:Screen Shot 2020-04-06 at 2.55.46 PM.png|right|150px]]

Revision as of 19:12, 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:

  • Design codes and distribution as python modules, packages (and libraries if that term is used)
  • 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
  • Potential build and deploy tools (ansible, others?)
  • Process of contributing new releases to pypy, conda (dockerhub, singularity)

Related Entries