add code of conduct #4

New Issue

wanderer · 2020-10-16T11:18:23+02:00

wanderer commented

2020-10-16 11:18:23 +02:00

for people to play nice, to know what playing nice means and also clearly know what comes next when they don't

for people to play nice, to know what playing nice *means* and also clearly know what comes next when they don't

👍 1

wanderer self-assigned this 2020-10-16 11:18:23 +02:00

dalahast was assigned by wanderer

2020-10-16 11:18:23 +02:00

wanderer added this to the General project 2020-10-22 11:14:18 +02:00

kreyren commented

2020-11-01 11:37:03 +01:00

What is the status of this? Happy to contribute

wanderer commented

2020-11-01 15:29:50 +01:00

@kreyren

What is the status of this? Happy to contribute

Contributions are welcome.
I was imagining something like the one that notabug folks have..

@kreyren >What is the status of this? Happy to contribute Contributions are welcome. I was imagining something like the one that notabug folks have..

wanderer commented

2020-11-01 16:01:11 +01:00

https://notabug.org/tos
@kreyren see this

but - atm this would either mean creating a fork of gitea to implement a special route just for tos or having a static tos site (I am in favour of this more than the former).
that would also be better off without git.dotya.ml css (at least until we have a fixed default theme) and stuff as it would have to be statically specified (no templating functionality for static sites), too, at which point no style at all provides for a cleaner ux imo.

https://notabug.org/tos @kreyren see this but - atm this would either mean creating a fork of gitea to implement a special route just for tos or having a static tos site (I am in favour of this more than the former). that would also be better off without git.dotya.ml css (at least until we have a fixed default theme) and stuff as it would have to be statically specified (no templating functionality for static sites), too, at which point no style at all provides for a cleaner ux imo.

wanderer referenced this issue

2020-11-01 16:06:27 +01:00

Handling of minors in terms of processing functional data #14

wanderer added a new dependency 2020-11-01 16:10:02 +01:00

#14 Handling of minors in terms of processing functional data

kreyren commented

2020-11-01 16:24:05 +01:00

i don't think TOS is in the best interest of the service Code Of Conduct is better in which case we can fork linux~

wanderer commented

2020-11-01 16:30:48 +01:00

i don't think TOS is in the best interest of the service Code Of Conduct is better in which case we can fork linux~

why would TOS not be in the best interest of the service?

> i don't think TOS is in the best interest of the service Code Of Conduct is better in which case we can fork linux~ why would TOS not be in the best interest of the service?

kreyren commented

2020-11-01 16:32:35 +01:00

@wanderer I find TOS being too restricting and requesting the service to do policing to enforce it compared to Code of Conduct that mostly works on the honor system that based on my experience is more apropriate for libre open source.

wanderer commented

2020-11-01 20:59:09 +01:00

@wanderer I find TOS being too restricting and requesting the service to do policing to enforce it compared to Code of Conduct that mostly works on the honor system that based on my experience is more apropriate for libre open source.

what is the difference in practice though? I guess we'll still have to do policing if somebody decides to not honor the CoC... the only difference then would be the more likable name.. but as this issue was even open with CoC in the name, I agree it should be called that. maybe the above mentioned tos could be edited where relevant to fit our needs.

> @wanderer I find TOS being too restricting and requesting the service to do policing to enforce it compared to Code of Conduct that mostly works on the honor system that based on my experience is more apropriate for libre open source. what is the difference in practice though? I guess we'll still have to do policing if somebody decides to not *honor* the CoC... the only difference then would be the more likable name.. but as this issue was even open with CoC in the name, I agree it should be called that. maybe the above mentioned tos could be edited where relevant to fit our needs.

kreyren commented

2020-11-01 21:48:14 +01:00

what is the difference in practice though? @wanderer

From my experience:

ToS is enforced by the service
CoC is enforced by the community with the service

> what is the difference in practice though? @wanderer From my experience: ToS is enforced by the service CoC is enforced by the community with the service

wanderer added this to the v1.0 milestone 2020-11-17 20:43:04 +01:00

wanderer referenced this issue from dotya.ml/hostmaster

2021-07-20 00:44:37 +02:00

dotya.ml in spamhaus.org's zen spamlist #1

Sign in to join this conversation.