Organisational "buildpack" shower thoughts #59
decentral1se
commented 2021-04-11 16:39:28 +00:00
Owner
> you know we have these apps now but we also have this kind of big-picture organisational strategy stuff too. So, like, imagine we say, Autonomic uses 6 apps to run the co-op. We could distill that down into docs as a sort of "co-op buildpack" or something, no? As an abstraction layer beyond categorising apps (useful but more is needed). If your org needs x,y,z then choose buildpack C (which is just a curated list of 6 apps)
> then you abra buildpack create coop and it wires it all up (this is maybe a dream level of automation)
decentral1se
added the 2021-04-11 16:39:28 +00:00
design
label
decentral1se
commented 2021-04-11 16:41:03 +00:00
Author
Owner
> yeah this kind of thing has been kicking around in my mind.
> step zero: firm up our tech choices, maybe make a blog post about our stack
> easy first step: lists of recommended package combos in the co-op cloud docs
> step 2: maybe adding some options to the installer?
> curl ... | bash -s -- --set-us-up-the-bomb=co-op
> step 3: meta-recipes ("meal plans"? 🙃) in abra itelf?
> abra mealplan co-op
decentral1se
added this to the (deleted) project 2021-04-30 07:31:47 +00:00
Labels
No Label
automation
bug
community organising
democracy
design
documentation
duplicate
enhancement
finance
funding
help wanted
invalid
publishing
question
security
wontfix
No Milestone
No project
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#59
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?