week2

ossd-s24 · Feb 4, 2024 · 8a5d86c · 8a5d86c
1 parent d619590
commit 8a5d86c
Show file tree

Hide file tree

Showing 6 changed files with 55 additions and 26 deletions.
diff --git a/.idea/modules.xml b/.idea/modules.xml
diff --git a/.idea/vcs.xml b/.idea/vcs.xml
diff --git a/.idea/week2.iml b/.idea/week2.iml
diff --git a/.idea/workspace.xml b/.idea/workspace.xml
diff --git a/_posts/2023-02-05-week02.md b/_posts/2023-02-05-week02.md
diff --git a/_posts/2024-02-04-week02.md b/_posts/2024-02-04-week02.md
@@ -0,0 +1,9 @@
+---
+layout: post
+title: Week 2
+---
+
+
+I believe the Code of Conduct represents a consensus, providing everyone with a sense of safety because projects that utilize a Code of Conduct allow contributors to operate within an environment and set of rules they are familiar with. Not using a Code of Conduct can amplify their concerns. These concerns often cover many aspects, such as whether their contributions will be accepted (due to unknown standards of acceptance), and whether their contributions meet the requirements, among other issues. Personally, I don’t necessarily think that projects without a Code of Conduct should not receive contributions. It depends. If I can see a record of past accepted contributions and I plan to make a similar contribution, then I would work on this. But if not, I would choose to stay away from the project.
+
+Regarding the Code of Conduct, since each project has different specifics, it's difficult to standardize the Code of Conduct. And rules like respecting others cannot be enforced through code, at least not currently,  things like insulting images and language can only be identified by human for now. Perhaps in the future, with more advanced technology, enforcing the Code of Conduct through AI might become possible.