On 06/01/2016 05:23 PM, Brian Proffitt wrote:
Not sure about number of people, but there should be at least one person assigned as "caretaker" at all times, and then each channel would have their own policy to figure out who else has moderator/poster status. This should be very small scale. A database like rattic should store the passwords and then assign each user only the passwords to which they are authorized. The trick here is a universal policy for the "caretaker" Who is it? How are transitions handled? These are really governance questions that have to be answered in case someone leaves the project(s). BKP
Sorry, lost track of this email chain until now… would it be possible to have multiple caretakers? I feel like it might be a good thing to have in place long-term if there were two to three caretakers set up to manage these.
We could create a ticket and put some ideas to a vote if that would help move this forward in terms of deciding on a policy.
Brian Proffitt 574-383-9BKP Twitter: TheTechScribe Skype: LinuxScribe www.proffitt.org <http://www.proffitt.org> On Wed, Jun 1, 2016 at 3:19 PM, Justin W. Flory <jflory7@xxxxxxxxx <mailto:jflory7@xxxxxxxxx>> wrote: Hi all, A while back, we were brainstorming ideas for password storage and distribution for things like the social media accounts and possibly other items later on. When the topic was brought up at an Infrastructure meeting, a few ideas were tossed around, but in order to find a solution that works best for us, we need to come up with a few basic requirements for what we need out of a password management solution. Some of the questions that would be helpful to devise a solution for this dilemma: * How many people will need access to the passwords? * How much data would be stored (e.g. how many passwords, for what services, is it small-scale or large-scale, etc.)? Anything else you might think of as useful would be great to add in so we can come back to the Infra team with more specific requirements. Thanks all! -- Cheers, Justin W. Flory jflory7@xxxxxxxxx <mailto:jflory7@xxxxxxxxx>
-- Cheers, Justin W. Flory jflory7@xxxxxxxxx
Attachment:
signature.asc
Description: OpenPGP digital signature
-- Fedora Marketing mailing list marketing@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/marketing@xxxxxxxxxxxxxxxxxxxxxxx
