NOTICEThere seems to be a problem connecting audio through Chrome. You might try Safari or another browser.
The next roadmap meetings are:
Tuesday 11th January - meeting 3 - time TBC
Friday 14th January - meeting 4 - time TBC.
NOTICEThere seems to be a problem connecting audio through Chrome. You might try Safari or another browser.
Further to the @executive meeting yesterday, we need to embark on some urgent work to facilitate and formalise the resonate roadmap.
The roadmap is the vision and plan for the platform and community. Both itās immediate future and in the future. It encompasses the urgent needs of the platform right up to eventual goals, tech specification and priorities, development of the co-op and our growth, associations etc.
The goal is to create a vision for us all to follow, alongside a more practical working document in the traditional platform dev roadmap sense that will allow us to more clearly see what is needed for the business development at each fork in the road.
It is advisable that the @executive are all present for this process (@angus involvement tbc), as well as the members of @Story any committed @directors members and any members of the resonate community at large - artists, listeners, workers - who would like to shape resonateās future.
I also really appreciate these types of initiatives. Unfortunately, I could only stay for the first 45mins or so, so if it would be a distraction if I left early, I completely understand holding off until I have more time. If not, I will definitely try to be there on the 14th for the first half of the meeting!
The code for todayās roadmap meeting 16:00 CET is
Suggested agenda for todayās meeting - ROADMAP MEETING 1
Strategy -
Designation of different areas of the roadmap - eg
platform/ product development
community
co-op/ governance
customer service & communication
board
music and content
payment/value
Finance
Comms
Fundraising
Ideas -
collective patronage, audio content, intercooperative vision, community credentials etc.
artist habitat - aka artistspace - the space resonate occupies and will occupy in the music platform/distribution/independent space in the coming years.
digital dignity
longterm stewardship - exit to community
disruption
tools
Features and requirements -
platform - artist uploader, bulk uploader, reporting, artist dashboard, payments, payment options, downloads, tokens, wallet integration
community - customer service team, artist team, industry team,
legal - merlin
Designating leads -
Milestones - key dates
Organisation of EPICS, fundraising, communication etc.
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.
