A problem that's been on my mind for a while:
how do I reduce WP-CLI's bus factor, and more generally lay a foundation for WP-CLI's long-term organizational stability?
WP-CLI is hugely important to the WordPress ecosystem. Thousands of developers use it on a regular basis, and tens, if not hundreds, of companies have integrated it deeply into their business processes. Additionally, I deeply value WP-CLI's a-commercial nature (e.g. not necessarily based towards or controlled by a specific company), and think said nature is in large part why WP-CLI has seen the success it has. I am biased towards doing whatever I can to maintain WP-CLI's a-commercial nature going forward.
WP-CLI is also solely maintained by me on a (mostly) volunteer basis. While I don't see this needing to change anytime soon, it is a bus factor I am very cognizant of. Furthermore, we haven't ever had a problem with it, but it would make me feel better if there was a formal organization backing WP-CLI to deal with any trademark difficulties, legal challenges, etc. that might arise in the future.
Prompted by (hugely valuable) research and blogging @nayafia has been doing, I thought it might finally be time to turn thoughts into more of a public discussion. If you'd like to weigh in on specific questions, here are a few:
- Is there a certain type of legal organization structure we (I, along with @scribu and @andreascreten if they want to be involved) should considering forming to ensure the long-term health of the WP-CLI project? Our current governance is essentially nil.
- Would taking donations, sponsorship, etc. through a service like OpenCollective positively contribute to the long-term sustainability of WP-CLI, or negatively impact the project because money has become involved?
- What other open source projects can we learn from, and why?
I'm also interested in thoughts and opinions on the topic broadly, if you have input that doesn't relate specifically to one of these questions. To pre-empt that too — even if I may disagree with your opinion, I do very much value your input.
Personally, I have mixed feelings about getting paid directly for maintaining WP-CLI. By "paid directly", I mean a company donates to WP-CLI as an entity, and I take money from that. One hand, I do like the idea of getting paid to contribute to WP-CLI. But, on the other hand, there are a variety of reasons why I feel uncomfortable about it. For instance, I stand on the shoulders of giants, and think it unfair to make money on what others have volunteered their time to produce. Also, while I can comfortably donate ~5 hours/week of time from my own business towards WP-CLI, I'd feel uncomfortable to consider maintaining WP-CLI a profitable venture (which is what it would need to become if I spent more time on it).
Consider this to generally be an open thread, although we may need to conduct the conversation through some other means if it gets unwieldy.
A problem that's been on my mind for a while:
WP-CLI is hugely important to the WordPress ecosystem. Thousands of developers use it on a regular basis, and tens, if not hundreds, of companies have integrated it deeply into their business processes. Additionally, I deeply value WP-CLI's a-commercial nature (e.g. not necessarily based towards or controlled by a specific company), and think said nature is in large part why WP-CLI has seen the success it has. I am biased towards doing whatever I can to maintain WP-CLI's a-commercial nature going forward.
WP-CLI is also solely maintained by me on a (mostly) volunteer basis. While I don't see this needing to change anytime soon, it is a bus factor I am very cognizant of. Furthermore, we haven't ever had a problem with it, but it would make me feel better if there was a formal organization backing WP-CLI to deal with any trademark difficulties, legal challenges, etc. that might arise in the future.
Prompted by (hugely valuable) research and blogging @nayafia has been doing, I thought it might finally be time to turn thoughts into more of a public discussion. If you'd like to weigh in on specific questions, here are a few:
I'm also interested in thoughts and opinions on the topic broadly, if you have input that doesn't relate specifically to one of these questions. To pre-empt that too — even if I may disagree with your opinion, I do very much value your input.
Personally, I have mixed feelings about getting paid directly for maintaining WP-CLI. By "paid directly", I mean a company donates to WP-CLI as an entity, and I take money from that. One hand, I do like the idea of getting paid to contribute to WP-CLI. But, on the other hand, there are a variety of reasons why I feel uncomfortable about it. For instance, I stand on the shoulders of giants, and think it unfair to make money on what others have volunteered their time to produce. Also, while I can comfortably donate ~5 hours/week of time from my own business towards WP-CLI, I'd feel uncomfortable to consider maintaining WP-CLI a profitable venture (which is what it would need to become if I spent more time on it).
Consider this to generally be an open thread, although we may need to conduct the conversation through some other means if it gets unwieldy.