Hi all, I would like to start a discussion about documenting the ownership, administrative access and recovery arrangements for the official Apache CloudStack accounts and online services.
Before anything else, I would like to thank Ivet for the exceptional amount of work she has done over the years around CloudStack marketing, conference organisation, social media and general project promotion. A very large part of CloudStack’s public visibility exists because of her continued effort, together with the colleagues who have supported this work. The quality, consistency and reach of the project’s marketing have improved significantly, and this work has brought a lot of value to the whole community. My suggestion is not intended to change the current coordination of these activities or to interfere with how content is prepared and published. I think the people already doing this work should continue coordinating the style, branding, scheduling and quality of the content. At the same time, I believe it would be useful for the project to maintain a clear inventory of all official accounts and services, including, for example: - YouTube; - LinkedIn; - X/Twitter; - Facebook, if still used; - Google accounts, Forms and spreadsheets used for the CCC CFP; - conference registration, mailing and sponsorship systems; - shared document folders; - and any other official CloudStack community or conference services. For each account or service, it would be useful to document: - who owns or administers it; - who currently has administrative access; - whether it is connected to a personal, company-owned or project-controlled account; - what recovery arrangements exist; - and how access can be restored if the main administrator is unavailable. I am not suggesting that passwords or recovery information should be shared publicly or widely. Where a platform supports multiple administrators, a small agreed group of trusted community members could have access. Where credentials must be stored, we could agree on an appropriate secure and project-controlled method. This would not change the current coordination of marketing activities or mean that people should publish content independently. I would still expect new videos, posts or campaigns to be coordinated with the people managing the channels, so that we keep a consistent style, branding and quality. The purpose would simply be continuity, transparency and shared project ownership, so that official CloudStack accounts and services do not depend entirely on one person, one personal account or one company. This would also make it easier for other community members to contribute content while still coordinating properly with the people managing the relevant channels. Would it make sense to create a simple inventory and agree on a small group responsible for administrative and recovery access? Thanks again to Ivet and everyone else who has maintained these channels and supported CloudStack’s public presence over the years. Regards, Andrija
