9 Matching Annotations
  1. Oct 2018
  2. May 2018
  3. Mar 2018
    1. Can you imagine a day when many of the most important contributions to many of the most important OER and open textbook projects are made by people who work for for-profit publishers and other companies, and who contribute to OER as part of their formal job responsibilities? Can you imagine a day when many of the world’s most-used OER were originally published by companies, who continue to invest in their ongoing updates and maintenance? Can you imagine a day when companies are releasing millions of new words, images, videos, and interactives under open licenses each year?

      Sounds a lot like the move of corps to contribute to open source code community.

  4. Jan 2018
    1. The school's founders believe that the commodification and ownership of knowledge is the primary reason for the inequity in access to quality educational resources.

      wow. nice!

  5. Sep 2017
  6. May 2014
    1. MIT-licensed

      It's stored in a [COPYRIGHT](https://github.com/gittip/aspen-python/blob/master/COPYRIGHT) file rather than a LICENSE one, but it's well licensed, all the same. :)

  7. Dec 2013
    1. Well-intentioned (and grammatically correct) though it may be, changing pronouns has very little impact on inclusivity. When you’re starting from a default position of exclusivity, when people automatically associate you with the tone-deaf cringefests that are one of open source’s worst problems, when people see your community and your leadership and find very few diverse participants, when your actions don’t illustrate how people can play a role if they won’t prove themselves better coders than those already involved, hanging up a sign saying “no one is disallowed” is not going to be enough. Saying you want to be inclusive does not create a culture of inclusivity.

      Actions, not words.

    2. I do not maintain any big open source projects, but in talking to people who do it’s become my understanding that the bulk of the work is sifting through issues and pull requests, not actually coding. The former is the thing they consider hardest, the thing that burns them out, their most overwhelming responsibility.