[SPDK] SPDK's success depends on you!

Hi Everyone,

First of all, thanks to everyone for you continued participation and contributions to SPDK over the years.  I am personally very proud to be a part of this community and I know I’m not alone with that sentiment 😊 Now I’d like to take a minute to remind everyone why SPDK is so successful and how we, as community members, can help make sure it stays that way:


     *   Review, review, review! Reviews are everyone’s job (not just maintainers).  Although our maintainers are the gate keepers to the repo, they need everyone’s help in reviewing the growing number of patches we see year over year.  A few points on reviews to keep in mind:
        *   You don’t have to be an expert on the code in question to provide a helpful review for the author.
        *   Simply asking questions about what the patch is trying to do can be a big help.
        *   If the problem that patch is trying to solve isn’t clear to you of if the commit message is hard to understand, ask for clarification.
        *   If you see style inconsistencies or typos in comments, helping identify those before maintainers review can save them a lot of time - time they can spend on your patches 😉
        *   And, of course, if you know the code in question well, feel free to question the implementation and/or suggest alternatives.
     *   Stay involved on Slack:
        *   Just like with reviews, you don’t need to have all the answers to engage.  Ask questions to help understand the question or scenario, this will help others jump in as well
        *   Feel free to tag another community member who you might think can help even if you can’t.
        *   If you have questions yourself, remember there’s no such thing as a bad question! We are all part of the same community and are all here to help one another.
     *   Watch for GitHub issues:
        *   Who fixes bugs? We all do!
        *   Attend the weekly community meeting that works for your time zone. It’s a great place to pick-up cool work and learn debugging techniques as well.
     *   Attend community events:
        *   We’ve not had many of these in the last few years for obvious reasons but we hope to have a developer meeting sooner than later… but we *do* have a virtual Hackathon coming up April 28th so be sure to register here<https://teams.microsoft.com/registration/iI3JRkTj1E6Elk7XcS4lXQ,kemVK82320u6Ozy2ZGc4dQ,kG-9XEZXKEyDI8aXugFltw,lAlDvaCL9U6VcqK5j3MxWQ,aJJxPV6l-kKqpF18fi_3XQ,uO0U5ZEuhkKSWjee0JkeCg?mode=read&tenantId=46c98d88-e344-4ed4-8496-4ed7712e255d>, come join the fun!

Thanks!!
Paul