issues
search
RMI-PACTA
/
practices
https://rmi-pacta.github.io/practices/
2
stars
0
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
upkeep: target GitHub issues ADO team
#39
jdhoffa
closed
4 months ago
0
Bump actions/configure-pages from 4 to 5
#38
dependabot[bot]
closed
5 months ago
0
move `CODEOWNERS` to HOW section
#37
jdhoffa
closed
5 months ago
0
migrate `CODEOWNERS` advice to "How" section
#36
jdhoffa
closed
6 months ago
1
consider if this is too prescriptive
#35
cjyetman
closed
5 months ago
1
feat: gains `version.md` guidance
#34
jdhoffa
closed
6 months ago
0
upkeep: create dependabot.yml
#33
jdhoffa
closed
6 months ago
0
style: align style of `git` and `maintainer` files
#32
jdhoffa
closed
6 months ago
0
Use GH-to-ADO instead of GH projects
#31
jdhoffa
closed
6 months ago
0
Branch protection rules vs rulesets
#30
AlexAxthelm
closed
4 months ago
1
Explicitly name `CODEOWNERS`
#29
jdhoffa
closed
7 months ago
0
Point readers to the `resources` repo
#28
jdhoffa
closed
7 months ago
0
Add `RMI-PACTA/developers` as `.md` `CODEOWNERS`
#27
jdhoffa
closed
7 months ago
4
Minor rewording of `README.md`
#26
jdhoffa
closed
7 months ago
0
Define `github` practices
#25
jdhoffa
opened
7 months ago
0
Define `pr-review.md` practice
#24
jdhoffa
opened
7 months ago
2
Define `documentation.md` practice
#23
jdhoffa
opened
7 months ago
0
Consider if we want to make use of the `CODEOWNERS` feature that allows different people to maintain certain files (or directories, or file-types)
#22
jdhoffa
closed
5 months ago
1
Add an explanation in `README.md` that the purpose of this repository is NOT for making assessments of employees
#21
jdhoffa
opened
7 months ago
0
Maybe add to `maintainer.md` – "On any `lifecycle stable` repository Ensure that a minimum of 2 tech staff"
#20
jdhoffa
opened
7 months ago
0
How to handle application configuration
#19
AlexAxthelm
opened
7 months ago
5
Define and document our "release" process
#18
jdhoffa
closed
6 months ago
28
Merge strategies
#17
AlexAxthelm
opened
7 months ago
4
Consider documenting our "Tech Review" process
#16
jdhoffa
closed
5 months ago
9
Consider pointing to our `resources` repo
#15
jdhoffa
opened
7 months ago
0
Create jekyll-gh-pages.yml
#14
jdhoffa
closed
7 months ago
1
Remove old `2DII` document link from the `README.md`
#13
jdhoffa
closed
7 months ago
0
Add guidelines around being a repo maintainer
#12
jdhoffa
closed
7 months ago
24
Define `dependencies` practices
#11
cjyetman
opened
7 months ago
11
Add issues and prs to maintainer project
#10
jdhoffa
closed
7 months ago
0
Archive of publicly documented best practices
#9
jdhoffa
opened
7 months ago
11
Define a practice around the documentation of our metrics
#8
jdhoffa
opened
7 months ago
1
Define a best practice around periodic repository reviews
#7
jdhoffa
opened
7 months ago
0
Define what `lifecycle` stages are, and how we want to use them
#6
jdhoffa
opened
7 months ago
3
Define the roles and responsibilities of a maintainer
#5
jdhoffa
closed
7 months ago
1
Consider how to implement open source governance strategies
#1
jdhoffa
opened
1 year ago
0
The `workflow` and `package` paradigm
#2
jdhoffa
opened
1 year ago
24
Decide what types of practices we would like to align on and document here
#3
jdhoffa
opened
1 year ago
8
Basis for defining some community values
#4
jdhoffa
opened
1 year ago
1