People will only (usually) fork your project if it doesn't do what they want it to do, if you are open with then and accepting of useful pull requests there is no need to fork the project.
Forking is expensive (and divisive) so there is no incentive to do it unless there is a major problem that they want to "fix" and you won't let them. I've been working on open source projects for 25 years now and have only seen one fork in that time (gis.stackexchange.com/questions/11...) so I wouldn't worry about it too much.
The biggest issue I find with open source projects is getting people to contribute to them in the first place. If you look at my repos you will see that most have 1 or 2 stars and a couple of "forks" which indicates a collaborator.
I am a certified trainer that likes to share my knowledge with the world.
Also, I am an adopter of continuous learning and evolving idea.
https://dev.to/wolfiton/who-am-i-3lj7
People will only (usually) fork your project if it doesn't do what they want it to do, if you are open with then and accepting of useful pull requests there is no need to fork the project.
Forking is expensive (and divisive) so there is no incentive to do it unless there is a major problem that they want to "fix" and you won't let them. I've been working on open source projects for 25 years now and have only seen one fork in that time (gis.stackexchange.com/questions/11...) so I wouldn't worry about it too much.
The biggest issue I find with open source projects is getting people to contribute to them in the first place. If you look at my repos you will see that most have 1 or 2 stars and a couple of "forks" which indicates a collaborator.
My project is a bit different I had in mind to build a CMS like WordPress but not in PHP and with a more performant database schema.