|
|
| Line 1: |
Line 1: |
| − | [[User:Jruderman|Jesse Ruderman]]: I often wonder what it is that motivates me to contribute to Firefox and create my own open-source software. Maybe I'll find out by joining this project.
| |
| | | | |
| − | [[User:IKing|Ian King]]: I'm interested in the subject matter, and I'm inclined to join if you'll have me. What's the overall approach? Or is that to be hashed out yet? It seems it could incorporate both new data - for which it would be necessary to formulate a good interview - and reviews of positions expressed in existing literature, e.g. Eric Raymond. I wonder if it would be interesting to examine the motivation behind licensing choices? That one paper we read for tonight (9/28) is an ode to the GPL, while BobGo's paper thrashes it soundly. Does Stallman's vision for the GPL really ring true today, are programmers simply defaulting to it, or has its viral nature given them no choice? Seems that's an element of the choice to go OSS.
| |
| − |
| |
| − | This collaboration could be quite interesting, since I'm employed by one of those "commercial" software companies. I've done work here that's required me to reflect considerably on the nature of open source and the different marketplace it represents, but by necessity I'm not a participant in that marketplace.
| |
| − |
| |
| − | [[User:KWatt|Kevin Watt]]: I don't think I've done anything quite so useful as contributing to Firefox, but before coming to Cal I was fairly active in contributing open-source software for modeling business situations, as well as generic code hacking and bug fixes for random software (ircd and irc bots, WYSIWYG html editors in their [very] early days, and most recently, a generic conversion program for Word files to PDF). I was also involved in some more infamous software design activities that I'll omit here, but I think there is an interesting open-source model that can be allied to those activities as well. Anyway, like Jesse, I am rather curious about what motivated me, as a junior high/high school student, to contribute time and code to open-source efforts. As an IT Policy course, I think the question of what inspires innovation is especially salient.
| |
| − |
| |
| − | Now, since we're a very geographically dispersed group, how do we envision collaboration for this policy brief? Do we want to restrict communication to the Wiki, or should we create some kind of mailing list?
| |
| − |
| |
| − | [[User:IKing|Ian King]]: I suggest we start with an attempt to use the Wiki; if that doesn't work out, I can set up a list on my server, if you'd like. How shall we begin creating an outline? I'd suggest we all offer bullet points in an outline on the Wiki here, and then let's try to organize them into a coherent structure. I'd start writing, but I have a family obligation right now :-) but I'll probably be back later.
| |
| − |
| |
| − | [[User:garf|Gail Frederick]]: On the organizational point, I envision us writing individual or pair sections on related subtopics, and stitching them together into the policy brief. I know I have a subtopic interest that I wish to pursue. Please add your ideas and plans into the project description draft! I hope we can take our individual interests, run with them, and merge into a wide survey of the motivations and rewards of open source.
| |
| − |
| |
| − | Look on the "article" section of this Wiki page for mailing list information.
| |
| − |
| |
| − | On the "motivations and rewards" topic, we never really defined whose "motivations and rewards" we are studying. Do we mean motivations and rewards of producting, consuming or propagating open source projects? Without much thought, I define them as (Producer = Programmer, Consumer = "civilian" - seeker of software product, customer of traditional commercial software, Propagator = incubator of project, like OSDN or sourceforge.net or similar...). Maybe the different targets of the "motivations and rewards" moniker translate into sub-topics or chapters? Just brainstorming here...
| |
| − |
| |
| − | [[User:IKing|Ian King]]: I'd add a subtopic of governmental entities who create policy that supports or even mandates OSS, and I'm happy to stake out this one. :-) OSS could be a flash in the pan but for entire nations that have mandated its adoption - what is ''their'' motivation? What is the perceived advantage?
| |
| − |
| |
| − | [[User:garf|Gail Frederick]]: I think our topic statement is looking a little thin .... maybe we can work on making it a true statement of intent for our paper? Maybe we can start by agreeing on the list of stakeholders for open source projects / products -- then talking about motivations of each stakeholder? Also, we barely have talked about rewards...
| |
| − |
| |
| − | [[User:garf|Gail Frederick]]: (11/6/2004) I haven't heard much from Kevin Watt and Jesse Ruderman in over a week -- are you two still on our project team? Please make contact on the Wiki or via email so we know whether and how you are participating...
| |
| − |
| |
| − | == Policy Brief Organization ==
| |
| − |
| |
| − | [[User:RLM|Richard Michaelson]]: The structure of our policy brief likely will have 7 components: the 4 chapters, an introduction, a conclusion, and an executive summary. I also suggest the use of boxes (with text) as a way to improve our paper's readability and allow for discussion of related topics (e.g., a detailed explanation of IBM, interviews of Chinese government officials, etc) that may not fit well in the main body of our paper. This also gives us flexibility in how we contribute to chapters with 2+ people.
| |
