Editorial nits on architecture #3
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "fricklerhandwerk/fedi-goals:architecture-edits"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Depends on #2
Most importantly this incorporates key results as discussed today with @niols and @kiara
@ -1,13 +1,11 @@
<style>* {font-family: sans-serif;}</style>
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
@ -258,0 +160,4 @@
- Integration tests pass for
- Setting up a fediversity hosting environment from a declarative configuration
- Configuring, deploying, and migrating a set of dummy applications
- Code passes data protection audit
idk about budgeting implications of this so originally ended up phrasing this as the more neutral 'check' as i considered it not really my call
@ -9,2 +6,3 @@
We are creating the deployment workflows and service configurations, and curate changes proposed by contributors.
- Developers
- Contributors
this name change invokes our KR phrasing yet ostensibly excludes SHB
As discussed yesterday I don't think the project proposal should tie itself to any implementation detail, or the success of any particular project.
what tying, i'm arguing keeping options open rather than using phrasing that may constrain them
merged now with my nits (given the stakeholder meeting now) addressed in a follow-up commit pending further consensus