Open gusaus opened 7 years ago
mmilutinovic1313 [1 minute ago] If we consider the 4 hat wearers to be Open Learning Lab people that would be the best way to think of it mmilutinovic1313 [< 1 minute ago] They run Open Ulmus but are aligned to the higher org
Let's look at this issue with this approach. We have to determine the rate and hours for the 4 hat bearers here. We know that they will post for resources against the Dojo - Open Ulmus - and Drupal Open Learning.
Rates proposed were:
Hat-wearing leads: $40-80 per hour Apprentices: $15-30 per hour
Rates Budgeted for in https://github.com/elmsln/openulmus.org/issues/5 were:
$100 / hour
We can also look at Forking https://docs.thinktandem.io/project-management/roles-responsibilities.html into a new repo under OpenUlmus.
Will research and make some notes. For example, the overall project may be the project-management/
I believe that this would constitute a Specialty (Individual) Project Team
Random Observation: As Open Learning Labs is to be the 'hand on the rudder' for OpenUlmus and both are OSS Projects, I believe it will be a good idea to ensure Open Learning Labs has two Program Mgrs at any given time.
Invariably there are going to be 'Life' blockers, because this will be a VERY part time job (during the initial year or two, at least), so having TWO hands on the rudder means those Blockers will only affect the individual, not the project.
I think we've agreed the same program team we're hashing out in https://docs.google.com/document/d/11g4tAxHIAu_LuTcDPx-9bFcBqBIxKt85KuKJeT1LvDM/edit#heading=h.35wt731xuosl would steer the ship initially until there's a budget for more staffing.
Goal again is generate enough funds for an average of 40hrs/month for 4 program leads via Drupal Dojo, Drupal Open Learning, and Open Ulmus collectives.
The platform and specialty project teams may also largely consist of the same people, but we'll have a better idea after properly scoping out the MVP for each.
I linked to a couple working docs above - https://github.com/openlearninglabs/administration/issues/2#issue-270856824
@mmilutinovic1313 As noted in https://docs.google.com/document/d/11g4tAxHIAu_LuTcDPx-9bFcBqBIxKt85KuKJeT1LvDM/edit?usp=sharing
Sound plan?
We need to determine the essential roles needed to run the service. A good bit of what is being worked out for Open Ulmus is relevant, but the breadth of services will require additional roles.
Here are links to two google docs in which we can draft essential roles needed to run the service
As we're setting up to be an open, transparent org, the following orgs could serve as inspiration -