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] - marksweb #17

Closed
2 tasks done
marksweb opened this issue May 24, 2024 · 4 comments
Closed
2 tasks done

🏗️ [ADMIN] - marksweb #17

marksweb opened this issue May 24, 2024 · 4 comments

Comments

@marksweb
Copy link

DSF member

  • I am a DSF member

Why do you want to join?

I like helping people out with the knowledge I have now, because back when I was getting started it was hard to find that know-how.

Please tell us about your packaging experience?

I've been releasing packages for a few years. I especially like it when you get GHA to do all the hard work for you & integrate a release process using GH releases.

Please tell us about your GitHub Actions experience?

I try to get GHA to do as much as possible to help maintain repos. I've never done anything massively complicated, but welcoming new members, running QA/test suites and then releasing to (test.)pypi are all the usual things I'll make sure are in place.

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

I don't see an end in sight to my python/django days yet.

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

Hi Mark, would you be willing to be on the Security team for the org? It would be managed via a Google Group, where upon a report occurring, 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.

There would also be monthly or quarterly summary reports via an email to the admin team to provide accountability. 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.

@marksweb
Copy link
Author

@tim-schilling Yeah that sounds good to me - something I'm used to already as well 👍🏼

@tim-schilling
Copy link
Member

Perfect, thank you! The next steps will be posted to that google group in the next month or so pending people's availability.

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