Leith Lives is a non-profit, collaborative community project. In alignment with the principles of platform cooperativism, it is run for the benefit of and collectively owned by member organisations.
To future proof the project as much as possible and ensure the archive can be maintained, the intention is for Leith Lives to run as a voluntary project, with running costs in terms of both time and expenses kept as low as possible and to ensure the project doesn’t rely on any one person or group of people, central systems have been designed to be as lightweight, transparent, and flexible as possible.
Working practices will evolve based on participants, areas of focus and preferred ways of working. Suggestions are always appreciated! The diagram provides an overview of current thinking.
The website is built on open source software – Drupal 7 and Bootstrap, which are both widely used. Standard online systems are used to provide non-hierarchical project communications and to support intermittent participation. The website itself does need regular checking and some maintenance by someone with a knowledge of Drupal, say half an hour per week (or more expensive hosting with built in support).
Email and file storage
G Suite is currently used to provide email and file storage. Emails are forwarded volunteer team, and responded to by the person and/or people likely to have the best response and/or most availability at the time of receipt. Volunteers use their own email address to respond, reducing the need for an official position and maintaining transparency. All replies are copied to back to admin@LeithLives.org for info and to maintain an audit trail.
Social media and collaborative project management
Once set up, social media and online project management platforms such as Trello, Bitrix24 and Loomio, need little or no central maintenance. Contributions to all only need to be made when there is sufficient interest or benefit to those involved.
All Leith Lives account details (including domain name) are known to several project participants, to be passed on as and when necessary. Hosting is on a shared server so account details cannot be made generally available, but regular backups stored in accessible locations make the site highly portable.