I had a call with people from OnlyDust last Friday and I would like to make a small intro to the platform here to gather some idea whether it is something we’d like to consider as a funnel to get more open-source contributors.
OnlyDust allows anyone to join and either promote their open source projects in search of contributors and maintainers or find interesting projects to contribute to.
They have indexed a big chunk of Github already, so you can even go and find our projects there:
…
They asked for a list of repos we’d like to promote and potentially include in they “hackathon” (although as they said they don’t like to call it that way as it should not be bound to a specific dates from the perspective of finishing the work, but rather as a way to put particular projects in front of devs).
What we’d need to do is
- Find good repos/projects to promote
- Come up with a few good first issues
- Dedicate time to people who are willing to contribute
There seems to be a mixture of knowledge and skill levels, but many will be new devs trying to gain some experience and exposure in the open source ecosystem.
There is also a risk of people just using AI to vibe code the “good first issues” without actually learning anything (which is a risk with simple issues anyway at the moment)
There is no payment from our side - they do have some paid internships that they pay from ecosystem grants they receive - so it is mainly just the effort to prepare our repos.
I’ll invite Emilie here to answer any questions you might have.
1 Like
Thanks for sharing. This is great because it covers the groundwork we need to do anyways in terms of prioritisation and creating a clear pipeline for those interested in that side of the funnel.
What is unclear to me:
- What is the process internally to decide what to prioritise? We essentially have three core protocols that are equally essential to Logos, how do we decide which to highlight and who makes that call?
- As I understand it a good chunk of what we need is people helping with the libraries - is this feasible given the complexity?
- Is it more interesting to pick one of these projects that we have been incubating, debating etc. and code something that is closer to an app that can work on Logos eventually?
1 Like
- I think we have 2 options - either coordinate and pick one repo to start with, or we let each project to decide - there are not just 3;) Status, Keycard, Vac…all can participate as well
- I honestly don’t know:) I think it is possible, but will be tough
- I was actually thinking about that as well Guru’s CypherShare, OpChan, Podex, the latest one Trollbox, or anything that comes up - small code base, easy to understand, big potential for small contributions - way way easier than contributing to Codex or Waku directly:-)
I am throwing this out here, I don’t have a clear answer, happy to experiment and see what works:-)
2 Likes
After much back and forth it seems to me like the 3rd option is the best to reduce hacktivation barriers. Will prioritise Guru’s on our Discord onboarding, as it connects with the Save the Songs campaign, anything else?
I would love for OpChan to be something we talk about more - from the perspective of usage, features and contributions - so that would be my pick:)
Hi everyone! Emilie here from OnlyDust 
Many thanks @vpavlin for introducing us
The next open-source week will start June 26th - feel free to add the repos that you would like to have participate over here: Wave #1 – Open Source Wave | OnlyDust
Looking at your questions - if you are looking for contributions in the libraries, make sure that the issues are structured or divided into chunks so that it’s easier to onboard.
Feel free also to add a few different repos to test it out.
Once you have made a decision, you can ping me and let me know as well the type of contributors you are looking for (their language skills, background). That way we can help put it more visible in the community.
happy to answer any more questions!