One of the rather positive outcomes of my case against College Publisher from a few weeks back has been the formation of a diverse group of people around a new project to provide an alternative: CoPress. A product of the sudden realization that many online editors across the country have many of the same opinions I do, CoPress is an initiative to build a technical eco-system of student newspapers working together and supporting each other on a common, open source content management system. Until this point, it has been largely the case that, when building and maintaining digital platforms, student newspapers have found only success on their own, with their own developers, creativity, and fortitude.
We hope to change things up.
Together we have strength. I think I can speak for everyone involved when I say that the collective vision of CoPress emphasizes the community, and how the community can work in harmony. Innovative, standards-compliant software is one immediate issue we’re trying to solve, but it isn’t the only one. Brian Murley, of the Center for Innovation in College Media, forwards that hosting is also an issue. From that discussion, we’ve also learned that supporting a piece of software with the technical expertise to keep it updated is critical. These problems will have to be addressed in order for any student newspaper to survive. It’s more powerful to work together than individually. We’re not profit driven, although the consortium will need to be financially sustainable. We’re driven by a genuine interest to work together because, when we do, we can create beautiful ways for student newspapers to flourish in the digital age.
In the interest of radical collaborative openness, we’re doing as many things as transparently as possible. The motivation for this comes from a concept I call an “open source organization,” although I’m well aware “open source” has become a buzzword for many recent projects. It started with Whitman Direct Action, I’m evolving it with Oregon Direct Action, and I think is applicable here, too. The idea is simple: put all of the data about what you’re doing online, and structure the data such that your audience, let it be the team, the partners, or the community, can follow along to the degree they would like to participate. Clay Shirky says we have a lot of cognitive surplus floating around. It’s time we put it to use.
Our conference calls are recorded and available as a MP3 download, with near future plans to create a podcast that will make listening in even easier. We synthesize research and coordinate efforts on our wiki. Information is also expressed with Twitter, delicious, and Flickr. We connect via a Google Group and, if you don’t find a piece of information you need, you’re more than welcome to contact CoPress.
At the moment, we’re working on a few things. First, we’re beginning to research the software options we’re most interested in: WordPress, Drupal, and the Populous Project (built on Django). CoPress would love to support the Populous Project, another student project, and eagerly awaits their alpha release in the coming weeks. WordPress and Drupal, however, have deployability and hackability characteristics that will be hard to match. Second, we’re compiling the names of online editors, webmasters, and internet geeks at student newspapers around the country who might have interest in what CoPress will have to offer. From this, our hope is to do a series of surveys gauging the technical expertise in today’s newsroom. We want to make sure as best we can that we’re serving the needs of everyone, not just ourselves. Last but not least, we’re continually evolving our web presence as a tool to help better achieve our aims.
And this is just the beginning. Thanks to Adam Hemphill, Greg Linch, Kevin Koehler, Joey Baker, Bryan Murley, Jared Silfies, Albert Sun, the Populous Team, and anyone I’ve missed. I look forward to working closely with you and others in the coming months to make all of these ideas and more our collective reality.