@flohack - yeah I respectfully disagree but see where you are coming from. For the sake of the community, I think this is a great conversation to be had since it would be helpful for others to examine (or re-examine) their own unique circumstances and tolerance levels that impact commitments to projects.
As a general rule of thumb, progress > perfection....and 100% agree with you. Compromise will always be needed to move forward in projects like this. Of course, just like with anything, there are always exceptions. For me, when over a course of a period you ask for basic things (like embed codes / unique tracking links to measure our efforts for financial sustainability campaign that never happened) and they go ignored, it becomes pretty challenging to tell yourself "Well, it is a compromise, you can't have it all!". The trust and belief of those making decisions begins to diminish when thinking about compromise. After all, you could only get ignored on telegram for so long. And when you do get a word, it is completely out of left field and mishandled with no room for discussion.
On your point about not being happy with a lot of things....this may sound funny but, I would be happy to be unhappy if folks on the marketing team at the time knew our cases were heard, considered, and met halfway...and discussions were going on in a transparent manner...and not just with those who had more access to Marius than others...
So, to summarize, it is hard to ask and reach a compromise without conversations
And I think that is a healthy marker for deciding to step away from something, especially when you are doing it as a volunteer position.
@Flohack , your experience might be different given your position. I understand that in this early stage in the project, those touching core technical components probably have more "time at the table" to discuss things and have a healthier more robust back and forth...that was certainly not my experience (and also, based on the @twinkybot 's post, not his either).
So, for the community, it is important to:
-
Know what are your own personal "deal breakers" are. For me, it was long periods of little to no communication and mishandled communication (which, by the way, caused mishandlings of my own).
-
Voice all concerns appropriately, and know what personal timetables you have before moving on to another issue worth fighting for, or moving on altogether.
-
Seek to find ways to support in more ways that are not "fixed point" (projects that are time-bound)...but can happen whenever and however (promotion on social media for example). Or even financially....or encouraging others to donate (which I think could happen more often).
Lastly, I just have to add this in there, this is a point that really made me scratch my head...
"As soon if you feel personal frustration you are doing it wrong."
Again, just my opinion, but I personally feel this is the completely wrong way to look at it...this might be your case, for you...which I am happy for you about....but I can't imagine this being the case for everyone...esp. those who are passionate about projects that are so important, like this one.
On a more macro level, I've seen some of this from some segments of the gnu/linux community....on one hand, they cry about not having enough options for free or open options for linux on mobile, the outcry for privacy and having control of our devices, etc etc....yet, so lax on discovering ways to improve our methods or models for scaling and sustainability...like, why would you NOT rush to discover industry best practices and not seek the best help in implementing them in a healthy way to speed track advancement? I am sure I am not alone when I say we are tired of projects being too little too late, meanwhile, proprietary solutions make the next leapfrog (e.g. Samsung - DEX). Even if it isn't the exact solution, it keeps people from looking elsewhere.
I don't know about you @Flohack , but when Canonical announced they dropped convergence, UT, and convergence overall, it crushed me, but then FIRED ME UP to do something about it. So yeah, I'm going to be a little frustrated if I find that those who are in the best position to do the greatest good in this area are fumbling a bit in certain areas...e.g. using becoming a foundation as a reason/excuse for not engaging in year-round funding initiatives or hiring more full time or part time devs.