Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🏗️ [ADMIN] - @carltongibson #12

Closed
2 tasks done
carltongibson opened this issue May 23, 2024 · 5 comments
Closed
2 tasks done

🏗️ [ADMIN] - @carltongibson #12

carltongibson opened this issue May 23, 2024 · 5 comments

Comments

@carltongibson
Copy link

carltongibson commented May 23, 2024

DSF member

  • I am a DSF member

Why do you want to join?

Enabling the community is the only ultimately stable approach. It’s the multiplier.

Please tell us about your packaging experience?

I’ve been a maintainer of packages in the Django ecosystem for a decade and more, including Django itself for a while there.

Please tell us about your GitHub Actions experience?

I’ve been using GHA extensively since they were introduced.

How long do you expect to be involved with Django Commons?

I’d expect involvement to wax and wane but, as with Django itself, more or less until the heat death of the universe.

Code of Conduct

  • I agree to follow Django Commons's Code of Conduct
@tim-schilling
Copy link
Member

Please see https://github.com/orgs/django-commons/discussions/19. I'm not sure if the tag actually pinged you.

@tim-schilling
Copy link
Member

Oh, and hi Carlton! Thank you for posting this.

@tim-schilling
Copy link
Member

Hi Carlton, would you be willing to be on the Code of Conduct and Security teams for the org? They'd both be managed via Google Groups.

For CoC, where upon a report occurring, we'd collect the details of the incident, discuss how to handle things, then come to an agreement on a path forward. At the conclusion of each report, we would send an email to the admin team and the CoC team with our decision (provides accountability and transparency).

For Security, upon a report, we'd collect the details of the incident, determine if it's a valid error, and facilitate coordination with the project maintainers to issue a fix.

As you can likely imagine, the involvement will be low until there's an incident.

Please let me know if this is something you'd be interested and available to do? We're looking at a 9-12 month cycle before we reassess team structures. Though you're free to step down at any point.

@carltongibson
Copy link
Author

@tim-schilling Happy on both counts ✅

@tim-schilling
Copy link
Member

Excellent, I think there was an issue adding you to a google group. I'll follow-up with you offline on how to resolve that. Marking this as completed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants