4 ms·
Thank you for these blog posts. One thing that isn't immediately clear to me is how one should start a new open source library (before there is any traction) to
by zorr 5y ago
Thank you for these blog posts. One thing that isn't immediately clear to me is how one should start a new open source library (before there is any traction) to be prepared for this structure of maintainership.
For example, I'm already a freelance developer with (my countries equivalent of) an LLC and I send invoices to my clients for my work. I'm also in the process of writing a few libraries in the mobile/desktop/web shared-code space that I want to release as open source. Should I just mention this on the projects Github and website properties? A simple "contact me for an invoice" link and process the invoices/payments manually? Is there a platform a la Github sponsors/Patreon that is compatible with this workflow?
- FiloSottile 5y agoHonestly, I can't give you an actionable plan at the moment. We are simply not there yet. Eventually I hope there will be social norms (like how you advertise the option), tools (like payment rails and platforms, hopefully not like Patreon, but more like those lawyers use to invoice clients), resources, and even training. I hope it will become a standard transaction, that companies have processes for approving with no ad-hoc work. But for now, whoever wants to try this is in uncharted territory, will have to discover what works by trial and error, will have to teach companies how to think about them, and will need some significant leverage to spend (such as personal networks, visible projects, and savings).