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
You, the community, are the stakeholders. You are opening issues and pull requests of various size (effort) and value ($$). Thank you! The feedback is a gift and we love code! 😄
I'm listening to you and making recommendations on what should go into the the backlog (the funnel) and (sadly) what should probably not. 👍 👎
Note that issues and pull requests are broken down into smaller sizes as they go through the funnel.
(By the way, not pictured are all the other funnels that also lead to the dev team. Many of these funnels contain grant deliverables that get priority. 🤔 )
If my recommendations are approved, the issues and pull requests will go to the dev team (which includes me) to be coded up or reviewed or tweaked, and eventually merged and released. 🎉 🚀 That's the goal anyway.
As releases go out to you, the stakeholders, you'll get additional ideas and write more code, allowing the cycle to continue. 🎉 🚀
At the moment, the Community Backlog column is mostly full of pull requests rather than issues. This is because we have many open pull requests (77 as of this writing) and I feel that we should make a decision about them. Move them forward or close them. I've put smaller pull requests that I think provide good value at the top of the column. Large, thorny pull requests are not at the top. 😄 Again, let's keep talking! This process is brand new.
p.s. The diagram above comes from an absolutely fabulous video called Agile Product Ownership in a Nutshell by Henrik Kniberg. I highly recommend watching it!
This README is for the Dataverse "Community Backlog" column at https://github.com/orgs/IQSS/projects/34/views/1
(We are also working on a customized view of just this column at https://github.com/orgs/IQSS/projects/34/views/6 .)
Please note the funnel in the diagram below:
You, the community, are the stakeholders. You are opening issues and pull requests of various size (effort) and value ($$). Thank you! The feedback is a gift and we love code! 😄
I'm listening to you and making recommendations on what should go into the the backlog (the funnel) and (sadly) what should probably not. 👍 👎
Note that issues and pull requests are broken down into smaller sizes as they go through the funnel.
(By the way, not pictured are all the other funnels that also lead to the dev team. Many of these funnels contain grant deliverables that get priority. 🤔 )
If my recommendations are approved, the issues and pull requests will go to the dev team (which includes me) to be coded up or reviewed or tweaked, and eventually merged and released. 🎉 🚀 That's the goal anyway.
As releases go out to you, the stakeholders, you'll get additional ideas and write more code, allowing the cycle to continue. 🎉 🚀
As show in the diagram, we all should communicate throughout this adventure. Let's all talk in real time (timezones permitting) at https://chat.dataverse.org or asynchronously on Dataverse mailing list at https://groups.google.com/g/dataverse-community 🐱 💬 🐶 💬
At the moment, the Community Backlog column is mostly full of pull requests rather than issues. This is because we have many open pull requests (77 as of this writing) and I feel that we should make a decision about them. Move them forward or close them. I've put smaller pull requests that I think provide good value at the top of the column. Large, thorny pull requests are not at the top. 😄 Again, let's keep talking! This process is brand new.
p.s. The diagram above comes from an absolutely fabulous video called Agile Product Ownership in a Nutshell by Henrik Kniberg. I highly recommend watching it!
p.p.s We talked about the board during the 2022-12-13 Dataverse Community Call and mentioned that discussion in the 2022-12 Dataverse Community News. There's an issue to update the guides about the old vs. new boards:
The text was updated successfully, but these errors were encountered: