decentral1se
commented
6 months ago Dived into this today, idea in development: https://pad.suroh.tk/p/bonfire.coop
Copy/pasta'd over in case that pad goes away:
11-03-2024
present: d1, ivan, mayel
Agenda
- review https://github.com/bonfire-networks/bonfire-app/milestone/55
- discuss specific questions of https://github.com/bonfire-networks/bonfire-app/issues/888
Notes
q: one-to-one or public announcement? another q: how did bonfire find userbase up until now? public outreach, users reaching out to bonfire (open science network have a concrete need) public seems to work well
1-to-1 is still valuable specific networks, people, friends network
mixed approach! public post & go into our network to ask them to fill it out
2 stakeholders for questionnaire:
- tech collectives
- users of the service
$announcement text for the forms
- specify our needs, desires, preferences as bonfire
- tech collectives (TBD in the call, see below (towards actions))
going into weeds
- who are you, website, name, where
- size of collective?
- are you incorporated, legal form, informal etc.?
- own your own server infrastructure? or cloud
- do you have backups and/or monitoring infrastructure?
- costing tiers of hosting, desired income x costs ratio
- small: 5 EUR a month
- medium: 10 EUR a month
- other: you specify
- desired support rates? amount of support possible (per month)
- what guarantees can you provide for ongoing maintenance / upgrade work?
- preferred method of billing:
- up front for the year
- monthly
- 40% up-front, the rest at the end
- specify: ???
- do you have billing capacity, bank account, finance / invoice experience?
- what tech stack do you use? provisioning servers, deploy apps, infrastructure operations specific
- abra / co-op cloud is the preferred deployment tool, would you be ok with using this?
- comment field: e.g. desired training or skillsharing etc.
- do you have capacity to migrate existing bonfire instances?
- do you need budget for project management? how much per month? weekly meetings etc.
- which comms channel do you want to use to connect with the group?
- ok with some of fee being used to support the platform? e.g. development costs
- would you be interested in other kinds of work (users, bonfire): moderation, new feature dev.
- do you have capacity to provide GDPR related documents?
- users of the service broader concept ideas (TBD in the call, see below (towards actions))
going into weeds
who are you, website, name, where
are you incorporated, legal form, informal etc.?
What kind of tech support do you expect? (buy a domain, setup dns, ...)
how much would you be prepared to pay
- small: 5 EUR a month
- additional: backups 3 EUR a month / ?
size of instance, expected users?
do you want a SLA from the tech collective (service level agreement)
- desired response times, written down agreements, matching expectations
what flavours of bonfire do you want to use?
do you own a domain name already? email provider?
do you want the tech collective to set up everything or just parts of it?
- "single source of billing" vs. "several services to pay for"
migrating from existing instance or starting fresh?
- budget for migration?
which comms channel do you want to use to connect with the group?
ok with some of fee being used to support the platform? e.g. development costs
Do you need other types of work (apart from hosting): moderation, new feature dev, designs
do you require a GDPR agreement with the tech collective? (many wont have...)
are you prepared to regularly download data backups, or do you wan the collective to handle off-site backups?
do you expect an online dashboard where you can monitor the status your services, or happy for the collective to handle it and communicate by choosen comm channel?
do you expect an online dashboard where you can self-manage your services, or happy for the collective to handle it and communicate by choosen comm channel?
- bonfire stakeholder (WIP idea...)
- our desires to be realised in the network
- e.g. if users cant migrate then they go offline & its bad for the network
- practically: additional clauses for the collaboration agreement - mutually beneficial
- providing the software, responding to issues & developing the platform
- support / moderation (of sorts) going forward
- improving how collaboration agreement is generated
- bonfire need capacity to do communications in general for this platform
- co-design new features, crowd-funding
thoughts:
- generation of expectations and constratints can come from the user side?
- what is the platform responsibility?
- initial connection between groups and collective
- expectations matching and facilitating agreement
- promote mutual aid between hosters/users in the network
- promote stable & reliable service
- visual aid for what we are imagining would be useful?
- generation of collaboration agreement (as a service)?
- exit agreements
- mutual accountability & responsibilities
- https://www.nycmesh.net/ncl.pdf
- input for consentually registering bonfire instance & supporting collective
(revolutionary) perspectives:
- gettting off corporate infrastructure
- CSA
- avoiding unpaid labour
- owning the means of production lol
- theory of change & how we relate to it - ala https://docs.coopcloud.tech/intro/strategy/
towards actions:
- we are developing the idea more deeply
- we prefer 1-to-1 call to explain the what this concept is about
- a call with a user group and a hoster collective + our concept
- mix of interview & work session
- timeline:
- comms with groups (crabfit + emails): ivan (radio free fedi), mayel (NZ tech collective)
- slides / content: d1, ivan -- text to read in advance, intro, context, visual aid, discussion
- 2-3 weeks for the call: aiming for the first week of april
tools? https://framaforms.org/abc/en/ https://apps.nextcloud.com/apps/forms (requires nextcloud) (asking doug for more) $corporate fancy form tools ?
questions could be simple because some tools don't support all features, e.g. conditional questions
Deliverables:
Questions: