Group items tagged

[Home » Community Grants Training: Writing a Community Grants Proposal Community Grants Training: Writing a Community Grants Proposal The Community Grants Programme will accept applications beginning Monday, 4 March 2013. The application round will close Monday, 01 April and award notifications made at the end of May 2013. This Training Session will be offered twice on 5 February 2013 in order to cover different time zones, namely at 10:30 UTC and at 20:00 UTC. Please sign up at http://www.doodle.com/d6adh23v9gucr4mt if you plan to participate in this session. Thanks! Venue: WebEx (see details for both sessions below) Agenda: Turning a project idea into a plan Characteristics of a great grant proposal Overview of the grant application Expectations of our grantees ...]

"My experience tells me there are a lot of people interested in trying open source, but they don't know where to start. And the perception that you have to write code to contribute to is a barrier to that curiosity. So, I've outlined 10 ways that anyone can get started with open source-no code writing involved. I welcome your ideas and additions, there are without a doubt more than 10 ways-let's get started."

"by Frazer Kline In a nutshell, collaborative writing is writing done by more than one person. There are benefits and risks of collaborative working. Some of the benefits include a more integrated / co-ordinated approach, better use of existing resources, and a stronger, united voice. "

"by Frazer Kline In a nutshell, collaborative writing is writing done by more than one person. There are benefits and risks of collaborative working. Some of the benefits include a more integrated / co-ordinated approach, better use of existing resources, and a stronger, united voice. "

Visions of endless conversations between different people's bots with no human participation. Then a human being reads a reply and files a libel lawsuit against the human whose bot posted the reply. Can the defendant obtain dismissal on grounds that she did not write the message herself; her Google autoresponder did and therefore if anyone is liable it is Google?  Our Brave New (technological) World does and will pose many novel legal issues. My favorite so far: Assume that genetics have progressed to the point that unknown to Bill Gates, someone steals a bit of his DNA and implants it in a mother-to-be's egg. Is Bill Gates as the biological father liable for child support? Is that child an heir to Bill Gates' fortune? The current state of law in the U.S. would suggest that the answer to both questions is almost certainly "yes." The child itself is blameless and Bill Gates is his biological father.

"Free Software, Free Society by Richard M. Stallman Publisher: Free Software Foundation 2002 ISBN/ASIN: 1882114981 ISBN-13: 9781882114986 Number of pages: 230 Description: The intersection of ethics, law, business and computer software is the subject of these essays and speeches by MacArthur Foundation Grant winner, Richard M. Stallman. This collection includes historical writings such as The GNU Manifesto, which defined and launched the activist Free Software Movement, along with new writings on hot topics in copyright, patent law, and the controversial issue of "trusted computing." Stallman takes a critical look at common abuses of copyright law and patents when applied to computer software programs, and how these abuses damage our entire society and remove our existing freedoms."

ptsefton continues his rant that OpenOffice does not support the Open Web. He's been on this rant for so long, i'm wondering if he really thinks there's a chance the lords of ODF and the OpenOffice source code are listening? In this post he describes how useless it is to submit his findings and frustrations with OOo in a bug report. Pretty funny stuff even if you do end up joining the Michael Meeks trek along this trail of tears. Maybe there's another way?

What would happen if pt moved from targeting the not so open OpenOffice, to target governments and enterprises trying to set future information system requirements?

NY State is next up on this endless list. Most likely they will follow the lessons of exhaustive pilot studies conducted by Massachusetts, California, Belgium, Denmark and England, and end up mandating the use of both open standard "XML" formats, ODF and OOXML.

The pilots concluded that there was a need for both XML formats; depending on the needs of different departments and workgroups. The pilot studies scream out a general rule of thumb; if your department has day-to-day business processes bound to MSOffice workgroups, then it makes sense to use MSOffice OOXML going forward. If there is no legacy MSOffice bound workgroup or workflow, it makes sense to move to OpenOffice ODF.

One thing the pilots make clear is that it is prohibitively costly and disruptive to try to replace MSOffice bound workgroups.

What NY State might consider is that the Web is going to be an important part of their informations systems future. What a surprise. Every pilot recognized and indeed, emphasized this fact. Yet, they fell short of the obvious conclusion; mandating that desktop applications provide native support for Open Web formats, protocols and interfaces!

What's wrong with insisting that desktop applciations and office suites support the rapidly advancing HTML+ technologies as well as the applicat

The author clearly missed that Sun is a full-fledged Microsoft partner and that StarOffice 9, of all OpenOffice.org clones, is the only one that has write support for both ODF v. 1.2 and ODF v. 1.1, the latter of which is the only ODF version being implemented by Microsoft. The other OOo clones write only to ODF 1.2, which is dramatically different from ODF 1.2. So StarOffice will almost certainly have better interop via ODF with MS Office 2007 than will OOo 3.x or Lotus Symphony. For $25 per seat in the enterprise, $34.95 retail. The author simply misses that "pretty much the same thing can [NOT] be had for nothing from OpenOffice.org." There is a method to the claimed Sun madness, methinks. IBM gets left standing at the altar again.

"Writing software is too hard and it takes too long. It's time for a new way to write software - especially application software, the user-facing software we use every day to talk to people and keep track of things. This new way should be radically simple. It should make it possible to build a prototype in a day or two, and a real production app in a few weeks. It should make everyday things easy, even when those everyday things involve hundreds of servers, millions of users, and integration with dozens of other systems. It should be built on collaboration, specialization, and division of labor, and it should be accessible to the maximum number of people. Today, there's a chance to create this new way - to build a new platform for cloud applications that will become as ubiquitous as previous platforms such as Unix, HTTP, and the relational database. It is not a small project. There are many big problems to tackle, such as: How do we transition the web from a "dumb terminal" model that is based on serving HTML, to a client/server model that is based on exchanging data? How do we design software to run in a radically distributed environment, where even everyday database apps are spread over multiple data centers and hundreds of intelligent client devices, and must integrate with other software at dozens of other organizations? How do we prepare for a world where most web APIs will be push-based (realtime), rather than polling-driven? In the face of escalating complexity, how can we simplify software engineering so that more people can do it? How will software developers collaborate and share components in this new world? Meteor is our audacious attempt to solve all of these big problems, at least for a certain large class of everyday applications. We think that success will come from hard work, respect for history and "classically beautiful" engineering patterns, and a philosophy of generally open and collaborative development. " .............. "It is not a

"How do we transition the web from a "dumb terminal" model that is based on serving HTML, to a client/server model that is based on exchanging data?" From a litigation aspect, the best bet I know of is antitrust litigation against the W3C and the WHATWG Working Group for implementing a non-interoperable specification. See e.g., Commission v. Microsoft, No. T-167/08, European Community Court of First Instance (Grand Chamber Judgment of 17 September, 2007), para. 230, 374, 421, http://preview.tinyurl.com/chsdb4w (rejecting Microsoft's argument that "interoperability" has a 1-way rather than 2-way meaning; information technology specifications must be disclosed with sufficient specificity to place competitors on an "equal footing" in regard to interoperability; "the 12th recital to Directive 91/250 defines interoperability as 'the ability to exchange information and mutually to use the information which has been exchanged'"). Note that the Microsoft case was prosecuted on the E.U.'s "abuse of market power" law that corresponds to the U.S. Sherman Act § 2 (monopolies). But undoubtedly the E.U. courts would apply the same standard to "agreements among undertakings" in restraint of trade, counterpart to the Sherman Act's § 1 (conspiracies in restraint of trade), the branch that applies to development of voluntary standards by competitors. But better to innovate and obsolete HTML, I think. DG Competition and the DoJ won't prosecute such cases soon. For example, Obama ran for office promising to "reinvigorate antitrust enforcement" but his DoJ has yet to file its first antitrust case against a big company. Nb., virtually the same definition of interoperability announced by the Court of First Instance is provided by ISO/IEC JTC-1 Directives, annex I ("eye"), which is applicable to all international standards in the IT sector: "... interoperability is understood to be the ability of two or more IT systems to exchange information at one or more standardised interfaces

"The Founding Fathers of the United States considered intellectual property so important that they gave it a special place in the Constitution: "To promote the progress of science and useful arts, by securing for limited times to authors and inventors the exclusive right to their respective writings and discoveries.""

"The Founding Fathers of the United States considered intellectual property so important that they gave it a special place in the Constitution: "To promote the progress of science and useful arts, by securing for limited times to authors and inventors the exclusive right to their respective writings and discoveries.""

The quote is somewhat misleading because it is out of context. The section is preceded by: "The Congress shall have Power ..." Those are words of discretion, not commandment. Nothing in the Constitution *requires* that patent and copyright systems be established. "Stable ownership is the gift of social law, and is given late in the progress of society. It would be curious then, if an idea, the fugitive fermentation of an individual brain, could, of natural right, be claimed in exclusive and stable property. If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it. Its peculiar character, too, is that no one possesses the less, because every other possesses the whole of it. He who receives an idea from me, receives instruction himself without lessening mine; as he who lights his taper at mine, receives light without darkening me. That ideas should freely spread from one to another over the globe, for the moral and mutual instruction of man, and improvement of his condition, seems to have been peculiarly and benevolently designed by nature, when she made them, like fire, expansible over all space, without lessening their density in any point, and like the air in which we breathe, move, and have our physical being, incapable of confinement or exclusive appropriation. Inventions then cannot, in nature, be a subject of property. Society may give an exclusive right to the profits arising from them, as an encouragement to men to pursue ideas which may produce utility, *but this may or may not be done, according to the will and convenience of the society, without claim or complaint from any body."* VI Writings of Thomas Jefferson, at 180-181 (Washington ed.).

"These companies don't have to agree in writing to carry this out or even raise their prices; they can simply, within their separate geographic and product territories, bundle and tie their services, buy up inputs that a competitor might need, and refuse to connect to competitors - among many other potential tactics. It's in their interest for these local monopolists to cooperate, because any defection would make the whole system crumble."

"These companies don't have to agree in writing to carry this out or even raise their prices; they can simply, within their separate geographic and product territories, bundle and tie their services, buy up inputs that a competitor might need, and refuse to connect to competitors - among many other potential tactics. It's in their interest for these local monopolists to cooperate, because any defection would make the whole system crumble."

"These companies don't have to agree in writing to carry this out or even raise their prices; they can simply, within their separate geographic and product territories, bundle and tie their services, buy up inputs that a competitor might need, and refuse to connect to competitors - among many other potential tactics. It's in their interest for these local monopolists to cooperate, because any defection would make the whole system crumble."

Thanks Marbux. ARC appears to be an extraordinary technology. Funny but Florian has been pushing Native Client (NaCL) since it was first ported from Firefox to Chrome. Looks like he was right. "In September, Google launched ARC-the "App Runtime for Chrome,"-a project that allowed Android apps to run on Chrome OS. A few days later, a hack revealed the project's full potential: it enabled ARC on every "desktop" version of Chrome, meaning you could unofficially run Android apps on Chrome OS, Windows, Mac OS X, and Linux. ARC made Android apps run on nearly every computing platform (save iOS). ARC is an early beta though so Google has kept the project's reach very limited-only a handful of apps have been ported to ARC, which have all been the result of close collaborations between Google and the app developer. Now though, Google is taking two big steps forward with the latest developer preview: it's allowing any developer to run their app on ARC via a new Chrome app packager, and it's allowing ARC to run on any desktop OS with a Chrome browser. ARC runs Windows, Mac, Linux, and Chrome OS thanks to Native Client (abbreviated "NaCL"). NaCL is a Chrome sandboxing technology that allows Chrome apps and plugins to run at "near native" speeds, taking full advantage of the system's CPU and GPU. Native Client turns Chrome into a development platform, write to it, and it'll run on all desktop Chrome browsers. Google ported a full Android stack to Native Client, allowing Android apps to run on most major OSes. With the original ARC release, there was no official process to getting an Android app running on the Chrome platform (other than working with Google). Now Google has released the adorably-named ARC Welder, a Chrome app which will convert any Android app into an ARC-powered Chrome app. It's mainly for developers to package up an APK and submit it to the Chrome Web Store, but anyone can package and launch an APK from the app directly."

"Fiona MacAlister September 1, 2016 In March we hosted the second Institute for Open Leadership. In our summary of the event we mentioned that the Institute fellows would be taking turns to write about their open policy projects. This week's post is from Fiona MacAlister, OER Specialist at Wits University in Johannesburg, South Africa."

"Fiona MacAlister September 1, 2016 In March we hosted the second Institute for Open Leadership. In our summary of the event we mentioned that the Institute fellows would be taking turns to write about their open policy projects. This week's post is from Fiona MacAlister, OER Specialist at Wits University in Johannesburg, South Africa."

"FOSS Force Staff FOSS Force has learned that we shouldn't write obituaries until we actually see a death certificate. SCO intends to file an appeal over the dismissal of its case against IBM."

"FOSS Force Staff FOSS Force has learned that we shouldn't write obituaries until we actually see a death certificate. SCO intends to file an appeal over the dismissal of its case against IBM."

"The World Wide Web has become an extremely strong source of information. Job seekers search for jobs on online job boards, while recruiters search for potential employees by listing their Web profiles. Such head hunting is, in particular, common when looking for a Linux professional."

"If there was ever any doubt about whether Microsoft or Google would win the war of office suites, there should be no longer. Within the last several weeks, Microsoft has pulled so far ahead that it's game over. Here's why. When it comes to which suite is more fully featured, there's never been any real debate: Microsoft Office wins hands down. Whether you're creating entire presentations, creating complicated word-processing documents, or even doing something as simple as handling text attributes, Office is a far better tool. Until the last few weeks, Google Docs had one significant advantage over Microsoft Office: It's available for Android and the iPad as well as PCs because it's Web-based. The same wasn't the case for Office. So if you wanted to use an office suite on all your mobile devices, Google Docs was the way to go. Google Docs lost that advantage when Microsoft released Office for the iPad. There's not yet a native version for Android tablets, but Microsoft is working on that, telling GeekWire, "Let me tell you conclusively: Yes, we are also building Android native applications for tablets for Word, Excel and PowerPoint." Google Docs is still superior to Office's Web-based version, but that's far less important than it used to be. There's no need to go with a Web-based office suite if a superior suite is available as a native apps on all platforms, mobile or otherwise. And Office's collaboration capabilities are quite considerable now. Of course, there's always the question of price. Google Docs is free. Microsoft Office isn't. But at $100 a year for up to five devices, or $70 a year for two, no one will be going broke paying for Microsoft Office. It's worth paying that relatively small price for a much better office suite. Google Docs won't die. It'll be around as second fiddle for a long time. But that's what it will always remain: a second fiddle to the better Microsoft Office."

Google acquired "Writely", a small company in Portola Valley that pioneered document editing in a browser. Writely was perhaps the first cloud computing editor to go beyond simple HTML; eventually crafting some really cool CSS-JavaScript-JSON document layout and editing methods. But it can't edit native MSOffice documents. It converts them. There are more than a few problems with the Google Docs approach to editing advanced "compound" documents, but two stick out and are certain to give pause to anyone making the great transition from local workgroup computing, to the highly mobile, always connected, cloud computing. The first problem certain to become a show stopper is that Google converts documents to their native on-line format for editing and collaboration. And then they convert back. To many this isn't a problem. But if the document is part of a workflow or business process, conversion is a killer. There is an old saw affectionately known as "Reuters Law", dating back to the ODF-OXML document wars, that emphatically states; "Conversion breaks documents." The breakage includes both the visual layout of the document, and, the "compound" aspects and data connections that are internal to the document. Think of this way. A business document that is part of a legacy Windows Workgroup workflow is opened up in gDocs. Google converts the document for editing purposes. The data and the workflow internals that bind the document to the local business system are broken on conversion. The look of the document is also visually shredded as the gDocs layout engine is applied. For all practical purposes, no matter what magic editing and collaboration value is added, a broken document means a broken business process. Let me say that again, with the emphasis of having witnessed this first hand during the year long ODF transition trials the Commonwealth of Massachusetts conducted in 2005 and 2006. The business process broke every time a conversion was conducted "on a busines

"Open source software is everywhere, and chances are high that you'll be writing, deploying, or administering it when you enter the workforce. Hiring managers are looking for candidates with experience in open source. Employers will often ask you for your GitHub username along with - or instead of - your resume. So, if you're all new to open source, where should you get started?"

"Open source software is everywhere, and chances are high that you'll be writing, deploying, or administering it when you enter the workforce. Hiring managers are looking for candidates with experience in open source. Employers will often ask you for your GitHub username along with - or instead of - your resume. So, if you're all new to open source, where should you get started?"

[ Ernesto on June 30, 2015 C: 62 Breaking The music industry has won a landmark ruling in France where a local magazine was fined €10,000 for showing readers how and where pirated films and music can be downloaded. The ruling is the first of its kind and serves as a warning to other publications that write about online piracy. ...]

[ Ernesto on June 30, 2015 C: 62 Breaking The music industry has won a landmark ruling in France where a local magazine was fined €10,000 for showing readers how and where pirated films and music can be downloaded. The ruling is the first of its kind and serves as a warning to other publications that write about online piracy. ...]

[...Paley avoided traditional film distribution deals and instead released the film under a Creative Commons Attribution-Share Alike license, writing: You don't need my permission to copy, share, publish, archive, show, sell, broadcast, or remix Sita Sings the Blues. Conventional wisdom urges me to demand payment for every use of the film, but then how would people without money get to see it? How widely would the film be disseminated if it were limited by permission and fees? Control offers a false sense of security. The only real security I have is trusting you, trusting culture, and trusting freedom]

Darryl Taft writes a follow up article covering the comments to his original AJAX-ARAX ruby on rails MS-iron python story

Like this http://www.hdfilmsaati.net Film,dvd,download,free download,product... ppc,adword,adsense,amazon,clickbank,osell,bookmark,dofollow,edu,gov,ads,linkwell,traffic,scor,serp,goggle,bing,yahoo.ads,ads network,ads goggle,bing,quality links,link best,ptr,cpa,bpa