sul-dlss/DeveloperPlaybook
A place to organize style guides, best practices, tools, and techniques for Stanford University's Digital Library Systems & Services group
Issues
- 1
- 3
- 0
add infrastructure tech lead best practices
#136 opened by ndushay - 24
- 0
Link github projects to dependabot
#71 opened by dazza-codes - 3
swagger for APIs
#46 opened by dazza-codes - 2
Provide guidelines for version control workflow
#48 opened by mjgiarlo - 2
- 5
Section for editors and IDEs
#47 opened by dazza-codes - 2
broken link
#57 opened by dazza-codes - 3
- 1
- 0
- 8
DeveloperPlaybook/best-practices/howto_readme.md needs how-to for gemnasium, coveralls etc.?
#42 opened by dazza-codes - 17
Ensure implicated people are informed
#35 opened by azaroth42 - 12
Link to dlss examples
#34 opened by azaroth42 - 9
Waffle board to facilitate voting
#33 opened by azaroth42 - 9
Non-content PRs should ship on 4 +1s
#31 opened by azaroth42 - 3
Clarify process goals
#28 opened by azaroth42 - 3
Automate ToC generation in the future
#30 opened by azaroth42 - 9
12 factor apps
#6 opened by dazza-codes - 8
Ruby apps best practices
#5 opened by dazza-codes - 8
We communicate effectively
#22 opened by azaroth42 - 0
documentation best practices
#11 opened by ndushay - 1
- 0
Licensing best practice
#4 opened by azaroth42 - 0
code dependencies and gemnasium
#8 opened by ndushay - 0
code complexity
#10 opened by ndushay - 6
- 6