Plone Admin -Team

Manage servers, software, and online (SAAS) services in support of the Plone community.

Purpose

We manage access and uptime of services like the different websites, DNS registration, e-mail services, uptime monitoring, GitHub account/group management, the CI-CD Jenkins setup, and the community discussion forum.

We also manage/configure external services, the provisioning of our virtual servers at different cloud hosting provider and respond to security alerts/announcements when they concern any of the (non Plone) software the Plone Foundation uses on its servers. 

We use tools like configuration management (Ansible) and centralised password management.  Most of the Team members have a background or affinity with system administration, devops, technical Project Management and Plone Development.

Active Team Members

Contact

Open issues at Plone Admin-Team repository on Github

Email admins

Activities

The Admin -team tries to have montly to quarterly meetings where we discuss new projects, but most of our activitis are 'incident' or request driven when the servers and services operate smoothly.

When there are bigger issues/projects that need more planning, like a new service or a mahor upgrade/migration of a service, the Admin-team can and will ask other experienced members in the Plone community and start a public discussion to community and rally community members to help.

Activities are coordinated through meetings, e-mail and tickets submitted with a mention of @plone/admin-team.

How to Join / Team Membership process

Please send an email to admins <at> plone.org and tell us a bit more about yourself, what your experience is and how you can help the sysadmin team of the Plone Community.

Profile of an admin-team member:

  • Commitment to the Plone project
  • Affinity with system administration
  • Handle the complex systems that comprise the Plone websites/services and development environment like GitHub en other SAAS services
  • Communicative skills to handle with internal (community) and external (service provider) requests
  • Completed and signed the core contributor agreement. This gives access to push to the Plone repository and provides protection against intellectual property ownership issues
  • Approx. 8-16 hours a month available to look after our infrastructure/software, depending on your knowledge, skills and available (standby) time

There's not an official member limit on the admin-team that needs to be strictly enforced. We need enough people 'on watch' so that at least someone has time to respond and look into issues/incident/security issues that come in.