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
We should improve the documentation around the structure of the project. Roles and responsibilities should be defined. Possibly including an org chart should be made of how the teams and committees interact with individual sub-projects.
The text was updated successfully, but these errors were encountered:
So, to be completely honest, most of that document was one of two things:
Writing out how things currently worked from a practical perspective, in order to, as frequently asked, provide "concrete documentation" on how stuff worked, and in the event that we got bus'd and someone else needed to take over.
Some well-received suggestions like the idea of technical teams or subproject leaders, which should be moved forward with, but for the most part never were due to lack of apparent interest from anyone.
So at this point, I'm pretty unsure about what anyone really wants out of this particular piece of documentation, and what it's ultimate purpose is, aside from being a living document about how I intend the project to work, and how it has worked, short-term.
We should improve the documentation around the structure of the project. Roles and responsibilities should be defined. Possibly including an org chart should be made of how the teams and committees interact with individual sub-projects.
The text was updated successfully, but these errors were encountered: