Skip to content

Commit f167f43

Browse files
committed
updated: coc
1 parent 09486b0 commit f167f43

File tree

4 files changed

+239
-183
lines changed

4 files changed

+239
-183
lines changed

src/components/Footer/Footer.jsx

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ const Footer = () => {
1818
window.open(url, "_blank");
1919
};
2020
return (
21-
<div className="footer" >
21+
<div className="footer">
2222
<div className="footer_top">
2323
<div className="footer_logo">
2424
<div className="footer_logo_first">
@@ -31,12 +31,13 @@ const Footer = () => {
3131
style={{ cursor: "pointer" }}
3232
onClick={() => openInNewWindow(footerData.instagram)}
3333
/>
34-
<LinkedinOutlined
34+
<LinkedinOutlined
3535
className="footer_logo_socials_icons2"
3636
style={{ cursor: "pointer" }}
3737
onClick={() => openInNewWindow(footerData.linkedin)}
3838
/>
39-
<YoutubeOutlined className="footer_logo_socials_icons3"
39+
<YoutubeOutlined
40+
className="footer_logo_socials_icons3"
4041
style={{ cursor: "pointer" }}
4142
onClick={() => openInNewWindow(footerData.youtube̦)}
4243
/>
@@ -45,12 +46,13 @@ const Footer = () => {
4546
style={{ cursor: "pointer" }}
4647
onClick={() => openInNewWindow(footerData.twitter)}
4748
/>
48-
4949
</div>
5050
<div className="footer_coc">
51-
<Link to="/coc">Code of Conduct</Link>
52-
<p className="footer_coc_email">Email us for more details</p>
53-
<a href="mailto: [email protected]" className="email_2">[email protected]</a>
51+
<Link to="/coc">Code of Conduct</Link>
52+
<p className="footer_coc_email">Email us for more details</p>
53+
<a href="mailto: [email protected]" className="email_2">
54+
55+
</a>
5456
</div>
5557
</div>
5658
<div className="footer_resources">

src/components/Footer/Footer.scss

Lines changed: 5 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -193,7 +193,6 @@
193193
justify-content: center;
194194
align-items: center;
195195
flex-direction: column;
196-
197196
}
198197

199198
.footer_bottom img {
@@ -217,19 +216,18 @@
217216
margin-top: 20px;
218217

219218
.footer_coc_email {
220-
color: #DCF2F1;
219+
color: #87a0f9;
221220
margin-top: 10px;
222221
margin-bottom: 10px;
223222
}
224223

225224
.email_2 {
226-
227-
228-
color: #DCF2F1;
229-
text-transform: lowercase;
225+
color: #ffffff;
226+
text-transform: lowercase;
227+
font-weight: 600;
230228
}
231229

232230
@media screen and (max-width: 560px) {
233231
font-size: 15px;
234232
}
235-
}
233+
}

src/pages/Coc/Coc.jsx

Lines changed: 164 additions & 108 deletions
Original file line numberDiff line numberDiff line change
@@ -1,110 +1,166 @@
1-
import React from 'react'
2-
import "./Coc.scss"
1+
import React from "react";
2+
import "./Coc.scss";
33
const Coc = () => {
4-
return (
5-
<section className='coc'>
6-
<h1 className='heading'>Code of Conduct</h1>
7-
<div>
8-
<p className='text__bold'>
9-
By participating in Winter Of Code, all participants agree to
10-
abide by this Code of Conduct. Failure to comply with this Code of Conduct may result in disqualification
11-
and expulsion from the event, and may also lead to legal action in severe cases.
12-
</p>
13-
<p className="coc__rules">
14-
<span className="text__bold">Respect: </span>
15-
All participants must respect each other's opinions, beliefs, and values.
16-
Discriminatory language or behavior will not be tolerated. This includes, but is not limited to, sexism,
17-
racism, homophobia, and ableism.
18-
</p>
19-
<p className="coc__rules">
20-
<span className="text__bold">Collaboration: </span>
21-
Participants should embrace collaboration and teamwork.
22-
Any attempts to sabotage or undermine other contributors' work will not be tolerated.
23-
</p>
24-
<p className="coc__rules">
25-
<span className="text__bold">Privacy: </span>
26-
Participants must respect the privacy of others. Any confidential information shared
27-
during the Winter of Code must not be disclosed
28-
without the express consent of the person or team that shared it.
29-
</p>
30-
<p className="coc__rules">
31-
<span className="text__bold">Professionalism: </span>
32-
Participants should conduct themselves in a professional manner throughout the Winter of Code.
33-
This includes dressing appropriately, refraining from using inappropriate language,
34-
and avoiding any behavior that would be considered unprofessional.
35-
</p>
36-
<p className="coc__rules">
37-
<span className="text__bold">Safety: </span>
38-
Participants should prioritize their safety and the safety
39-
of others throughout the Winter of Code. Any behavior that puts others in danger,
40-
including but not limited to physical violence or verbal threats, will not be tolerated
41-
</p>
42-
<p className="coc__rules">
43-
<span className="text__bold">Code of Conduct Violations: </span>
44-
Any participant who violates the Code of Conduct may be subject to disciplinary action,
45-
up to and including expulsion from the Winter of Code.
46-
All participants have the right to report any Code of Conduct violations to the event organizers.
47-
</p>
48-
<p className="coc__rules">
49-
<span className="text__bold">Inclusivity: </span>
50-
The Winter of Code should be inclusive to all individuals regardless of gender,
51-
ethnicity, race, religion, age, or any other characteristic.
52-
All participants should work towards creating a safe and welcoming environment for everyone involved.
53-
</p>
54-
<p className="coc__rules">
55-
<span className="text__bold">Intellectual Property: </span>
56-
Participants should respect the intellectual property rights of others. Any use of copyrighted
57-
or trademarked material must be properly attributed or cleared for use
58-
</p>
59-
<p className="coc__rules">
60-
<span className="text__bold">Compliance with Laws: </span>
61-
All participants must comply with all applicable laws and regulations throughout the Winter of Code.
62-
Any illegal activities will not be tolerated.
63-
</p>
64-
<p className="coc__rules">
65-
<span className="text__bold">Accountability: </span>
66-
All participants are accountable for their own actions and should take responsibility
67-
for any consequences that may arise from those actions.
68-
</p>
69-
</div>
70-
<h1 className='heading'>Reporting a Breach</h1>
71-
<div>
72-
<p>
73-
If you experience or witness a breach of the Winter of Code Code of Conduct,
74-
we encourage you to report it immediately. You can report it in the following ways:
75-
</p>
76-
<ul className='coc_list'>
77-
<li>
78-
<span className="text__bold">Speak with a member of the Winter of Code team: </span>
79-
<span>You can approach any member of the Winter of Code team and share your concerns with them.
80-
They will take appropriate action to address the situation. The team will be identifiable by Winter of Code official t-shirts,
81-
bearing the Winter of Code logo, along with a lanyard and identity card.</span>
82-
</li>
83-
<li>
84-
<span className="text__bold">Email the Winter of Code team: </span>
85-
<span>You can send an email to the official Winter of Code email address</span>
86-
<a href="mailto: [email protected]"> [email protected] </a><span> and describe the incident in detail.
87-
We will investigate the matter and take appropriate action.</span>
88-
</li>
89-
<li><span className="text__bold">Contact the following Winter of Code Representatives:</span>
90-
<span> If you prefer to tell us in person but the team is not near, call the lead organizers below:</span>
91-
<ul className="emails">
92-
<li>Debojit Saha: <a href="mailto:[email protected]">[email protected]</a></li>
93-
<li>Subhajit Hait: <a href="mailto:[email protected]">[email protected]</a></li>
94-
<li>Manish Kumar Barnwal: <a href="mailto:[email protected]">[email protected]</a></li>
95-
<li>Kajal Jaiswal: <a href="mailto:[email protected]">[email protected]</a></li>
96-
</ul>
97-
</li>
98-
</ul>
99-
<p><span>We take all reports of Code of Conduct breaches
100-
seriously and will take appropriate action to address the situation.</span>
101-
</p>
102-
<p><span>Winter of Code reserves the right to amend, make exceptions, or otherwise revise the policies either partially or fully.
103-
If you have any questions regarding the policies, please contact us at
104-
</span><a href="mailto: [email protected] "> [email protected] </a><span></span></p>
105-
</div>
106-
</section>
107-
)
108-
}
4+
return (
5+
<section className="coc">
6+
<h1 className="heading">Code of Conduct</h1>
7+
<div>
8+
<p className="text__bold">
9+
By participating in Winter Of Code, all participants agree to abide by
10+
this Code of Conduct. Failure to comply with this Code of Conduct may
11+
result in disqualification and expulsion from the event, and may also
12+
lead to legal action in severe cases.
13+
</p>
14+
<p className="coc__rules">
15+
<span className="text__bold">Respect: </span>
16+
All participants must respect each other's opinions, beliefs, and
17+
values. Discriminatory language or behavior will not be tolerated.
18+
This includes, but is not limited to, sexism, racism, homophobia, and
19+
ableism.
20+
</p>
21+
<p className="coc__rules">
22+
<span className="text__bold">Collaboration: </span>
23+
Participants should embrace collaboration and teamwork. Any attempts
24+
to sabotage or undermine other contributors' work will not be
25+
tolerated.
26+
</p>
27+
<p className="coc__rules">
28+
<span className="text__bold">Privacy: </span>
29+
Participants must respect the privacy of others. Any confidential
30+
information shared during the Winter of Code must not be disclosed
31+
without the express consent of the person or team that shared it.
32+
</p>
33+
<p className="coc__rules">
34+
<span className="text__bold">Professionalism: </span>
35+
Participants should conduct themselves in a professional manner
36+
throughout the Winter of Code. This includes dressing appropriately,
37+
refraining from using inappropriate language, and avoiding any
38+
behavior that would be considered unprofessional.
39+
</p>
40+
<p className="coc__rules">
41+
<span className="text__bold">Safety: </span>
42+
Participants should prioritize their safety and the safety of others
43+
throughout the Winter of Code. Any behavior that puts others in
44+
danger, including but not limited to physical violence or verbal
45+
threats, will not be tolerated
46+
</p>
47+
<p className="coc__rules">
48+
<span className="text__bold">Code of Conduct Violations: </span>
49+
Any participant who violates the Code of Conduct may be subject to
50+
disciplinary action, up to and including expulsion from the Winter of
51+
Code. All participants have the right to report any Code of Conduct
52+
violations to the event organizers.
53+
</p>
54+
<p className="coc__rules">
55+
<span className="text__bold">Inclusivity: </span>
56+
The Winter of Code should be inclusive to all individuals regardless
57+
of gender, ethnicity, race, religion, age, or any other
58+
characteristic. All participants should work towards creating a safe
59+
and welcoming environment for everyone involved.
60+
</p>
61+
<p className="coc__rules">
62+
<span className="text__bold">Intellectual Property: </span>
63+
Participants should respect the intellectual property rights of
64+
others. Any use of copyrighted or trademarked material must be
65+
properly attributed or cleared for use
66+
</p>
67+
<p className="coc__rules">
68+
<span className="text__bold">Compliance with Laws: </span>
69+
All participants must comply with all applicable laws and regulations
70+
throughout the Winter of Code. Any illegal activities will not be
71+
tolerated.
72+
</p>
73+
<p className="coc__rules">
74+
<span className="text__bold">Accountability: </span>
75+
All participants are accountable for their own actions and should take
76+
responsibility for any consequences that may arise from those actions.
77+
</p>
78+
</div>
79+
<h1 className="heading">Reporting a Breach</h1>
80+
<div>
81+
<p>
82+
If you experience or witness a breach of the Winter of Code Code of
83+
Conduct, we encourage you to report it immediately. You can report it
84+
in the following ways:
85+
</p>
86+
<ul className="coc_list">
87+
<li>
88+
<span className="text__bold">
89+
Speak with a member of the Winter of Code team:{" "}
90+
</span>
91+
<span>
92+
You can approach any member of the Winter of Code team and share
93+
your concerns with them. They will take appropriate action to
94+
address the situation. The team will be identifiable by Winter of
95+
Code official t-shirts, bearing the Winter of Code logo, along
96+
with a lanyard and identity card.
97+
</span>
98+
</li>
99+
<li>
100+
<span className="text__bold">Email the Winter of Code team: </span>
101+
<span>
102+
You can send an email to the official Winter of Code email address
103+
</span>
104+
<a href="mailto: [email protected]"> [email protected] </a>
105+
<span>
106+
{" "}
107+
and describe the incident in detail. We will investigate the
108+
matter and take appropriate action.
109+
</span>
110+
</li>
111+
<li>
112+
<span className="text__bold">
113+
Contact the following Winter of Code Representatives:
114+
</span>
115+
<span>
116+
{" "}
117+
If you prefer to tell us in person but the team is not near, call
118+
the lead organizers below:
119+
</span>
120+
<ul className="emails">
121+
<li>
122+
Souvik Pal:{" "}
123+
<a href="mailto:[email protected]">
124+
125+
</a>
126+
</li>
127+
<li>
128+
Subhajit Hait:{" "}
129+
<a href="mailto:[email protected]">
130+
131+
</a>
132+
</li>
133+
<li>
134+
Nikhil Mishra:{" "}
135+
136+
</li>
137+
<li>
138+
Debojit Saha:{" "}
139+
<a href="mailto:[email protected]">
140+
141+
</a>
142+
</li>
143+
</ul>
144+
</li>
145+
</ul>
146+
<p>
147+
<span>
148+
We take all reports of Code of Conduct breaches seriously and will
149+
take appropriate action to address the situation.
150+
</span>
151+
</p>
152+
<p>
153+
<span>
154+
Winter of Code reserves the right to amend, make exceptions, or
155+
otherwise revise the policies either partially or fully. If you have
156+
any questions regarding the policies, please contact us at
157+
</span>
158+
<a href="mailto: [email protected] "> [email protected] </a>
159+
<span></span>
160+
</p>
161+
</div>
162+
</section>
163+
);
164+
};
109165

110-
export default Coc
166+
export default Coc;

0 commit comments

Comments
 (0)