Well we have been just about the top trending Ruby project on GitHub consistently since going open source a year ago, so on some level we are.
But I think there's a natural bottle neck where it's hard to provide guidance where to contribute sometimes when the core team itself is busy with things to do which require a lot of context.
We had over 500 pull requests opened on the project this past month, so there is plenty, but I think if we play our cards right and continue to build towards a project much bigger than just the single deployable instance of dev.to we will, in fact, reach that point of thousands and thousands of simultaneous contributors.
Well we have been just about the top trending Ruby project on GitHub consistently since going open source a year ago, so on some level we are.
But I think there's a natural bottle neck where it's hard to provide guidance where to contribute sometimes when the core team itself is busy with things to do which require a lot of context.
We had over 500 pull requests opened on the project this past month, so there is plenty, but I think if we play our cards right and continue to build towards a project much bigger than just the single deployable instance of dev.to we will, in fact, reach that point of thousands and thousands of simultaneous contributors.
Are there any other instances running the DEV code base as their backend? Or is the project still very DEV'd at the moment?
Very DEV'd at the moment but we're actively working with early adventurers who want to run the code for their own communities.
We now have a GitHub label for tasks which get us closer to generalization. As you can see we closed a couple issues just this week 🙂