Great post. I'm going to change the word "Constitution" to "Consensus". I don't want a formal document, just an agreement on a guideline of responsibilities moving forward.I tend to be skeptical of any effort to make a decentralized project like Dash too formalized, which this constitution idea seems to want to do. Let Dash develop organically (which will include some overlapping responsibilities and clashes at times).
A few random thoughts on the matter:
Okay, I've rambled on longer than I planned, so I'll shut up now!
- I don't like the term "core team" myself, probably because of my opinion of the Bitcoin core team. I prefer to call them the "development team." Their primary duty is to develop the code, and, as I understand it, anyone can contribute code, but only Evan (anyone else?) can approve it. I see no problem with this; if you don't like it, fork the code!
- At this stage in Dash's lifecyle, Evan has an outsized influence on the direction of the project, which is natural. If you look at projects like Linux or Bitcoin, this is how they started as well. Eventually Evan might get tired of the project or he comes up with a few bad ideas and gets pushed out, but until then, this is what Dash is.
- The development team does just that: software development. They are not in charge of marketing or third-party apps or things of that nature, and I'll imagine they don't want to be. (BTW, I admit that other than Evan and Andy, I can never remember who is on the development team.) There is no need for other efforts to go through the development team for approval. For example, before publishing the recent article I wrote for Dash World, I asked Evan to check it for factual errors and to give me a few quotes (which he graciously did). But I didn't ask him his opinion of the article or what it should be about, because, frankly, that isn't his responsibility. Let him be the lead visionary and dev, not the lead marketerer, copywriter, web designer, etc.
- I know the "team" listed on the dash.org website includes a marketing guy and business development guy, but I don't see them as the final arbiters of all Dash marketing and business development, as is the case with Evan and software development. I assume they get paid from the blockchain, but that just ensures that *someone* is doing marketing and business development, not that they are the *only* ones doing it. But anyone else can do it as well, and as we have seen with Dash World, they too can be paid by the blockchain!
- Regarding the official website, this seems to be a sensitive issue with all cryptos. The website initially gets set up by the development team, and then they have control over it, probably longer than they should. Really the website should be controlled by marketing people not dev people. But I understand that this transition can be tricky.
- Someone in this thread said something about letting the majority decide the direction of the project. If you mean by that the Masternode owners, okay, but in many cryptos this means the loudest voices on the forum or reddit. With Dash, all that should matter is Masternode votes.
- But I don't think Masternode owners should micromanage the development team. If the dev team takes the project in a direction the Masternode owners don't like, there is a solution: simply stop paying them, and start paying another development team. Then move your masternodes over to the new implementation. I don't think the MNs should be voting on every new concept Evan and the dev team comes up with.
- That being said, I do think it important that Evan and the dev team take into consideration the feedback of the community. I don't see any reason to think they don't do this currently, however.
I tend to be skeptical of any effort to make a decentralized project like Dash too formalized, which this constitution idea seems to want to do. Let Dash develop organically (which will include some overlapping responsibilities and clashes at times).
A few random thoughts on the matter:
Okay, I've rambled on longer than I planned, so I'll shut up now!
- I don't like the term "core team" myself, probably because of my opinion of the Bitcoin core team. I prefer to call them the "development team." Their primary duty is to develop the code, and, as I understand it, anyone can contribute code, but only Evan (anyone else?) can approve it. I see no problem with this; if you don't like it, fork the code!
- At this stage in Dash's lifecyle, Evan has an outsized influence on the direction of the project, which is natural. If you look at projects like Linux or Bitcoin, this is how they started as well. Eventually Evan might get tired of the project or he comes up with a few bad ideas and gets pushed out, but until then, this is what Dash is.
- The development team does just that: software development. They are not in charge of marketing or third-party apps or things of that nature, and I'll imagine they don't want to be. (BTW, I admit that other than Evan and Andy, I can never remember who is on the development team.) There is no need for other efforts to go through the development team for approval. For example, before publishing the recent article I wrote for Dash World, I asked Evan to check it for factual errors and to give me a few quotes (which he graciously did). But I didn't ask him his opinion of the article or what it should be about, because, frankly, that isn't his responsibility. Let him be the lead visionary and dev, not the lead marketerer, copywriter, web designer, etc.
- I know the "team" listed on the dash.org website includes a marketing guy and business development guy, but I don't see them as the final arbiters of all Dash marketing and business development, as is the case with Evan and software development. I assume they get paid from the blockchain, but that just ensures that *someone* is doing marketing and business development, not that they are the *only* ones doing it. But anyone else can do it as well, and as we have seen with Dash World, they too can be paid by the blockchain!
- Regarding the official website, this seems to be a sensitive issue with all cryptos. The website initially gets set up by the development team, and then they have control over it, probably longer than they should. Really the website should be controlled by marketing people not dev people. But I understand that this transition can be tricky.
- Someone in this thread said something about letting the majority decide the direction of the project. If you mean by that the Masternode owners, okay, but in many cryptos this means the loudest voices on the forum or reddit. With Dash, all that should matter is Masternode votes.
- But I don't think Masternode owners should micromanage the development team. If the dev team takes the project in a direction the Masternode owners don't like, there is a solution: simply stop paying them, and start paying another development team. Then move your masternodes over to the new implementation. I don't think the MNs should be voting on every new concept Evan and the dev team comes up with.
- That being said, I do think it important that Evan and the dev team take into consideration the feedback of the community. I don't see any reason to think they don't do this currently, however.
what really matters is how the development team is defined (who determines who is in it?)
the relationship between the development team(s) and the other entities (masternodes, miners, merchants,...etc). If the masternodes don't like the project direction, is de-funding the dev team really a solution though? I'm trying to imagine what would actually happen in such a scenario. And we absolutely do need to protect against giving power regarding the direction of the project to squeaky wheels. How do we decide which project direction/conceptual issues get voted on, or which ones get opened up for feedback before the dev team starts coding it?
The distinction between marketing team vs. development team is a great point that I'm interested to hear more about. The issue with the website was one of the key points of contention in the Slack channel earlier.
@ericsammons - excellent points.
I agree on all points, except on one thing, and that might just be due to semantics. Website controlled by the marketeers.
Who are the marketeers?
What qualifies one to become a marketeer?
How can this be verified?
Who elected them?
Who do the marketeers answer to?
What if the marketeers decide to market the project in a totally different angle as the founder and lead dev?
What happens when marketeers clash in ideals, each furiously wanting to hammer their own vision?
Is there a master-marketeer? Who, and why?
If there is, isn' that centralisation? What's his role?
If there isn't, who mediates conflict?
All good points. Like I said, the website can be a bit tricky.
In an ideal world, the official website for any crypto should eventually be handed over from the development team to a marketing team. When and how that occurs would depend on the crypto in question and where it is in its lifecycle. In the case of Dash, I think it would be appropriate to be confirmed by a Masternode vote. But in any case, the marketers chosen would be trusted by the community (thus, the MN vote) to present the message of the crypto to the world. But I would also think it wise if someone from the original dev team (such as the creator of the crypto) maintained access just in case that trust were to be broken down the road.
Is this centralization? Possibly, but if so, I don't see how it can be avoided. There is only one "official" site, and I don't think it wise to have multiple parties maintaining that one site concurrently.
BTW, I am not saying anything against the current webmasters; in fact, I don't even know who currently controls the website!
Yes!Ohhh... Just realised that you probably writing about business controlling content of the website and not the website from technical standpoint.
@ericsammons - excellent points.
I agree on all points, except on one thing, and that might just be due to semantics. Website controlled by the marketeers.
Who are the marketeers?
What qualifies one to become a marketeer?
How can this be verified?
Who elected them?
Who do the marketeers answer to?
What if the marketeers decide to market the project in a totally different angle as the founder and lead dev?
What happens when marketeers clash in ideals, each furiously wanting to hammer their own vision?
Is there a master-marketeer? Who, and why?
If there is, isn' that centralisation? What's his role?
If there isn't, who mediates conflict?
Now, I'm not writing this directed to you in particular Eric, but as a general answer to this thread. To think that any project, especially a decentralised one like ours can work with a 100% hands-off, free for all, structure free, responsibility free environment is utopia. Only chaos can emerge. And again, why with 12.1 Evo, Sentinel and onwards, the need for further formal structure is needed.
We listen to the community. There are numerous threads since forever discussing ALL aspects, including the website. Some points are taken into very serious consideration, other are considered but discarded as they are not aligned with the direction intended. All points are considered, always!
Just because someone is talented and experienced in any given field does not automatically give them instant privileges. I prefer someone less qualified to develop a project fully aligned with the original vision, than a super proficient someone that is going to steer it out of path just because they think it's best thing to do. Not pointing fingers at all - just an example
Which brings me to another point. I have no clue what happened in Slack, nor do I want to, as it seems it's just another episode of a common situation. Someone has a strong opinion about something they are knowledgeable about, their point is heard but not instantly adopted, they throw a fit and start arguing, then realise they're not going to get anywhere with it, and throw a tantrum in rage. Am I close enough?
If that is even slightly close to what happened, it's sad. How many gzillion times have I been very vocal about something that had zero effect? I lost count. I never took it personally or make a fuss about it. If people cannot behave in a mature fashion and agree to disagree, only toxicity develops, and nothing good comes out of that.
On the other hand, people who consistently contribute in a positive, prolific and communal way, are ever more invited to participate in more sensitive initiatives and decision making, like the website. We started as a group of 3 or 4, we're now more than 28 in that particular development group. Not all doing the same thing, each contributing with what they know best. For instance, I did info-architecture structure right at the beginning, but right now just watching on the sidelines as I have nothing valid to add at this stage, until I do again. I may give my opinion, but at this point that's it.
Is @fernando the best web-dev or webmaster on earth, or even within the Dash community? Certainly not. Is there anyone more trustworthy than him to hold access to the website's backend? Certainly not. See where I'm trying to get at here?
The way Xcoin/Darkcoin/Dash has been self-organising has been continuously and gradually morphing, never has there been a radical change. So I don't understand what doubts are being risen here. If anything, it's lack on structural understanding on how this project is edified.
Threads like these only serve to confuse and divide. The roles and dynamics are very clear. There have been moments of shift and doubt, but certainly not at this point. The "rules" have been laid out already, whoever agreed participates, whoever doesn't is not forced to either.
Dash Nation started as a welcome thread that got stickied as a very positive community welcome thread. Now it's being referred to as something more official, or worse, as being corrupted/hijacked from some sort of a community driven project. This will only confuse newcomers.
Self-organised initiatives are great, the more the merrier! Just as long as they don't pretend to be something they're not. The only result is conflict and confusion.
.
I was on board all the way until the 3rd to last paragraph. The roles and dynamics might be clear to the people who are on the innermost circles in the project development, but they aren't always clear to those of us who aren't, or who are looking to contribute in other ways. Even though yes we have a development team, I think it's a good thing to have essentially anyone who wants to bring things to the table, to be able to do so and to feel like they are being fairly treated, respected and listened to, even if ultimately their idea is shot down or if they don't get their way. In this case, even if it may not have been the *intention*, the result was that some people felt like the dev team was deliberately ignoring or working against people.
The dev team obviously can't be spending all their time chatting it up with the community for every little thing, but I think this can be improved. There are a lot of people who are passionate about the success of the project and we should hope to retain these individuals and make the expectations clear so that we make best use of the resources we have.
I'm not really following about what you mean by "official"? I don't think what we are trying to accomplish is necessarily the same thing as what you are thinking of.
Let me give you one example so you know where I'm coming from.
@GreyGhost and the Dash World proposal did a report on dash.org SEO. The Dash World proposal passed by the DGBB. Now, @GreyGhost is requesting access to the official website to perform his recommendations. He is not core team, should he be making changes to the official website? I say yes, because the Masternodes voted the proposal in. Now if you believe in the "core team" and community, you would say no because he is not core team. Ambiguous. See what I'm getting at? This is just one potentially distracting example going forward. That's why we need clearly defined roles in Dash Nation.