This thread is to decide on the roles and responsibilities that we need to have in the consortium.
Please input the roles and responsibilities that you have in mind below in order for us to brainstorm them during our meetings and come up with a final structure.
Suggestions:
Chairperson: leading meetings and managing things from high level
Dev. Lead: leading development efforts and implementation
Community Lead: leading community activities, communication and social media
Partnerships Lead: leading discussions with existing and new partners
Hey - overall, having multiple leaders makes sense, provided you have enough folks to do that. We should make sure the Partnerships Lead is connected with James Sullivan, and the Community Lead is connected to Dan Brown.
I would recommend the term ‘Chairperson’ vs. ‘Chairman,’ just to ensure gender-neutral terms.
We’re in the process of finalizing the details, but I’d like to give you a brief overview of the roles we’re defining:
Development Lead: This role involves leading the software development of our open source projects. Responsibilities include setting architectures, defining goals, creating timelines, engaging in discussions with community developers, and occasionally contributing to software development.
Partnerships Lead: This role focuses on managing communications with our existing partners to understand their needs, reaching out to potential new companies to join our initiative, and coordinating with LF Energy.
As we are still in the early stages of onboarding people and the community is relatively small, everyone will be expected to contribute across various aspects. However, it’s important that each lead takes ownership of their respective goals and timelines.
We’re open to any suggestions or thoughts you might have, so please feel free to share.
In terms of commitments, we would need you to:
Attend the BDA meetings, scheduled for Tuesdays at 6:30 PM GMT+2.
Achieve the goals set for your role, with the support and collaboration of our community.