The Social Benefits of a Public Roadmap

ACF To-do list

Roadmap for development for the Advanced Custom Fields plugin for WordPress.

I am working with a team to redo a rather large NGOIt is worth noting that there are different flavors of NGOs. This particular NGO is also a non-profit charity and also a volunteer organization (most of the staff are volunteers). Not all NGOs fit this category, though I do make some assumptions in this post as if all NGOs do fit this characterization. website (both the NGO and the website are large). One of the questions through the process is How do we “dismantle a huge 1995 era website” and replace it with a “modern CMS system”? The new CMS of course is going to have to be phased in as its detailed features are built out. The social challenge is that if something which is not meeting the organizational (NGO’s) needs is replaced with something else which also appears to not meet the organizational needs then the people within the organization (the spectators, not the people directly involved with the website project) have a tendency to think that the newly launched product is a flop. The bottom line is that there is a general loss of confidence in the development and implementation team. In my particular context this often means that when people loose confidence in a development or implementation team that they stop expecting great things and start looking for other “more suitable” solutions. One way to combat this loss of confidence is to address the the people (and their concerns) who are watching the phased role-out. One part of that engagement strategy can be to do use a public Roadmap. Continue reading

Comment on Open Source development at NASA

A comment on: http://open.nasa.gov/blog/2011/09/08/open-source-development-at-nasa/

I am all for OpenData and Open.NASA. But how does NASA being a government entity relate to how it “licenses” it’s data and software? What I mean is that, shouldn’t the things being “open sourced” be public domain, rather than licensed content? I agree that creating a license which is not widely recognized is not useful, that is the whole point behind Creative Commons. But are there cases where NASA is “over licensing” content that it shouldn’t because it is the content should be released into the public domain? Reference CC Salon in Jan 2011, Time segment 1:05:00 where Joi Ito talks about the issue. http://blip.tv/creative-commons/creative-commons-salon-mountain-view-what-does-it-mean-to-be-open-in-a-data-driven-world-4725230

What prevents, or what reasons are there for not putting NASA’s data and software, which it releases, in the public domain? Is that not more open?

Open Change

I was recently looking at licenses for databases and discovered the ODbL license. This license was pioneered by the OpenStreetMap Project. I was reading their introduction to why the change was needed. This introduction outlined what the change was, what the change would allow them to do, who agreed, who disagreed, what the cost of the change would be, among other things. I thought it was a very open, engaging and confidence building way to move a group of volunteers through change. It allows for more kinds (also different kinds) of product use. It is well worth the look at not only if you are interested in the open licensing of data in databases and why CC-BY-SA and CC0 licenses do not work for data [also as PDF], but also how they are answering the questions of the community as they are moving the community through change.

Radiant a CMS developed in Ruby

I was browsing – cause that is what I do. – And I came across this very flexible, yet young CMS. :: http://radiantcms.org/

One of the cool things that I liked off the bat:

  • Update the data on display from an XML feed.

I immediately thought of a site I consulted for : scriptureearth.org that this could be a solution for that. (The site is in production but I am not sure how easy it is to update the data it displays. The connivence of a XML feed is that the site would be able to be updated from an app based in the workflow of the publisher.)