You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the roadmap, it’d be great if we had better ways to feature items marked as "needs contributions", like we do with "Sponsor this".
Display a label ("Contribute")
Have it link to the item’s issue by default, and have a way to set a custom URL when appropriate
We don’t tag things as "Needs contributions" often (only when something is really big and easy to collaborate on with lots of people) – but it’d be neat anyway.
The text was updated successfully, but these errors were encountered:
On the roadmap, it’d be great if we had better ways to feature items marked as "needs contributions", like we do with "Sponsor this".
Display a label ("Contribute")
Have it link to the item’s issue by default, and have a way to set a custom URL when appropriate
We don’t tag things as "Needs contributions" often (only when something is really big and easy to collaborate on with lots of people) – but it’d be neat anyway.
I would like to work on this issue. Can you share some more details. Like, I have some questions ...
Does every feature which doesn't have "sponsor this" tag need to have "Contribute" tag?
If not, will there be some prop or state like need_contributor:true/false based on which we will render Contribute tag.
Because as you mentioned in the msg, you only need collaborator when the feature is easy to collaborate.
@kituuu great! See the top of my initial message, some items are tagged as "needs contributions". Those are the ones that should be displayed with a more prominent "Contribute" tag.
On the roadmap, it’d be great if we had better ways to feature items marked as "needs contributions", like we do with "Sponsor this".
We don’t tag things as "Needs contributions" often (only when something is really big and easy to collaborate on with lots of people) – but it’d be neat anyway.
The text was updated successfully, but these errors were encountered: