Detailed list of responsibilities:
For a hight level overview see: http://pad.p2pu.org/p/community-responsibilities
Tech lead:
- Manage and work on the overall development of lernanta [Dirk]
- facilitate the tech call (+ sharing notes) and dev priorities section of the community call
- set roadmap and priorization work in collaboration with other staff members to work towards specific deadlines (and prepare small bullet report for board meeting)
- feature review / design
- communicate with product manage or feature owners to clarify specifications and feedback about new functionalities or changes being implemented
- ticket management
- coordinate project pipeline, lighthouse, trello, help desk
- maintain project roadmap on the github wiki (sync with trello project pipeline)
- Manage releases [Dirk]
- set up pre-release demos on alpha.p2pu.org for review and testing - nginx (web server), git, django, sqlite
- update code on production - git, django
- update database structure (move data around if necessary) - mysql admin
- less frequent apache configuration changes if necessary - apache
- less frequent celery setup changes -- celery: queue for sending notifications and other asyncronous tasks
- communication with dev and community - "people" skills
- monitor notifications from django logging
- perform small fixes in between releases if neccesary
- Manage open source contributions [Dirk]
- maintain list of possible easy contributions and other specific projects volunteers can work on
- merge pull requests from voluntary contributors -- git, django
- review code and give feedback
- mentoring new developers
- pin point areas of the source code relevant to new features and bugfixes
- propose alternative solutions for new features and bugfixes
- support localization
- collaborate with the translators of the 4 non-english languages currently supported
- maintain lernanta setup documentation on the github wiki (connected to intro to contributing to lernanta challenge at p2pu)
- hangout at #p2pu-dev on freenode and p2pu-dev mailing list
- Technical support for p2pu.org users, community, staff and partners
- provide technical user support for community members and general users of the site at help.p2pu.org
- done by someone else and only tech related issues defered to Dirk +1
- Everyone [Philipp, Bekka, Alison] does this! Answer things as they come in. Be proactive!
- John to make sure nothing gets missed (he's already reading everything) / we hand over to the new person we bring in as community manager
- We get a relatively small amount of support email, at most one or two a day.
- follow discussions in p2pu-community, p2pu-dev and other p2pu mailing lists [Dirk]
- everyone should do this - low traffic
- forward help desk issues to help@p2pu.org
- identify if reported problems are a bugs, a pending tasks on our todo list, or a new feature requests [Dirk]
- This should go to help.p2pu.org, tech will escalate to Dirk.
- use django admin site and shell in production for site admin tasks (e.g., manual creation of badges, deletion of courses, handling of spam, disabling user accounts) [Dirk]
- we should will try to remove tech requirements for admin tasks like deletion, spam, etc] +1+1
- automate this! you can make this easier
- extract ad hoc metrics / reports from the databases of p2pu.org, archive.p2pu.org and badges.p2pu.org for reports (usually working with Philipp or Learning Lead) [ someone trusted (ST) who knows SQL]
- for now or for specialized reports -> dirk (because he will know the database structure best)
- @zuzel: did you store the queries we've used in the past somewhere? we should keep an archive of those queries. i can probably update those to adjust for different reports, but need the basic queries.
- if we work on anonymization of data anyone can do the reports!
- future and for general research -> offer anonymized database dump feature as part of the University of Maryland project [Philipp owns]
- we already have queries to anonymize the database (see lighthouse ticket)
- @zuzel - can you add the link to the ticket here?
- this task usually takes time so it is good to get help (the data necessary tends to change and some communication between the people that needs the data is neccesary)
- I know SQL, but don't know the DB structure so well
- setup integration of p2pu.org with external trackings like google analytics, adwords, chartbeat, stats.p2pu.org (usually working with product manager)
- dirk for any dev work
- current -> does this happen on an ongoing basis or once off? -- ongoing basis at the moment (john probably has a better idea of were are we going in this area and how much work is upcoming)
- future -> should not require ongoing support / updates
- @john: could we document what's there / how we use it somewhere?
- create recipient lists for surveys and other global notifications -- django shell or mysql to create .csv file with the contacts [ST who knows SQL]
- dirk
- all users or sometimes the users who had -- will check if there was some ticket for one of this and i saved the query there (i maybe did it on the django shell not sql)
- serve as technical contact for partners [Dirk]
- openbadges
- participate in open badges mailing list
- maintain compatibility of django-obi and lernana with the obi
- System administration
- administrates, maintains and monitors overall status of p2pu sites and services
- linodes
- manage dns - not common (dirk/john)
- os upgrades - ubuntu (andre truter)
- linode resize (andre truter)
- backups - (andre truter)
- mysql (andre truter)
- apache / nginx web servers (andre truter)
- ssl certificates (andre truter)
- setups daemons (e.g., celeryd, statsd)
- creation of new user accounts for ssh access (andre truter)
- monitor overall status and health of sites hosted by p2pu (set up pingdom, track responsiveness) [ ST, Dirk ]
- set up monitoring for dirk, john, philipp (andre?)
- 1st line support (andre truter)
- troubleshoot server problems (andre truter)
- setup new sites and services (andre truter)
- production linode (andre truter)
- p2pu.org
- archive.p2pu.org
- delete accounts given requests from users
- badges.p2pu.org
- dev linode (dirk)
- pad.p2pu.org
- use etherpad-lite rest api to setup protected pads
- question: what are protected pads? how can i set one up?
- recover corrupted pads
- stats linode (john)
- services and sites hosted elsewhere (usually only done on onboarding of staff/contributors)
- google apps (john)
- create new accounts or groups
- give access to calendars and other google based services
- maintain general passwords/credentials doc [Anyone creating new accounts and with access to the doc should work on this]
- mailman (osuosl / john) and google groups mailing lists (john)
- authorize new members and discard spam
- request creation of new mailing lists to support.osuosl.org
- sendgrid (john) and mailchimp (bekka)
- create and send news letters given text for the notification and recipient list
- monitor bounces list (clean list from time to time)
- setup subscriptions forms for planned announcements
- blog.p2pu.org (stian)
- new wordpress accounts and permissions on the blog
- help.p2pu.org (john)
- new staff accounts and queues
- bbb.p2pu.org (osuosl / john)
- wiki.p2pu.org (philipp)
- authorize users requesting acces (bekka)
- consider saving money (would love to, but setting up our own wiki will not necessarily save money)
- freenode
- channel registration
- channel access management