I personally don’t care about the language used. Yet, the reality we’re dealing with is it matters to those we’re hoping to help.
There’s a strong aversion to words like “manager”, “leader” and “owner” in the decentralized and open source world. That’s why I’ve been thinking about terms like “coordinator” and “orchestrator”.
@noot @cosmosys, @ricmoo, @yuetloo and I spoke about this last night after our meetup. The fact that there is such clear aversion to the terms that you mentioned means that we have to care about our language. We can say semantics don’t matter but because people care about them I will go along with it. Yet this does not actually change our actions even if we call ourselves coordinators. I have never managed one of our projects, I have worked with people to make sure they are able to manage themselves. Human beings are perfectly capable of self organization, we just need to make sure that entrenched systems, processes and language does not stop them from being able to achieve their defined goals. That is why I think this ring should be more focused on studying development cycles as I voiced at the council of Prague when @cosmosys organized the ring. However if I am the only one that feels this way, I am not looking to cause any trouble. Just reflecting on lessons learned during my brief stint in university about how important semiotics are within the context of communication.
Who are Product Manager and what kind of product do they manage?
How are you going to fulfill their decisions in decentralized community?
Sorry, can you elaborate on your question here, I am not sure by what you are trying to ask.
While I agree that on a practical note, it doesn’t matter. However with Aidan’s point on language, I definitely agree that language matters a lot, especially with dealing with all sorts of backgrounds, esp. with those who may not understand the role of product managers and don’t understand how PMs don’t really ‘manage’ people. (well product managers do and they don’t in MANY ways.)
But on the other hand, I personally think people need to be managed/guided and a lot of people also WANT to be managed/guided (if you have experienced great management, you know what I am talking about ~ great product leadership makes the whole team happy and productive - and most importantly WIN together as a team) We shouldn’t shy away from calling it product management just because there are aversions to not wanting to feel to be ‘managed’. (In many cases, my hypothesis is that these aversions are the result of extremely poor management and sometimes complete lack of product management in some cases). But yes, happy to put this aside for the great good so we can share more of the PM love. 
I think such aversions can be remedied and also part of our effort to improve the coordination of various teams in the space (which potentially starts with the conversation of “So… What is product management? What is it not?” my guess is that many are not aware, PMship can be arcane at times).
For those reasons, I can see both sides to why we should keep and also change the name. I lean towards keeping the name but I also agree that a different name could provide significant social advantages. Happy to keep the name but also happy to align with a new one if there is rough consensus.
Will you manage independent teams in ethereum space?
How will you do it if they do not like to be managed?
I don’t see how it could work in our anarchistic space…
Unsure if it is true in our space by itself. I see our community as quite leadership resistant 
It is this lack of clear distinction of what a PM does that creates barriers when trying to coordinate development cycles IMO. We have the opportunity to take the lessons learned from principles, frameworks and processes of the traditional PM role and define it more accurately for web3.0. Let’s take this as a positive opportunity to do things better and never create an image of management!
I agree with @Ethernian, some people may want principles, frameworks and or processes but if there is a need for management in the development cycle than IMO our principles, frameworks and or processes are not good enough.
Yes. Great point. We should be cautious with management patterns.
If we take it seriously, we could find people who is able manage communities and then create “guidelined and best practices” based on their experience. Leadership is not easy to formalize, but I don’t know another way to go.
+1 Agreed, we can make it much better
Leadership isn’t about just one individual in a team. It is about everyone! This comment maybe be from my own experience with other engineers and my own preference back when I was a designer. I really enjoy great product management - allowed me to focus on what I am good at. I believe our definitions of management differ! But happy to agree that we disagree But nonetheless, I do see where you are coming from and agree your comment on the the anarchistic sentiment of the community.
+1 Bingo 
I guess this is where the magicians and our group comes in. I really want to drive more conversation on how we can better coordinate and conduct product management in this space. First step is sharing and learning from each other
Hey y’all! I’m a product manager at Status and would love to join and talk product. Kudos for bringing us all together.
Hey sent you a message! more deets there
Hola, I’d like to join in on this one. Have you a cal link?
hey! just PM me your telegram handle 
Hey, I just caught up on all this - super exciting and I’d like to join as well.
Thanks a lot for pushing it @pet3rpan!
Interviews on product management in the web3 open source ecosystem is super insightful. I’m happy to provide some info on how we work at Gnosis.
Threw you a message on telegram. Cheers!
Hey just reading up on the thread and this is very exciting. I’ve been working on project management with the Whiteblock team and am actively learning more day by day. Would love to be involved in the discussion. Thanks for organizing @pet3rpan
I just joined the Geth and Swarm teams at the EF as a PM and I’m experiencing new types of challenges, resistance. So I find this ring really exciting and potentially helpful. I’d like to join the call too.
Great discussion in this thread, thanks for kicking things off here.
Recent history - In Feb 2013 the Swedish pirate party shared it’s “swarm” organisation method, there was a ted talk on this too. Some links…
A few points mentioned in the thread that I’d like to further:
Naming is important
Starting by clarifying PM is product management (not project management). Both are important, but starting with defining terms like: product, management, and users. Then defining what problem PMs would like to solve
Decentralised management
Can come across as an oxymoron, so roles like motivator/coordination-assistant might work better. In this space I feel that managers can serve projects well with “management suggestions” that are backed by data/experience, and then it is up to the developers to opt-in to one
Coming from several angles here (Engineer, educator, and PM) my 2c cents with points of value: leadership through doing, encouraging an open-environment with autonomy, and creating a roadmap that is backed with experience and data.
Lastly, is the Telegram group intentionally hidden, or can a link be shared?
Thank for the clarification. The reason why we use product management is because there is much more to it than just project management - it’s important to make that distinction - it’s not just development cycles, it’s not just coordination
And yes, I am intentionally not sharing the link out into the public because public join links kill telegram groups (seen too many groups go down this path + admin a few other telegram groups). Rather have it stay high quality and grow organically.
Caught up on some reading and there were some great points in a few places.
But primarily from the original SODC thread, Self Organised Development Cycles.
and thought this was well summarised:
Would love to hear from long-established open-source projects and how they guide products, and thoughts on possible differences with web3 products.
Also making the distinction between consumer products (user = layman), vs protocol “products” (user = developer).
Absolutely agree. Its definitely on the list of things to do ~ but I am only one person doing this on the side Currently I am exploring the problem more, gaining greater understanding our own problems before looking at possible solutions. I foresee a bigger focus on such frameworks maybe later when we begin moving into the realm of trying to solve things.