Skip to content

Conversation

@henrybear327
Copy link
Collaborator

Adding code of conduct according to Swisscom's FOSS guideline

@henrybear327 henrybear327 self-assigned this Sep 5, 2024
@henrybear327
Copy link
Collaborator Author

@ashanvbs @jstudler do you have an idea what to use for [INSERT CONTACT METHOD]? :)

@henrybear327 henrybear327 marked this pull request as draft September 5, 2024 07:33
@jstudler
Copy link
Collaborator

jstudler commented Sep 5, 2024

@ashanvbs @jstudler do you have an idea what to use for [INSERT CONTACT METHOD]? :)

So either we link the GitHub profiles of some of us that have a contact method listed or abuse@swisscom.com?

@henrybear327
Copy link
Collaborator Author

Given that we are maintaining it under NetBox Org instead of under the Swisscom org now, maybe it could be either you or Ashan? What do you think?

@henrybear327 henrybear327 force-pushed the docs/add_code_of_conduct branch 3 times, most recently from 64f28db to 365b6f8 Compare September 9, 2024 15:09
@henrybear327
Copy link
Collaborator Author

@ashanvbs @jstudler do you have an idea what to use for [INSERT CONTACT METHOD]? :)

So either we link the GitHub profiles of some of us that have a contact method listed or abuse@swisscom.com?

On second thought, it might be easier to use abuse@swisscom.com, as GitHub accounts don't come with a direct communication channel.

WDYT @jstudler ?

@henrybear327 henrybear327 force-pushed the docs/add_code_of_conduct branch from 365b6f8 to 3fda0fb Compare September 13, 2024 11:20
@henrybear327 henrybear327 marked this pull request as ready for review September 13, 2024 11:20
@ashanvbs
Copy link

Given that we are maintaining it under NetBox Org instead of under the Swisscom org now, maybe it could be either you or Ashan? What do you think?

Yeah I'm in favour of adding abuse@swisscom.com. We can as well ask compliance team what we've used on other projects.

@henrybear327 henrybear327 force-pushed the docs/add_code_of_conduct branch from 3fda0fb to 1f9fa4c Compare September 17, 2024 08:20
@henrybear327
Copy link
Collaborator Author

Based on the reply from the compliance team, we should probably put the maintainer's email.
@jstudler @ashanvbs can I use your email?

Thanks

@jstudler
Copy link
Collaborator

jstudler commented Oct 1, 2024

Based on the reply from the compliance team, we should probably put the maintainer's email. @jstudler @ashanvbs can I use your email?

Thanks

I cannot find this statement in the thread. I'm still in favor of abuse@swisscom.com. If we need to change it later, we can always do that.

@henrybear327
Copy link
Collaborator Author

Based on the reply from the compliance team, we should probably put the maintainer's email. @jstudler @ashanvbs can I use your email?
Thanks

I cannot find this statement in the thread. I'm still in favor of abuse@swisscom.com. If we need to change it later, we can always do that.

Email forwarded to you (sorry that I missed this).

Let's stick with abuse@swisscom.com :)

@henrybear327 henrybear327 force-pushed the docs/add_code_of_conduct branch from 1f9fa4c to 3677171 Compare October 1, 2024 11:35
@henrybear327 henrybear327 requested review from jstudler and removed request for ashanvbs and jstudler October 1, 2024 11:35
@henrybear327 henrybear327 force-pushed the docs/add_code_of_conduct branch from 3677171 to 868a40c Compare October 1, 2024 11:36
@henrybear327 henrybear327 force-pushed the docs/add_code_of_conduct branch from 868a40c to 4558f64 Compare October 1, 2024 13:37
@henrybear327 henrybear327 merged commit 1e30330 into main Oct 1, 2024
5 checks passed
@henrybear327 henrybear327 deleted the docs/add_code_of_conduct branch October 1, 2024 15:07
vaishutin pushed a commit to vaishutin/netbox-operator that referenced this pull request Aug 17, 2025
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

Successfully merging this pull request may close these issues.

4 participants