Write Hacktoberfest organizers to update onboarding information

[Providence-o]

Overview

We want new joiners (through Hacktoberfest) to read the Contributing file first before creating a good first issue.

Action Items

• [ ] Go through the Hacktoberfest website and check that there is no directive to study a README.md document or CONTRIBUTING.md document first
  • If research shows that such a document exists,
  • [ ] put the links here (in this issue):
  • [ ] Then, review links with Bonnie
  • If research shows that it doesn't exist;
  • [ ] Prioritize this issue as time sensitive #2919
    • [ ] Add discussing issue with the dev team to their agenda.
  • [ ] Email hacktoberfest organisers to request that they update their instructions so that new joiners read the contributing.md file and ask them 'what answer should all maintainers give participants when they don't follow guidelines for new contributors'

Resources/Instructions

Contributing.MD

[github-actions[bot]]

Hi @Providence-o.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing: Size, Role, Feature

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards. To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Milestone" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels

[Providence-o]

Findings:

• On the beginners page they have information for participants new to open source on a third party website Up for grabs where they talk about reading the contributing guidelines, but they are not directly affiliated with Hacktoberfest, so not every participant will see this.

• The website does not have an official statement instructing participants to read the contributing file first. They have a guide on how to get started in their FAQ's where this instruction can be added. (The Participants page mostly has information on pull requests so it is unlikely to be added here.

[Providence-o]

We want to write the Hacktoberfest organizers about their invalid/spam label definition because it's different from the GitHub label guide they provided on their website, and we don't want to apply such labels to our participants' issues

[7kram]

Did we ever reach out to the Hacktoberfest organizers?

We want to write the Hacktoberfest organizers about their invalid/spam label definition because it's different from the GitHub label guide they provided on their website, and we don't want to apply such labels to our participants' issues

Is this still an issue in 2022/23?

[oliviazhai]

Availability: Apr 3rd ETA: Apr 4th end of the day

[garrettallen0]

Availability for this week: Wednesday evening, Thursday office hours My estimated ETA for completing this issue: Saturday 4/ 15

[garrettallen0]

I assigned myself this as a good first issue, but is it still an issue? I don't understand. Since Hacktoberfest 2022 is over, and 2023 is not yet live, what is our goal?

On the Participation page, they have many resources regarding contributing, such a this one. In the video (4:10) on the Participation page, they direct people to read the CONTRIBUTING guidelines of the project they are contributing to.

[ExperimentsInHonesty]

We never wrote to the organizers. We just decided that the solution was to put the prerequisite on each issue.