Collaboration -- what projects are you working on?
Chris Beer
what is going on out there -- what projects are you working on, what
can you share?
Amanda Hirsch
CPB-funded collaboration:
Blog: http://www.economystory.org
(On the blog, be sure to read the About section for info on each
organization's contributions - the blog is just a snapshot of the work/
coverage taking place)
Twitter: @economystory
Facebook: http://www.facebook.com/economystory
We're funded through May and are trying to figure out how to build on
the incredible momentum we've got going - this project came on the
heels on the Election 2008 collab, and between the two efforts, we've
built some really strong relationships between news rooms/ web shops.
We've also learned a LOT about what it takes to collaborate
effectively, and are putting together lessons learned/ best practices
to share across the system...
Chris Beer
to answer:
What projects or tools or tech are you interested in hearing more
about? What questions do you have?
Yesterday I got the 30-minute version of theworld.org workflows and
tools, and learning about what our colleagues are doing is fun, and
generates some great ideas discussions about problem solving and
sharing solutions. I'd love to see more of that in a systematic,
system-wide way -- it's just hard to talk about those things
unprompted.
johntynan
http://twitter.com/SusanMeyerWOSU has done with
http://www.columbusneighborhoods.org/
Specifically as it relates to user generated content and their
partnerships with the Columbus Metropolitan Library and
interactiveknowledge.com .
johntynan
projects are we working on, *what lessons we are gaining* from the
projects we're working on.
For instance, I'm toying with the idea of writing a series of blog
posts on these topics:
* Building a CMS is a red herring! Building discreet apps are more
fun and more likely to succeeed
* Don't be afraid to scrap everything and start over
* Lowering the cost of failure (and increase the frequency at which
you make your next attempt) with open source / software as a service
* Deploying with Google App Engine has its benefits (and its
challenges)
* Use a versioning system to build the app incrementally "Commit
Early, Commit Often"
* Practice Iterative Development: Involve the user early on both in
the design and in fine tuning the app prior to launch
At the risk of getting overly technical, I've been working on a list
of common tasks and processes used in developing apps with python
(specifically django and web2py):
http://docs.google.com/View?id=dssw3xx_42hb2mfmgw
Something like this might be useful to a subset of our community (and
I'd like to know who those people are).
On Mar 14, 10:41 pm, johntynan <jgty...@gmail.com> wrote:
> A recent project that I'd like to hear more about the work thathttp://twitter.com/SusanMeyerWOSUhas done with
Chris Beer
I completely agree, building a CMS isn't worth the time or effort.
There are plenty of good solutions out there (django, wordpress,
drupal) with really great communities already out there. Even when
building discrete applications, there are some really good starting
places (e.g. for the digital library project I'm working on, we're
taking advantage of a next generation library catalog ruby on rails
app called Blacklight <http://projectblacklight.org/>).
I'd also strongly second iterative development, and add building
prototypes allows the users to figure out what they _actually_ want.
On Mar 14, 11:01 pm, johntynan <jgty...@gmail.com> wrote:
> I think there might be value in discussing, maybe more than what
> projects are we working on, *what lessons we are gaining* from the
> projects we're working on.
>
> For instance, I'm toying with the idea of writing a series of blog
> posts on these topics:
>
> * Building a CMS is a red herring! Building discreet apps are more
> fun and more likely to succeeed
> * Don't be afraid to scrap everything and start over
> * Lowering the cost of failure (and increase the frequency at which
> you make your next attempt) with open source / software as a service
> * Deploying with Google App Engine has its benefits (and its
> challenges)
> * Use a versioning system to build the app incrementally "Commit
> Early, Commit Often"
> * Practice Iterative Development: Involve the user early on both in
> the design and in fine tuning the app prior to launch
>
> At the risk of getting overly technical, I've been working on a list
> of common tasks and processes used in developing apps with python
> (specifically django and web2py):
>
> http://docs.google.com/View?id=dssw3xx_42hb2mfmgw
>
> Something like this might be useful to a subset of our community (and
> I'd like to know who those people are).
>
> On Mar 14, 10:41 pm, johntynan <jgty...@gmail.com> wrote:
>
>
>
> > A recent project that I'd like to hear more about the work thathttp://twitter.com/SusanMeyerWOSUhasdone with
Barry Gilbert
playlist system and to replace our scheduling and program log systems.
This will allow us to schedule shows, features, underwriting, new
stories, announcements, etc. It also is our music catalog, tracking
what's in our library (both physical and digital) with ties to Amazon
Web Svcs for ease of data entry. The DJ's and program hosts will have
an elegant interface, called Show Builder, that tells them what to
play, provides them with the text of whatever they need to read, to
confirm what they've played or read, allows them to add items, like
psa's music tracks, announcements, etc. The output of the system will
be used to drive all public-facing website representations of our
programming, Sound Exchange reporting, and the schedule that drives
the recording of our archives.
It is being developed by a group of five students from the University
of Colorado's computer science program to fulfill their senior project
requirements. It uses PHP, JQuery, mySql, as well as some third party
libraries. There are a lot of AJAX, drag-n-drop and auto-complete type
features. The code is being written using as much OO design as
possible and using all open source tools. It will serve as the
framework for a lot of additional features that we anticipate
developing in the years to come. My hope is that we will eventually
make the app available to all community radio stations, perhaps as an
open source project.
We are expecting to launch the app by early summer.
Barry Gilbert
KGNU
Chris Beer
How much overlap with the Denver Open Media/Open Media Project <http://
groups.drupal.org/open-media-project> is there? It sounds like there's
at least a conversation in there.
Will the code be released as open source at some point? It sounds
pretty useful, and a good starting point for alternatives to some
proprietary software.
Chris
Barry Gilbert
To unsubscribe from this group, send email to public_media+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
--
99andbarry.com "It's Supposed To Sound Like That"
Twitter.com/99andbarry