The Visual Framework 2.0 is an open source project meant for the wider life science community, so we aim to be transparent about which components are canonized, what isn't and why decisions are made.
With this wide remit, the VF needs to be disciplined and flexible — empathy, consideration and consultation are key to our governance approach.
This process will help the overall quality of the VF and ensure users don’t need to fork code, can deliver quality sites and are able to deliver the correct corporate identity.
We aim to produce consistency and clear guidance on best practice. We also want to revise existing components to share lessons learned.
At a high level it follows this flow diagram.
My idea gets rejected? The agreed implemention doesn't cover my needs?
Even if your need can't be acconomidated in the global VF repositiory, You can still create and use a custom component in your local project. You can also share that component on npm for others to use.
We work to avoid entropy and fragmentation of the VF through a consultative process that has been proven to work with the VF 1.x.
We strive for an inclusive process that guides the 300+ developers to make the right decisions. We avoid being website police — we know past experience that we neither have the resources to monitor all sites nor can we force services to do a re-development.
We remain mindful to support communicating, collaborating, engaging.
Find an issue on this page? Propose a change or discuss it.