Some projects work to actively alienate corporations trying to contribute because of ideology. This is not the path that will lead us to sustainable open source software development and companies that can contribute responsibly.
:+1:
/me pats IBM on the back one more time. :)
There are (a very few) companies that balance these worlds of community and commerce well.
If you know of another, please reply!
The company refuses to expand the core development team with non-employees
From what I've seen these projects are often licensed under the AGPL and essentially amount to "loss leader source." Community === "add on builders" and "consumers" in the minds of the product team not future "land owners."
Be sure the project is community lead (or in transition that way at least!) before you sign that CLA...or even bother with that patch.
TwitterOSS team (hint: their funding as a department was cut)
Sad news.
sometimes you find a bounty like this one where a company has added a significant amount to a bug
Unsurprisingly (to me) that company is IBM.
Keep up the greatness!
Steven Downes on return of investment from OER.
Useful introduction to how source maps work. The code for Mozilla's source map library is very readable and an easy way to test this in practice.
The Training and Learning Architecture (TLA) encompasses a set of standardized Web service specifications and Open Source Software (OSS) designed to create a rich environment for connected training and learning.
open source tools
a chaotic way of managing a project as that project gets big
Don't let it get big? Maybe.
the nature of low-bandwidth communication on the internet probably just exposes you to misunderstandings and you end up stressing out over things vs being the friends you normally would.
Engineers who worked on a lot of open source projects had high levels of creativity
Developers felt more ownership over their work, and pride in it
Open source developers work well together because of their similar ways of thinking
Peer pressure from GitHub—having their name on a project—was a big motivator for engineers to work harder and not let the community of users down.
If they leave, they're likely to keep working on the project, so you're still getting value for free!
Any contributor to our open source projects is already familiar with a bit of software that we use internally and would require less training if they joined the company.
At Twitter, our open source program has a team of developer advocates focused on growing open source ecosystems which are important for us to ensure they thrive and evolve to our benefit.
hosting events, speaking at conferences, reaching out to contributors, writing documentation to lower the barrier of entry to new contributors
suffers from an over protective legal organization
respecting open source licenses to making it easier for engineers to open source code and ensuring we’re giving back to the open source projects we depend on
the critical role that big data open source projects play in the Internet of Things (IoT).
Issues can be reported at: https://github.com/hypothesis/h/issues
If we believe in equality, if we believe in participatory democracy and participatory culture, if we believe in people and progressive social change, if we believe in sustainability in all its environmental and economic and psychological manifestations, then we need to do better than slap that adjective “open” onto our projects and act as though that’s sufficient or — and this is hard, I know — even sound.
WordPress, Drupal and many other complete web applications come ready made for deployment.
Even if cheap, I wonder what the TCO (total cost of ownership is like)
Technology leadership is not defined by patents, which history has repeatedly shown to be small protection indeed against a determined competitor, but rather by the ability of a company to attract and motivate the world’s most talented engineers. We believe that applying the open source philosophy to our patents will strengthen rather than diminish Tesla’s position in this regard.
"Technology leadership is....defined by...the ability of a company to attract and motivate the world's most talented engineers."
The key components of this applied "open source philosophy" seem to be about increasing input, visibility, and collective motivation by taking fear out of the interaction equation.
THE ART OF
The Art of Community
For example, imagine you are annotating the second page of a New York Times article. You probably want to see your annotation when you are looking at the article later as a single page, right? Or perhaps you've annotated the HTML for a PLOS ONE article. Wouldn't you like to see those annotations when you are looking at the PDF version of the same article? If annotations were only associated with the URL you happened to be looking at in your browser then the scenarios above would not work, because the documents being annotated all have different URLs.
Publisher Best Practices is a great idea that I would like to see codified in the authoring and publishing tools to make the practices commonplace by default.
I would like to mix PBP with other techniques, though, for richer connection between source and rendering-- I have some source mapping ideas that make it possible to keep annotations linked even as the original source is edited over time.
Open Source[edit] LightSide[43] EASE[44] - Published by EdX.
Open Source software for Automated Essay Scoring