That's a great question John.
The board are proposing is based on an Operating Board function.
The point of the exercise is to remove the rigid boxes of a traditional board. Real-world board of directors slide back and forth in engagement from project to project. This would allow board members to map their skills, experience and backgrounds against criteria for the project or initiative at hand.
To a certain degree the current board acts in this manner when it comes to projects and project phasing. An example of this was the EOLO partnership and BRRR workshop. Both projects required the executive members to engage at different levels and not particular to their defined roles. This agile effort is required to run a modern organization such as OREIO as we get into more ambitious projects.
The project roles within the Board would be voted upon by the Board.
There should be two protected roles which require formal education or real world experience: IT/Webmaster and Treasurer.
Michael