1. 16:29 30th Sep 2014

    Notes: 13

    Reblogged from yahooeng


    Today we are happy to open source gifshot, a client-side JavaScript library that can create animated GIFs from media streams (e.g. webcam), videos (e.g. mp4), or images (e.g. png). Gifshot leverages cutting edge browser APIs (sorry IE9 and below) such as WebRTC, FileSystem, Video,…

  2. image: Download

    This was drawn during the wedding ceremony itself, and it captured the moment.

    This was drawn during the wedding ceremony itself, and it captured the moment.

  3. image: Download

    Visiting the Cardo

    Visiting the Cardo

  4. 03:09 15th Aug 2014

    Notes: 1110

    Reblogged from littlelimpstiff14u2


    by Nastia VoynovskayaPosted on July 25, 2014
    Kiev-based photographer Oleg Oprisco’s works modify small details in their real-world settings to convey the essence of fantasy. It is as if his photos give off the fresh, dewy aroma of a wild escape to a desolate countryside that seems to belong to no specific time or place. In one piece, a girl holds up a rolled-up piece of a grassy lawn. Though anyone could do this in real life, in the photograph she seems to wield a sort of power over the land with her powerful, summoning gaze. In another, a model holds a stained umbrella that briefly gives the impression of a multi-colored rain shower before Oprisco’s process of dousing the set in paint gives itself away. These small details invite viewers to indulge Oprisco’s innocent, storybook-like fantasies.
  5. What is Yahoo’s role in open source software development?

    Answer by Gil Yehuda:

    tl;dr: To be a good, contributing citizen. To use standard open source technology in our products when there is good code to use, and to create the new standards when that is needed. To attract the kind of developer who has proven Open Source cred already, with the promise that they’ll do even more once they get a purple badge.

    Longer answer: Yahoo engineers use lots of Open Source software in Yahoo’s products and tools. The company is built on Open Source in just about every section of the stack and corner of the code. When you use Open Source, you realize that code can have a life of its own beyond your particular use of it. This happens when you view code in a communal way — not just as a utilitarian tool. When you find problems with the code, you are very motivated to fix it, care for it, enhance it. Yahoo engineers do that with our code. We don’t just use code — we love code and care for it.

    So Yahoo contributes code fixes and enhancements to those Open Source projects. Not doing so would be foolish and shortsighted. Doing so shows that we care to curate and support the very ecosystem that supports us. It’s simply good business and good citizenship.

    Yahoo also contributes new projects that were created within Yahoo to the Open Source community. There are many examples of this which you can find on Yahoo’s http://Github.com/Yahoo page, in various Apache Software Foundation Communities, and in niche communities like CPAN and elsewhere.  This is how the top engineers work — we attract this talent because they know we respect their ethos, it’s our ethos too. Moreover by participating in the community, we work with others, not against them. This reduces the friction to partner — and this helps make Yahoo one of the best companies in the valley to partner with. Few companies in the world have the depth and breadth size and scope deals with Microsoft and Google and Facebook and Apple like Yahoo does.

    Some of the projects Yahoo contribute to have helped create and revolutionize the technology industry as a whole (like Big Data and Computational Advertising), yet many of the projects we publish are small and fairly insignificant to most people. The do however matter to the person who wrote that code and perhaps to a dozen or so others who use it. We don’t try to hit grandslams every time we publish code. We just want to make it a regular habit, to get good at it. To work out loud when we can, since it makes for better engineering, better documentation, good feedback, good discipline, etc. Sometimes we publish code that really makes a deep impact on many, and we accept pride for that. It feels good (See: What is it like to have a trending repository on GitHub?).

    We have some really talented Node.JS folks working in that community. Some of the most respected machine learning folks contributing that their community. Hadoop and many of its related projects were either created at Yahoo, brought in and scaled out (and published back), or stress tested at Yahoo to a degree that others would not be able to. We have folks working on Storm, Spark, Shark, Druid, Chef, Ceph, Pig, Jenkins, and a dozen other open source projects that deal with compute, storage, management, monitoring, configuration, and other elements of internet engineering at scale. We publish code in Perl, PHP, C++, Java, Objective C, Javascript, and more. We have a team dedicated to OpenStack, with developers who’s full time job is to contribute back to the OpenStack community. And we have a pretty solid set of activities in the open source mobile world — with contributions to iOS code, responsive design code in PureCSS, YUI, Mojito, Node.JS and in the Android space. (see: Does Yahoo have a good Android team? How do they compare with the engineers from companies like Square, Pinterest, or Yelp?, and some of my other answers on this site.)

    We have a very small ‘team’ of people who help make sure that we do this right — legally, with licenses, attributions on the code when we need to, CLA’s signed where appropriate, providing answers to questions about the various licenses that come up daily — with new hires who ask if they can still work on their favorite projects, acquisitions of companies (and their code), product launches (and our obligations w/r/t giving credit), partnerships (and the legal stuff), software purchases, and science publications (that usually contain code). On behalf of my ‘team’, I say hello and hope that you use our code, contribute to it, and be inspired to be great citizens in the communities that sustain you too.

    So I’d say Yahoo’s “role” is to be a good citizen, at least that’s what I’m striving for. Yahoo’s accomplishments in this space have been even more profound. I expect for this to continue, as it is very much a part of the engineering culture at Yahoo.
    What is Yahoo’s role in open source software development?
  6. 23:11 9th Aug 2014

    Notes: 382670

    Reblogged from sizvideos

  7. 12:43 28th May 2014

    Notes: 5

    Reblogged from yahoopolicy


    By Patricia Moll Kriese, Advisor to the CEO

    At Yahoo, social responsibility is more than just a tagline. Through Yahoo for Good, we strive to make doing good a daily habit both for our employees and our users. We take pride in the fact that we are an active partner in the communities in…

  8. How does copyright relate to open source licenses?

    Answer by Gil Yehuda:

    I’ll add a little color to the excellent answers here which could explain the strange but understandable relationship between how copyright law is designed to work, and how it applies to open source code. Moreover, I’ll explain why we are in the situation we are in with code, copyrights, and open source licenses

    Imagine you were a freelance writer working in Hollywood who wrote movie scripts. You spent hours writing what you thought was a fantastic movie with great dialogue. You pitched it to a movie executive who rejected the story, crushing your dreams of stardom. Somehow, someone got hold of your movie script and thought it was quite good, so she pitched it to a different producer, and landed a great deal for her, using your script (maybe she modified it, or not). You’d probably be upset.

    Copyright law protects your creative works (not ideas in your head, but the script you record on paper, a picture you take on film, a story you record on tape — or code you write on your computer), so that only you have the right to copy that work (right to copy = copyright). Someone else who finds your work cannot make a copy of it without your permission, nor can she display or perform your work without your permission. And she can’t present it to her favorite movie executive — even if she admits that she did not write the script; even if she says you wrote it. It’s not hers to share, it’s yours. The copyright protects you from someone taking your stuff without your permission. Of course, since you have the right to your movie script you also have the right to allow this other person to pitch it to a different movie executive — but she’d need permission from you — a license. You might pay her to pitch the script for you, you might ask her for money to have the rights to pitch the script. Or you might just share the script with her as a collaborator. You get to decide.

    When developers started to write source code in the 70’s, lawmakers felt that source code was similar to movie scripts. They involve creative effort and people are willing pay,  therefore they should be given the protection that other works of literature would get. Eventually, the Open Source movement began to inspire many developers to think about their code differently; that sharing their code permissively with other developers was worth more than keeping the code under copyright protection. Open Source projects demonstrated that opening code has significant value to the code quality, to the original author, and to the community of developers. Now, many developers would rather open their code so that others could use it and add to it. But the copyright-by-default laws creates the situation that if another developer takes your code (even if you were OK with it conceptually), you could decide to sue that developer (much like in the movie script case). Open Source licenses were created to enable authors to give explicit permission to others developers to use the code — protecting the intent of sharing from unintended legal consequences.

    As others have said in response to this question, the copyright is a statement that expresses the legal fact that you (or your company) owns the copyright on the code. You have a right to copy the code, and you have the right to grant others the right to use the code. The license is an expression of the right you grant others to use that code. You cannot grant rights to use code if you don’t have the rights in the first place. So you need the copyright (and it’s very helpful to add it explicitly), and then you can add the license on the code. If you just have code with no license, other people do not have the right to use the code (even if you don’t mind, you need to be explicit so that they know you are giving them permission). Open Source licenses grant broad permissions with (usually) very few conditions of use. Most common is that you have to give credit to the original author. Under some licenses, you have to be explicit about the changes you made to the code so that others can tell what you added. Other licenses require that changes you make to the code be publicized under certain conditions. So the specific open source license you use does matter.

    Back to being the movie script writer: lets say you wanted to write a script and publish it so that anyone could use it, could modify it, and could perform it (in other words, you’d rather build your reputation by giving your script for free, and getting feedback on it, instead of the all or nothing pitch to a movie executive). You could “open source” the script, but you would not use an Open Source license, rather an Open Content license (like the Creative Commons licenses which are designed for content). You’d still have the copyright on the script, and then you’d add the permissive license telling people they could use it (under the specific terms you select based on the license type you choose).

    Note: I am not a lawyer. Corrections to the above are invited.
    View Answer on Quora
  9. 06:40 20th Apr 2014

    Notes: 339421

    Reblogged from thatyamperson

    After a week of nonstop eating.

    After a week of nonstop eating.

  10. Is Open source more secure?

    Interesting article on GigaOm today about the OpenSSL bug and the implications to Open Source.

    I commented that Open Source is not fundamentally more secure, but it is fundamentally easier to become more secure.


  11. Enjoying the idea of Beethoven Barbershop during work.

    (Source: Spotify)

  12. In a striking example of poetic justice, a Massachusetts teenager who says she was fired from 7-Eleven for giving a cup of coffee to a homeless man has landed a new job within days—at a homeless-services organization. More on Yahoo Shine: How Going Undercover as Homeless Changed These Men “My lesson learned is that good deeds pay off,” Ava Lins, 19, tells Yahoo Shine.

  13. 14:19 11th Feb 2014

    Notes: 3871

    Reblogged from demand-progress

    image: Download


The NSA “is gathering nearly 5 billion records a day on the whereabouts of cellphones around the world.” (Washington Post)
Join us in protesting the National Security Agency’s wide-ranging invasion of privacy.
Take action →


    The NSA “is gathering nearly 5 billion records a day on the whereabouts of cellphones around the world.” (Washington Post)

    Join us in protesting the National Security Agency’s wide-ranging invasion of privacy.

    Take action →

  14. Listening and relaxing.

    (Source: Spotify)