Posted 2014-04-25 by Greg Wilson in Community, Lab Meeting.
We held another online lab meeting yesterday,
which covered a fairly wide range of topics.
The notes are below;
comments about what we missed,
and suggestions for the next lab meeting,
are very welcome.
Mozilla Science Lab one year on (Kaitlin T.)
Hoping to bring a couple more people onto the team in the next couple of months
Two sessions of office hours (first right after this call) on the "DOI for Code" project
Badging for contributions to papers
Governance (Kaitlin T.)
Software Carpentry has grown too big for one person to keep track of all the changes being made to all the lesson material. This is good news, but it does mean that the way we do things has to grow as well. We'd therefore like to try the following:
Small changes and additions will be merged when and as they're ready.
Large changes and additions will be voted on at lab meetings; every instructor will get to vote.
Any proposed changes to the Code of Conduct and/or requirements for calling a workshop "Software Carpentry" will also be voted on at lab meetings; again, every instructor will get to vote.
We will vote at the September 2014 lab meeting on whether to keep these rules or try something else.
Q: who gets to decide what's big or not?
For now, Greg will, but will err on the side of caution (when in doubt, put it up for a vote).
Q: what about the really big things being done by small teams (e.g., the R module being put together by half a dozen people)? If the changes all had to be voted on, it would never happen.
Agreed; in that case, a vote up front (as we did for the MATLAB material) may work better.
As with the previous Q, we'll try a few things for the next few months and figure out what we should have done.
Q: any type of "owner(s)" of each module to approve small changes?