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
As part of a recent Stacks grant the Ecosystem DAO will be displaying more information about SIPs through an external website.
An example can be seen here, although the link may change as a large part of this is still under development 🙂
Since the website data is served via what's available in the GitHub API, there were some open questions around what tags should be represented and used to help make the information easier to go through.
In the current interface GitHub issues = SIP Suggestions and GitHub pull requests (PRs) = SIP Proposals.
Issues don't contain any labels right now save some old Stacks 2.1 stuff, what would be the best way we could break them up and make them easier to digest? Do they fall into natural categories? https://github.com/stacksgov/sips/issues
Pull requests are labeled based on SIP status, which is helpful, but should we also add labels for considerations and other SIP-related definitions? https://github.com/stacksgov/sips/pulls
Open Q: should we define this structure in the README or similar?
Tagging @Hero-Gamer and issue #79 to get the discussion started 🎉
The text was updated successfully, but these errors were encountered:
As part of a recent Stacks grant the Ecosystem DAO will be displaying more information about SIPs through an external website.
An example can be seen here, although the link may change as a large part of this is still under development 🙂
Since the website data is served via what's available in the GitHub API, there were some open questions around what tags should be represented and used to help make the information easier to go through.
In the current interface GitHub issues = SIP Suggestions and GitHub pull requests (PRs) = SIP Proposals.
Issues don't contain any labels right now save some old
Stacks 2.1stuff, what would be the best way we could break them up and make them easier to digest? Do they fall into natural categories?https://github.com/stacksgov/sips/issues
Pull requests are labeled based on SIP status, which is helpful, but should we also add labels for considerations and other SIP-related definitions?
https://github.com/stacksgov/sips/pulls
Open Q: should we define this structure in the README or similar?
Tagging @Hero-Gamer and issue #79 to get the discussion started 🎉
The text was updated successfully, but these errors were encountered: