Enabling all maintainers to perform all maintenance tasks for Shouldly

[Joseph Musser]

@shouldly/core This is high priority for me given the docs site being down for months (#860). Given that no single person has guaranteed time to resolve problems in a timely fashion, I would like every maintainer to have ability to:

• Publish and edit metadata for NuGet packages
  ✔️ @josephwoodward is a package owner
  ✔️ @slang25 is a package owner
  ✔️ @SimonCropp is a package owner
  ❌ I am not a package owner
  ❌ @JakeGinnivan is a package owner but has stepped back as an active maintainer
  ❌ @xerxesb is a package owner but is not known to me as a current Shouldly maintainer
  ❌ @ShouldlyAutomator is a package owner but I'm not sure it's currently used
  ❓ Is it beneficial to create a NuGet Shouldly org? NUnit does this, for instance.

• Renew and configure the shouldly.org domain
  ✔ I can do this.
  ❌ No one else can. I'd like to transfer this domain out of my personal Namecheap account.
  ❓ Should we set up a Namecheap 'Shouldly' org account and share credentials for it?

• Configure the shouldly.org hosting (GitBook)
  ✔ I can do this through a temporary GitBook organization I set up
  ❌ No one else can. To fix this, we need to ask GitBook to reduce the org member count limitation on the free "OSS" tier, or we need to create an email-based account and share the credentials. ➡️ @josephwoodward needs to do this or let me do this by removing someone else so that I can get in.

• Spend money from our OpenCollective donation funds by submitting receipts (for things like the domain registration I paid for)
  ✔ @josephwoodward is an administrator and has successfully submitted a single expense (https://opencollective.com/shouldly/expenses/54287)
  ✔ I'm an administrator
  ❌ @SimonCropp is not an administrator
  ✔ @slang25 is an administrator
  ❓ Do want everyone to be able to pay for things like this without requiring a second maintainer to validate it?

• Store and share credentials in a way that is both secure and does not require one maintainer to contact another
  🔎 What solutions are out there?
  ❓ The .NET Foundation provides a secret management service (https://dotnetfoundation.org/projects/why-join). Would we have other reasons for wanting to join the .NET foundation?

• Receive reminders for things like domain renewals being required, so any maintainer can see what's happening and jump in
  🔎 What solutions are out there?

Action

1️⃣ Do you agree with the premise of enabling everyone to do everything? Please give opinions on all the ❌ and ❓ icons at least.

2️⃣ @josephwoodward, I believe we can't make use of the original Shouldly GitBook account until you in particular complete one of the alternatives at the ➡️ icon. Please let us know when you can get this done.

3️⃣ Anyone who is a current NuGet package owner, please make me a NuGet package owner for now. (https://www.nuget.org/profiles/jnm2)

After these three steps are completed, I will be unblocked and able to implement whatever consensus we reached.

[Simon Cropp]

Do you agree with the premise of enabling everyone to do everything

yes

Do want everyone to be able to pay for things like this without requiring a second maintainer to validate it?

yes. if people want to check if an expense is ok, they can take the initiative to ask

Anyone who is a current NuGet package owner, please make me a NuGet package owner for now.

u should have an invite

Is it beneficial to create a NuGet Shouldly org? NUnit does this, for instance

i have no experience with this. does that make it easier to use or mange users?

@JakeGinnivan @xerxesb @ShouldlyAutomator still having access

i dont mind people still having access. some people like the metrics of nuget counts associated with their name. i have also heard people say it can help with job applications. The one thing i would ask is that people all have 2FA enabled. The same for GitHub accounts

[Joseph Musser]

I've renewed the shouldly.org domain today for another year. (I initially registered the domain last year to resolve #860.) I submitted expenses to be reimbursed at https://opencollective.com/shouldly/expenses?period=2023-09-05T04%3A00%3A00.000Z→2023-09-06T03%3A59%3A59.999Z. Receipts are attached and privately visible to Shouldly team members.

I think I have the ability to approve the reimbursements myself and will do so after a few days if I think of it again, if no one is available to look at them.

[Stuart Lang]

Thanks @jnm2 🙂 If you add me to the team I'd be happy to approve

[Joseph Musser]

@slang25 Thanks so much! I added you, and I think you'll have an invitation email.

[Joseph Musser]

Thanks for approving! I just received the reimbursements.