--- breaks: false --- Data.coop ========= Prompts: * For who is this instance meant? - Members of data.coop: anyone who is interested in support the data.coop association's goals and accept our Acceptable Usage Policy can become a member. * Who is not welcome? Think not only broadly (e.g. no racists) but more subtly.. your friendly but quite boring colleague? - People that are not members (might change) - Members that don't follow our AUP - Members that go against the association's goals - Wider definition of data.coop members can only be done in a forum with all our members - Someone behaving "badly" on a completely different data.coop service will also be banned/blocked/suspended * You know your crowd the best: to what extent does this server need to be a sheltered or a hyper-connected space? - Limited: Only contents from followed accounts are visible - Suspended: No federation at all - None (filtered media and/or reject reports): filters media and or reports * Should people mostly talk to each other as a community, or should they be individuals grouped together who each talk to an "audience" (twitter-like)? How do you facilitate that? - Our audience seems very used to twitter and hard to change their routines, they just do "birdsite as usual" - May change once we get Hometown going, but the group is diverse (in a sense) * How will you recruit new people? How much time do you spend introducing newcomers? - We recruit people by recruiting new data.coop members - General onboarding necessary, but for more than one service - We should consider doing 1:1 personal onboardings * Are you ok with institutional and/or promotional accounts? Are you ok with automated posts (bots, Twitter cross-posting, blog to fedi bridges, etc)? How does that decision affect the (community) experience you are trying to build? - Promotional accounts OK to a limit if they are aligned with data.coop's goals. - Delegated responsibility for members that give out organizational accounts (pending board approval) - Automated posts: undecided - is it risky to allow this, might other instances then block us? * What size server are you planning for? Your immediate friends? Your association? Your co-workers? Your association + some others? Your city? - Maybe 20-100 accounts, our association + a few aligned organizations - <!--World Domination!!!1--> # Day two, block 6 > Prompt: > Who is the team? Data.coop has a sysadmin team consisting of trusted members chosen by the board. In addition more moderators volunteered from the board; subject to change. > What are the resources / strengths in the team? Who is enthusiastic? Who is a good communicator? Who is technically very proficient? Who is a good fixer? Who has a lot of money? Who has a lot of time? ... > Which resource is the most scarce? (time, money, computation, bandwidth, etc) Time is definitely a scarce resource among the sysadmin team. > Who can take over if the one doing the task really can't or doesn't feel like it? The sysadmin team consists of three members that support each other. The board can pick new sysadmins if needed. > How are things paid? Which things are paid (i.e. what are your priorities)? What rate? Things are paid by the association through membership fees. Domain renewal, server hosting and **bank fees** is what we pay for at the moment. Sysadmin work and other labour is not compensated at the moment. Compensation would require more members to fund paying out, and at the moment we require some members to pay more than the nominal membership fee to pay for the server costs and bank fees. It has come up that it would be more sustainable to pay for the labour. > How much work are you willing and realistically able to put in? The work put in varies *a lot*. Sometimes the work is neglected for many months and then we see somewhat intensive sprints at other times. The work is as mentioned unpaid and volunteer based, and we expect people to work when they have time and will. > How do you take care of the ecological footprint? (computational limits, recycled repurpose hardware, so-called green datacenter) Our two servers are both bought second hand. We run only one of the servers at the moment due to power usage (both energy waste and cost). > Note: we will look into server infrastructure mapping later today, for now just focus on resources > (machinic, humans) and financial/environmental/labor sustainability consideration and ethics. ## Day two, block 7 Prompts block 7: > * Does your group have already established norms and guiding documents that you could rely on? Yes! We wrote an Acceptable Usage Policy that also covers desirable and undesirable behaviour. It is only available in Danish at the moment: https://git.data.coop/data.coop/dokumenter/src/branch/master/Acceptable%20Usage%20Policy.md > * What kind of behaviour do you want to see? * Show empathy and compassion for other people. * Respect other people's (non-oppressive) opinions and values. * Be constructive and respectful when giving feedback - both towards data.coop and others. * Take responsibility - and if the situation calls for it apologize for our mistakes. * Focus on what's best for all of the association and not on individuals. * Actively participate, to the degree that you want, in the social and professional(?) environment of data.coop > * What kind of behaviour do you not want to see? * Sharing offensive(?), pornographic, etc content * Spamming * Denial of Service attacks * ACcessing other members' data without consent * Trolling, offensive or demeaning comments, personal or political attacks * Harrassment, in public or in private * Publishing other people's private information such as physical address or email address without explicit consent * Promoting things that within reason can be seen as fascist, racist, sexist, homophoboic, transphobic, militaristic, and similar > * how do you take the first step to ensure that you are creating a space where your community feels safe? which safeguards should be put in place? We make sure our members know our bylaws and AUP. > * how do you take the different relations of power within your own community into account when writing these document? > * Which things are you promising, do you have the resources to make good on those promises? > * Look back on block 4 & 6 and modify the above accordingly? > * Start drafting COC, TOS and Privacy statement # Day two, block 8 > Prompts block 8: > > * How are your CoC and TOS accomodated pro-actively/preventatively? > > * How is the CoC enforced? Who does that? > > * Who are admins, who are mods? How are they reachable? > > * How do you assist each other with grey/vague issues regarding moderation? > > * Is there a group account for mod/admin or individual accounts? > > * How is the place governed in theory? How is it in practice? > > * How explicit can you or do you want to be about how things are enforced and directed?