"Yancey Spruill will continue to serve as Chief Executive Officer until a successor has been appointed, at which point he will step down from his role and as a member of the Board."
This is not the case here. The teams responsible for DigitalOcean’s tutorials were completely removed in this round of layoffs. Not only is is unlikely CSS Tricks won’t be migrated, there may never be another new tutorial again.
If this is true then I really am screwed. I have an article due for publication under that program, it had already passed the tech test, just a review of the actual text was needed. Angry because my article was with them for over 60 days tch.
I sent them emails asking for updates 4days ago and yesterday, no response.
I've mostly given up now, but I still kind of hold out hope, that $300 payout would've changed this Nigerian's life...even if only for just a while
The year that this blew up the DigitalOcean team (I was on this team) met with nearly 100 open source maintainers over the course of weeks to ask their opinions on Hacktoberfest and how we could make it better. We opened up these roundtables to anyone who would attend, and had great attendance from major projects such a Kubernetes, CPython, Gentoo, and others. We took all of this feedback and immediately changed the program. Many maintainers in the community have lauded us for these changes both publicly and in private.
We did listen to the community and we made the program better.
Changes were enacted in 2020 to make the program less spammy. Hacktoberfest is now opt-in and repeated spammers are permanently banned. The amount of spam PRs dramatically dropped after this change was implemented.
I'm very excited about the no-code contributions this year. The entire world benefits from open-source, why should the only people who get to help make it better and shine a light on it be people who code? There is _way_ more to a project than the code.
A great way to get the most out of Hacktoberfest for your repo is to identify where you need help before and create issues in those repositories with the label "hacktoberfest" or "good first issue" or any other tag to signify the task is a good entry point into your project. A lot of first time contributors check out websites like https://goodfirstissues.com/ to find issues to work on.
Other than that be vocal about your participation. Write a blog post, post on twitter, participate in the Hacktoberfest Discord, attend local Hacktoberfest events in your area, or even how your own Hacktoberfest event!
What is the requisite amount of time to keep bringing up the past? In 2020 a problem was identified, the team acted on it, and has since improved the program.
How long should they have to continue to apologize for an honest mistake while trying to do good?
First impressions are important. We rely on them to filter out a lot of information and reduce options when making decisions. For example, a bad first impression will result in no second-round interview, no first or second date, a lost sales opportunity. I don't think it's unfair to extend that to events such as this. Especially because it's still ultimately a tool to promote Digitalocean services.
If it were up to me, I think I'd modify the site title and social media card data to properly reflect that they've made changes to reduce the negative impact of their promotion on the public. "Hacktoberfest 2022: Lessons Learned Edition" or something slightly tongue-in-cheek and self-effacing. The way it is presented now makes it look like it'll be more of the same.
I wonder why the tips mentioned in your talk are not applied to the article. As you said, engineers looking to improve their writing skills don't want to read a novel.
What are some of your favorite examples of existing documentation?
Libraries, platforms, etc?
Personally I've always thought Vue's guide to be stellar, and I use it as my North Star when writing my own docs. I also like Spring's tutorials but they're a bit messy
That's corporate speak for removal. Based on the speed in which this announcement was made in regard to the investigation into misleading financial statements https://www.globenewswire.com/news-release/2023/08/21/272896... it's pretty obvious.