Revision to Previous Post - Write-Up

So Yishay made a great observation in the write-up that I previously posted. I responded to his comment, but it so apt that I think it warrants a posting unto itself.

Here is the comment and my response below:

Yishay -

all good, EXCEPT - I would start with f. First, get a system up and running with the minimal set of features you need to do a. Then add the features you need to do b, etc.

If you want to get people to buy into your plan, you need to show them something that moves. Then they'll tell you what's missing, and you can add it. People don't do well in abstract (unless they're mathematicians, computer scientists or theoretical physicists). They need an object to talk with.

Justin -

Thanks Yishay for this reminder as you are exactly correct in my opinion. Unfrotunately, I didn't articulate this point in the write up . But I did initiate the project in this manner.

After our discussion about ning as a platform for this project I went ahead and started site: MyCSA Network.

This served as the showcase piece that I sent to the decision maker on this project. After reviewing the site along with a few ideas driving the site, he told me to go ahead and produce a quick project proposal that addresses the rationale, the approach for building and maintaining the site.

So, going back to your comment, this just shows the need to be more methodical in recognizing the process of practice!

This is certainly important and underscores the need to effectively "enroll" potential users by showcasing something that can serve as a guide or reference for helping people conceptualize the types of things one hopes to accomplish. We all need to see or have something tangible to provide concrete evidence to our abstract ideas.

So here is the revision on Methodology Portion of the write-up to reflect this VERY important insight, informed by a pattern nonetheless!:

Methods for Design and Development:

• After defining an initial problem (see: rationale), build a base site with general functionality as a showcase.


• Extend Problem Definition (Interviews, Literature Review, Survey of Potential Stakeholders).


• Identify Specific Patterns linked to the Problem Definition (use: Liberating Voices, Learning Patterns, Conservation Economy.


• Adapt identified pattern to address specific program goals.


• Merge with Web 2.0 principles to guide decisions on final platform choice and subsequent implementation.


• Identify useful patterns for promoting and building user interactions on the final site, i.e viral marketing, mass mailers/e-mails, print media, word of mouth, blogging, etc...


• Iterate based upon user feedback to address potential emergent issues.

I would like to annotate my comment regarding the need to provide objects to talk with. Yes, it is critical, but simultaneously, it is just as critical to first understand what problems you are attempting to solve. So in looking at my own process it was the identification of a specific issue that initiated the idea to create a CSA focused social network. However, in the context of building any sort of participatory program the use of the pattern cited by Yishay becomes central as it can be used as a talking point to frame the rationale, purpose and eventuate an enrollment of potential users.

Software for Pattern Language Development and a Cool Intership Opportunity

So Yishay notified me yesterday that the base system for the collaborative pattern language development site is up and working. Pretty cool stuff! Here is the link to the new site: http://patternlanguagenetwork.myxwiki.org/

If we can get the pieces we want in the system I think this tool could become extremely useful upon completion. I posted some of these wants in posting on the Planet site already but if you missed that please go back and take a look.

The pattern language network project (Planet, http://patternlanguagenetwork.org/) is developing a system for collaborative authoring of pattern languages, based on the XWiki platform. We're having our own "summer of code", offering one or two intern opportunities for students of computer science or related fields.

Interns will contribute to the exploration of novel forms of knowledge representation, organization and visualization in this domain. A solid knowledge of a high level programming language (e.g. Java) is essential, as is a creative approach to web development.

Please note that this is not a paid position.

If anyone is interested get in contact with Yishay.

Guest Post on Patternlanguagenetwork.org

So there is an interesting group working in London called the Pattern Language Network. They are currently developing a pattern system called PlaNet, similar to what I have been envisioning for a while now, and it looks like a great group to collaborate with.

Anyway, Yishay and I have been in cahoots and discussing elements of the "PlaNet" system and I have posted some thoughts on their site to help initiate further discussion for building the system.

Check out the site and the post!

On the Framework Merry-Go-Round

So I have been actively working with drupal for the past several months, trying to get it up and running for an NGO in India. The experience has been fairly smooth and I have even gotten the hang of developing and extending modules for the system. Just a couple of weeks ago following some self-assessment on working with drupal I began considering it as framework for developing a pattern based knowledge management system.

That was of course until two interesting conversations took place. The first conversation was with Yishay who pointed me to the Google Appengine project. He already knew I was a fan of python and django so he brought this up as an alternative to working with drupal.

In all honesty (as I have said in previous posts) I would rather develop with a language like python and framework such as django. Now with the added integration with Appengine it seemed as a an interesting direction to take.

Strangely, the next day at work I was given the green light to begin diving head first into this django/appengine phenomena. We have been actively using SharePoint for most of our projects. Whereas myself I have bucked the system from the get go, instead opting to use google apps and/or building my own as needed.

Well, it seems that my efforts did not go unrecognized and with the help of a few collegues it seems that the google route was partially embraced even if it was just from the standpoint of conducting an investigation of what we might be able to do.

Personally, I would love to develop solely with django and python at work, and well it looks like I get my wish. So for this summer I get to spend all of my time getting acquainted with appengine and see what it can do. Where does this leave me with drupal and my knowledge management system? Well, it leaves with wrapping up my current project for JESA and most likely focusing on using the django framework as the foundation for developing the components needed for my system.

I feel like I have been on a merry-go-round, but considering the options, this summer's work and fellow colleagues giving me the space to become relatively proficient with this system it seems like a given that I will try and use this framework to produce my software.

I'm actually pretty excited about the prospect, as it seems like I'm in a perfect position to take advantage of the django/appengine integration. I'm a huge python fan and it is the language I'm most proficient with. I know django, having built a couple of blog and wiki apps (one day I will move this blog to the one I built), and well appengine uses BigTable and that looks to be an interesting adventure. So taking that together with what I want to do with the application I'm building it seems like a great tool set.

So, thanks Yishay, thanks Gary and definitely thanks to Jamie and Theron for pushing a multi-paradigm software shop at CTLT.