Skip to content

Latest commit

 

History

History
114 lines (85 loc) · 8.62 KB

points.md

File metadata and controls

114 lines (85 loc) · 8.62 KB

Points Eligibility, Tracking & Logistics

General Guidelines

Follow these gardening guidelines to be eligible for prizes all month long, and set us up for maximum community impact.

  • All participants earn points, redeemable for prizes, for each individual contribution made between 12 AM PDT October 19th through 9 AM PDT November 12th.
  • Review the list of eligible contributions to see what’s eligible—pull requests are most welcome, but explore other ways to add value.
  • Attendees must register for Summit Gardening Days to be eligible to earn prizes.
  • Attendees must check in to be eligible to earn prizes and appear on the leaderboard.
  • Teams must demo their project at the demo session on November 12 at 9:00 AM Pacific, or add a demo post to #gardening-general before 9:30 AM Pacific on November 12, to be eligible for a team prize package.
  • Match advisors will use your answers to the registration questions to place you on a team. During kickoff week or after you've registered, we will notify you of your team placement to confirm participation, and provide Slack introductions to teammates.
  • Teams can mention @on-call-gardener and @gardening-admin in Slack for help in choosing a project.
  • Read more about how to get started on the getting started page

Challenge Judging

Along with individual rewards, we will award team prizes using an anonymous judging process. We'll use Google Forms to create a demo survey, and will finalize it to include all eligible projects at or before 9:30 AM Pacific on November 12. During the demo session, our panel of on-call-gardeners, organizers, and SDLC partners will use the survey to vote for the winners. We will award divisible team prize packages to winning teams at the demo's conclusion and on Slack in #gardening-general.

Points Tracking

Visit the Leaderboard to track your points! Gardening organizers will track and tally points based on GitHub activity in eligible organizations, and other eligible content contributions as tracked in the spinnaker-hackathon organization and in the #gardening-general channel on Spinnaker Slack.

GitHub Event Contributions

To receive points for your open source GitHub contribution activity during Gardening, you must work in a tracked organization. These include:

Eligible GitHub events include pull request creation, commiting, issue creation, and issue and pull request commenting in Spinnaker project repositories. Those event types, along with pushing and repository creation will be tallied where contributors can perform those events, in spinnaker-hackathon.

You should create repositories for the work in this spinnaker-hackathon organization to receive GitHub event points for contributions such as:

  • Demos
  • Plugins
  • Automation projects

All participants will be added to the spinnaker-hackathon organization after checking in to the event. If you would like your work in another public repository to be counted, mention @gardening-admin in #gardening-general, and we will evaluate exceptions on a case-by-case basis.

Slack Tracking for Content Contributions

To submit content for points eligibility, do the following:

  1. If possible, initiate your content in a respository in the spinnaker-hackathon organization (see Extra Points Opportunity below).
  2. Once content is published in its public destination, take a clear screenshot of it.
  3. Post a message about your contribution in #gardening-general. Your message should include:
    • Screenshot
    • A brief description of the content
  4. After you post your message, add a :burn-book: emoji reaction to your message. Your points will not be counted unless you add this reaction. If needed, learn how to use reactions in Slack.

Extra Points Opportunity for Content

You have multiple opportunities to receive points for content contributions such as:

  • Tutorials
  • Blog posts
  • Solution briefs
  • Whitepapers
  • Training guides
  • Videos
  • Twitch streams
  • Contributor interviews

These contributions are eligible for points as GitHub event contributions if you initiate the content or scripts as respositories in the spinnaker-hackathon organization, and then again as Content contributions once you post or publish them and follow the steps to redeem your points!

Besides those listed above, content contributions include community help responses, such as stackoverflow answers and spinnaker slack answers. While these shouldn't be added to a repository and are not eligible as GitHub event contributions, they will earn points through the Slack tracking system for content contributions. See a list of contribution types on the What to Hack page.

Slack Tracking for Bonus Points

Engaging in Spinnaker Slack, whether in #gardening-general, team channels, or SIG channels is worth points! Gardening staff react with the :gold-coin: emoji to reward helpful, fun and positive engagement in Slack. Feel free to reward yourselves and others for these messages with coins! Bonus Submissions are tracked here on the leaderboard. Gardening staff will review submissions before announcing final points tallies and awarding prizes.

Leaderboard

Use our Leaderboard to track your contribution totals, noting the time delay detailed below. We will use the following query against the GH Archive dataset of public GitHub activity to track contributions according to organization name:

SELECT
  actor.login,
  COUNT(*) as cnt,
FROM
  `githubarchive.month.*`
WHERE
  (repo.name LIKE 'spinnaker/%' OR  repo.name LIKE 'spinnaker-hackathon/%')
  AND created_at >= '2020-10-19 08:00:00'
  AND created_at < '2020-11-12 18:00:00'
  AND _TABLE_SUFFIX > '2020'
  AND type IN ('IssuesEvent',
    'IssueCommentEvent',
    'PullRequestReviewCommentEvent',
    'PullRequestEvent',
    'PushEvent',
    'CreateEvent',
    'CommitCommentEvent')
GROUP BY
  actor.login
ORDER BY cnt DESC
LIMIT
  180

Note: Our leaderboard on Google Sheets uses BigQuery to grab this data. This archive is a great way to get it, but there is a lag in the way the data is aggregated from GitHub APIs and aggregated into the archive. There is typically a 24-hour lag in the reflection of GitHub events in the archive, but it can sometimes be longer than 24 hours depending on what time the contribution was made. Therefore, there will be a delay in the visualization of your contributions.

The Spinnaker-Hackathon Organization

Create repositories

Starting fresh with some new plugin code, or writing a tutorial? Create all new project repositories in Spinnaker-Hackathon. Name your repo with a descriptive project string that you’ll use in your Slack channel name. Note: Your GitHub handle will be added as a member to the Spinnaker-Hackathon organization after registration, and you must register to receive repository creation privileges if this is your first Spinnaker Gardening Days.

Fork Spinnaker repositories

Need to fork an existing Spinnaker project(s) to hack? Fork into the Spinnaker-Hackathon: where to fork When it's time to submit a pull request, do so from your fork. Read more on best practices in fork & pull request workflows.