mmegger

"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."

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.

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.

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.

You should check out SendGrid's case study on how they managed Hacktoberfest. It has a lot of good information there. https://sendgrid.com/wp-content/uploads/pdf/SendGrid-Hacktob...

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!

Be sure to review the maintainer best practices on the website https://hacktoberfest.com/participation/#maintainers

Happy Hacktoberfest and best of luck!

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?

Exactly. I find it amazing how many people are willing to keep bashing something that they haven't taken the time to look into in the past two years.

Hey look, I made it to Hacker News. Neat :) Glad y’all enjoyed the presentation and article