Maybe we can exchange some thoughts about this, because i feel some tension between the core team and sporadic contributors like myself. I want to make clear the enourmous effort you put in, and recognize that AP is a huge amount of work. At the same time my experiences with PRs for AP (i have also contributed to other, arguably smaller scale projects) has not been nice and is a major factor for my seldom contributing. I consider that i might be out of line and would appreciate your thoughts on this.
Communoicationwise it get a strong hierarchical feel between the core team and infrequent or new contributers. I know its annoying to repeat stuff or to have to explain things you know because of insides from your contributing history. I also get a strong german “every little detail has to be mapped out beforehand”-vibe. Which leads to endless discussions over even minor one-line changes and results in (overly) strict style requirements. All of which run againt a more creative, organic workflow that comes more natural to people like me.
I did a few minor UI/UX tweaks that i feel like turned out to be great and proofed really use- and impactful - but where preceded by hours of unenjoyable discussions and reformating to meet core team ideas/conceptualizations and style requieremnts.
I want to reiterate, that i see the huge amount of work all of this is and the effort you put in.
My feeling is that the communication could be enchanced and top-down requirement loosened to make contributing easier and more enjoyable, which in turn might lead to a better sharing of the workload (more contributing/-ers!) and quicker and better progress.
If i may say so, i see potential for a more effective project-management, especially in regard to communication. I think it is a vicous cycle, the core them (which seems to be @ByteHamster, @keunes, @tonytamsf, @Matth78) is doing so much, that communication can seem like an extra burden. But that might be what is keeping off infrequent or new contributers (i know this to be the case for me).
Effective Communication shouldn’t and doesn’t have to be a burden. It should and can help to share tasks more effectively and reduce unnecessary or duplicate work.
At the same time, in order to break this cycle, i believe the core team needs to let go of some felt responsibility and (learn more) to practice satisficing for solutions they didn’t work on and dont want to work on (and don’t have to).
I know this is a long statement and while i tried to phrase it esteeming/appreciative as well as contructive, i know this is a harsh critique of the status quo. So please read it carefully, be open, judge it fairly and be honest about what your answers are.
I worked for years as a part-time iOS/android dev in a startup. I recognize these patterns seeking to avoid, it goes like this:
do we really need this feature?
It would be way to much work ;(
But do we really really need that feature?
And so on.
It kinda works when I was working alone, if I said I’m not working on it, it’s not getting done.
For AP it’s different, firstly we work on (some)things we want to do ourselves and if I propose a PR I have already done the work and if I only give an idea for a feature I must hope someone is exited about it as well and takes over or do it myself. And there is a need for more effective communication the bigger the team grows. The hierarchy and style/structure requirements feel maybe to strong to only contribute from time to time to be, but I’m also just a part-time/hobby dev. But I feel like it would be nice to have a pool of people that do a little bit when they have time instead of the core team having to lift such heavy loads.
We need structure and style but it must be workable and the focus must remain on getting the code out. That requires discussion and communication and I feel there’s potential to improve, as well as sharing responsibilities and decision making more