Replies: 4 comments 8 replies
-
Hi @AbcSxyZ |
Beta Was this translation helpful? Give feedback.
8 replies
-
If you want, I can invite you as a collaborator. You can do Experience with promotion of Open-Source-Project and help me to create a community! Let me know! |
Beta Was this translation helpful? Give feedback.
0 replies
-
@AbcSxyZ Some other suggestion? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I saw your post on dev.to where you're looking for collaborators. I explored your repository, I'm not a CXX user and even less doing ML learning, but I thought I may help you to attract more contributor by giving you some tips about Open Source project. I saw multiple area where improvement seem possible.
To be transparent, for now I do not have the experience of maintaining a successful OS project myself, but I'm studying the topic and hope to give you useful feedback and resources to think about how to attract more users & contributors. Actually, I'm starting a project called Open Source Education to educate about the topic.
First of all, I can warmly suggest you to take a look at "Producing Open Source Software, How to Run a Successful Free Software Project" by Karl Fogel & "The cathedral and the bazaar" of Eric Raymond.
To attract more contributor, I guess you should more target your users rather, Hacktoberfest contributor who do not use you repo won't stay here for mid/long term. It's about how you can make your actual users becoming potential contributors, and how to increase user base to have more potential people who will do this switch.
Concrete improvement suggestion
As a fisrt tips & the most obvious to me, there is one major area of improvement : Documentation :)
Without speaking about your other repo having an empty doc, making the software difficult to use and understand, here you've a lot of content, it's more about the docs organization which can be more efficient.
Karl Fogel is speaking about
hacktivation energy
, the energy it cost to use and get involved in your software, as user and as contributor. From a maintainer perspective, your goal is to reduce the entry barrier as much as possible. For example here, how long it takes for the user to see the installation section & jump in with your software ?As I see it, you can make it really more easy to install. The current installation is not at the top of the document (take a look some other repo when install instructions are coming), and you're even showing how to compile test before how to use your soft. Just by changing how your doc is structured may help to facilitate usage.
Without a deep thinking, I would see your README structured more like that:
It may be a more intuitive path from a user point of view.
I'm sure by improving your maintainer skill, you will be able to attract more people :) There is good resources to learn about it !
Beta Was this translation helpful? Give feedback.
All reactions