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.
In addition to the quarterly consultation, we meet on regular basis in three channels:
These form initial discussion and debate on new ideas before they are further tested and actioned on the GitHub issue queue.
If you have an idea you'd like to suggest, the best places to begin are:
In any case we'll help you convert it to an actionable proposal for the correct group of consultation.
The agreed implementation doesn't cover my needs?
Even if your need can't be accommodated:
The Visual Framework allows "local rule". You won't be blocked from adding and overriding components.
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.