20 Matching Annotations
  1. Dec 2018
    1. All of this means that the only way to make this project sustainable is to turn it into an open source project that has a lot of different institutions invested in it so that we can have a front-end developer and a back-end developer who can spend one or two days a week making sure that it’s running smoothly. A big challenge for me is figuring out how can we activate an open source community around this project — specifically in this region. We need to consolidate the power of the open community so that our projects become more sustainable over the long term, both technically and financially.

      Needs over longer term. How people can help.

  2. Jun 2018
    1. Following the history of information technology and the massive trend towards open source, wecan see that democratizing information is the natural next step in the incessant trend to opensource, and thus the next big opportunity for innovation.
  3. Apr 2018
    1. “The number of moving parts is so vast, and several of them are under the control of different groups. There’s no way you could ever pull it together into an integrated system in the same way as you can in a single commercial product with, you know, a single maniac in the middle.”

      While there are indeed many moving parts modern Version Control Systems take care of that properly and automatically. The idea of a Benevolent dictatorship dictating the course of the software is not wrong, but it's been shown that it limits the software itself, no matter how smart or good the dictator is, he/she will never be able to think about every aspect and possible applications of the software. And considering this is a tool for research and experimentation, limiting the tool on purpose is not a very good idea, if you ask me. EVEN THEN, an open-source model leaves space for a Benevolent dictatorship (just as Linux and Google does for many of its FOSS projects), so that isn't really an argument against an open-source non-commercial developing model, in the worst case scenario.

  4. Feb 2018
    1. A better marketing plan for your open source software project The history and evolution of marketing in open source demonstrates a need for new approaches.

      marketing for open source

  5. Sep 2017
    1. A commercial/proprietary vendor borrows funding, setting that borrowed funding against potential future revenue; an open-source community pools present capacity to create a sustainable future.

      The roadmap differences between proprietary and open/community source.

    2. the fact that open-source software is the best guarantor of open standards

      while I agree, can we substantiate this claim?

  6. Aug 2017
    1. <script src="https://hypothes.is/embed.js" async></script>

      One line of code adds open, standards-based annotation to any website.

  7. May 2017
  8. Sep 2016
    1. We are unapologetic tinkerers who neither invent the wheel, nor are satisfied with the wheels already at our disposal.

      More and more, I come back to this as the core philosophy underpinning all I do in education.

  9. Jul 2016
    1. What is necessary, however, is that enough investment be put into presentation that newcomers can get past the initial obstacle of unfamiliarity.

      "Investment" being the key term, here...difficult judging how much time to invest in documentation and presentation, as opposed to continuing to develop the application.

      @Adrian: This comment was added using the Hypothes.is browser extension. You are viewing the file (archive.org) as rendered by the Hypothes.is proxy, which emulates the effect of that browser extension.

  10. May 2016
    1. Hence Linux, hence Wikipedia. Because these communities could grow and collaborate without geographic constraint, major work was done at significantly lower cost and often zero price.

      I would argue this was a mistake which we are now paying for structurally.

      If Linux was licensed such that derivative profitable use payed equity to the contributors to Linux, than many more people would share in the profits of Google, Facebook, Amazon, Rackspace, and so many more. If you take Google as an example, the company earns ~4.5M$ in profit per employee, of course 80% of their infrastructure is free software. Now imagine that each project on github was wired up using microtransaction systems and a system for assigning equity to those who contribute to the source code. Then as for-profit use of the application generates microtransactions that revenue is split by the current equity distribution to the equity holders.

      This distribution of revenue would allow for a hybrid between the open and distributed, also a more sovereign participation model of open source and the benefits of economic integration rather than simple exposure to economic exploitation.

  11. Feb 2014
    1. Think how much could be saved if new foundation grants begin requiring interoperability with a set of core community source projects.

      making interoperability a requirement for the receipt of a grant

    2. Other institutions can spend nothing and download the full, free software from the Sakai Project, but they will not have had any influence in the evolution of the software, nor will they have gained the considerable skills from inter-institutional knowledge-sharing.

      Influence and skills are benefits to contributing financially and in-kind to an open source project

    3. Ineffective governance of projects, unproductive debates over technology nuances, or failure to sustain an IT strategy over multiple years could all impede community source success.

      risks: behaviors that threaten community source success

    4. If partnering for software development were easy, it would be the norm today. It is not easy. It requires a cooperative mindset, disciplined choices among staff, and leaders’ consistent vision that the value of partnering over the long term exceeds the easy short-term gains of defecting to local priorities.

      partnering is hard

    5. the first challenge for participants in a community source project is to find like-minded partners who share a similar vision and timeline.

      find like-minded partners who share similar vision and timeline

    6. If the community source model proves viable, it will do so because it is an economically efficient coordinating mechanism for software investments in higher education as an industry. An analysis of any historical software system—online card catalogs, Web-based registration, course management systems—over a five-year period will reveal that individual institutions separately invested hundreds of millions of dollars in home-grown or commercial software. Can that flow of higher education resources be harnessed to create better economics and shared innovation outcomes for everyone?

      takeaways: community source needs to be an economically efficient coordinating mechanism for software investments. instead of each institution separately investing, these resources can be harnessed to create better economics and shared innovation outcomes for everyone

    1. When I organized the Freeware Summit (later known as the Open Source Summit) in 1998, it was because I recognized that there were multiple communities like that, that their leaders had never met in person, and would benefit from talking about common problems and shaping a common story. And being a media company, we organized a press conference at the end of the day to get that story out. And sure enough, two months later, Linus Torvalds was on the cover of Forbes , with full-page pictures inside of Larry Wall, Richard Stallman, Brian Behlendorf, and others.

      didn't realize "freeware" was used for a bit