6085 comments
2357 subscribers
6224 on Twitter
Subscribe! Feed reader E-mail

Ethical issues in open source

([[OpenSource#note1][OpenSource:1]]”[[oss]]”[[OpenSourceIssues#note1][OpenSourceIssues:1]]”[[ToBlog#note1][ToBlog:1]])

One of my students e-mailed me asking for help finding interesting
ethical issues in open source. Here’s the partial list I sent him:

  • What is the fundamental ethical issue behind open source software?
    There are zealots in both the open source and closed source camps,
    but the world isn’t as black and white as people paint it. What do
    _you_ personally feel about the issue of open source? Think about
    this a great deal. I think it’ll give you an aha moment. =) This is
    something really worth writing about.
  • Think about the difference between open source software and closed
    source software, and the difference between free software and
    commercial software. Note that free != open source, and commercial
    != closed source. Think about what the different combinations mean
    from the point of view of users, developers, and companies.
  • Businesses would like to be able to hire fresh graduates and put
    them to work right away without having to train them in the specific
    software used in the business. Learning how to properly use a
    toolset takes a lot of time, and these companies argue that this
    kind of training should be part of students’ formal education. In
    addition, many HR personnel filter resumes based on keyword.
    Students also sometimes become restless when they’re asked to use
    languages or toolsets not seen in the job ads. As a result, there’s
    strong incentive to teach the quirks of vendor-specific products
    like Microsoft Visual Studio .NET instead of focusing on general
    ideas. This is one of the biggest barriers to open source adoption
    in schools. Should schools cater to their market, or should they
    also explore alternatives?
  • Large companies complain about the unlicensed distribution and use
    of commercial software (popularly known as piracy). However, it
    actually strengthens dominant companies. For example, would we
    really be so dependent on Microsoft Office if people only used
    legitimate copies? If enough people chose not to buy Microsoft
    Office, then alternative office suites could flourish.
    Unfortunately, the unlicensed distribution and use of software means
    that other people can assume people run Microsoft Office, leading to
    a vicious cycle. What do you think about that?
  • Non-trivial software programs have errors. Sometimes these
    errors are severe, exposing your system to attacks. Some major
    software vendors practice ‘security through obscurity’; security
    holes are not publicized, and the companies sometimes aggressively
    go after whistle-blowers who try to point out weaknesses in the
    software. Because the companies are the only ones with access to the
    source, they are the only ones who can fix the broken programs, and
    their resources are limited. On the other hand, open source exposes
    all source code for potential audit. This means that other
    organizations and developers can examine the code for security
    errors, which often results in faster fixes when an exploit is
    actually discovered. On the other hand, it also means that crackers
    who want to exploit systems can find holes more easily. What do you
    think about disclosure versus non-disclosure?
  • Many people in the Philippines are not completely comfortable with
    English. We are too small a market for multinational companies to
    develop Tagalog versions, but some volunteers have been working on
    translating open source software. This has met with mixed reactions.
    Some people say that localizing software for the Philippines is a
    waste of time and students should get used to English versions right
    away; others say that localization is the key to helping more
    Filipinos get into information technology. What do you think?
  • Closed source software tends to optimize for number of features and
    ease of use, because that’s what draws customers. It makes common
    things easier. Open source software often comes with a high learning
    curve but focuses on power and security, making it easier for people
    to use it to fit their individual needs. Think about the different
    markets for open source and closed source software, particularly in
    terms of security. What are the implications of these choices?
  • Open source means there’s a lot of code out there that you can base your
    programming projects on. As a student, where should you draw the line on
    acceptable use of other people’s code?
  • Closed source software often carries a “click-through license”
    severely limiting your rights and giving no warranty anyway
    (although this last part is buried in the fine print). Open source
    software tells you right away that there is no warranty. It’s kinda
    funny the way closed source companies keep criticizing the fact that
    open source software isn’t backed by a company. Look into the
    usefulness of support contracts for large and small clients. (Hah.
    Leading question. Sorry. ;) )
  • What do you think about NDAs?

On Technorati: ,

Short URL: http://sachachua.com/blog/p/2541

On This Day...

  • 2013: Imagining the next five years and planning 2013 — One of the assignments in the Rockstar Scribe course I’m taking through Alphachimp University (affiliate link) is to sketch where [...]
  • 2012: Quantified Awesome: Squishing my excuses — I’ve been fiddling with Quantified Awesome, this personal dashboard that I’m building so that I can keep track of what’s [...]
  • 2011: Sketches: If you want to make the most of your next conference, you should blog
  • 2010: Weekly review: Weeks ending December 27, 2009 and January 3, 2010 — Busy, busy, busy! From the previous week’s plans for the week ending December 27, 2009: Work Set up Idea Lab needed for January [...]
  • 2010: How I explore my interests — Looking for your passions? You might be starting with the wrong question. Except in rare circumstances, passion doesn’t hit people [...]
  • 2009: Hooray! Tax-free savings account! — To encourage people to save, the Canadian government created a tax-free savings account. You put after-tax dollars into it, and [...]
  • 2009: Ideas for making my work more effective and efficient, creating value, and rocking my work — Change to Ubuntu Set up virtual machine for my Windows partition Use Emacs to handle my mail? Hard to do calendar acceptance Set [...]
  • 2008: Working two jobs — “Next time I do this, I’m going to have to find a day job that isn’t this similar to my [...]
  • 2008: Tagging in Org – plus bonus code for timeclocks and tags! — The section on projects introduced tags as a way to differentiate active and inactive projects. In this section, you’ll learn more [...]
  • 2007: Deja vu — The Internet is still crawling. Takes me back to the days of BBSing, when you could type faster than the modem [...]
  • 2007: Hate is as useful as love — … sometimes even more so. I’m beginning to hate the stress I feel about this thesis. The best way to deal with [...]
  • 2007: Working through the funk — I felt tired this morning. Things weren’t working smoothly. It turns out that the Philippines is probably not part of the [...]
  • 2007: Whatever gets the job done — I should’ve tried dialing into the IBM conference center last night to confirm that our landline could connect to it. Had [...]
  • 2007: It’s nice to be missed! — Bryce Johnson e-mailed me to ask me why I hadn’t signed up for Enterprise Camp. I sent my regrets and explained that [...]
  • 2006: It’s official – I’ll be working on social search! — I’m thrilled to report that a large company has given the go signal for research on social computing. Social search, in [...]
  • 2005: Emacs channel chat logs — Also, if someone can help me set up logging (split into text files by day, please) for irc://irc.freenode.net/#emacs, I volunteer to summarize [...]
  • 2005: Looking for Emacs blogs — I’d love to read more about the wonderful editor/way-of-life that is Emacs. Know of any Emacs-related blogs? (Occasional off-topics are fine.) Please [...]
  • 2005: debian-installer Tagalog translation complete! — ([[OpenSourceInThePhilippines#note4][OpenSourceInThePhilippines:4]]”[[oss]]”[[l10n]]”[[Localization]]) Eric Pareja and other volunteer translators have finished the translating level 1 of the debian-installer into Tagalog. Please check out the [...]
  • 2005: A question of scale — ([[OpenSource#note2][OpenSource:2]]”[[oss]]”[[OpenSourceIssues#note2][OpenSourceIssues:2]]”[[ToBlog#note2][ToBlog:2]]) Open source allows people to work on an individual basis. Developers can jumpstart their projects by using existing code, creating [...]
  • 2005: xtla goodness ([[EmacsTips#note19][EmacsTips:19]]”[[emacs]]) — I used xtla to browse my TLA archives today. xtla’s bookmarks and missing patch summary made merging missing patches much easier. [...]
  • 2005: Planner cited as a reason to defect to Emacs — (PlannerModeMaintenance”[[GoodKarma#note2][GoodKarma:2]]) You point is well taken. I find myself living in an application more and more. At work, it’s my [...]
  • 2004: Cat collar — That hated bell! Although it provided music for her every move, it stopped her from being sneaky – and being sneaky [...]
  • 2004: Counting in Dutch — - een kus, twee kussen - ik kus, jij kust, hij kust, wij kussen, jullie kussen, zij kussen
  • 2004: Factoid surprise — Looks like my bot implants are working. Remember that hack I added to ../emacs/bbdb-config.el to let me hippie-expand factoids? Earlier in #linuxhelp, [...]

Get the highlights as a PDF!

Stories from my Twenties: Highlights from a Decade of Blogging