Skip to content

Commit 6545790

Browse files
thehowlKouteki
authored andcommitted
docs(gnoland/pages): pause bounty program (#5172)
Also changes the page to consistently use `gno.land` per branding. --------- Co-authored-by: Nemanja Aleksic <kouteki@gmail.com>
1 parent 0eea20e commit 6545790

File tree

1 file changed

+12
-52
lines changed

1 file changed

+12
-52
lines changed

examples/gno.land/r/gnoland/pages/page_contribute.gno

Lines changed: 12 additions & 52 deletions
Original file line numberDiff line numberDiff line change
@@ -13,72 +13,32 @@ As an open-source project, we welcome all contributions. On this page you can fi
1313

1414
## Where to get started
1515

16-
If you are interested in contributing to Gno.land, you can jump on in on our [GitHub monorepo](https://github.com/gnolang/gno/blob/master/CONTRIBUTING.md) - where most development happens.
16+
If you are interested in contributing to Gno.land, you can jump in on our [GitHub monorepo](https://github.com/gnolang/gno/blob/master/CONTRIBUTING.md) - where most development happens.
1717

18-
A good place where to start are the issues tagged ["good first issue"](https://github.com/gnolang/gno/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22). They should allow you to make some impact on the Gno repository while you're still exploring the details of how everything works.
18+
A good place to start are the issues tagged ["good first issue"](https://github.com/gnolang/gno/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22). They should allow you to make some impact on the Gno repository while you're still exploring the details of how everything works.
1919

2020
## Gno Bounties
2121

22-
Additionally, you can look out to help on specific issues labeled as bounties. The Gno bounty program is a good way to find interesting challenges in Gno, and get rewarded for helping us advance the project. We will maintain open and rewardable bounties in the gnolang/gno repository, and you can search all available bounties by using the ["bounty" label](https://github.com/gnolang/gno/labels/bounty). For more detals on the categories and types of bounties, we have a [bounties README](https://github.com/gnolang/bounties).
22+
> **Note: The Gno Bounty Program is currently paused until further notice.**
2323

24-
Recommendations on participating in the Gno.land Bounty Program:
24+
Two reasons prompted this pause:
2525

26-
- Identify the bounty you want to work on, and join in the discussion on the issue for anything that is unclear; or where you want to more clearly define the work to be done. At this stage, you can also start working on an initial implementation in your local enviornment.
27-
- Once you have spent time on the code related to the bounty, we recommend submitting a 'draft' PR as soon as possible.
28-
- The draft PR doesn't indicate that the bounty has been assigned to you, others are free to work on other draft PRs for the bounty.
29-
- Make sure to reference the bounty issue on the PR description you're writing.
30-
- After submitting the 'draft' PR, continue working until you are ready to mark the PR as "ready for review".
31-
- The core team will review the bounty PR submission after the work on the bounty has been completed, and determine if it qualifies for the bounty reward.
32-
- Ask for clarification early if an element on the requirements or implementation design is unclear.
33-
- Aside from publishing the PR early, keeping regular updates with the core team on the bounty issue is key to being on the right track.
34-
- As part of the requirements, you must adhere to the [contributing guidelines](https://github.com/gnolang/gno/blob/master/CONTRIBUTING.md); additionally, it is expected that any newly added code or functionality is properly documented, tested and covered, at least in 80% of added code.
35-
- You're welcome to propose additional features and work on an issue should you envision a plausible expansion or change in scope. The core team may assign a bounty to the additional work, or change the bounty with respect to the changed scope.
26+
- **Focus on Mainnet.** The team is fully focused on the Gno.land Beta Mainnet launch — the highest priority — as well as the critical post-beta work required to deliver a complete Mainnet.
27+
- **Decline in submission quality.** The bounty program was created to encourage innovative, creative, and technical contributions that meaningfully advance Gno.land. However, with the rise of generative AI, the overall quality of submissions has declined significantly. A large portion of entries are clearly AI-generated; others, though less obviously so, are often inaccurate upon review due to overreliance on AI. Reviewing and validating these submissions has become increasingly time-consuming, diverting focus from development work.
3628

37-
You may make your submission at any time; however we invite you to publish your draft PR very early in the development process. This will make your work public, so you can easily get help by the core team and other community members. Additionally, your work can be continued by other people should you get stuck or no longer be willing to work on the bounty. Likewise, you can continue the abandoned or stuck work that someone else worked on.
29+
Community contributions remain strongly encouraged, particularly:
3830

39-
Don't fear your work being "stolen": if a submission is the result of multiple people's efforts, we will look to split the bounty in a way that is fair and recognises each participant in creating the final outcome. Here are some examples of how that can happen:
31+
- Tooling and infrastructure projects
32+
- Application-focused development
33+
- Longer-term, high-quality initiatives
4034

41-
- If Alice does most of the work and abandons it; then Bob comes around and finishes the job, then Bob's PR will be merged. But the core team will propose a split like 70% for Alice and 30% for Bob (depending, of course, on the relative effort undertaken by both).
42-
- If Alice makes a PR that does only 50% of the work outlined in the requirements for the original issue, she will get 50%. Someone can still come up and finish the job; and claim the remaining part.
43-
- If you, for instance, cannot complete the entirety of the task or, as a non-developer, can only contribute a part of the specification/implementation, you may still be awarded a bounty for your input in the contribution.
44-
- If Alice makes a PR that aside from implementing what's required, also undertakes creating useful tools among the way, she may qualify for an "outstanding contribution"; and may be awarded up to 25% more of the original bounty's value. Or she may also ask if the team would be willing to offer a different bounty for the implementation of the tools.
45-
46-
Participants in the Gno.land Bounty Program must meet the legal Terms and Conditions referenced [here](https://docs.google.com/document/d/e/2PACX-1vSUF-JwIXGscrNsc5QBD7Pa6i83mXUGogAEIf1wkeb_w42UgL3Lj6jFKMlNTdwEMUnhsLkjRlhe25K4/pub).
47-
48-
### Bounty sizes
49-
50-
Each bounty is associated with a size, to which corresponds the maximum compensation for the work involved on the bounty. A bounty size may under rare occasion be revisited to a bigger or smaller size; hence why it's important to talk about your proposed solution with the core team ahead of time.
51-
52-
In some cases, the work associated with a bounty may be outstanding. When that happens, the core team can decide to award up to 25% of the bounty's value to the recipient.
53-
54-
The value of the bounty, aside from the material completion of the task, considers the involved time in managing the created pull request and iterating on feedback.
55-
56-
57-
t-shirt size | expected compensation
58-
-------------|-----------------------
59-
[XS] | $ 500
60-
[S] | $ 1000
61-
[M] | $ 2000
62-
[L] | $ 4000
63-
[XL] | $ 8000
64-
_[XXL]_ \* | $ 16000
65-
_[3XL]_ \* | $ 32000
66-
67-
[XS]: https://github.com/gnolang/gno/labels/bounty%2FXS
68-
[S]: https://github.com/gnolang/gno/labels/bounty%2FS
69-
[M]: https://github.com/gnolang/gno/labels/bounty%2FM
70-
[L]: https://github.com/gnolang/gno/labels/bounty%2FL
71-
[XL]: https://github.com/gnolang/gno/labels/bounty%2FXL
72-
[XXL]: https://github.com/gnolang/gno/labels/bounty%2FXXL
73-
[3XL]: https://github.com/gnolang/gno/labels/bounty%2F3XL
74-
75-
\*: XXL and 3XL bounties are exceptional. Almost no issues will have these sizes; most will be broken down into smaller bounties.
35+
These types of contributions are better aligned with Gno's goals than short-term bounties, and are very welcome provided they follow the [contributing guidelines](https://github.com/gnolang/gno/blob/master/CONTRIBUTING.md). Sustained, high-quality contributions will be rewarded over time via the Gno.land GovDAO.
7636

7737
## Gno.land Grants
7838

7939
The Gno.land grants program is to encourage and support the growth of the Gno.land contributor community, and build out the usability of the platform and smart contract library. The program provides financial resources to contributors to explore the Gno tech stack, and build dApps, tooling, infrastructure, products, and smart contract libraries in Gno.land.
8040

81-
For more details on Gno.land grants, suggested topics, and how to apply, visit our grants [repository](https://github.com/gnolang/grants).
41+
For more details on Gno.land grants, suggested topics, and how to apply, visit our grants [repository](https://github.com/gnolang/grants).
8242

8343
## Join Game of Realms
8444

0 commit comments

Comments
 (0)