Replies: 3 comments 2 replies
-
@beatboxchad - Moving our comments here because they were not a question or reply with projects to issue #278 On 3/7 you wrote:I'm willing to work on Equalify Everything and web accessibility, but not willing to evaluate the codebase/issues and prepare an estimate/proposal for free. You can do lots of big-time commercial consulting on top of this OSS product -- I'd guess that web accessibility is a regulatory/compliance issue (especially in the EU), which means there's probably an under-served pool of large corporate clients. Anyone who spends time on this tool deserves to be compensated for that time, and that classic business model can support the expense. If I was a consultant in this area, I'd be more willing to make a personal investment. Meanwhile, I've got something burning on my mind that I'll share here in the spirit of the previous comment (click to expand):
|
Beta Was this translation helpful? Give feedback.
-
@beatboxchad said:
In reply to my comment. |
Beta Was this translation helpful? Give feedback.
-
In reply to my comment, @beatboxchad said: Thanks. Look, I wouldn't be worried about someone else doing it. I'm honest about my capacity, my strengths and weaknesses. I'm disabled and can't work full-time. It's more about being paid for my contribution so that I don't get entirely excluded from the process. Mature OSS projects get contributions from staff at the businesses that are consulting or building services on top of them. If you're still bootstrapping, you might want to instead put in the legwork of deciding which issues have priority and preparing some resources. I still don't like the flat-rate bounty structure, baseline. One way or another, paying developers for all of their labor is crucial to a healthy ecology. I should have been paid for that "interview" -- I might be more generous with you now, because we are aligned. I would still criticize this approach. This (unfortunately common) practice you are engaging in is anti-labor, and therefore anti-accessibility. There's a better way to structure this opportunity. It's somewhat personal, I have felt genuinely ripped off by people in your circle, but it's just an unhealthy culture and a misunderstanding of how to create the most value together. I understand your defensiveness about my long posts interfering with the clarity of this discussion. I appreciate your transparency in preserving my original comments (my irritation at the obfuscation stands, but let's de-stigmatize conflict so that we can all accommodate each other). I will take care to make these my final remarks on the topic. I respect your time, but you're being paid to engage with me here and I think I'm giving you something valuable. I don't recommend anyone post a feature or bug that they are worried about someone else doing. @bbertucc responds:
I am not. I only get paid for coding Equalify features. Please allow me to focus on coding. |
Beta Was this translation helpful? Give feedback.
-
Equalify is focused on web accessibility. Still, we should be a humanistic project and have a place for discussion of off-topic issues. This is that place. Speak freely, but I might not respond because I'm focused on web accessibility.
Beta Was this translation helpful? Give feedback.
All reactions