How to grow an open source project ?
Hello Indie Hackers.
I'm part of a team of developers that created Gitutor: a command line app that makes Git easy.
Gitutor provides beginner friendly versions of Git's commands so anyone can start using git in no time. You can learn more here : https://gitutor.io/guide/
We recently posted our project on reddit and had a positive reaction : 1.2 k upvotes in less than 12 hours and a bit of controversy on the comment section haha https://www.reddit.com/r/Python/comments/iajyrr/gitutor_a_command_line_app_that_makes_git_easy/
How could we grow our project ?
I do agree with others it is confusing if you are actually teaching or just wrapping to create an "easier" interface/CLI.
I think these can't co-exist in a way conceptually while you have made them one technically in a way.
If you were only teaching and not putting new terms and such it was clear you'd target students or questions about how to do X/Y like in stackoverflow or other places, build your own content site and try to rank it as another option.
but "simplifying" in this context and the way you point to, I get with the objections of this would not be socially acceptable to professional work environments in a way. It's yet another thing people would split on and can't use the same terms. I guess solo developers won't care, and could easily use that in place.. but then it should probably also be marketed differently of like 'git alternative interface' of sorts that is git compatible.. "better/simpler than git but compatible"..
The 2nd might be better for you, and than there is the 'translation' layer to explain to original git users what you are doing..
I don't think that simplification is incompatible with learning. In school many times a subject is simplified to make it easier for students to learn. Perhaps it should be more explicit how the transition between the easy commands to git commands should happen
the specifics that make this look off is teaching new terms that don't seem like they are on a progression path to teach the actual terms one needs to know.
Often schooling teaches a higher (more generic) or lower level (specific examples) term, that term isn't garbage at the end of the teaching process, which it feel you have here.. as in if I had learned it the other way / how other people learned, these terms would not exist.
to use a specific example, I'd rather you have something like "simple commit"/ commit_simple/ whatever and not make up 'checkpoint'
reasoning is, others git users can immediately identify what that's about.
so a simple commit to someone who didn't use you thing, is probably "commit -am"
no idea what check point would be
at best for an expert git user it should mean staging the commit.