Project assets

From diaspora* project wiki
Revision as of 16:26, 27 May 2021 by Jhass (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

By project assets we mean anything officially belonging to the Diaspora Project. This should not be confused with being owned in a legally binding way, but something that is recognized as being used officially by and for the project. These kind of assets should be recognized and documented, including the names of the key community persons who hold the keys. If possible, keys to project assets should be distributed to several key project members.

The purpose of this page is to keep information on who to contact in the event that some administrative things need to be done to a critical asset for the project.

List of assets

Please help keep this list up to date. Note however that pods are not project assets, they are run by individuals community members or organizations. Also it should be kept in mind that this page should only contain officially recognized assets that can be said to "belong" to the community. So if someone is running a blog, statistics or service that doesn't fall under Diaspora Project governance - it is not a project resource.


Domain name Usage Legal owner DNS administration Project site, wiki, Discourse, ... Dennis Schubert Dennis Schubert, Jonne Haß, Steffen van Bergerem Obsolete, kept for parking


Hostname/Alias Usage Physical location Owner Administative access For hosting the site, wiki, Discourse, project mail domains, ... Equinix Datacenter, Munich, Germany Dennis Schubert Dennis Schubert, Jonne Haß, Steffen van Bergerem Used to run the distribution lists Dennis Schubert - adding more admins not possible due to technical limitations. diaspora* HQ pod Hetzner Datacenter, Falkenstein, Germany Benjamin Neff Benjamin Neff, Dennis Schubert, Jonne Haß, Steffen van Bergerem

Code repositories

All code is managed on GitHub. Different parts of the project have different people responsible for it.

GitHub team Responsibility Members
Owners Managing access to GitHub Dennis Schubert, Florian Staudacher, Jonne Haß, Steffen van Bergerem
Core team Push access to all repositories, including the main code Benjamin Neff, Dennis Schubert, Florian Staudacher, Jonne Haß, Steffen van Bergerem
Federation team People responsible for the federation implementation Benjamin Neff
Others Various people are members of the GitHub org to manage issues, assign people and help out in other ways. Check GitHub for a full list of people who are member of the org.

Tools and Services

Name Description Managers
Discourse Discussions, project decisions, and support. See the list of core team members and the list of community members with moderation privileges.
Gemnasium Alerts for security-critical Gem updates Jonne Haß
Travis Continuous integration All GitHub core team members
WebTranslateIt Translation management Benjamin Neff, Dennis Schubert, Jonne Haß, Waithamai

Social Media

Platform Managed by
diaspora* HQ Core team, Flaburgan, Goob, Lukas Zauberstuhl
Facebook Flaburgan, Sean Tilley
Google+ Jason Robinson, Sean Tilley
Twitter Dennis Schubert, Flaburgan, Jason Robinson, Sean Tilley
Vimeo Jason Robinson, Augier


All official channels are hosted by Libera Chat, there's secondary channels on Freenode.

Official, English-speaking project channels

Name Founder access Successors and ACL modification
#diaspora-* (managed via the project registration) All diaspora-related channels are managed via a project registration Group. Primary contact: Jonne Haß, Secondary group contacts: Benjamin Neff, Waithamai
#diaspora Waithamai Dennis Schubert, Benjamin Neff, Jonne Haß

Funds and donations

Description Managing access
BountySource Dennis Schubert, Flaburgan, Jonne Haß
Donations via PayPal through the FSSN Please email for funding requests or other questions.


Please contact the listed owner if you want to have access to a given product.

Name Owner contact