@boopboop @brndnkng @sganesh @Hakanto Hey guys, just to get this moving, let’s schedule in our first call for next week at 2021-09-15T01:00:00Z → 2021-09-15T02:00:00Z. We can potentially change that if it really doesn’t work, but let’s set it as that for now.
In between now and then, here’s a longer description of what we’re going to be doing here.
This group will have a practical focus. As mentioned in the OP (“Original Post” in a topic, i.e. my first message), we’ll be working on
- Site Administration
- Software Development
- Relationship between the community and the co-op membership
Each of these items touches on some broader themes, however the focus in this group will be on the pointy end of things where we’ll be changing some settings, writing some code and helping to run things on the community
On the terminology of “Community” v “Forum”, we’ll use “Community” as our work may sometimes go beyond the bounds of the Discourse Forum per se, onto other community software platforms. For now it’ll be focused on the Discourse Forum.
Where we will work
There’s three main places where we’ll work
In the Resonate Community Forum category. This is for
- Posing ideas
- Developing plans
- General discussion
In our weekly (or fornightly, or monthly, depending on what we decide) meetings. These serve as a “check-in”, i.e. to touch base on what’s going on, to keep a sense of momentum about what we’re doing here, and to deal with any issues or questions in realtime
In github, for community-related development efforts, for example Disocurse themes and plugins, or identity services (i.e. the ID server will be relevant to community deveopment).
How much work will be involved?
This is relative to how much time you have, and what our tasklist looks like. We’ll be looking to set a clear community work agenda here. That will give you a sene of what work needs to be done, and how you can best spend your time to contribute.
In other words, see how our task list develops over time and think about how you want to best apply your efforts. You may feel that this kind of work isn’t for you and you want to apply your efforts elsewhere in the co-op. That’s also fine
One note I’ll make here is that in the near future we’ll be launching both two “Advocate” programs: Community Advocate and Developer Advocate, which some of your may be eligible to apply for and will involve certain benefits, including a small amount of compensation. One of the things we’ll be talking about as we go here is how to best recognise voluntary efforts in the cooperative.
What’s our initial agenda?
We’ll be setting our agenda in our first in-person check-in, but here’s what it will likely include (suggestions also welcome)
Forum UX, in particular the user funnels. The Discourse forum is used for multiple purposes. We have started to develop user funnels that direct people to different parts of the forum depending on their purpose. We need to keep developing that, including adding things like analytics.
Forum Design. We’re rolling out a new design update as part of the Resonate Re-Launch. This currently is being worked on for the website and player. We may need to apply some of the same designs to the Community.
Forum Visibility. We’re planning to make parts of the forum public. This has been summarised nicely by @Hakanto here we need to continue that effort and flesh out:
- which categories are going public
- what stakeholders to we need to explicitly reach out to before we pull the trigger
- how this interrelates with point 1 (i.e. the user funnels)
Group management. We’ve started to use the group system in Discourse to manage different aspects of the cooperative. We need to think though our approach here in a more systematic fashion so we’re not leaving anyone out of the loop, or missing any opportunities to improve the way we work and cooperate
Diversity. As it is already an important nexus for the cooperative, and will be more so over time, it’s important we keep the values of the cooperative a first priority in the way we administer the community. This may mean a few things in practice, e.g.
- should we add identity signifiers into community profiles
- how do we improve usability for non-english or non-english-as-a-first-language users?