The difference between open source, foss code, closed source is this: business model(purpose, license).
As they are different business models, that can scare people. Why? For some people with the more traditional business model (closed license), it can be strange to receive donations from a project.
The GPL, MIT etc licenses never said that open or freedom software should be something free(when I say free, I mean in the financial sense - you can receive donations for plugins etc you create, commercial partnerships etc or pay through donations projects in these licenses). This proves that people have not read the terms of the license as usual or most of the time they are not interested in a license of this type, as you usually don’t have accurate technical support. I, for example, when I’m going to use a distro on my server, I check if the distro has long-term support like Ubuntu, if it doesn’t, I don’t use it, it will make my life difficult.
Yeah, is true. So… Remember I said that the difference between foss, open source and closed source was the purpose?
I for example use Windows and use tiddlywiki. For my daily use linux is fine for servers and windows is great for my daily activities. Although I consider that android is a great mobile operating system made with linux.
In that sense, my life is something like foss, closed-source and open source.
What I mean here is to analyze the purpose of the tiddlywiki project.
I think this question is relevant and I’ll see if I can answer it accurately, quickly, coherently, logically and concisely. So… How to make money with tiddlywiki?
Monthly/annual donation for plugins it you create, develop and/or keep
Monthly/annual donation for themes you create, develop and/or keep
Another way would be a commercial partnership with a company to develop exclusive themes or plugins and earn some money from it.
Another way would be if tiddlwiki adopted a business model like open-core, part of the code was community and part of the code was closed. Closing here would just be themes, customizations, plugins and specialized technical support like GitHub, Bitwarden etc.
Offer courses on how to use tiddlywiki, these courses you can create on Youtube or any social network in order to earn money with a tool as tiddlywiki.
Another way is to be a tiddlywiki consultant and earn money teaching how to use tiddlywiki - unlike the video courses I mentioned. Tiddlywiki consultant would be someone on the technical team registered to perform this role/position. “Bitwarden has several roles so that Bitwarden is something community and at the same time paid for companies as frontend, backend, designers, engineers etc.”
If you open a category, it would be interesting and with that you could have products/services inside tiddlywiki. People could leave their phone, email or bitcoin or paypal link to get paid for themes, plugins, etc.
This can somehow increase the use of tiddlywiki as a marketplace, framework or even as I said earlier as a product/service.
This can define the scope of tiddlywiki as a product/service or even project.
notes
“acquitting everything is not always feasible.”
Linux is used today for many things, but what makes linux free is the variety of companies that use linux.
Part of the money that comes to linux is made by donations from companies or individuals.
Also, there are linux certifications to make people more qualified to teach or install linux correctly.
This is what gives linux its value, in addition to the dozens of articles telling the ins and outs of linux.
In this sense, if there are donations from people and companies and also certifications for specialized people, it could make tiddlywiki more usable given the example I mentioned about Linux.
I’m not criticizing Linux or tiddlywiki, just seeing what they both have in terms of the market.
When I say “acquitting everything is not always feasible.” - there was a discussion about the characteristics of tiddlywiki if it would be a marketplace/framework or even a product/service.
When I say “absolving everything is not always feasible”. - sometimes the product/service is defined by the market, developers or technology.
We are all volunteers here. Which is why I am pushing back on things that people are asking for asking them to commit to volunteering and organizing. There are many non programmer tasks.
Absolutely not a problem if you (or anyone else!) doesn’t have time to volunteer, but the reality is that then things will not get done otherwise. This is the classic case of some need for self organizing and group collaboration.
Github has a sponsorship technology (GitHub Sponsors · GitHub) . But the developer has to sign up, of course. Don’t know if GH takes a cut or invades privacy like PP does. But considering that almost all developers have a presence on GH, it might be worth investigating.
@Mark_S@boris@TiddlyTitch Hi! This idea is great, it would be interesting to have a tiddlywiki sponsorship program. Volunteers could be paid by people that donating for tiddlywiki, or volunteers could be paid by companies that believe in tiddlywiki potential. This idea is similar to the aforementioned consulting program.
I don’t know the answer to this question, but I can give you my thought process and experience as a user.
A few months ago I decided to try out LogSeq and ended up liking it a lot. I continued using it for a while, but I had an uneasy feeling about the business model. I knew that the devs wanted to monetize it, but I couldn’t find any clarification on how they would do that. I just wasn’t sure if certain features would be paywalled in the future, and I didn’t feel comfortable investing a lot of my time into it.
One of the main things that drew me back to TiddlyWiki was knowing that the sky is the limit with the software, and nothing will ever be locked behind a paywall.
While I think that it is important for the core product to remain free and open source, I think that there are some good ways to monetize it:
paid synchronization service
paid mobile apps
GitHub sponsorship
plugin/theme competitions with prize money (from donations)
