Editorial nits on architecture #3

Merged
kiara merged 8 commits from fricklerhandwerk/fedi-goals:architecture-edits into rewrite 2025-06-13 08:40:44 +02:00
Contributor

Depends on #2

Most importantly this incorporates key results as discussed today with @niols and @kiara

Depends on https://git.fediversity.eu/kiara/fedi-goals/pulls/2 Most importantly this incorporates key results as discussed today with @niols and @kiara
fricklerhandwerk added 15 commits 2025-06-11 18:06:24 +02:00
kiara approved these changes 2025-06-11 22:23:52 +02:00
@ -1,13 +1,11 @@
<style>* {font-family: sans-serif;}</style>
Owner

i feel inclined to add this back in, given it affects the result

i feel inclined to add this back in, given it affects the result
Owner

oh god, it affects the html yet not the pdf... i hate this, but i'll yield

oh god, it affects the html yet not the pdf... i hate this, but i'll yield
Owner

fixed in 323e520344

fixed in https://git.fediversity.eu/kiara/fedi-goals/commit/323e5203449ae04fa69616c64c6c7d807eeaf3c7
kiara marked this conversation as resolved
@ -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
Owner

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

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
kiara reviewed 2025-06-12 10:18:07 +02:00
@ -9,2 +6,3 @@
We are creating the deployment workflows and service configurations, and curate changes proposed by contributors.
- Developers
- Contributors
Owner

this name change invokes our KR phrasing yet ostensibly excludes SHB

this name change invokes our KR phrasing yet ostensibly excludes SHB
Author
Contributor

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.
Owner

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
kiara merged commit 53af240ccf into rewrite 2025-06-13 08:40:44 +02:00
kiara deleted branch architecture-edits 2025-06-13 08:50:38 +02:00
Owner

merged now with my nits (given the stakeholder meeting now) addressed in a follow-up commit pending further consensus

merged now with my nits (given the stakeholder meeting now) addressed in a follow-up commit pending further consensus
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: kiara/fedi-goals#3
No description provided.