120 likes | 272 Vues
ENTICE Survey Results. David Foster IT Aug 2010. Survey. Piggybacked on the “Desktop Computing” survey. Reduced scope, only a few key questions asked. See if there is an indication for a more detailed survey.
E N D
ENTICE Survey Results David Foster IT Aug2010
Survey • Piggybacked on the “Desktop Computing” survey. • Reduced scope, only a few key questions asked. • See if there is an indication for a more detailed survey. • Not the best questions and perhaps not all well formulated, but interesting results nevertheless. • Wide audience (survey was sent to all CERN users) • Most interesting results were in the “free format” part of the survey: tell us what you think ... A lot did! • Results (from >1000 people) still being analysed. What is presented today are preliminary.
Accumulated response over time Time Each unit is half a day
The “other” category produced a long list of known (Python, vi, emacs, perl, PHP) and exotic (TextWrangler, SeaMonkey, KompoZer, plin, redmine, ezPublish etc)
“Other” produced things such as Root, Atlas Data Formats, Mathematica, .asp pages, Tex, .vi labview files, vhdletc ...
“Other” includes: AISMedia, JIRA, twiki, but not too much in fact.
Conclusions • Survey was well received • It is part of an overall plan to improve IT communications with the community. • Results will be presented at the next ITSRM • IT will act on a number of clear trends that emerged: • Macintosh Support • Opensource: the first example being a Web CMS. • IT is engaged in understanding how to be more flexible and respond faster with a “community style” support structure. • ENTICE: The Opensource services will be in this style.
Known Drupal “Interest” • CERN Website (Bulletin, public, user and press) • IT Website • PH/SFT • Service Catalogue (GS/IT) • KTT (as part of the CERN website) • HR • FI and Procurement • Library
Future ENTICE Meetings • Engage with the web application developers in the context of the Drupal and Sharepoint services. • Membership may change • Continue to work on the major areas of: • Common policies • Content accessibility • Community support • Establish the community support model • Mailing list already started
Detailed Drupal service/policy issues to be worked on • Site Request Process • Guidelines and Policy for site creation (Themes, Modules etc) • Roles and Responsibilities for site owners • Domains Management and Rewriting • Central Module Management • Site Module Management • Central Theme Management • Site Theme Management • Integration with Content Repositories • File access for theme development • File uploads (restricted to begin with - part of an org policy. Need to work with CDS) • Monitoring and Statistics • Search (How should it work? A design) • Change Management (upgrades) • Incident and Problem Management