Hey all, I've been part of pulling this initiative together and thought I'd just put together some of our early thoughts.
The primary purpose is to get the open source program managers from companies together. It turns out there are a bunch of challenges for companies who want to run open source projects effectively, and we discovered we had only rarely even shared our own experiences of doing so - let alone figured out how to improve things.
A roadmap for the group's work is still to be defined... at this point you should consider this an invite to get involved. But we imagine some of the outputs might include things like:
- shared best practices for running large open source programs well
- certain criteria or qualities that 'good' projects should aspire to (responsiveness to community, maintenance, test-coverage, clear licensing, etc)
- tooling & instrumentation that makes it easier for companies to reach and maintain those standards
- a directory of projects from members that meet some or all of those criteria
I don't want to imply that we're committing to do all of these, but perhaps these non-normative examples give a bit more colour to the sort of things we'll tackle.
If you're at all interested, please sign up. We hope to have a face-to-face workshop very soon to kick off the work and understand what members want to prioritize.
If I'm understanding the intent correctly, it sounds like the home page could use something like this:
"Does your company release open source projects? Would you like to
improve how you interact with the open source community to better manage
and run your projects? Join your peers at //TODO and collaborate on
practices, tools, and other ways to run a successful and effective open
source program."
Comments
Hey all, I've been part of pulling this initiative together and thought I'd just put together some of our early thoughts.
The primary purpose is to get the open source program managers from companies together. It turns out there are a bunch of challenges for companies who want to run open source projects effectively, and we discovered we had only rarely even shared our own experiences of doing so - let alone figured out how to improve things.
A roadmap for the group's work is still to be defined... at this point you should consider this an invite to get involved. But we imagine some of the outputs might include things like:
- shared best practices for running large open source programs well
- certain criteria or qualities that 'good' projects should aspire to (responsiveness to community, maintenance, test-coverage, clear licensing, etc)
- tooling & instrumentation that makes it easier for companies to reach and maintain those standards
- a directory of projects from members that meet some or all of those criteria
I don't want to imply that we're committing to do all of these, but perhaps these non-normative examples give a bit more colour to the sort of things we'll tackle.
If you're at all interested, please sign up. We hope to have a face-to-face workshop very soon to kick off the work and understand what members want to prioritize.
If I'm understanding the intent correctly, it sounds like the home page could use something like this:
Yes. Maybe this is why we are not in marketing :)
PS: we're going to use this text. Thanks!