craig foc 08 afterinterview

Craig Hansen - New Zealand

Open SourceCommunityEducation

Prepared after the online interviewFor Facilitating Online Learning 2008Graduate Certificate in eLearningManukau Institute of Technology


Open SourceCommunityEducation

The interview was completed using Skype. Craig facilitated the interview, Bill responded for BISAM. The interview was recorded live, edited and segmented by topic using Audacity. Links to the audio files can be found on http:/craighansensblog.blogspot.com/


1. Client describes the problem or issue2. BISAM seeks client ideas about solutions that would suit their industry

• CLIENT has; big idea about industry, small ideas about IT solutions• BISAM has; small ideas about the industry, big ideas about IT solutions

• Provide general advice, book further time for more detailed solutions• Google potential solutions, speak with other experts• Gain clarification, increased understanding from client of issues in the industry• Produce a brief of tools for potential solutions, alternatives from present practiceAn example from the Print industry was used, describing the need for online ordering. The

client thought they would use• Scan and email solutions was proposed by client• BISAM provided an online option, capturing bookings and provide a ‘proof’ for

customers onlineThe outcome provided greater effectiveness (quality/milestones achieved), efficiency

(time/dollars) then expected by the client.

The Process used by BISAM


•We covered:• Open source verses freeware•Open source software can be developed feely

•Start a community on the new development•Grow a base of developers•A completely different product may result

The Mambo vs. Jooma was givenIt was suggested business models can be built on the strategic vision of company, rather than the commercial boundaries set by non-open source ownersThe role of community in developing open source software was highlightedThe CINDEOS CMS vs. site@schools example was givenThe real power of open source software is the quality of what can be created and the specialisation it can achieve, and can rival commercial products due to user input being extensive, with precise feedback that is implemented.

The use of Open Source solutions


Key Points2.Straight forward to install3.Easy to use, intuitive to create content and modify4.Cost effectiveness of set up and ready to go being $300 to $500 in total

•Users set up•Themes and modules and plug ins installed and ready to go•Ready to use

Drupal installs have organic groups, though do need more precise control levels of page developmentJooma as an alternative was discussed, not as powerful for collaboration as Drupal.Jooma has attractive templates that look clean, slick, tidy.The time commitment needed to keep a Drupal website looking good is a factorCommercial use of Drupal by very large publishing and media organisations (Fast Company)

The use of Drupal as a CMS


Managing updates – be mindful of2.Compatibility with content3.Time consuming compared with initial install4.Security updates could be a lower level of priority5.Back ups of users and content is highly important – of the server and a local back up6.Must-have updates should be done keep things cost effective

The update cost can be reduced by only installing updates that provide both functionality and security revisions

The updates issue


Organic groups with Drupal2.Self developing, maintaining, enabling3.Set authority levels, authentication

Organic Groups


Wikis provide the opportunity for people to:2.Contribute ideas, learning, experiences3.Add, Modify, Share contributions on a global platformWikis may contain a variety of contributions:•Subjective thoughts on topics or events, Perceptions or viewpoints, Perspectives and opinions, •Facts – verifiable information with dates, times, events, people and contributions that can be substantiated Wikis can track how the contributions have developed over time:Versions showing how alterations were made; like an editing track•History – showing who, what, when, how and possibly why changes were made•The capability to refer back to previous versions to identify the workflow and•To understand the development of knowledge as a whole

Wikis


Check out http:/craighansensblog.blogspot.com/