elevated-access by stevepiercy · Pull Request #1600 · collective/icalendar

stevepiercy · 2026-07-26T11:16:28Z

Linked issue

n/a

Description

Documented how to join the icalendar team.

Checklist

I added a change log entry, following the instructions in Change log entry format.
I followed icalendar's Artificial intelligence policy and disclosed my Responsible AI use in my commit messages, if applicable.
I added or updated tests, if applicable.
I ran and ensured all tests pass locally by following Run tests.
I added or edited documentation as necessary, both as docstrings to be rendered in the API documentation and narrative documentation, following the Style guide.

WIP

Change log entry

github-actions · 2026-07-26T11:16:39Z

Profile summary:

GitHub user: stevepiercy
🟢 No concerns found with user's profile.
🟢 No concerns found with recent PR activity.
🟢 No concerns found with recent issue activity.

For a more detailed report, run `gh-profiler stevepiercy`.

Full profile

GitHub user: stevepiercy
🟢 No concerns found with user's profile.
   🟢 Account age: 17 years
   🟢 Profile information:
        name: Steve Piercy
        company: Steve Piercy - Website Builder
        blog: https://stevepiercy.com/
        location: Eugene, OR
        bio: Contributor to open source projects icalendar, Plone, Pyramid, and Deform. Everyday cyclist. Backyard farmer. Tree hugger. Living simply.
        mastodon: https://fosstodon.org/@stevepiercy
      Empty fields: email
      Orgs: plone, collective, Pylons, zopefoundation, knop-project, pycalendar

🟢 No concerns found with recent PR activity.
   14 PRs opened in the last 21 days.
      0 opened against repos the user owns.
      14 opened against repos in publicly associated orgs.
      0 opened against external repos.

🟢 No concerns found with recent issue activity.
   10 new issues opened in the last 21 days.
      0 opened in repos the user owns.
      8 opened in repos in publicly associated orgs.
      2 opened in external repos.

   🟢 0 external issues closed as NOT_PLANNED.
   🟢 0 external issues opened with the same title.

read-the-docs-community · 2026-07-26T11:17:42Z

Documentation build overview

📚 icalendar | 🛠️ Build #33807925 | 📁 Comparing b5d62d2 against latest (bf49097)

🔍 Preview build

8 files changed · + 1 added · ± 7 modified

+ Added

contribute/join-the-icalendar-team.html

± Modified

coveralls · 2026-07-26T11:21:07Z

coverage: 97.998%. remained the same — elevated-access into main

…tense

…and Triage

SashankBhamidi · 2026-07-27T05:57:34Z

Hi, I'll make some time to review this on Wednesday.

niccokunzmann

I added my thoughts and will have a look at the document again.

niccokunzmann · 2026-07-28T15:34:57Z

+
+Additionally, the icalendar team may contact you to encourage you to apply.
+
+The icalendar team recognizes that many individuals might not feel qualified to apply. Please rest assured that the worst that can happen is that the team will say "not yet, but here's a path you can follow to become qualified." The icalendar team wants to lift people up.


Can we say "we" instead of icalendar team?

The Microsoft Style Guide recommends avoiding "we" to focus the subject on the reader, not the product. However, that's a different context.

In this context, "We" may have a negative connotation of exclusivity, or "us, not you, the reader". If you're not a member of "we", then that can be a turn off. At other times, it may include the reader, making it unclear who "we" consists of. I could explicitly state "'We' in this document refers to the icalendar team." but I prefer to explicitly state the subject. It also reinforces that we're a team.

niccokunzmann · 2026-07-28T15:38:03Z

+
+The icalendar team will review your application, and collect relevant information for evaluation.
+
+If the icalendar team determines that you qualify for elevated access, then you'll receive an invitation through an email notification from GitHub to accept.


We have the maintenance page - we do not need to be a faceless team but people can know who is the team - should that be restructured then?

A few friendly faces with roles.
Hi, we are the team behind icalendar.
Join us... Here is how...

Then three tabs

Review Triage Maintain

What we really need is review work. We get a lot of contributions and this helps scale up. When you review, you show that you know how to be a team player, not just a coder. Issues need to be checked and PRs merged. Once you showed that you can review, we can trust you with your judgement on issues and PRs. You know how to cooperate. It is always good for the project to have a few maintainers.... ????

Maintenance is written primarily for people who are interested in maintaining icalendar. This page's purpose is to describe how to join the icalendar team. Let's not mix their purposes.

I could add a section about who are members of the icalendar team, which coincidentally are those people listed on Maintenance.

For the tabs, Review can be done by anyone with a GitHub account via Read access. Maintainers is outside the scope of this PR, and needs a separate discussion about who may become one. I focused on Triage and getting people to join the icalendar team. In another PR, we could amend this page with how to be promoted to Maintainer, once we determine those qualifications.

Added a Members section in b7dd62a

I should remark that GitHub has shitty permission management for FOSS organizations. Access may be granted on the entire organization and all its repos, but not a singular repo. Instead we must use direct individual access.

We can also create an organization team, such as icalendar-triage or icalendar-maintainers, and add members to each team, but that won't change their individual access. It's only practical use is to tag a team or request a review from a team, such as @icalendar-maintainers`, which would send a notification to its members.

niccokunzmann · 2026-07-28T15:38:57Z

+The icalendar team reviews pull requests and issues for quality, makes releases to PyPI, and protects and promotes the icalendar community.
+To familiarize yourself with the icalendar community, read :doc:`index`.
+
+To encourage collaboration and community, the icalendar team is actively seeking contributors who are interested in elevated access to icalendar to help review and triage issues and pull requests.


I would say we are seeking people who are interested in doing the work. I do not really want those who seek the access as primary motivation.

Done in 94d6c2c

stevepiercy added 2 commits July 20, 2026 01:44

Add Join the icalendar team guide

de77c6f

WIP

Document how to join the icalendar team

12415bb

Change log entry

stevepiercy requested a review from niccokunzmann as a code owner July 26, 2026 11:16

stevepiercy requested review from SashankBhamidi and angatha July 26, 2026 11:17

Vale

eac25fb

stevepiercy added 3 commits July 26, 2026 13:21

Change verb tense for consistency, as "traiges" is not really a verb …

56fee96

…tense

Merge branch 'main' into elevated-access

cfa6e62

Explicitly list elevated access permissions differences between Read …

efb669c

…and Triage

Merge branch 'main' into elevated-access

386fbeb

niccokunzmann requested changes Jul 28, 2026

View reviewed changes

stevepiercy added 3 commits July 29, 2026 03:26

Replace elevated access with apply phrasing

94d6c2c

Add Members section and add a heading Apply

b7dd62a

Merge branch 'main' into elevated-access

b5d62d2

stevepiercy requested a review from niccokunzmann July 29, 2026 01:41


		Additionally, the icalendar team may contact you to encourage you to apply.

		The icalendar team recognizes that many individuals might not feel qualified to apply. Please rest assured that the worst that can happen is that the team will say "not yet, but here's a path you can follow to become qualified." The icalendar team wants to lift people up.


		The icalendar team will review your application, and collect relevant information for evaluation.

		If the icalendar team determines that you qualify for elevated access, then you'll receive an invitation through an email notification from GitHub to accept.

Uh oh!

Uh oh!

Conversation

stevepiercy commented Jul 26, 2026

Linked issue

Description

Checklist

Uh oh!

github-actions Bot commented Jul 26, 2026

Uh oh!

read-the-docs-community Bot commented Jul 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Documentation build overview

Uh oh!

coveralls commented Jul 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

SashankBhamidi commented Jul 27, 2026

Uh oh!

niccokunzmann left a comment

Choose a reason for hiding this comment

Uh oh!

niccokunzmann Jul 28, 2026

Choose a reason for hiding this comment

Uh oh!

stevepiercy Jul 29, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

niccokunzmann Jul 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

stevepiercy Jul 29, 2026

Choose a reason for hiding this comment

Uh oh!

stevepiercy Jul 29, 2026

Choose a reason for hiding this comment

Uh oh!

stevepiercy Jul 29, 2026

Choose a reason for hiding this comment

Uh oh!

niccokunzmann Jul 28, 2026

Choose a reason for hiding this comment

Uh oh!

stevepiercy Jul 29, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

read-the-docs-community Bot commented Jul 26, 2026 •

edited

Loading

coveralls commented Jul 26, 2026 •

edited

Loading

niccokunzmann Jul 28, 2026 •

edited

Loading