Blog
- Home
- ASP.NET Core
- Blazor
- What plans for Awesome Blazor?
What plans for Awesome Blazor?
For 2 years now I have been managing a GitHub repository, Awesome Blazor, which is a collection of great resources about Blazor, an open-source product from Microsoft that enables us to run .NET in the browser (yes, it's as awesome as it sounds; if you are discovering this term right now, you really have to check it out after reading this post).
Like Blazor, the repository, which was just a personal Markdown file 2 years ago, has grown a lot, and so has its responsibility, as the community that uses Awesome Blazor and expects great resources and information from it gets bigger every day. Moreover, Awesome Blazor is linked by Microsoft from the official Blazor website, so this repository has definitely reached a certain level of quality.
Awesome Blazor has reached a point that led me to wonder how to do this well in the long term. I have thought about this a lot in the last few weeks and I'm considering adding new collaborators to the repository, for two main reasons.
First, I really like the spirit of Blazor, and the spirit of all the .NET Core products by the way, which is open-source and really community-welcoming. That is why I find it a little disturbing to be the only owner of this repository, and I feel that it will embrace the spirit of .NET Core more once it has several owners.
The second reason is that I am not always available, and Awesome Blazor deserves to have some backup. For example, I went on vacation for the last two weeks of May this year, to a place without an Internet connection (which was a little bit the point, to be honest), and when I came back there were 10 pull requests and several issues that had been left unanswered for 10 days. I think that this is disrespectful to the people who wanted to help us build a better repository and to the people who maintain libraries or samples; besides, it doesn't give a good image of Blazor, maybe even of Microsoft, and they don't deserve that. I do not plan to take a break or to be less active on this project, on the contrary, so I feel that it's time to open this repo up to include the community completely in the process.
I still need to address some questions like "How many collaborators?", "Which kinds of profile are suited to becoming collaborators?", "Which responsibilities for these new collaborators?", "Where is my place in all of this?" and "Does it make sense to have this repository attached to my GitHub profile? Or does it make more sense to move this repository to a dedicated organization?". Anyway, the process has started.
I created an issue and posted a tweet two days ago and I was not expecting so much interest: several people would like to get involved, which is something I did not anticipate. These questions are now more urgent than ever and I will answer them quickly, so here is the thing to keep in mind: the process of opening Awesome Blazor to the community has started! And I hope that it will help to build a better repository, to help Blazor grow as much as we can, and to take care of its really awesome community.
Cheers.