✨ Contribution Opportunity: Review Ecosystem Contributions Issue Template

[smartcontracts]

What is a Contribution Opportunity?

A Contribution Opportunity is a concrete task that you can work on to contribute to the Optimism Collective.

---

Summary

If you're reading this, you're probably on the Ecosystem Contributions GitHub repository. Each issue on this repository follows a standard template that contains key information related to a project. We are looking for ways to improve this template to give potential contributors access to more relevant information.

Areas for improvement could include, but are not limited to:

• Need for additional task information
• Need for additional resources
• Need for additional context on the contributing process

Generally, think like a contributor and try to see if there's additional information that could be included in every issue that would help you be more successful when completing a task.

Potential Features

• Detailed document explaining your thoughts on the standard template (looking at this issue as an example)
• Highlighted key points of improvement overall
• Highlighted key points for additional information
• Thoughts on structure and ease of access to required materials

Impact

• A better contributor experience means more tasks get done
• More tasks get done means more work gets done
• More work gets done means more RPGF for everyone!

[zer0jean]

Hello everyone ! Here are a few feedbacks and addition on the template (between "") :

Summary

If you're reading this, you're probably on the Ecosystem Contributions GitHub repository. Each issue on this repository follows a standard template that contains key information related to a project. We are looking for ways to improve this template to give potential contributors access to more relevant information.

Areas for improvement could include, but are not limited to:

• Need for additional task information
• Need for additional resources
• Need for additional context on the contributing process

Generally, think like a contributor and try to see if there's additional information that could be included in every issue that would help you be more successful when completing a task.

"### Preleminary elements

• Elements which lead to create the issue
• Potential existing documentation on the subject
• Potential exisitng issues linked to the current subject"

Potential Features

• Detailed document explaining your thoughts on the standard template (looking at this issue as an example)
• Highlighted key points of improvement overall
• Highlighted key points for additional information
• Thoughts on structure and ease of access to required materials

Impact

• A better contributor experience means more tasks get done
• More tasks get done means more work gets done
• More work gets done means more RPGF for everyone! #

"### Potential answer structure

• A clear answer template to avoid contributors to think and which information they should but more on their contribution
• The best way to submit the answer
• The type of submission (one-shot/short term/ long term)
• The ability for contributors to submit existing tools or solutions or development from scratch are required"

Note on intentions : Those additions are meant to stay generic and simple to document by giving as much information as possible to contributors so that they can quickly know if what they have in mind could answer the need and access every needed informations to avoid loosing time while

[juli1875]

Gran proyecto

[juli1875]

Gracias por la información

[andytudhope]

Hey @smartcontracts - here you go.

1. When creating an issue, I am met with 4 options, based on the config.yml. Two of those options - though different - lead to the same place (i.e, the Optimism forum). I would suggest changing that first and foremost. In particular, I suggest #78
2. I like @JeanGuillemont's suggestion for preliminary elements - that is a helpful thing that is missing. I'm hesitant to add much more, because getting good contributions is often a case of finding the middle way between providing enough context and not overwhelming people.
3. That said, we can definitely make more exact some of the current bullet points.

Features

• Highlight key points of improvement overall
• Highlight necessary addition information
• Key contact and steward for this issue (rather than the abstract "Thoughts on structure and ease of access to required materials". 'Who can I talk to' when I get stuck is much better than a paragraph about how some docs are not public)

Impact

• What new work this enables/unlocks
• The teams and/or people working on related topics who this will bring you closer to (this is actually the greatest impact for these contributions imo, because if I do them well, I could get to work with awesome people on cutting edge stuff, which is surely one of my motivations for being here in the first place. In general: think through concrete, individual motivations rather than abstract theories about what impact is)

Particulars

• Where to submit,
• In what form
• What type of work is involved (one-shot/short term/long term)

You'll see I changed "Potential Answers" to "Particulars". My experience of running similar programs is that, if I can put together a good answer template that removes the need for contributors to think (which is the whole point here, no?) then I might as well just fill it in myself. So, rather than suggesting that: just give people as much detail as possible about where to go and what form to think through from the start, recognising that framing it as a PR, or a document submitted, or a change to an issue will change the kind of responses you get.

[nanobro]

I tried to start contributing and read the 'Readme' many times. The readme was clear, but the contribution opportunities weren't.

As a non-dev who isn't familiar with GitHub, @JeanGuillemont and @andytudhope suggestion is extremely helpful. It is exactly what is missing from some of contribution opportunities.

example https://github.com/ethereum-optimism/ecosystem-contributions/issues/10 https://github.com/ethereum-optimism/ecosystem-contributions/issues/69

I want to contribute them but the tasks aren't clear. I also want to suggest adding Objective

• How will the result be used? https://github.com/ethereum-optimism/ecosystem-contributions/issues/69
• Are we brainstorming for features? https://github.com/ethereum-optimism/ecosystem-contributions/issues/10

For example Wallet UX Research #69

• What will the research used for? Are we looking to promote existing wallet or creating new one? The clear objective will get tasks done better.

[nanobro]

I have attempted to consolidate them. Here is the result. Please make any edits or suggestions as you see fit.

Summary

Provide a short description of this ecosystem contribution.

Objective

• How will the result be used?
• Are we brainstorming for features?
• What does this enable/unlock?

Preliminary elements

• Elements that led to the creation of the issue.
• Potential existing documentation on the subject.
• Potential existing issues linked to the current subject.

Features

• Detailed documentation explaining your thoughts on the standard template (using this issue as an example).
• Highlighted key points for overall improvement.
• Highlighted key points for additional information.
• Thoughts on the structure and ease of access to required materials.

Particulars

• Where to submit?
• In what form?
• Example of submission (if any).
• What type of work is involved (one-shot/short-term/long-term)?
• Key contact, where and who to discuss with."

[Likethiss]

Hey you fine people! Im very interested in contributing something and anything to help the collective. I read through your ideas for a new economic system and how it could scale to be a real world solution in the future.

My proposal is to add clear requirements of technical stuff on every contribution. Also i think it would be an awesome idea to have some sort of training program, where i for example could go study about some subject and then get tested somehow that i have absorbed the information.

Also i think it would be an excellent idea to have some sort of certification badges for coding in different languages etc, Also specific skillsets that could be studied to be able to provide value.

So what im proposing is if it would be a good idea to have a training program for new people with possibly no technical skills to study and master specific areas of the project. Links to good training resources and then providing proof of completing a coding course or a blockchain basics course. Learning a skill and using it to contribute should be rewarded i think. Then we could get a lot more people invested at this stage.

At the moment i am very keen on helping the vision come true but quite frankly i have no clue how to start being of use in bringing it all to life,

[nanobro]

@Likethiss that sounds awesome. I believe it can be a big separate project. You can apply grant for it here https://app.charmverse.io/op-grants/page-701220845245208