Editorial nits on architecture #3
1 changed files with 3 additions and 3 deletions
|
@ -2,10 +2,10 @@
|
|||
|
||||
kiara marked this conversation as resolved
|
||||
- Maintainers
|
||||
|
||||
The group maintaining this repository.
|
||||
We are creating the deployment workflows and service configurations, and curate changes proposed by contributing developers.
|
||||
The group developing and maintaining this project.
|
||||
We are creating the deployment workflows and service configurations, and curate changes proposed by contributors.
|
||||
|
||||
- Developers
|
||||
- Contributors
|
||||
kiara
commented
this name change invokes our KR phrasing yet ostensibly excludes SHB this name change invokes our KR phrasing yet ostensibly excludes SHB
fricklerhandwerk
commented
As discussed yesterday I don't think the project proposal should tie itself to any implementation detail, or the success of any particular project. As discussed yesterday I don't think the project proposal should tie itself to any implementation detail, or the success of any particular project.
kiara
commented
what tying, i'm arguing keeping options open rather than using phrasing that may constrain them what tying, i'm arguing keeping options open rather than using phrasing that may constrain them
|
||||
|
||||
People with the technical background to engage with our work, and may contribute back, build on top of, remix, or feel inspired by our work to create something better.
|
||||
|
||||
|
|
Loading…
Add table
Reference in a new issue
i feel inclined to add this back in, given it affects the result
oh god, it affects the html yet not the pdf... i hate this, but i'll yield
fixed in
323e520344