BTW, the event also encourages low-code and non-code contributions as shown in below matrix.
LOW-CODE NON-CODE WRITING * TECHNICAL DOCUMENTATION * TRANSLATING * COPY EDITING DESIGN * TESTING * USER EXPERIENCE TESTING * GRAPHIC DESIGN * VIDEO PRODUCTION ADVOCACY** * TALKS OR PRESENTATIONS * TECHNICAL BLOG POSTS * PODCASTS * CASE STUDIES * SOCIAL MEDIA * BLOG POSTS CONTRIBUTORS SUBMITTING LOW- OR NON-CODE CONTENT TO PROJECTS SHOULD CREATE A PR/MR TO TRACK IT. WHILE HACKTOBERFEST TRACKS ALL PR/MRS SUBMITTED FOR THE EVENT, MAINTAINERS MAY NEED TO FACILITATE TRACKING OF THOSE CONTRIBUTIONS THROUGH AN ACTIVITY LOG OR SIMILAR. Kind regards, Yihao Chen (Superskyyy) yihaoc...@apache.org<mailto:yihaoc...@apache.org> From: Yihao Chen<mailto:supersk...@outlook.com> Sent: September 17, 2022 12:14 AM To: dev@skywalking.apache.org<mailto:dev@skywalking.apache.org> Subject: Hacktoberfest is here Dear community, Hacktoberfest is a month-long event that runs each year to encourage people contributing to open source in October. This year I propose the SkyWalking community to participate in the event on the maintainers side. There’s no requirement for setting months-long tasks like OSPP or GSOC, simply come up with some good first issues and be ready to review pull requests and help new contributors. We need to set a new topic for our repo (main repo should be enough), and add an issues label `hacktoberfest` to be qualified as a participating community. Please raise any concerns or questions in this email thread to discuss. Below are copied from the Hacktoberfest website: https://hacktoberfest.com/participation/#maintainers Prepare your project for contributions by following these best practices: [TODO] Add the “hacktoberfest” topic to your repository to OPT-IN TO HACKTOBERFEST and indicate you’re looking for contributions. [TODO] Apply the “hacktoberfest” label to issues you want contributors to help with in your GitHub or GitLab project. Add a CONTRIBUTING.md file with contribution guidelines to your repository. Choose issues that have a well-defined scope and are self-contained. Adopt a code of conduct to create a greater sense of inclusion and community for contributors. Be ready to review pull/merge requests, accepting those that are valid by merging them, leaving an overall approving review, or by adding the “hacktoberfest-accepted” label. Reject any spammy requests you receive by labeling them as “spam,” and any other invalid contributions by closing them or labeling them as “invalid.” Kind regards, Yihao Chen (Superskyyy) yihaoc...@apache.org
