Skip to main content

Home/ Future of the Web/ Group items tagged open source open

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Gonzalo San Gil, PhD.

Top 10 Open Source Developments of 2015 | Business | LinuxInsider - 0 views

www.linuxinsider.com/...evelopments-of-2015-82816.html

top 10 open source developments 2015

shared by Gonzalo San Gil, PhD. on 04 Dec 15 - No Cached
  • Gonzalo San Gil, PhD. on 04 Dec 15
     
    "Open source is driving an ever-expanding market. The notion of community-driven development is a growing disruption to proprietary software controlled by commercial vendors, and the free open source software concept has become a major disruption in industry and technology."
  • Gonzalo San Gil, PhD. on 04 Dec 15
     
    "Open source is driving an ever-expanding market. The notion of community-driven development is a growing disruption to proprietary software controlled by commercial vendors, and the free open source software concept has become a major disruption in industry and technology."
Gonzalo San Gil, PhD.

The impact of open cloud technologies on IT- The Inquirer - 0 views

www.theinquirer.net/...-open-cloud-technologies-on-it

impact open open source cloud technologies it Zemlin

shared by Gonzalo San Gil, PhD. on 15 Jun 15 - No Cached
  • Gonzalo San Gil, PhD. on 15 Jun 15
     
    " Column Open source developments are at the heart of new cloud technologies, says Jim Zemlin By Jim Zemlin Fri May 29 2015, 12:00 Jim Zemlin NOWHERE are we seeing more open source and collaborative development than in cloud computing."
  • Gonzalo San Gil, PhD. on 15 Jun 15
     
    " Column Open source developments are at the heart of new cloud technologies, says Jim Zemlin By Jim Zemlin Fri May 29 2015, 12:00 Jim Zemlin NOWHERE are we seeing more open source and collaborative development than in cloud computing."
Gonzalo San Gil, PhD.

Open Source Life: How the open movement will change everything - 1 views

envienta.net/...ovement-will-change-everything

open source movement will change Life

shared by Gonzalo San Gil, PhD. on 10 Aug 16 - No Cached
  • Gonzalo San Gil, PhD. on 10 Aug 16
     
    Dániel Szőke July 6, 2016 Lifestyle | Values, Topics Consider this: in just a few short years, the open-source encyclopedia Wikipedia has made closed-source encyclopedias obsolete - both the hard-bound kind and the CD-ROM or commercial online kind. Goodbye World Book and Brittanica.
  • Gonzalo San Gil, PhD. on 10 Aug 16
     
    Dániel Szőke July 6, 2016 Lifestyle | Values, Topics Consider this: in just a few short years, the open-source encyclopedia Wikipedia has made closed-source encyclopedias obsolete - both the hard-bound kind and the CD-ROM or commercial online kind. Goodbye World Book and Brittanica.
Paul Merrell

Sun on open source: What doesn't kill you... | The Open Road - CNET News - 0 views

news.cnet.com/8301-13505_3-10111061-16.html

Sun cloud computing business strategies open source

shared by Paul Merrell on 04 Dec 08 - Cached
  • Open source is the very thing that has crippled Sun, yet Sun is looking to open source, to hobble its competitors and revive its future. We often talk in the technology industry about the need to cannibalize your own business before someone else does it to you. Sun may be a little late off the starting blocks, but it's fascinating to watch its race against time.
  • Having open-sourced its own Solaris operating system, Sun has now tried to corner the market in open source databases with its $1bn purchase of MySQL, the database management system. It now also has its eyes set on the storage market, with a plan to inflict the same pain on incumbents there that it has itself felt from the rise of Linux. It's a hugely gutsy move. It remains to be seen whether it will work, but with Sun's OpenStorage business growing dramatically faster than the rest of the storage industry, it just might work.
Gonzalo San Gil, PhD.

How 2 Legal Cases May Decide the Future of Open Source Software | Network World [# ! Pe... - 0 views

www.networkworld.com/...e-of-open-source-software.html

open source egal case decide future bad use GPL bad use problem not code way software

shared by Gonzalo San Gil, PhD. on 10 Mar 15 - No Cached
    • Gonzalo San Gil, PhD.
      Gonzalo San Gil, PhD. on 10 Mar 15
       
      # ! This is: The 'Problem' is not 'Open Source' but # ! 'Those' who do a bad use...
    • Gonzalo San Gil, PhD.
      Gonzalo San Gil, PhD. on 10 Mar 15
       
      # ! The Attacks on Open Source continue... # ! wonder why... and take part for The Freedom.
  • Gonzalo San Gil, PhD. on 10 Mar 15
     
    [ The open source universe may soon be less collaborative and more litigious. Two cases now in the courts could open the legal floodgates. By Paul Rubens Follow CIO | Mar 6, 2015 6:00 AM PT ...]
Gary Edwards

XML Production Workflows? Start with the Web and XHTML - 0 views

quod.lib.umich.edu/...n-workflows-start-with-the-web

OpenWeb XML XHTML-CSS HTML5-CSS3-JavaScript IDML

shared by Gary Edwards on 07 Nov 13 - No Cached
  • Challenges: Some Ugly Truths The challenges of building—and living with—an XML workflow are clear enough. The return on investment is a long-term proposition. Regardless of the benefits XML may provide, the starting reality is that it represents a very different way of doing things than the one we are familiar with. The Word Processing and Desktop Publishing paradigm, based on the promise of onscreen, WYSIWYG layout, is so dominant as to be practically inescapable. It has proven really hard to get from here to there, no matter how attractive XML might be on paper. A considerable amount of organizational effort and labour must be expended up front in order to realize the benefits. This is why XML is often referred to as an “investment”: you sink a bunch of time and money up front, and realize the benefits—greater flexibility, multiple output options, searching and indexing, and general futureproofing—later, over the long haul. It is not a short-term return proposition. And, of course, the returns you are able to realize from your XML investment are commensurate with what you put in up front: fine-grained, semantically rich tagging is going to give you more potential for searchability and recombination than a looser, more general-purpose approach, but it sure costs more. For instance, the Text Encoding Initiative (TEI) is the grand example of pouring enormous amounts of energy into the up-front tagging, with a very open-ended set of possibilities down the line. TEI helpfully defines a level to which most of us do not have to aspire.[5] But understanding this on a theoretical level is only part of the challenge. There are many practical issues that must be addressed. Software and labour are two of the most critical. How do you get the content into XML in the first place? Unfortunately, despite two decades of people doing SGML and XML, this remains an ugly question.
  • Practical Challenges In 2009, there is still no truly likeable—let alone standard—editing and authoring software for XML. For many (myself included), the high-water mark here was Adobe’s FrameMaker, substantially developed by the late 1990s. With no substantial market for it, it is relegated today mostly to the tech writing industry, unavailable for the Mac, and just far enough afield from the kinds of tools we use today that its adoption represents a significant hurdle. And FrameMaker was the best of the breed; most of the other software in decent circulation are programmers’ tools—the sort of things that, as Michael Tamblyn pointed out, encourage editors to drink at their desks. The labour question represents a stumbling block as well. The skill-sets and mind-sets that effective XML editors need have limited overlap with those needed by literary and more traditional production editors. The need to think of documents as machine-readable databases is not something that comes naturally to folks steeped in literary culture. In combination with the sheer time and effort that rich tagging requires, many publishers simply outsource the tagging to India, drawing a division of labour that spans oceans, to put it mildly. Once you have XML content, then what do you do with it? How do you produce books from it? Presumably, you need to be able to produce print output as well as digital formats. But while the latter are new enough to be generally XML-friendly (e-book formats being largely XML based, for instance), there aren’t any straightforward, standard ways of moving XML content into the kind of print production environments we are used to seeing. This isn’t to say that there aren’t ways of getting print—even very high-quality print—output from XML, just that most of them involve replacing your prepress staff with Java programmers.
  • Why does this have to be so hard? It’s not that XML is new, or immature, or untested. Remember that the basics have been around, and in production, since the early 1980s at least. But we have to take account of a substantial and long-running cultural disconnect between traditional editorial and production processes (the ones most of us know intimately) and the ways computing people have approached things. Interestingly, this cultural divide looked rather different in the 1970s, when publishers were looking at how to move to digital typesetting. Back then, printers and software developers could speak the same language. But that was before the ascendancy of the Desktop Publishing paradigm, which computerized the publishing industry while at the same time isolating it culturally. Those of us who learned how to do things the Quark way or the Adobe way had little in common with people who programmed databases or document-management systems. Desktop publishing technology isolated us in a smooth, self-contained universe of toolbars, grid lines, and laser proofs. So, now that the reasons to get with this program, XML, loom large, how can we bridge this long-standing divide?
  • ...44 more annotations...
  • Using the Web as a Production Platform The answer, I think, is right in front of you. The bridge is the Web, a technology and platform that is fundamentally based on XML, and which many publishers are by now comfortably familiar with. Perhaps not entirely comfortably, but at least most publishers are already working with the Web; they already either know or have on staff people who understand it and can work with it. The foundation of our argument is this: rather than looking at jumping to XML in its full, industrial complexity, which seems to be what the O'Reilly-backed StartWithXML initiative[6] is suggesting, publishers instead leverage existing tools and technologies—starting with the Web—as a means of getting XML workflows in place. This means making small investments and working with known tools rather than spending tens of thousands of dollars on XML software and rarefied consultants. It means re-thinking how the existing pieces of the production toolchain fit together; re-thinking the existing roles of software components already in use. It means, fundamentally, taking the Web seriously as a content platform, rather than thinking of it as something you need to get content out to, somehow. If nothing else, the Web represents an opportunity to think about editorial and production from outside the shrink-wrapped Desktop Publishing paradigm.
  • Is the Web made of Real XML? At this point some predictable objections can be heard: wait a moment, the Web isn’t really made out of XML; the HTML that makes up most of the Web is at best the bastard child of SGML, and it is far too flaky/unstructured/underpowered to be taken seriously. We counter by arguing that although HTML on the Web exists in a staggering array of different incarnations, and that the majority of it is indeed an unstructured mess, this does not undermine the general principle that basic, ubiquitous Web technologies can make a solid platform for content management, editorial process, and production workflow.
  • With the advent of a published XML standard in the late 1990s came the W3C’s adoption of XHTML: the realization of the Web’s native content markup as a proper XML document type. Today, its acceptance is almost ubiquitous, even while the majority of actual content out there may not be strictly conforming. The more important point is that most contemporary Web software, from browsers to authoring tools to content management systems (from blogs to enterprise systems), are capable of working with clean, valid XHTML. Or, to put the argument the other way around, clean, valid XHTML content plays absolutely seamlessly with everything else on the Web.[7]
  • The objection which follows, then, will be that even if we grant that XHTML is a real XML document type, that it is underpowered for “serious” content because it is almost entirely presentation (formatting) oriented; it lacks any semantic depth. In XHTML, a paragraph is a paragraph is a paragraph, as opposed to a section or an epigraph or a summary.
  • n contrast, more “serious” XML document types like DocBook[8] or DITA-derived schemas[9] are capable of making semantic distinctions about content chunks at a fine level of granularity and with a high degree of specificity.
  • So there is an argument for recalling the 80:20 rule here. If XHTML can provide 80% of the value with just 20% of the investment, then what exactly is the business case for spending the other 80% to achieve that last 20% of value? We suspect the ratio is actually quite a bit steeper than 80:20 for most publishers.
  • Furthermore, just to get technical for a moment, XHTML is extensible in a fairly straightforward way, through the common “class” attribute on each element. Web developers have long leveraged this kind of extensibility in the elaboration of “microformats” for semantic-web applications.[10] There is no reason why publishers shouldn’t think to use XHTML’s simple extensibility in a similar way for their own ends.
  • XHTML, on the other hand, is supported by a vast array of quotidian software, starting with the ubiquitous Web browser. For this very reason, XHTML is in fact employed as a component part of several more specialized document types (ONIX and ePub among them).
  • Why re-invent a general-purpose prose representation when XHTML already does the job?
  • It is worth pausing for a moment to consider the role of XHTML in the ePub standard for ebook content. An ePub file is, anatomically, a simply disguised zip archive. Inside the zip archive are a few standard component parts: there are specialized files that declare metadata about the book, and about the format of the book. And then there is the book’s content, represented in XHTML. An ePub book is a Web page in a wrapper.
  • To sum up the general argument: the Web as it already exists presents incredible value to publishers, as a platform for doing XML content management with existing (and often free) tools, and without having to go blindly into the unknown. At this point, we can offer a few design guidelines: prefer existing and/or ubiquitous tools over specialized ones wherever possible; prefer free software over proprietary systems where possible; prefer simple tools controlled and coordinated by human beings over fully automated (and therefore complex) systems; play to our strengths: use Web software for storing and managing content, use layout software for layout, and keep editors and production people in charge of their own domains.
  • Putting the Pieces Together: A Prototype
  • At the SFU Master of Publishing Program, we have been chipping away at this general line of thinking for a few years. Over that time, Web content management systems have been getting more and more sophisticated, all the while getting more streamlined and easier to use. (NB: if you have a blog, you have a Web content management system.) The Web is beginning to be recognized as a writing and editing environment used by millions of people. And the ways in which content is represented, stored, and exchanged online have become increasingly robust and standardized.
  • The missing piece of the puzzle has been print production: how can we move content from its malleable, fluid form on line into the kind of high-quality print production environments we’ve come to expect after two decades of Desktop Publishing?
  • Anyone who has tried to print Web content knows that the existing methods leave much to be desired (hyphenation and justification, for starters). In the absence of decent tools for this, most publishers quite naturally think of producing the print content first, and then think about how to get material onto the Web for various purposes. So we tend to export from Word, or from Adobe, as something of an afterthought.
  • While this sort of works, it isn’t elegant, and it completely ignores the considerable advantages of Web-based content management.
  • Content managed online is stored in one central location, accessible simultaneously to everyone in your firm, available anywhere you have an Internet connection, and usually exists in a much more fluid format than Word files. If only we could manage the editorial flow online, and then go to print formats at the end, instead of the other way around. At SFU, we made several attempts to make this work by way of the supposed “XML import” capabilities of various Desktop Publishing tools, without much success.[12]
  • In the winter of 2009, Adobe solved this part of the problem for us with the introduction of its Creative Suite 4. What CS4 offers is the option of a complete XML representation of an InDesign document: what Adobe calls IDML (InDesign Markup Language).
  • The IDML file format is—like ePub—a simply disguised zip archive that, when unpacked, reveals a cluster of XML files that represent all the different facets of an InDesign document: layout spreads, master pages, defined styles, colours, and of course, the content.
  • IDML is a well thought-out XML standard that achieves two very different goals simultaneously: it preserves all of the information that InDesign needs to do what it does; and it is broken up in a way that makes it possible for mere mortals (or at least our Master of Publishing students) to work with it.
  • What this represented to us in concrete terms was the ability to take Web-based content and move it into InDesign in a straightforward way, thus bridging Web and print production environments using existing tools and skillsets, with a little added help from free software.
  • We would take clean XHTML content, transform it to IDML-marked content, and merge that with nicely designed templates in InDesign.
  • The result is an almost push-button publication workflow, which results in a nice, familiar InDesign document that fits straight into the way publishers actually do production.
  • Tracing the steps To begin with, we worked backwards, moving the book content back to clean XHTML.
  • The simplest method for this conversion—and if you want to create Web content, this is an excellent route—was to use Adobe’s “Export to Digital Editions” option, which creates an ePub file.
  • Recall that ePub is just XHTML in a wrapper, so within the ePub file was a relatively clean XHTML document. It was somewhat cleaner (that is, the XHTML tagging was simpler and less cluttered) than InDesign’s other Web-oriented exports, possibly because Digital Editions is a well understood target, compared with somebody’s website.
  • In order to achieve our target of clean XHTML, we needed to do some editing; the XHTML produced by InDesign’s “Digital Editions” export was presentation-oriented. For instance, bulleted list items were tagged as paragraphs, with a class attribute identifying them as list items. Using the search-and-replace function, we converted such structures to proper XHTML list and list-item elements. Our guiding principle was to make the XHTML as straightforward as possible, not dependent on any particular software to interpret it.
  • We broke the book’s content into individual chapter files; each chapter could then carry its own basic metadata, and the pages conveniently fit our Web content management system (which is actually just a wiki). We assembled a dynamically generated table of contents for the 12 chapters, and created a cover page. Essentially, the book was entirely Web-based at this point.
  • When the book chapters are viewed online, they are formatted via a CSS2 stylesheet that defines a main column for content as well as dedicating screen real estate for navigational elements. We then created a second template to render the content for exporting; this was essentially a bare-bones version of the book with no navigation and minimal styling. Pages (or even the entire book) can be exported (via the “Save As...” function in a Web browser) for use in either print production or ebook conversion. At this point, we required no skills beyond those of any decent Web designer.
  • Integrating with CS4 for Print Adobe’s IDML language defines elements specific to InDesign; there is nothing in the language that looks remotely like XHTML. So a mechanical transformation step is needed to convert the XHTML content into something InDesign can use. This is not as hard as it might seem.
  • Both XHTML and IDML are composed of straightforward, well-documented structures, and so transformation from one to the other is, as they say, “trivial.” We chose to use XSLT (Extensible Stylesheet Language Transforms) to do the work. XSLT is part of the overall XML specification, and thus is very well supported in a wide variety of tools. Our prototype used a scripting engine called xsltproc, a nearly ubiquitous piece of software that we found already installed as part of Mac OS X (contemporary Linux distributions also have this as a standard tool), though any XSLT processor would work.
  • In other words, we don’t need to buy InCopy, because we just replaced it with the Web. Our wiki is now plugged directly into our InDesign layout. It even automatically updates the InDesign document when the content changes. Credit is due at this point to Adobe: this integration is possible because of the open file format in the Creative Suite 4.
  • We wrote an XSLT transformation script[18] that converted the XHTML content from the Web into an InCopy ICML file. The script itself is less than 500 lines long, and was written and debugged over a period of about a week by amateurs (again, the people named at the start of this article). The script runs in a couple of seconds, and the resulting .icml file can then be “placed” directly into an InDesign template. The ICML file references an InDesign stylesheet, so the template file can be set up with a house-styled layout, master pages, and stylesheet definitions for paragraphs and character ranges.
  • The result is very simple and easy to use. Our demonstration requires that a production editor run the XSLT transformation script manually, but there is no reason why this couldn’t be built directly into the Web content management system so that exporting the content to print ran the transformation automatically. The resulting file would then be “placed” in InDesign and proofed.
  • It should be noted that the Book Publishing 1 proof-of-concept was artificially complex; we began with a book laid out in InDesign and ended up with a look-alike book laid out in InDesign. But next time—for instance, when we publish Book Publishing 2—we can begin the process with the content on the Web, and keep it there throughout the editorial process. The book’s content could potentially be written and edited entirely online, as Web content, and then automatically poured into an InDesign template at proof time. “Just in time,” as they say. This represents an entirely new way of thinking of book production. With a Web-first orientation, it makes little sense to think of the book as “in print” or “out of print”—the book is simply available, in the first place online; in the second place in derivative digital formats; and third, but really not much more difficult, in print-ready format, via the usual InDesign CS print production system publishers are already familiar with.
  • Creating Ebook Files Creating electronic versions from XHTML source is vastly simpler than trying to generate these out of the existing print process. The ePub version is extremely easy to generate; so is online marketing copy or excerpts for the Web, since the content begins life Web-native.
  • Since an ePub file is essentially XHTML content in a special wrapper, all that is required is that we properly “wrap” our XHTML content. Ideally, the content in an ePub file is broken into chapters (as ours was) and a table of contents file is generated in order to allow easy navigation within an ebook reader. We used Julian Smart’s free tool eCub[19] to simply and automatically generate the ePub wrapper and the table of contents. The only custom development we did was to create a CSS stylesheet for the ebook so that headings and paragraph indents looked the way we wanted. Starting with XHTML content, creating ePub is almost too easy.
  • Such a workflow—beginning with the Web and exporting to print—is surely more in line with the way we will do business in the 21st century, where the Web is the default platform for reaching audiences, developing content, and putting the pieces together. It is time, we suggest, for publishers to re-orient their operations and start with the Web.
  • Our project demonstrates that Web technologies are indeed good enough to use in an XML-oriented workflow; more specialized and expensive options are not necessarily required. For massive-scale enterprise publishing, this approach may not offer enough flexibility, and the challenge of adding and extracting extra semantic richness may prove more trouble than it's worth.
  • But for smaller firms who are looking at the straightforward benefits of XML-based processes—single source publishing, online content and workflow management, open and accessible archive formats, greater online discoverability—here is a way forward.
  • Rather than a public-facing website, our system relies on the Web as a content management platform—of course a public face could easily be added.
  • The final piece of our puzzle, the ability to integrate print production, was made possible by Adobe's release of InDesign with an open XML file format. Since the Web's XHTML is also XML, is can be easily and confidently transformed to the InDesign format.
  • today, we are able to put the process together using nothing but standard, relatively ubiquitous Web tools: the Web itself as an editing and content management environment, standard Web scripting tools for the conversion process, and the well-documented IDML file format to integrate the layout tool.
  • Using the Web as a Production Platform
  • Gary Edwards on 07 Nov 13
     
    I was looking for an answer to a problem Marbux had presented, and found this interesting article.  The issue was that of the upcoming conversion of the Note Case Pro (NCP) layout engine to the WebKit layout engine, and what to do about the NCP document format. My initial reaction was to encode the legacy NCP document format in XML, and run an XSLT to a universal pivot format like TEI-XML.  From there, the TEI-XML community would provide all the XSLT transformation routines for conversion to ODF, OOXML, XHTML, ePUB and HTML/CSS. Researching the problems one might encounter with this approach, I found this article.  Fascinating stuff. My take away is that TEI-XML would not be as effective a "universal pivot point" as XHTML.  Or perhaps, if NCP really wants to get aggressive; IDML - InDesign Markup Language. The important point though is that XHTML is a browser specific version of XML, and compatible with the Web Kit layout engine Miro wants to move NCP to. The concept of encoding an existing application-specific format in XML has been around since 1998, when XML was first introduced as a W3C standard, a "structured" subset of SGML. (HTML is also a subset of SGML). The multiplatform StarOffice productivity suite became "OpenOffice" when Sun purchased the company in 1998, and open sourced the code base. The OpenOffice developer team came out with a XML encoding of their existing document formats in 2000. The application specific encoding became an OASIS document format standard proposal in 2002 - also known as ODF. Microsoft followed OpenOffice with a XML encoding of their application-specific binary document formats, known as OOXML. Encoding the existing NCP format in XML, specifically targeting XHTML as a "universal pivot point", would put the NCP Outliner in the Web editor category, without breaking backwards compatibility. The trick is in the XSLT conversion process. But I think that is something much easier to handle then trying to
  • Gary Edwards on 07 Nov 13
     
    I was looking for an answer to a problem Marbux had presented, and found this interesting article.  The issue was that of the upcoming conversion of the Note Case Pro (NCP) layout engine to the WebKit layout engine, and what to do about the NCP document format. My initial reaction was to encode the legacy NCP document format in XML, and run an XSLT to a universal pivot format like TEI-XML.  From there, the TEI-XML community would provide all the XSLT transformation routines for conversion to ODF, OOXML, XHTML, ePUB and HTML/CSS. Researching the problems one might encounter with this approach, I found this article.  Fascinating stuff. My take away is that TEI-XML would not be as effective a "universal pivot point" as XHTML.  Or perhaps, if NCP really wants to get aggressive; IDML - InDesign Markup Language. The important point though is that XHTML is a browser specific version of XML, and compatible with the Web Kit layout engine Miro wants to move NCP to. The concept of encoding an existing application-specific format in XML has been around since 1998, when XML was first introduced as a W3C standard, a "structured" subset of SGML. (HTML is also a subset of SGML). The multiplatform StarOffice productivity suite became "OpenOffice" when Sun purchased the company in 1998, and open sourced the code base. The OpenOffice developer team came out with a XML encoding of their existing document formats in 2000. The application specific encoding became an OASIS document format standard proposal in 2002 - also known as ODF. Microsoft followed OpenOffice with a XML encoding of their application-specific binary document formats, known as OOXML. Encoding the existing NCP format in XML, specifically targeting XHTML as a "universal pivot point", would put the NCP Outliner in the Web editor category, without breaking backwards compatibility. The trick is in the XSLT conversion process. But I think that is something much easier to handle then trying to
Gonzalo San Gil, PhD.

5 Open Source Mobile OS Alternatives To Android | tsfoss.com/ [# ! Note...] - 0 views

itsfoss.com/en-source-alternatives-android

shared by Gonzalo San Gil, PhD. on 20 Nov 16 - No Cached
  • Gonzalo San Gil, PhD. on 20 Nov 16
     
    "If I say that Open Source mobile OS are ruling the world of mobile devices, it won't be an exaggeration. Though many don't consider, Android is still an open source project. This is another thing that the devices you use come with a bundle of proprietary software along with Android and hence many people don't consider it open source"
Gonzalo San Gil, PhD.

Open Source Software: Top Sites - Datamation - 2 views

www.datamation.com/...source-software-top-sites.html

open source software top sites www

shared by Gonzalo San Gil, PhD. on 24 Jun 16 - No Cached
  • Gonzalo San Gil, PhD. on 24 Jun 16
     
    "Frequently, Datamation puts together lists of top open source software. This time we've done something a little different and made a list of top open source Web sites."
Gonzalo San Gil, PhD.

Debunking the top open source myths | Network World - 1 views

www.networkworld.com/...the-top-open-source-myths.html

debunk open source myths network world black legend debunked

shared by Gonzalo San Gil, PhD. on 12 Jan 15 - No Cached
  • Gonzalo San Gil, PhD. on 12 Jan 15
     
    " ... Open source increases security and privacy, encourages an engaged community and offers the ability to "look under the hood" to diagnose and resolve issues quickly. ...." (# ! Guess who spreads the black legend about open source...)
  • Gonzalo San Gil, PhD. on 12 Jan 15
     
    " ... Open source increases security and privacy, encourages an engaged community and offers the ability to "look under the hood" to diagnose and resolve issues quickly. ...."
Gonzalo San Gil, PhD.

How the current intellectual property landscape impacts open source | Opensource.com - 0 views

opensource.com/...ectual-property-practice-group

intellectual property vs open source opensource.com progress promotion useful arts

shared by Gonzalo San Gil, PhD. on 30 Mar 15 - No Cached
  • Gonzalo San Gil, PhD. on 30 Mar 15
     
    - Interview with Doug Kim chairs the Intellectual Property Practice Group at McNair Law Firm - "I caught up with Doug to ask him a few questions about his background, upcoming presentation, and thoughts on the current intellectual property landscape and how it impacts open source."
  • ...2 more comments...
  • Gonzalo San Gil, PhD. on 30 Mar 15
     
    "I caught up with Doug to ask him a few questions about his background, upcoming presentation, and thoughts on the current intellectual property landscape and how it impacts open source."
  • Gonzalo San Gil, PhD. on 30 Mar 15
     
    - Interview with Doug Kim chairs the Intellectual Property Practice Group at McNair Law Firm - "I caught up with Doug to ask him a few questions about his background, upcoming presentation, and thoughts on the current intellectual property landscape and how it impacts open source."
  • Gonzalo San Gil, PhD. on 30 Mar 15
     
    - Interview with Doug Kim chairs the Intellectual Property Practice Group at McNair Law Firm - "I caught up with Doug to ask him a few questions about his background, upcoming presentation, and thoughts on the current intellectual property landscape and how it impacts open source."
  • Gonzalo San Gil, PhD. on 31 Mar 15
     
    - Interview with Doug Kim chairs the Intellectual Property Practice Group at McNair Law Firm - "I caught up with Doug to ask him a few questions about his background, upcoming presentation, and thoughts on the current intellectual property landscape and how it impacts open source."
Gonzalo San Gil, PhD.

7 Truths that Open Source Struggles With - Datamation - 0 views

www.datamation.com/...n-source-struggles-with-1.html

open source struggles

shared by Gonzalo San Gil, PhD. on 22 Jan 16 - No Cached
  • Gonzalo San Gil, PhD. on 22 Jan 16
     
    Open source development has consistently proved many ideas that were once considered impossible. For instance, thanks to open source, we now know that people can be motivated by more than money, and that co-operation can be more effective in some aspects of development than competition.
Gonzalo San Gil, PhD.

Whatever You Call It -- Open Journalism, Social Media Journalism, Open-Source Intellige... - 0 views

www.techdirt.com/...ligence-going-mainstream.shtml

open free independent social media social journalism intelligence media go mainstream

shared by Gonzalo San Gil, PhD. on 24 Jun 15 - No Cached
  • Gonzalo San Gil, PhD. on 24 Jun 15
     
    "from the first-draft-of-first-draft dept We've written a couple of times about the use of publicly-available information, typically posted on social networks, to verify developing stories where traditional sources are scarce or unreliable. This new field doesn't seem to have a fixed name yet -- open journalism, social media journalism, open-source intelligence are all used -- but whatever it is, it's clearly going mainstream, as this announcement on the YouTube blog of The First Draft Coalition makes clear: "
Gonzalo San Gil, PhD.

The digital open source library of tomorrow Posted 20 Nov 2014 by Nicole C. Engard | ... - 0 views

opensource.com/...open-sourcing-public-library

Phil Shapiro vision libraries future open source

shared by Gonzalo San Gil, PhD. on 24 Nov 14 - No Cached
  • Gonzalo San Gil, PhD. on 24 Nov 14
     
    "Phil Shapiro's vision for the libraries of tomorrow Phil Shapiro, one of my fellow Opensource.com Community Moderators, gave a talk at All Things Open 2014 about open source and libraries. This is a recap of that talk."
  • Gonzalo San Gil, PhD. on 24 Nov 14
     
    "Phil Shapiro, one of my fellow Opensource.com Community Moderators, gave a talk at All Things Open 2014 about open source and libraries. This is a recap of that talk."
Gonzalo San Gil, PhD.

Open source is in our DNA | Network World - 0 views

www.networkworld.com/...open-source-is-in-our-dna.html

Open Source is in our DNA we are open natural

shared by Gonzalo San Gil, PhD. on 31 May 16 - No Cached
  • Gonzalo San Gil, PhD. on 31 May 16
     
    "The same thing that compels us to make Linux (and many other projects) free and open source is present in many of humanity's greatest achievements"
  • Gonzalo San Gil, PhD. on 31 May 16
     
    "The same thing that compels us to make Linux (and many other projects) free and open source is present in many of humanity's greatest achievements"
Gonzalo San Gil, PhD.

Top 50 Open Source VoIP Apps - 1 views

www.studyweb.com/p-top-50-open-source-voip-apps

open source voip apps

shared by Gonzalo San Gil, PhD. on 09 Jul 16 - No Cached
  • Gonzalo San Gil, PhD. on 09 Jul 16
     
    "by The StudyWeb.com Team 20 Comments For many businesses, open source VoIP programs and apps offer a great way to save thousands of dollars every year in telephony costs. Better yet, open source programs are fully customizable to a business' specific needs, making them a popular solution that often just can't be beat. "
Gonzalo San Gil, PhD.

Learn how to calculate ROI for open hardware projects | Opensource.com - 0 views

opensource.com/...rce-hardware-return-investment

#HowTo calucate OSH ROI

shared by Gonzalo San Gil, PhD. on 11 Apr 16 - No Cached
  • Gonzalo San Gil, PhD. on 11 Apr 16
     
    "Free and open source software advocates have courageously blazed a trail that is now being followed by those interested in open source for physical objects. It's called free and open source hardware (FOSH), and we're seeing an exponential rise in the number of free designs for hardware released under opensource licenses, Creative Commons licenses,or placed in the public domain."
Gonzalo San Gil, PhD.

How to treat government like an open source project | Opensource.com - 0 views

opensource.com/...open-collaborative-government

how to treat government open source project opensource way the open source way

shared by Gonzalo San Gil, PhD. on 03 Jun 14 - No Cached
  • Gonzalo San Gil, PhD. on 03 Jun 14
     
    "Open government is great. At least, it was a few election cycles ago. FOIA requests, open data, seeing how your government works-it's arguably brought light to a lot of not-so-great practices, and in many cases, has spurred citizen-centric innovation not otherwise imagined before the information's release."
  • Gonzalo San Gil, PhD. on 03 Jun 14
     
    "Open government is great. At least, it was a few election cycles ago. FOIA requests, open data, seeing how your government works-it's arguably brought light to a lot of not-so-great practices, and in many cases, has spurred citizen-centric innovation not otherwise imagined before the information's release."
Gonzalo San Gil, PhD.

Is being open worth the effort? | A recap of the August 25 #OpenOrgChat | Opensource.com - 0 views

opensource.com/...being-open-worth-effort

#OpenOrgChat recap do being open worth it open source effort way satisfaction

shared by Gonzalo San Gil, PhD. on 09 Sep 16 - No Cached
  • Gonzalo San Gil, PhD. on 09 Sep 16
     
    "Becoming (or remaining) an open organization is challenging. This month, the open organization community at Opensource.com discussed those challenges-and so much more-during our #OpenOrgChat on Twitter. If you missed it, check out the recap below as you prepare for our next chat."
  • Gonzalo San Gil, PhD. on 09 Sep 16
     
    "Becoming (or remaining) an open organization is challenging. This month, the open organization community at Opensource.com discussed those challenges-and so much more-during our #OpenOrgChat on Twitter. If you missed it, check out the recap below as you prepare for our next chat."
Gonzalo San Gil, PhD.

What we mean when we say 'open music' | Opensource.com - 0 views

opensource.com/...what-open-music-means

open open source beyond code music open Music

shared by Gonzalo San Gil, PhD. on 15 Jul 16 - No Cached
  • Gonzalo San Gil, PhD. on 15 Jul 16
     
    "Learning about Bolero's recent entry into the public domain made me think about the concept of "open music" in general. Where is it found? What characteristics define open music? And so I've let my favorite search engine help me do detective work to see what a hunt for open music turns up."
Paul Merrell

The People and Tech Behind the Panama Papers - Features - Source: An OpenNews project - 0 views

source.opennews.org/...-and-tech-behind-panama-papers

Panama-Papers technology open-source

shared by Paul Merrell on 12 Apr 16 - No Cached
  • Then we put the data up, but the problem with Solr was it didn’t have a user interface, so we used Project Blacklight, which is open source software normally used by librarians. We used it for the journalists. It’s simple because it allows you to do faceted search—so, for example, you can facet by the folder structure of the leak, by years, by type of file. There were more complex things—it supports queries in regular expressions, so the more advanced users were able to search for documents with a certain pattern of numbers that, for example, passports use. You could also preview and download the documents. ICIJ open-sourced the code of our document processing chain, created by our web developer Matthew Caruana Galizia. We also developed a batch-searching feature. So say you were looking for politicians in your country—you just run it through the system, and you upload your list to Blacklight and you would get a CSV back saying yes, there are matches for these names—not only exact matches, but also matches based on proximity. So you would say “I want Mar Cabra proximity 2” and that would give you “Mar Cabra,” “Mar whatever Cabra,” “Cabra, Mar,”—so that was good, because very quickly journalists were able to see… I have this list of politicians and they are in the data!
  • Last Sunday, April 3, the first stories emerging from the leaked dataset known as the Panama Papers were published by a global partnership of news organizations working in coordination with the International Consortium of Investigative Journalists, or ICIJ. As we begin the second week of reporting on the leak, Iceland’s Prime Minister has been forced to resign, Germany has announced plans to end anonymous corporate ownership, governments around the world launched investigations into wealthy citizens’ participation in tax havens, the Russian government announced that the investigation was an anti-Putin propaganda operation, and the Chinese government banned mentions of the leak in Chinese media. As the ICIJ-led consortium prepares for its second major wave of reporting on the Panama Papers, we spoke with Mar Cabra, editor of ICIJ’s Data & Research unit and lead coordinator of the data analysis and infrastructure work behind the leak. In our conversation, Cabra reveals ICIJ’s years-long effort to build a series of secure communication and analysis platforms in support of genuinely global investigative reporting collaborations.
  • For communication, we have the Global I-Hub, which is a platform based on open source software called Oxwall. Oxwall is a social network, like Facebook, which has a wall when you log in with the latest in your network—it has forum topics, links, you can share files, and you can chat with people in real time.
  • ...3 more annotations...
  • We had the data in a relational database format in SQL, and thanks to ETL (Extract, Transform, and Load) software Talend, we were able to easily transform the data from SQL to Neo4j (the graph-database format we used). Once the data was transformed, it was just a matter of plugging it into Linkurious, and in a couple of minutes, you have it visualized—in a networked way, so anyone can log in from anywhere in the world. That was another reason we really liked Linkurious and Neo4j—they’re very quick when representing graph data, and the visualizations were easy to understand for everybody. The not-very-tech-savvy reporter could expand the docs like magic, and more technically expert reporters and programmers could use the Neo4j query language, Cypher, to do more complex queries, like show me everybody within two degrees of separation of this person, or show me all the connected dots…
  • We believe in open source technology and try to use it as much as possible. We used Apache Solr for the indexing and Apache Tika for document processing, and it’s great because it processes dozens of different formats and it’s very powerful. Tika interacts with Tesseract, so we did the OCRing on Tesseract. To OCR the images, we created an army of 30–40 temporary servers in Amazon that allowed us to process the documents in parallel and do parallel OCR-ing. If it was very slow, we’d increase the number of servers—if it was going fine, we would decrease because of course those servers have a cost.
  • For the visualization of the Mossack Fonseca internal database, we worked with another tool called Linkurious. It’s not open source, it’s licensed software, but we have an agreement with them, and they allowed us to work with it. It allows you to represent data in graphs. We had a version of Linkurious on our servers, so no one else had the data. It was pretty intuitive—journalists had to click on dots that expanded, basically, and could search the names.
« First ‹ Previous 41 - 60 of 525 Next › Last »
Showing 20▼ items per page