Group items tagged

In this paper, we describe our findings from interviews with participants working in two relatively new consortia in the government sector: the Government Open Code Collaborative or GOCC, and the Open Source Software Institute or OSSI. For each case we consider six major questions: (1) How and why did these collaborative efforts begin? (2) What are their motivations? (3) How are these collaborative efforts governed? (4) What communication and collaborative infrastructure do they utilize? (5) What software do they focus on? and, (6) What is their current status? Our findings suggest that incentives, membership structures, stable paid staff, concentrated focus and attention to the creation and delivery of "value" to participating organizations are important factors leading to successful open source consortia.

This article offers open source software (oss) for FAT over MMC SDC. We have many options of open source TCP/IP stack implementations. However we don't have enough choices for open source FAT file system

"Politicians, journalists, and bands all want to share what they do. We have a system for distributing information, and we want to remove limits for people with a lot of constituents to share," added Facebook's Chris Cox.

we seem to instinctively realize as "producers" we provide incredible value - but have never stopped to put it together in this way.

With User Labor, we propose an open data structure, User Labor Markup Language (ULML), to outline the metrics of user participation in social web services. Our aim is to construct criteria and context for determining the value of user labor for distribution. We believe that universality, transparency, and accessibility of user labor metrics will ultimately lead to more sustainable service cycles in social web. ULML outlines the metrics user labor, but does not provide direction for calculating its value. Calculating the value of labor is a fairly subjective matter, and formulations may vary from service to service. In order to deal with this subjectivity in the best way possible, the metrics of user labor need to be accessible and transparent as a basis for initiating actual value discussions. >> aka: PEERS IMS needs this info to calculate value!

We must work together for all life on the life abundant planet we call, Earth.

Due to browsers' prohibition on cross domain XMLHTTP calls, all AJAX websites must have a server side proxy to fetch content from external domains like Flickr or Digg. From the client-side JavaScript code, an XMLHTTP call goes to the server-side proxy hosted on the same domain, and then the proxy downloads the content from the external server and sends back to the browser. In general, all AJAX websites on the Internet that are showing content from external domains are following this proxy approach, except for some rare ones who are using JSONP. Such a proxy gets a very large number of hits when a lot of components on the website are downloading content from external domains. So, it becomes a scalability issue when the proxy starts getting millions of hits. Moreover, a web page's overall load performance largely depends on the performance of the proxy as it delivers content to the page. In this article, we will take a look at how we can take a conventional AJAX Proxy and make it faster, asynchronous, continuously stream content, and thus make it more scalable.

Plurk Karma is an interesting little creature. We constantly tell ourselves it isn't really important, yet we can't wait to see the next update. Many of our peers and fellow Plurkers say not to worry about it because Karma is designed to benefit those without motive of personal reward.

One of the core issues on the web for many people who try to keep themselves up to date is the increasing noise of information; it means that there are load of information on the web which are irrelevant to the people and we have to look in all those irrelevant information in order to

Librarians have adapted amazingly well to the challenges of an Internet-enabled, web-dominated world. It's been quite a ride as we worked with digital content, learned new search tools, and strived to get our many and varied systems interconnected. Now the roller coaster really begins as we deal with the next generation-those "born with the chip"-who have grown up in the 1980s with computers and don't think of them as technology. They are part of their cultural DNA.

We live in the era of Google Maps. What started off as an impressive refresh of Mapquest-style maps now fuels web mashups. With APIs official and unofficial, Google Maps is simple enough for front-end designers to embed and for back-end programmers to target. Along the way to becoming nearly ubiquitous, it has played a major role in the "democratization of mapping." For the practical developer who wants to add geospatial information to a site or application, the Google Maps API has been an easy call. But, perhaps no longer. As websites mature and the demand for geographic applications grow, the old mashup arrangement is starting to chafe. Mapping components are more and more vital, and so we demand greater control, expressiveness, and functionality from them. Fortunately, as in many aspects of internet technology, an ecology of open source online mapping tools has emerged alongside the market leader. It is now possible to replicate Google Maps' functionality with open source software and produce high-quality mapping applications tailored to our design goals. The question becomes, then, how?

We've gotten a number of comments and questions about the maps that appear on EveryBlock. People are wondering if we have created our own mapping platform, and why we didn't use the map offerings from services like Google, Yahoo!, or Microsoft.

Accessible data visualization in HTML has always been tricky to achieve, particularly because elements such as images allow only the most basic features for providing textual information to non-visual users. A while back, we wrote an article describing a technique we came up with to use JavaScript to scrape data from an HTML table and generate charts using the HTML 5 Canvas element. The technique is particularly useful because the data for the visualization already exists in the page in structured tabular format, making it accessible to people who browse the web with a screen reader or other assistive technology.

IAR systems was founded in Uppsala, Sweden in 1983. We were one of the first companies that developed the C compiler for the ColdFire architecture. Since then we have grown to become a global organization with offices in 6 countries, North America, Brazil, China and some of the countries in Europe and distribution infrastructure in 25 countries.

About 2 years ago, we announced our Flexis product families. These are products that offered the promise of software and hardware compatibility between 8 bit and 32 bit. And what we offer this compatibility between our SO8 products which are 8 bit and our ColdFire products on 32 bit.

We all know Google Inc. is an American public corporation, earning revenue from advertising related to its Internet search, e-mail, online mapping, office productivity, social networking, and video sharing. But here is the intresting part, we know a lot about Google and about their products and services, In the screenshot let me show you what according to some intresting Twitter users Google is all about.

The mantra of the information age has been "The more information the better!" But what happens when we search the web and get so much information that we can't sort through it, let alone evaluate it? Enter the semantic web, or Web 3.0. Among other things, the semantic web makes information more meaningful to people by making it more understandable to machines.

A year ago, we ranked the top 25 social networking sites by monthly visits, and I was curious to see how the positions would change if we re-ranked those same sites with the most recent figures.