Replies: 1 comment 2 replies
-
This "category" field should be optional because if we implement automatic addition of partner project URLs via bot's PR then it is tricky to get project category from the code. I mean only a partner knows the exact project category so he would need to manually create a PR which adds the "category" field here. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We started experimenting with using the DevPool system for roles beyond software development.
https://github.com/ubiquity/grants is a good example of our initiative for grant writing.
We also have a miscellaneous tasks repo at https://github.com/ubiquity/.github
Perhaps in the pull request to monitor the repository, we should add a property, e.g. "category" that will automatically tag those issues with a certain customizable label.
For every repository added so far, the category can be "Development". Perhaps we could also populate all of the extra labels for extra metadata as we sometimes label bounties as "CI/CD" or "Solidity" or "UI/UX"
Ultimately we want to allow non developers to contribute to DAOs and I think we might be able to get it to work with this current infrastructure.
Beta Was this translation helpful? Give feedback.
All reactions