2012 Developer budget: Difference between revisions

From Wikimedia UK
Jump to navigation Jump to search
(starting page; draft for improvement)
 
(expanding notes. Need to make these more verbose.)
Line 11: Line 11:
* DirectDebit form (custom software)
* DirectDebit form (custom software)
* glamwiki.org
* glamwiki.org
* Email
* Email - POP/IMAP/SMTP, webmail


We also have service providers for domain names and SSL certificates.
We also have service providers for domain names and SSL certificates.
Line 20: Line 20:
* Gift Aid for CiviCRM
* Gift Aid for CiviCRM
* QRPedia
* QRPedia
* Hosting a mirror of the Wikimedia project dumps
* Hosting a mirror of the Wikimedia project dumps - see [http://meta.wikimedia.org/wiki/Mirroring_Wikimedia_project_XML_dumps]
* OTRS/other CRM system
* OTRS/other CRM system
* More robust backup plan
* More robust backup plan
* Security review, and improvements based on the outcome of that review
* Security review, and improvements based on the outcome of that review
* Mediawiki development
* Mediawiki development
* 2012-13 fundraiser (does this fall under this budget?)
** Banner design
** Landing page design, including forms
* wikipedia.org.uk portal (e.g. like http://www.wikipedia.pl/ )?
* Expense system?
* Community server?


== General approach ==
== General approach ==
Since our needs are so varied in terms of the skills and knowledge they require, and each need does not require a significant amount of work at the current time, our general approach is to hire contractors as needed, and to collaborate with partners where possible.
Since our needs are so varied in terms of the skills and knowledge they require, and each need does not require a significant amount of work at the current time, our general approach is to hire contractors as needed, and to collaborate with partners where possible. Also offer bounties for development of specific non-urgent things?
 
Note that a single person could fulfill the needs of several contracts.


== Infrastructure ==
== Infrastructure ==
* Servers
=== Servers ===
* SSL certificates
The current solution of a VPS works well for our current purposes, but our needs will go beyond this. Suggest a trio (or quadruple) of setups:
* Domain portfolio
# 'Confidential' server - donation website, internal wikis, email. Either stick with existing VPS fully migrated to WMUK ownership, or new VPS.
# 'Community' server - WMUK projects (QRPedia etc), tools that don't fit in on the toolserver or Wikimedia Labs. Could go with either VPS or dedicated server. Would need logins for individuals, an SVN, etc.
# 'Mirror' server - needs to have large disk and bandwidth capacity. Needs to be a dedicated server.
# 'Backup' server - not sure whether this is needed or not, but we need somewhere off the main servers to keep backups.
 
=== SSL certificates ===
 
=== Domain portfolio ===
* Currently renewed on one or two year terms: should increase to longer terms for extra stability
* What to do about UK Wikimedia project domains?


== Contracts ==
== Contracts ==
=== Sysadmin ===
=== Sysadmin ===
Skills needed:
* Sysadmin experience
* PHP (programming), MySQL (database)
* Experience with Mediawiki, CiviCRM, Wordpress
Tasks:
* Migrate projects to new servers as needed
* Maintain software, carrying out upgrades, reconfigurations and ensuring security
* Ensure regular backups, both online and offline
* Set up a CRM system for dealing with incoming emails
* Manage domain names, including renewal and subdomains
Would report to the Chief Exec for management purposes, would liaise with Mike Peel on the technical side.
Hourly rate - unsure what the norm is here. Suggest somewhere between £15-£20 per hour (probably an underestimate), with the expectation that they'd be working between 5 and 10 hours per week (will vary unpredictably over the course of the year). Hence would cost somewhere around £7k per year.
=== External security review ===


=== QRPedia development ===
=== QRPedia development ===
Things like:
# Multilingual user interface for the webpage?
# Stats tools
# Special features for partnership organisations?
=== Mediawiki development ===
Needs identification of Mediawiki projects to support.
=== Fundraising ===
Will become relevant in the run-up to the 2012-13 fundraiser, particularly during the testing period over the summer, and the actual fundraiser period.


== Partnerships ==
== Partnerships ==
=== Direct Debit solution ===
=== Direct Debit solution ===
* Using SmartDebit API. Integrate with CiviCRM.
* Partnership with others via [http://civicrm.org/mih#ukdd] - details at [http://wiki.civicrm.org/confluence/display/CRM/Direct+Debit+integration+%28UK%29+requirements+and+specification]


=== Gift Aid solution ===
=== Gift Aid solution ===
== Other relevant budgets ==
There are two budget lines relevant to the general issue of tech, but which aren't covered here:
* Toolserver grant
* Mass upload tool

Revision as of 00:14, 9 January 2012

Comment This is currently a draft being put together by Mike Peel. Please help improve it!

Status as of January 2012

Our websites and general online tech needs currently utilize a Virtual Private Server donated and managed by Mike Peel, as well as hosting provided by the Wikimedia Foundation. These needs are (hosted by WMUK unless otherwise stated):

  • Wikis
    • Public wiki: hosted by the WMF (tied in with Single User Login)
    • Private wikis (office and board, plus the largely-unused internal wiki)
    • Project wikis (britainloveswikipedia.org)
  • Wordpress for our blog
  • CiviCRM (with Joomla) for donations
  • DirectDebit form (custom software)
  • glamwiki.org
  • Email - POP/IMAP/SMTP, webmail

We also have service providers for domain names and SSL certificates.

Upcoming needs and opportunities

  • All of the above need maintaining and upgrading
  • The direct debit form needs moving from an iframe solution to an API solution, ideally directly integrated with CiviCRM
  • Gift Aid for CiviCRM
  • QRPedia
  • Hosting a mirror of the Wikimedia project dumps - see [1]
  • OTRS/other CRM system
  • More robust backup plan
  • Security review, and improvements based on the outcome of that review
  • Mediawiki development
  • 2012-13 fundraiser (does this fall under this budget?)
    • Banner design
    • Landing page design, including forms
  • wikipedia.org.uk portal (e.g. like http://www.wikipedia.pl/ )?
  • Expense system?
  • Community server?

General approach

Since our needs are so varied in terms of the skills and knowledge they require, and each need does not require a significant amount of work at the current time, our general approach is to hire contractors as needed, and to collaborate with partners where possible. Also offer bounties for development of specific non-urgent things?

Note that a single person could fulfill the needs of several contracts.

Infrastructure

Servers

The current solution of a VPS works well for our current purposes, but our needs will go beyond this. Suggest a trio (or quadruple) of setups:

  1. 'Confidential' server - donation website, internal wikis, email. Either stick with existing VPS fully migrated to WMUK ownership, or new VPS.
  2. 'Community' server - WMUK projects (QRPedia etc), tools that don't fit in on the toolserver or Wikimedia Labs. Could go with either VPS or dedicated server. Would need logins for individuals, an SVN, etc.
  3. 'Mirror' server - needs to have large disk and bandwidth capacity. Needs to be a dedicated server.
  4. 'Backup' server - not sure whether this is needed or not, but we need somewhere off the main servers to keep backups.

SSL certificates

Domain portfolio

  • Currently renewed on one or two year terms: should increase to longer terms for extra stability
  • What to do about UK Wikimedia project domains?

Contracts

Sysadmin

Skills needed:

  • Sysadmin experience
  • PHP (programming), MySQL (database)
  • Experience with Mediawiki, CiviCRM, Wordpress

Tasks:

  • Migrate projects to new servers as needed
  • Maintain software, carrying out upgrades, reconfigurations and ensuring security
  • Ensure regular backups, both online and offline
  • Set up a CRM system for dealing with incoming emails
  • Manage domain names, including renewal and subdomains

Would report to the Chief Exec for management purposes, would liaise with Mike Peel on the technical side.

Hourly rate - unsure what the norm is here. Suggest somewhere between £15-£20 per hour (probably an underestimate), with the expectation that they'd be working between 5 and 10 hours per week (will vary unpredictably over the course of the year). Hence would cost somewhere around £7k per year.

External security review

QRPedia development

Things like:

  1. Multilingual user interface for the webpage?
  2. Stats tools
  3. Special features for partnership organisations?

Mediawiki development

Needs identification of Mediawiki projects to support.

Fundraising

Will become relevant in the run-up to the 2012-13 fundraiser, particularly during the testing period over the summer, and the actual fundraiser period.

Partnerships

Direct Debit solution

  • Using SmartDebit API. Integrate with CiviCRM.
  • Partnership with others via [2] - details at [3]

Gift Aid solution

Other relevant budgets

There are two budget lines relevant to the general issue of tech, but which aren't covered here:

  • Toolserver grant
  • Mass upload tool
Retrieved from "https://dev.wikimedia.org.uk/w/index.php?title=2012_Developer_budget&oldid=18153"