Customization for big enterprises is actually a viable business model, only if it generates as much money as the company sustains and can continue to expand?
Yes, it is only a viable business model in the end if it generates enugh revenues to cover materials and labour, like every business on planet Earth.
I am sorry to say some of what you write is not correct.
Red Hat — I know they had their slice of controversies lately, but still — is a ≃33bn USD company, how is that not making money? They sell solutions based on OSS (different from selling software!), which is one viable way of making money.
Other ways are: selling support, selling licence exceptions (when you are the sole copyright holder of the codebase, MySQL did that), sponsored development for new features, SaaS (bad!), customization for big enterprises/public actors, open-sourcing software but keeping assets proprietary (some games do that), and many more.
I feel one of the most important things for a thriving open source project is easy onboarding.
Statement of friendliness and similar are not that useful if I don’t know where to start to contribute to your project. A clean, up to date CONTRIBUTING file goes a long way, architecture documentation is extremely good, optimal is having an experience developer checking your patches and offering help.
Repositories that I contribute to the most helped me in the first phases of the journey, it was awesome, I gave back.
Nope! Little known to people, you just need to locally clone your repository with --bare and upload that. You will see you can clone it even if you don’t have a git server!
It is a very slick, minimalist solution.
It might not be a solution for everyone, but you can self host a git repository on your static site!
stagit is a static git site generator. It is lean, you can self host it even of the cheapest of shared hosting and it makes code browseable via html, which is a plus for sharing and receiving suggestions/contributions.
For a relatively small, low bandwith project it is a charm. As an example, here are my repositories.
Documentation is very useful today (to clarify our thoughts on what is useful and what is not, what is in scope and what is not), and for our future selves.
Writing small bits of software made me appreciative of the work teams put on large pieces of infrastructure!
If some code links to your GPL library, the whole project has to be licenced GPLv3, full stop. This does not “prevent people to use [it] at all”, it just stipulates that they have to make the source available and the source of improvements they make available. Each substantial library I write in my free time is GPLv3. I want to contribute to the ecosystem and I want everyone enjoying my work contributing back to the ecosystem.
A similar licence, called LGPL, allows dynamic linking without having to make the code of the whole project available, just the code of the specific library + improvements. If for some reason you need this, I invite you to check how dynamic linking works in Pharo and read this FAQ by the FSF (and all other FAQs, it is a very clear, informative document).
Scribus is an excellent libre desktop publishing program.
I used to write a small postcard game for the “Wish you were here” jam, but it is suited to any job up to professional level.