PSE alpha web masters meeting 10/12/12
London: Royal Festival Hall
Charlotte Du Cann
EM co-ordinate changes from workshop into project tickets for tech work
EM show MG how to run project reports
EM organise editorial workday for FAQs and editorial guides for entry
EM clarify what happens if webmaster does/does not approve projects
EM contact RH about marketing widget/projects form to his contacts
EM contact Nominet about possible changes to use of remaining budget (slower spend)
Suggested enhancements and suggestions
(All the detailed changes and suggestions from the screen grab are also in the spreadsheet)
Search by date (to show latest for newsletter) – possible, EM to show MG
Include clear editorial direction at point of entry incl. examples and definitions
Option for web masters to choose what projects do/don’t appear in their widget
Randomise the project display in the widget to show variety
User-centred geo-location to present nearest projects to user’s IP
Widget name change to ‘Project Widget’
Text changes on the widget (see spreadsheet)
Text changes on the administration pages (see spreadsheet)
FAQ for web masters on process, and for different platforms
Marketing suggestions through personal contacts
UK only beta
Slightly longer beta with more time for product adoption and later changes
Widen the project scope (via a phase 2) to create a TN framework, initially for the major platforms, starting with a PSE Widget plugin
1. what are we bringing what do we want to get out of the meet?
CC: have suggested improvements on widget use
EM: looking for feedback and suggestions for taking to beta
CDC: have feedback on content in project forms and widget use
LW: looking for feedback and suggestions particularly around design
MG: couldn’t add widget on Ning; looking for Ning suggestions and figures for Ning use
CS: add value for future projects, bring life’s experience and ideas, want to understand how the TN implements projects in case he can help TN bring about more significant ones, enabling Transition to be more directly steered by the tremendous human capital in the wider TN community.
2. Walkthrough of webmaster adding a widget and user submitting a project with screen grabs
Detailed feedback in spreadsheet ‘alpha widget meeting feedback sheet’
High level suggestions added to these notes
CDC has been assessing and tidying the projects directory content as part of the project. Has now read every project. Took 4 days. (Details of brief can be read on project wiki)
Three main things arising from this work:
a) Need ability to define a ‘Transition’ and ‘Not Transition’ project
b) Need stages of a project: planning, live, finished
c) Content quality assessment: *very* estimated: three main types of addition
i) Excellently completed project profile of good Transition project: 10%
ii) Reasonably well completed project profile of good Transition project: 40%
iii) Idea that hasn’t happened: 25%
iv) Promotion for service or event or other unsuitable use for entry: 25%
Discussion around this content quality – generally considered pretty good!
Suggestions to raise the content quality:
a) add ideal project entry suggestions
b) promote excellently profiled projects
c) include editorial direction at point of entry
d) include project definition at point of entry
e) budget for regular content checks of this kind, incl. search request checks
EM outlined the moderation process (documented in design docs on project wiki). Asks group directly, now they have hosted a widget and added projects, if they are happy as web masters to moderate submissions. All agree, with the exception of CS. CS has not added a widget or project, but disapproves of any moderation. CS also disapproves of the modal pop-up design (roll-over of the host website), and CS disapproves of the requirement for users to register if they are adding content. All of these are core design elements agreed in the design phase in 2011 which are not in discussion.
a) the risk of users gaming the system (by using nearest postcodes, or re-editing etc.)
b) reward for users adding information
c) various ‘loops’ of information ownership that could arise (esp. person a adds project for person b, so person b would need to register and be added as project editor later)
d) a sense of the addition ‘missing longevity’ – the reason for adding projects
5. Plugins and platforms
Chance to develop specific ‘Transition plugins’ for specific platforms (e.g. WordPress)?
Social Reporters’ favourite projects?
Tie in with Rob H’s list of projects gleaned from TC blog for new book?
TIe in with REconomy works?