search

openulmus / openulmus.org

Openulmus.org - an open collective sustained project for the public production and sharing of knowledge
MIT License
6 stars 2 forks source link

Determine the essential roles needed to operate Open Ulmus #2

Open btopro opened 7 years ago

btopro commented 7 years ago

'Determine the essential roles needed to operate Open Ulmus' #15 (comment). We need to have a baseline understanding of each role needed to run an Open Ulmus instance. These roles will be finalized in the wiki and any contributors (interns/mentees) to individual projects that run Open Ulmus (drupal open learning, etc.) will be updated on a project to project basis.

kat-wehr commented 6 years ago

I can go 5-10 hrs/week as needed based on project scope month to month. I have an 8-5 job that in reality does not involve any ELMS stuff, so I need to make sure I'm doing my best to keep day job hours and consulting hours separate in order to stay out of trouble. My 8-5 job runs me ragged at certain times of the year (like right now - gearing up for new semester) but then at other times (spring/summer months) I have a lot of mental bandwidth post 5 pm to bang out additional work.

The work of an ID and efficiency is based a lot on the client as well and how complete of a picture they have going into a project, and also how organized/timely/communicative they are. If the ID has to hold their hand and work through their ideas with them from ground zero through completion then it's a lot more time consuming than working with a client who knows what they want right away, can provide a detailed plan and let the ID do the work and just provide timely feedback.

cleverington commented 6 years ago

My availability is roughly along the same lines as @kat-wehs.

As for the existing Roles, if the current version of the Wiki feels insufficient, we need to separate the Role-requirements into Phases and create a separate issue.

I closed out the task because continually re-hashing Roles at this stage is Scope Creep. Let's schedule a revisit of this topic early January and focus our efforts on MVP items. With the knowledge that we are on 'paid' time (once sponsorship arrives), we need to focus our hours unto tasks within the current projects.

We have confirmed contributions and efforts of @kat-wehr, @mmilutinovic1313, @gusaus, and @cleverington for the Core Team.

Also, I back-tracked some of @gusaus changes:

gusaus commented 6 years ago

Personally I think today we made some huge steps forward 'cuz team members like @btopro and @kat-wehr provided clarity in terms ideal scope of responsibilities (sorry if I'm just making up clever terms) and realistic short term and long term commitment towards managing, maintaining, and sustaining Open Ulmus. That in turn should provide us with a better sense of who/what is needed to scope out and launch the Open Ulmus MVP https://github.com/elmsln/openulmus.org/issues/1

Trying to avoid too much of a groundhog day situation, I'd just refer back to my comment from yesterday regarding my reasoning for reopening this task https://github.com/elmsln/openulmus.org/issues/2#issuecomment-346133430

With that, I'd recommend we consider the google doc or wiki more of an internal working doc as we scope out the product.

djfusco commented 6 years ago

Like the others, I also have a day job and also got a new assignment in my job at Penn State. My time, like @kat-wehr goes in highs and lows, depending on the time of year. I could give 5-10 hours per week. I'm most likely able to help with server-side stuff, including cloud hosting, as well as some data exchange scripting and xAPI things. I'm better when you let me know 'we need X by date Y' and some direction on where you want to go.

gusaus commented 6 years ago

With clarity from the entire team, I'd like to suggest we do the following -

mmilutinovic013 commented 6 years ago

@gusaus -- what is a DOYOT project?

gusaus commented 6 years ago

We touched on this during our last meeting #55 , but only a few team members have reviewed and provided input in the discussion thread. As it's important to gauge current interest and availability from everybody who has done so previously in this issue, I'd suggest the following 'before' the next meeting.

If we do that, we should have a better idea for what we need to review and decide during our next meeting.

gusaus commented 6 years ago

Ok - based on our decision to go for 501c3 status #57 and alter our mission and scope #58 to ensure we're approved, I think we do need to make some adjustments to how we’re defining and trying to budget for the Open Ulmus Core Team

First it would be good to gauge current interest and availability from everybody who has done so previously in this issue https://github.com/openulmus/openulmus.org/issues/2#issuecomment-366797773

Based on the 5-10 hrs/wk range of total availability that everybody noted previously, I think we should consolidate all roles needed to manage Open Ulmus under ‘Program Team’ https://github.com/openulmus/openulmus.org/wiki/2.-Open-Ulmus-Core-Team#program-team

Platform Team is sort of a mishmash of roles https://github.com/openulmus/openulmus.org/wiki/2.-Open-Ulmus-Core-Team#platform-team

Aside from time needed for platform updates (which we could estimate as part of the hosting cost), the other roles are more about developing the platforms #1 or creating content. Funds for that type of work should actually flow through ELMS:LN, Open Learning Labs https://github.com/openlearninglabs/administration/wiki/Budget-and-Sustainability#sustainability, or some other partner collective.

Does that make sense?