Security strategist for Synopsys cyber security research center. Former tech evangelist. Supporter of tech ranging from embedded to cloud and opinions are mine.
.@TimInTech with #SynopsysCyRC will be presenting at #RSAC! Log onto our virtual booth and register below to listen to his sponsor session talk below ⤵️ :
Calling all tech writers!
Open source benefits when we all contribute. If you've struggled to deploy a project - or hear people moaning about a lack of docs - help improve the docs!
Thank you @Didicodes#opensource#devops#cloud
I had an amazing time talking to the attendees at @AllThingsOpen today.
The open source ecosystem needs more technical writers. If you are a technical writer, you should consider contributing💛.
#AllThingsOpen
Don't miss our webinar with @RedHat today at 1pm EST, "The State of Open Source with Synopsys and Red Hat" presented by @TimInTech and Gordon Haff ⤵️: https://t.co/GBslgwhzR9
@mary_grace I tend to ask "why" questions which can place people on the defensive, so when someone is new I explain that their contribution is welcome but without test cases, it could fall on someone else to fix issues and that someone won't have the context the contributor has
@mary_grace I try and walk them through. I can't assume anything about their experience level or access to resources, so generally I want to see in the PR something about what testing was performed. If nothing else, it lets me know if I need to test something specific before merging.
@mary_grace@vmbrasseur Best case is finding out that your project has become a cornerstone of their business, and you've never heard of the business. Then having them step up to become a community leader in their own right.
@mary_grace@vmbrasseur For me it's users who think open source projects are commercial software. Stuff like wanting roadmap presentations, getting angry that features are "taking too long", or a "what's taking so long to fix this bug" sentiment