We just had a call with Ed discussing the biggest items he learned from the survey results, plus we formed the IA team and selected a date for the final IA documents. Other people are welcome to join the IA team...just get in contact with Jacob (http://groups.drupal.org/user/158453/contact)
http://files.me.com/aangel/drewsx.mp3 (64 min)
Here is the transcript:
Ed Mitchell: have a look at the transition primer for some handy info on TT:
[5/20/10 8:13:08 AM] Ed Mitchell: http://www.transitionnetwork.org/resources/transition-primer
[5/20/10 8:14:18 AM] Andre Angelantoni: Also check out:
http://www.postpeakliving.com/preparing-post-peak-life
[5/20/10 8:14:21 AM] Andre Angelantoni: (video)
[5/20/10 8:22:04 AM] Ed Mitchell: 1. get related
[5/20/10 8:22:09 AM] David Herron: I just dropped off
[5/20/10 8:22:31 AM] Ed Mitchell: http://transitionculture.org/2010/05/19/energy-descent-action-plans-for-...
[5/20/10 8:24:08 AM] Ed Mitchell: 2. Ed feedback from surveys and consultation
[5/20/10 8:24:38 AM] Ed Mitchell: 3. initiatiate IA group to point of dates and deliverables
[5/20/10 8:26:32 AM] Ed Mitchell: http://www.slideshare.net/edmittance/transition-web-project-survey-prese...
[5/20/10 8:32:26 AM] Andre Angelantoni: Interesting...another axis to look at for the IA is time and the maturity of the group
[5/20/10 9:00:46 AM] pauljmackay1: http://trac6.assembla.com/transition-initiatives-web/wiki/Information%20...
To anyone who listens to this call please consider taking notes along the way and adding them to this discussion.
If you're just joining the conversation, the project kick-off call (May 7, 2010) is posted below (start with that call to understand more project details):
http://groups.drupal.org/node/67123

Comments
My notes on today's IA discussion
First, I just wanted to say I wish I could have made it on this meeting because it sounds like it was really interesting and inspiring. I've just finished listening and I made these notes along the way. Please prod me if I've misrepresented something you said or if I missed something important - it's quite late here now. [NB. My comments are in square parentheses in a few spots throughout]:
=====
Basic intros
[BTW sounds as if someone's sitting in a jungle while this was recorded!]
Wes: in his intro, Wes mentioned a requirement which there wasn't time to expand on later. I think it's worth returning to when we discuss different site structures: he suggested we structure the San Fran site [and, by definition, any major city site] into small neighbourhood groupings but that some steering groups would need to be city-wide. Not sure how this could work - perhaps with a geographical taxonomy vocabulary separate from a thematic vocab.
After intros, Ed gave an overview of the 2009 UK TT survey findings:
Questions for Ed on his overview:
André quickly asked about Ed's concerns about Google Groups and it was mostly around data ownership [which hopefully won't be a problem with this team.]
Paul asked about what Ed sees as being the major barriers to volunteers using the sites and did he see it as an issue of competence of the users or the complexity or is it an education gap? Ed replied that on the whole there were many people who weren't into the web. He also mentioned there's a correlation between the complexity of the TT and the complexity of the needs. It's up to you to use. At the release or introduction of a new initiative's website, you have to ask who's the facilitator, where are the domain experts, who are the champions and assign roles.
He also mentioned you should aim to find an editor for the site and identify "reporter(s)" for each thematic group within an initiative to ensure content is added regularly and make sure the site features useful content. And he also suggested you should review the site occasionally and the sections which aren't being used should be "pruned" or removed, which is happening in Totnes.
Paul then raised a very interesting question about expanding this to the much bigger issue of offering access to content via a whole array of media channels such as mobile apps, SMS, printable content (i.e. newsletters for noticeboards), kiosk-type terminals in community cafes, etc.
Ed mentioned the fact that the Feed aggregator will be able to offer a report printer. He then elaborated on the fact that the UK will move further towards mobile being the primary access point for the web and added that it's a far more diverse channel with less socio-economic barriers so essential that we're able to offer content/functionality over mobile. Ed also mentioned that he's seen some really innovative ways of using SMS to coordinate groups effectively or as a collaboration tool. Providing interfaces for users who don't have access to the web is vital (examples given were faith groups and those on low incomes) and that the poster is still a very strong way of communicating.
André mentioned how vitally important it is that we ensure the interface is really clear and as simple as possible.
Jacob's Information Architecture project
Jacob asked about whether or not we already have a Requirements Specification or similar document and André admitted that there isn't a detailed document in existence yet although there's the beginnings of one on the TD site. Jacob then also inquired about the existence of User Stories or Personas and Paul explained that we don't have anything like that but that the London team had been working on writing up very brief "agile"-style functional narratives. [as an aside, I should mention that, had we had more time, the London team would have made personas and user stories].
André next asked what Jacob would do next, had he been contracted to work on this project. Jacob responded that since he's jumped onboard, there's one word that's come up through many of the discussions and emails and that's "taxonomy" and he suggested that what we might want to aim to design is a hybrid between a taxonomy and a "folksonomy" because otherwise it's really going to fail. Ed corroborated this with experience from their site. Then Jacob went on to expand on this by explaining that the majority of users don't really use tagging themselves [this conversation shifted but I was interested to learn more about what Jacob meant here so will probably start a discussion on it just to clarify]. And Ed added that they use it as a research tool to pick up differences in tagging patterns rather than making a big song and dance about it.
André shifted the conversation back onto Project Management and asked what we'd need to do to get to a "site blueprint" by August 01 and Jacob queried whether he meant a blueprint, a sitemap or a project plan then, André explained he meant all of the above and Paul attempted to clarify by asking what artefacts we really need to produce and what they need to contain. Jacob suggested there are three artefacts: the persona charts, a sitemap and a simple functional specification (i.e. what is the backend situation, a content list or a content analysis of content contributors which could be as simple as an Excel spreadsheet based on the taxonomy).
Jacob mentioned we already have a taxonomy [I assume he means the draft wiki I created] but André interjected to point out that we're not sure this is the correct taxonomy for our needs since it's a taxonomy based on the needs of a small initiative. Jacob asked whether that would be an issue and André admitted we don't know yet; he went on to explain that we think someone needs to sit down and analyse all the different axes that a site should take into account whether its time-based, scale of the initiative [by which I think he means the number of nodes or layers in the network], location (urban/rural/in-between).
Ed then asked whether we should take an agile approach, build a basic IA then expand it to meet new requirements as they emerge or whether the needs of a large city such as SF [or London] are complex enough to mean we need to design a complex IA up-front. André suggested that it's worth spending some time thinking about these issues up-front to prevent later issues which can be caused by using an over-eager agile approach. Ed responded by asking whether we could at least start simple in terms of product releases and André agreed that's definitely what we'd want to do.
[I would have butted-in here to point out that the London team have been thinking along the lines of at least designing several IA structures which can flex and grow over time to allow say a "mulling" town to upgrade to the status of "official", then "mature" and presumably we could also grow this to meet whatever needs the Transition movement itself identifies as time passes. On a related note, I spotted the other day that the Aegir site management system for Drupal which André has recently been discussing on the forums has the ability to "upgrade" individual sites within your manifest from one configuration to another, thereby providing a tool we could use to move a site, once the initiative feel ready to expand their functions and tools to the next level].
André then went back to ask what kind of persona Jacob needs to sit down and create: ie. would an urban persona be different to a rural one? [I like Ed's mention of the old lady in Norfolk and the energy entrepreneur in NYC - perhaps we can use them as the basis of our personas?] He then went on to ask Jacob if he'd be willing to take on the task and marshall the troops and take on this task, adding that the date is not fixed.
There followed a conversation around the optimum platform for developing the core IA documents: ie. do we use GDO, TRAC or Ed's wiki site? Although it was felt there's enormous value in maintaining the GDO presence for the team as it is garnering attention right now, a distinction was drawn between the ongoing conversations as opposed to development-level work.
[Having used them, I side with Paul on this issue: the wiki pages on GDO aren't very good - I would prefer to be working either on TRAC, Ed's site or possibly Google Wave since it's so good for collaborative writing]. I was glad to hear that by the end we'd arrived at the conclusion we stay off GDO for document collab activity.
Paul then reiterated his point from our last call about wanting to have a D6 version of the site up and running in advance of the TD7V1.0 release. [It occurs to me that the reason he raised this was because he was thinking perhaps whatever we develop for D6 might be a model for a relatively simple town, rather than a full city-wide network mature initiative].
Jacob agreed to lead the IA process [Jacob, let's talk about how we can play together]. He also thought it would be fine to meet the August 01 deadline. There were no objections to aligning with the IA.
Ed offered to help out with publicising to the network.
André suggested Chris might want to work with Jacob quite closely [I do] and asked if anyone else on the call would like to work with him. Paul and Wes said they did and Ed made himself available for outreach, info and research. André said he wouldn't be on the core IA team though.
Ends
great transcription - and I'd remind about simlicity to all
Great transcription Chris, nice one!
No time to clear up some of my less clear statements (I ramble at times to say the least so am sometimes hard to work out what I"m saying - and I am working on this!) - but it's great.
I've thought about the whole thing a bit more and I think my key suggestion is to start simple - work outwards from a basic set up. This is a highly experienced and very ambitious group (which is awesome), made largely of folks in quite sophisticated initiatives, so do think of how to start this whole thing for people who are a bit baffled by the web, with simple needs, that quite possibly will change, but they start simple (I'll report back on my local initiative http://www.transitionmontpelier.org.uk who I set up a WP config for and are at the point of wanting something more sophisticated)...
And a point with my facilitatory building and maintaining bridges hat on - how this fits in with the other sites in the TT web constellation - the national hub sites, the TN site with the directories, the initiatives with their own sites, the social networks, etc. etc. (I think I'm going to create a page for this on TN.org when I've got a moment)...
There are great opportunities for overlap, which also bring risks of conflict and confusing users...
For example, the projects directory http://www.transitionnetwork.org/projects is a critical component in the puzzle - at the moment it's centralised, proving the concept - in the future we want to be able for it to be applied and shared anywhere, and used in partnership with other movements (e.g. we are using it to collect projects for the UK's Zero Carbon Britain project), as well as appearing in local initiative sites (e.g. creating a badge for it or a local view - e.g. a 'transition projects in your area' badge, or a 'transition projects on energy' badge - I'm sure you can see where I'm going with this - open data, open access, open standards etc. The same goes for the initiatives directory http://www.transitionnetwork.org/initiatives - how can we maintain the process of using one standard reliable user-managed directory of initiatives (utterly, utterly vital) amid this wonderful crazy world of millions of sites/networks/services?
So we've got a lot of work to do to agree formats and APIs etc. which I'm keen to keep open, nay, build an expert user group from around the movement (like a standards and sharing group) to ensure that we're all doing our stuff in such a way as it's distributed and find-able, shareable etc.
I'm working to drum up some funds for our 'sharing engine' track which can help us all connect users with different data sets across platforms etc. and we're keeping an eye on this work here so that enhancements done on the TN.org site are aligned with work here - all suggestions appreciated about how we do this...
This is unbefreakingly
This is unbefreakingly great!! Thanks for writing this up, Chris!!!
Andre Angelantoni
Founder, PostPeakLiving.com
Word of the week
Well it was an unbefreakingly brilliant call and I was feeling left out so I wrote it up so I could get my two cents'/pennies' worth in.
Let's make sure the whole project is unbefreakingly brilliant.
I was glad that Jacob agreed to take on IA. Have you had any luck engaging with any themers? I'll try to put out a call.
Themers
Not yet but I haven't asked any directly yet...just putting out notices in newsletters and such.
I'll make an announcement at the Berkeley Drupal User Group meeting this week.
Andre Angelantoni
Founder, PostPeakLiving.com
web stats
I agreed in our skype that I would put a call out to see how many TI sites would share their stats. I've popped a little piece in the forum here: http://www.transitionnetwork.org/forum/support/web-usage-statistics-tran...
The forums aren't launched yet, so they're not getting much attention, but it's a start, and let's keep pointing people back to it :)
Kicking-off the IA project
I just thought of a few more notes after this evening's call:
There seem to be a fair number of separate high-level requirements for a TD site. I'm sure there are more but here are some I can identify:
Finally a few other observations:
replies
We started the TN.org site with standard drupal set up as you can all imagine and civiCRM is lurking big time in my mind for a significant enhancement at some point - as we stand now it's a hammer to crack a nut - but I have a suspicion we'll need to have something similar in not too long.
On fundraising - I'm really not a money/sales guy, but will point people to opportunities if I find them. Likewise, the Network (UK) is aware that initiatives are saying 'we need money!' and trying to keep those cross-initiatve conversations going (it'll come up in the conference next month I'm sure, and it's an interesting question).
and bartering - this came up in the public consultations last year and it's a definite possibility and benefit of a centralised platform - if/as the TN virtual space gets more sophisticated - can it move to bartering/trade? Another reason for drupal and openid. Or do we partner with the number of great sites out there already?
Web analytics for the TI sites. Goooood thinking batman. Hmm. I'll ask around and do a forum post and some tweeting about it. You are welcome to the TN web analytics (people are after the directories first and foremost and then the support materials like the primer etc.), but I know that's hub stats.
You see, this is where the whole transition technologist and transition webcomms groups are needed. Once a figment of my imagination (early 2009), then a trial group (the transition technologists doing the TN site, 2010), now a pure bottom up group (transition drupal here we are) - it's so close now - err.. what am I saying (told you I ramble)? I'm saying we need a space for web comms folks to chat about stuff - I had a plan to use the TN forums for this (a sensible place for TT web comms folk to meet imo) - I'll bung up a post in the new forums (haven't made them public really yet).
Good list
re: the Transition Drupal name I'll send an email to the Drupal Association to get some clarity on that.
Andre Angelantoni
Founder, PostPeakLiving.com
naming
re: the name: I don't want to barge in but would you mind if we thought about how we might perhaps work it within the constellation of TI sites, national hubs, 'transition technologists' etc.? If you say 'no it's our project, we'll call it what we like' that's fine :)
Sounds good to me...
Personally I think it would be best if we could fit in with the general Transition ecosystem as much as possible. Ed, do you have any more specific thoughts on this?
Are we looking at the name for the overall project and potentially names for different versions or installation profiles that would map to sites, hubs, etc?
Where will the name be seen?
I think there are two slightly separate issues here:
I'd definitely support fitting into the general existing TT ecosystem but I'm a bit unsure how much the name of our project would be seen once it had been installed...
For instance, in my head I'd pictured a scenario whereby any new town that applies for "Official status" would then be sent a message (Ed, is there some sort of TT "Starter Kit"?) from the core network to offer them our Installation Profile to run their site (along with instructions, documentation etc). If they then decided to use it, they'd name their site www.transitionlasvegas.org or whatever they'd want, and you would no longer see any reference to TransitionDrupal from that moment onward.
The reason I raised this is because I was concerned the Drupal Association's Trade Mark definition http://drupal.com/trademark would potentially restrict us from calling ourselves "TransitionDrupal" because another project might start up with exactly the same idea (in the same way "Open Atrium" isn't called "Intranet Drupal").
One more thing to consider
I'm not attached to the Transition Drupal name. Without going through a big naming process it was easy and started to indicate what the project was about. But the more I think about it the more we may not be able to use Drupal in the name. We'll see.
In any case, as Paul points out, Ed could you say a bit more about what you think it would mean to work the project into the existing Transition naming scheme given what Chris distinguished above?
Right now people would use the name in the following way:
Person 1: "What software are you using to run your site?"
Person 2: "We're using version 2.0 of Transition Drupal distribution/project/package with the bartering and local currency modules added."
Really it would be no different than saying one uses Microsoft Word as one's word processor...the documents themselves don't ever say "Made with Microsoft Word" (though the footer of this project probably should have a link back to the project site).
Andre Angelantoni
Founder, PostPeakLiving.com
naming
sorry I've been away all... hmm naming, eh?
I've been thinking about this for a few days and am still wrestling with it. I'm going to be meeting Paul and Chris at the TT UK conference in 10 days (hurray, cant' wait!), perhaps we could discuss it then? But I am thinking about it :)
We call the aggregator/syndication/synthesis stream the 'sharing engine', which is quite hippy, but does what it says on the tin.
Hmm. Will ponder.
user stories
here are the user stories that came out of the public consultation for the TN.org site from Josiah - it's conversational as that was our frame but (a) there are some good human stories here and (b) you'll see we were wrestling with some similar issues!
I'm not sure exactly who we're working for - but I'm guessing that it is everyone already involved in Transition and everyone who might want to get involved at some point in the future.
Obviously some people will really want to engage with the on-line incarnation of Transition and will make a huge contribution. Of those there will be a broad range of interests - some very focused on local activity, others interested in the national and international aspects of the movement. I think we can come up with something to meet these people's needs.
But what about everyone else?
The muller with very limited experience of the net who wants to meet others in their area. The gardening enthusiast who just wants to find out how another group set up their food project. The core group without the skills to put up a basic website.
I think we're certainly talking about meeting their needs - but will we? Do we really understand this group?
I'm often surprised at just how little most people make use of on-line resources and at how little experience they have with even simple systems. My partner is a classic example. She uses the internet a fair bit and uses computers at work all the time, yet she really struggles to extract the information she wants and often gets 'lost' in big websites. She frequently gives up on a search, a forum or some kind of electronic transaction frustrated and confused (the last thing she wants at this point is an offer of help from me!!).
So I thought about one of the local Transition Initiatives I know well-ish (not the one in my own town - though I could have done this exercise with them too) and I decided to try and write a short biography of a few core members - those driving the initiative, thinking about their interest in all things virtual and electronic.
What follows is just a thought experiment, it isn't scientific and it offers no answers - but these are real people (names changed) and I think we need to keep them in mind:
All are TT Core group members and commit a great deal of their spare time to the group.
Mary: Retired pottery teacher, runs a small B&B, life long resident of the town and keen cyclist. Since retiring Mary has travelled to South America to do voluntary teaching work and thrown herself into community work back home. She’s an environmental activist of the old school and can be quite fiery. Mary has an email address and checks it every weekend - it helps her keep up with her children in Sheffield and Scotland. Generally speaking she finds she has a lot of messages to go through and so only opens the ones from people she knows; this is mainly to save time but also because she worries about viruses. This weekly email check is her only significant contact with the internet.
James: Is a healthcare professional in his mid-thirties, newly moved to the town and with a young family. He’s keen to get involved with the practical work of the group - it’s a good way to meet like minded people, do something worth while and get out with the kids. James has to work with various IT systems but isn’t a big fan, he’s able to check his personal e-mails at work, but doesn’t have time to reply or to surf the net. When he gets home in the evening and at weekends he likes to spend time with his wife and children so time on the net is limited. James has been persuaded by old university friends to set up a facebook account, but only responds to messages - he’s not an active poster. He has no desire to ‘hang-out’ in a virtual space, but sees the power of the internet to accomplish specific tasks such as researching travel arrangements - he also did all last year’s Christmas shopping on-line.
Jess: In her mid-twenties Jess runs a small business and is very well connected locally. In her spare time she’s active in the local light opera group as well as keeping horses. The internet is her primary marketing tool and she’s had a website built (though she’s unsure how to up-date it). Jess often finds herself in front of a computer but has limited time to dedicate to non-work related research or communications.
Toby: In his mid-forties Toby is a professional book searcher. He works from home which fits in well with his responsibility for his two children. The nature of his work means that Toby is generally in front of a screen for three or four hours a day and is an expert in extracting information from the web. However, his clients are getting better and better at doing their own on-line searches and Toby is increasingly finding that his best contacts are those book shops and dealers not yet on-line. Toby has some basic programming skills and enjoys spending time exploring the more esoteric fringes of the web, he’s a member of and regular contributor to a range of forums, he also maintains his own blog.
I suppose what I'm wondering is:
How do we make sure we connect the virtual and the physical?
How do we ensure that the web doesn't become a barrier or a 'transition info' gatekeeper'?
Ed, I think these kind of
Ed, I think these kind of user stories are a great way to approach the IA! (Not least because they can be derived from real people.) Interesting that the examples above represent a real TT Core Group. Out of curiosity, how do the less web-savvy folks (like, say, "Mary") keep in touch with the rest of the group about meeting times, etc? From the once a week email check? Over the telephone? Do they just run into each other in person regularly? Or do they just announce the upcoming schedule at each meeting and everyone jots it into their pen-and-paper notebook?
physical world interactions
Hi Wesley,
good - glad they're of assistance. On the whole, people stay in touch at regular meetings, knocking on eachother's doors, bumping into eachother on the street, mobile phone. We have members in our core team (Montpelier Bristol) who visit the library once per week to check all their mails - so last minute changes leave them high and dry (making the use of the web exclusive, which isn't great).