article thumbnail

Reply Comments on the Proposed Treaty for Access to Copyrighted Works

Beneblog: Technology Meets Society

We filed the following comments to the Copyright Office's request for comments on issues about access for people with print disabilities. Everything that needs doing can be done by license voluntarily. It’s completely rational for a publisher to not bother signing a license that represents either zero or trivial sums of money.

Copyright 158
article thumbnail

OpenOffice.org to get a boost

Zen and the Art of Nonprofit Technology

It’s stable, feature rich, uses open standards, reads and writes MS files, and, did I mention it’s free? No administration fees, no license checking, no running out of licenses for larger organizations, nothin’ Download it and put it on every desktop and get rid of that license manager thingy.

professionals

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Are Social Enterprises Viable Models for Funding Nonprofits?

ASU Lodestar Center

The traditional method of receiving tax-deductible donations is to file for 501(c) status with the Internal Revenue Service, an application for 501(c)(3) status designed for a religious, charitable, or educational purpose. However, the impact of the “Great Recession” in 2009 and 2010 left its founders with dwindling funds.

Model 53
article thumbnail

Guest Post by Alan Levine: Social Media Recap from NMC 2009

Beth's Blog: How Nonprofits Can Use Social Media

Submitted by Alan Levine, publisher of CogDogBlog Since it is already a week in the rear view mirror, this ought to be my last post about the 2009 NMC Summer Conference. cc licensed flickr photo shared by alumroot. cc licensed flickr photo shared by cogdogblog. cc licensed flickr photo shared by cogdogblog.

article thumbnail

Case Study: Moving to Google Apps

NTEN

My job was to keep everything up and running: the network, file servers, computers, printers, email systems, etc. In 2009, we finalized a technology plan. At this point, the servers were aging and needed to be replaced, and we needed new software and user licenses (MS Exchange Server), as well.