The next steps - we will create a form to invite feedback and comment from co-op members and the wider artist community, this will be shared asap. That will form a period of consultation until early January, when the next meeting will take place.
Was the plan for the next meeting to be this Friday? I haven’t seen follow up posts in the forum or publicizing about it on socials – at this point, I’d expect turnout to be low. Do we feel we have enough time to get the participation we were hoping for?
Planned to publicise today with an event and on socials. also inviting participation and feedback via the form for those who cannot attend the meeting.
This is the second meeting, the third was planned for the following week. So there are more ops to join.
At the AGM we announced that there would be a meeting 2022-01-07T15:00:00Z and also next Tuesday. @melis_tailored do you have a preferred time for next week’s meeting?
Does that mean a reasonable time for Europe or Asia? (Not sure we are going to get member feedback.) I was looking to you since you pitched the meeting. Do you want to be there? Early evening in Western Australia, for example would be about 2022-01-11T09:00:00Z (6pm in Tokyo)
Now that everyone has the ability to create forum events, let’s all commit to making calendar events for gatherings, especially public ones.
Without a calendar event, no one can RSVP – and the dates and times can easily be lost in a thread. It took me multiple readings to understand that the meeting was scheduled for Friday at 9:00 AM CST – it seemed to still be up in the air at a quick reading.
I’m happy to meet with anyone who wants to learn more about:
creating forum topics
calendar events
inviting usergroups to events
using markdown to style the post’s information and headers
perhaps this is a forum question but since I probably can’t make it to these meetings, how do I advocate for the supported proposals we discussed and refined previously? For example:
Good question. I’ve been thinking we could do Worker Assemblies every 1-2 months which would be times to take #supported-proposals and organize them into projects/epics.
Alternating between Community Assemblies as places to raise proposals, and then Worker Assemblies as places to launch projects seems a really natural rhythm. Or at minimum, the schedule would guarantee a place to bring ideas and not have them get lost in the aether.
I am fine with the rhythm, but it seems like the purpose of any roadmap is to prioritize those items that end up on the roadmap. I’m bringing up the #supported-proposals so that they actually happen, or if the exec board determines they don’t like a supported proposal, then it changes state to “rejected” or something so that they doesn’t just sit there.
For those who cannot make today’s meeting, you can add to the process with the Resonate Roadmap Survey, where we are gathering additional information and feedback for the process.
Aplogies for not being able to make the roadmap meeting today, but this survey was great to have! Thanks to everyone who was involved in making it, and hopefully a good amount of people were able to fill it out so we can have some useful information to work with for the future. Thanks!
@melis_tailored sorry if I have missed them, but are the roadmap survey results available?
(also fyi, if it helps, our previous survey is still running - may need to stop it? - and has about 200 responses in it which may have some helpful relevance and context - worth checking them out?
See:
It was self-selecting (people who care about the issue) and not a big sample… but maybe useful?