Skip to content

Latest commit

 

History

History
78 lines (46 loc) · 5.86 KB

README.md

File metadata and controls

78 lines (46 loc) · 5.86 KB

image

Welcome to Flow's FLIP Fest

This event is being moderated through HackerEarth. If you interested in participating, please review all the details of the event and register through the link above.

What is FLIP Fest?

The Flow FLIP Fest is a two-month event that will engage and reward participants for creating innovative and effective improvements to Flow's Ecosystem. A FLIP is a Flow Improvement Proposal; a community-driven initiative to discuss and execute impactful improvements on Flow.

Teams or individuals can sign-up to tackle high impact projects through any of the issues listed in this repository. Core contributors to Flow will aid and guide you through your project as you work to deliver an optimal solution alongside other teams.

Rewards are given per issue for both high quality completion as well as a large reward given to the best solution per project. Read more about the rewards here.

Issues, Tracks, & Tiers

Issue Tracks

Issue Tiers

  • Tier 1: Large task, spanning 4 milestones requiring extensive work and/or knowledge.
  • Tier 2: Medium task, spanning 2-3 milestones requiring a moderate level of domain knowledge.
  • Tier 3: Small task, spanning 1 milestone, generally can be completed with limited domain knowledge.

Others

Getting Started

  1. Sign up on HackerEarth.
  2. Find a team through HackerEarth, our Discord server, or through GitHub. You may also complete a ticket by yourself, however collaboration is highly encouraged. Please contruct and confirm a team with a team name via the HackerEarth platform.
  3. Find an issue you or your team would like to do and post a comment on the issue with a link to your team's Hacker Earth Team Profile and tag all GitHub usernames of the members on the team.

For more details on logistics and process, read more here.

Milestone Submissions

Each project is divided into one or more milestones depending on the complexity. Read more about milestones here.

Instructions

Complete the required work on the respective milestone via any relvant repsoitory/repositories (make a new public one if required). Follow any relevant guidelines and including proper PR documentation on those repos. Once all the work for a milestone has been completed, summarize the work done across all repos into a single PR on this repository.

To be eligible for rewards, teams must submit a PR to: /submissions/issue-#/milestone-#/team-name

In this PR, please follow the template. Your point-of-contact (PoC, the assignee on the issue) will provide official feedback and/or approval every Thursday/Friday for the duration of the event.

Requirements

Each issue has its own requirements outlined inside the issue. Along with this, there are some high-level judging criteria outlined that should be followed.

Resources

Announcements & Updates

All announcements and updates regarding FLIP Fest will be delivered on Discord and GitHub.

Community

To discuss any specific issues or have general discussion on this event, please visit the discussions page!

Help

Your point-of-contact (PoC) will be the first person to contact for help regarding your specific issue. They may help you connect with others as needed to help you solve your problem. Outside of that, core contributors to Flow will be available on our Discord to answer any comments, concerns, or questions. They will also answer questions on GitHub through discussions, issues, and PRs. You can also use our directory to find potential members to connect with via any of the channels listed.

Useful Links