Hi, 2015-05-07 2:45 GMT+02:00 Niclas Hedhman <nic...@hedhman.org>:
> Daniel, > great initiative and I think it will become popular over time (new ideas > takes a while). > > 1) I think you should bring up the difference between "Open Source" a la > MySQL, i.e development at a corporation and releases thrown over the wall, > versus "Open Collaboration" a la Apache, where everything is expected to be > happening in the open, asynchronously and relatively slow pace. There is > also a third model, which is the "Lone Wolf GitHubber" who does it in the > open, maybe even get a lot of Pull Requests, but doesn't expand into a > developer's community. > I did a talk about this a while ago. I usually call this "Open Development". For me the difference is the following: - Open Source: the source code is free for everyone, like MySQL or Spring Framework - Open Development: Code is free, but also the organization and the processes around the code. There is no single company/entity that decides what is going on. Instead everybody is invited to work on the organization and the processes. Would probably be good to define a term for this. I like Open Development because at the end of the day we're doing software development. But Open Collaboration is fine as well. Benedikt > > 2) In the "Open Collaboration" model, there is then the need for some type > of Governance, which varies from "all volunteers" to "paid membership" to > "commercial invite only" or combination of all. I recall people mentioning > studies that shows that the dynamics changes dramatically as soon as "paid > for" _anything_ is introduced, where _anything" might be membership, > influence, developer time, evangelism and so on. > > 3) Adoption pattern(s). I recall that when Gianugo Rabellino (ASF Member) > was a SourceSense, they had an "Adoption Path" on their website which was > pretty thorough and something we take for granted, but made a lot of sense > to unaware commercial entities, and I think this "road map" of how to move > from "commercial-only" to "contributor" or even "project leader" is > important, even to students, who might end up spear-heading such changes > when they get jobs. > > Good Luck, and please keep this list in the loop > > Niclas > > On Thu, May 7, 2015 at 7:42 AM, Daniel Ruggeri <drugg...@primary.net> > wrote: > > > Hi, all; > > We had an interesting chat during the barcamp at ACNA2015 discussing > > ideas for spreading the word about open source. A few folks mentioned > > that it would be a good idea to partner with local universities to do > > talks/programs/etc. This sounded like an interesting idea so I > > squirreled it away in the back of my mind to be revisited after I > > settled back into the not-apachecon-routine... Interestingly enough, the > > day I got back from ApacheCon, a former professor (and mentor of mine) > > had asked if I would be willing to send the head of the IS program a > > letter of recommendation to accompany his nomination for an award. I > > mentioned the idea of doing something with the university regarding open > > source and introducing students to the idea in the P.S. of the email... > > Well, one conversation led to another and now I find myself teaching a > > credited class about open source in the fall. > > > > I think this is really neat and exciting but a challenge at the same > > time. Since the idea was planted in my head w/ the ASF, I thought it > > would be a good idea to float the question here to ask, "What would go > > in a college class about open source?" I think I can work through a > > syllabus, but I'd love to hear suggestions from those who have been > > involved in the ASF longer than my 4-ish years. > > > > Here are some of the ideas I have in mind for things to cover: > > *What IS open source? The history/birth of the movement. > > *Source control with Subversion/GIT/? > > *Bug tracking > > *Mailing lists/IRC/communication tools > > *Participating in an open source community > > *Lab(s) where we create a repository and commit/work through examples of > > using the tools > > *Guest speaker: How we make money with Open Source > > *Guest speaker: The Apache way (of course!) > > *Guest speaker: Why I trust open source software in my production > > environment > > *Guest speaker: Why NOT open source (?) > > *Popular open source licenses - discussion around each > > *??? > > > > I've only been on this list since ApacheCon this year, so I'm not sure > > what areas (if any) I would have commit access to in the community > > project, but I am more than willing to provide the materials I create as > > part of the class for those similarly interested in putting on such a > > program. > > > > P.S. > > I'm in the process of mining > > http://community.apache.org/speakers/slides.html for additional ideas, > > too... > > > > -- > > Daniel Ruggeri > > > > > > > -- > Niclas Hedhman, Software Developer > http://zest.apache.org - New Energy for Java > -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter
