Changed to correct tags, if it's wrong, feel free to fix it.

This seems like a good use-case for our restricted repo policy.

@ppenloglou could I get you to review, agree, and acknowledge the following (full details on wiki):

• All owners and maintainers have GitLab 2fa enabled and are using strong passwords
• Private repositories are only for restricted information, not confidential information
• Accept the risks associated with private repositories, e.g.:
  • Configuration changes – Any repository owner may change the visibility of your repository
  • Forks – Anyone with the ability to fork your repo may change settings on their fork and expose information
  • Forge vulnerabilities – GitLab may have an unknown vulnerability that may leak information contained within or metadata about this repository

Can I ask why these cannot be public?

Hi everyone!

@taavi I work with the fundraising team and my main body of work is to produce HTML emails that we send out to donors. I save my work for posterity as part of the fr-email-templates repository. General public shouldn't be able to view these as it's sensitive information and can reveal insights into our fundraising strategies.

The other two repositories facilitate the work I mentioned above so again, general public shouldn't have access to these.

If it's possible, I'm asking for these repos to be viewable by any WMF employee, they shouldn't be exclusively private to me.

I agree with the following @thcipriani and confirm that I have 2FA enabled for GitLab.

• All owners and maintainers have GitLab 2fa enabled and are using strong passwords
• Private repositories are only for restricted information, not confidential information
• Accept the risks associated with private repositories, e.g.:
  • Configuration changes – Any repository owner may change the visibility of your repository
  • Forks – Anyone with the ability to fork your repo may change settings on their fork and expose information
  • Forge vulnerabilities – GitLab may have an unknown vulnerability that may leak information contained within or metadata about this repository

Thank you everyone!

Kind regards,
Panos

Why our fundraising strategies considered sensitive and have to be hidden from the community? This might lead to another enwiki RFC situation.

Hey @Ladsgroup , I want to address a misunderstanding regarding the privacy level of our fundraising strategies and email work. It has come to my attention that all of our work is publicly accessible, and there is no need to change the visibility of these repositories to private. I was misinformed regarding the above. Please disregard this request.

In T345215#9137523, @ppenloglou wrote:

misunderstanding regarding the privacy level of our fundraising strategies and email work. It has come to my attention that all of our work is publicly accessible, and there is no need to change the visibility of these repositories to private

Thank you! I am so glad to see this correction. This very much helps reduce friction between foundation and community.