\n
\n );\n });\n}\n\n","import React from \"react\";\nimport {Link} from 'react-router-dom';\nimport Timeline from \"./Timeline\";\nimport NITKLogo from '../../assets/NITK_Logo_1.png'\n\nconst timeline = [\n { event: \"Deadline to submit project proposals by organizations in NITK. Submit by 6th October to get the project proposals reviewed!\", date: \"October 6\" },\n { event: \"List of selected projects released. Students start discussing project details with mentors\", date: \"October 10\" },\n { event: \"Students can start submitting project proposals\", date: \"October 12\" },\n { event: \"Last day for students to submit project proposals\", date: \"November 12\" },\n { event: \"List of selected students for projects released\", date: \"December 2\" },\n { event: \"Coding phase begins\", date: \"December 9\" },\n { event: \"Mid evaluation\", date: \"January 9\" },\n { event: \"Final evaluation\", date: \"February 9\" }\n]\n\nconst Home = () => {\n return (\n <>\n \n
\n \n
\n {timeline.event}
\n{timeline.date}
\n\n
\n \n
\n
\n 
NITK Winter of Code
\n Kickstart your open source journey
\n {/* View Projects */}\n {/* Apply as a mentor */}\n Apply as a mentee \n View Projects \n\n
Timeline
\n\n \n About NITK Winter of Code\n \n\n
\n \n );\n}\n","import React from \"react\";\n\n\n\nexport default function Guidelines() {\n return (\n <>\n Aim
\nNITK Winter of Code aims at helping students get started with open source projects that directly impact peoples' lives.
\nWinter of Code has a philosophy very similar to larger programs like GSoC and Outreachy. Winter of Code is designed to acclimatize people to the steps involved in taking up various projects in large organizations like VLC, Mozilla, and others through GSoC and other similar programs.
\nThe participants will learn how to prepare a project application, work in teams, understand the importance of effective communication, and most importantly, work with large codebases. They will also learn the intricate workflows and good coding practices.
\n\nProgram Overview
\nWinter of Code is a program organized by the Centre for Open-Source Software and Hardware (COSH) at NITK Surathkal with a focus on introducing the student developers across the world to open source software and hardware development. The students can work with projects proposed by the Technical clubs, Open Source Organizations and Faculty Members of NITK over the winter break. This program also plans to introduce to students the rigorous process of developing a project proposal similar to that of GSoC.
\nA team of students will act as an organizing committee for the Winter of Code. The organizing committee will ensure that the program is conducted smoothly and will also maintain a website for the event. The organizing committee is responsible for creating a basic filter for project proposals.
\nFor the first time in the year 2021, we have opened the NITK Winter of Code program for the students other than NITK to submit proposals and participate in this program. They will be mentored by the organizations from NITK Surathkal.
\n\nTarget Audience
\nAnyone who is interested in contributing to open source! There will be students from all years and so projects of varying difficulty are needed.
\n\nProjects
\nProjects of different levels of difficulty, catering to different skill sets and expertise, will be available. The projects will cover different domains, as much as possible. The projects can be proposed by students (Bachelors, Masters and Ph.D.), faculty members, administrative offices (for example, HODs, Chairman, Deans, Deputy Director and Director), and by the various clubs at NITK willing to mentor students. The projects will be accepted by the organizing committee based on their merit and feasibility for the duration of the Winter of Code program. New projects, as well as projects with an existing codebase, are allowed.
\nMentors must submit projects which can be worked on for a minimum period of 8 weeks. Each project must have 2 mentors. If an organization (any club) proposes projects, the organization must have an organization coordinator. Projects should be divided into small tasks/issues. The mentors should also include some tasks to judge the candidate prior to selecting them for the progra,. The mentors are free to conduct any kind of evaluation (interviews, patch requirements, etc) required to select the candidates before the deadline.
\nThe students can apply to projects either by filling a Google form or completing a small task, which is at the discretion of the mentors. A student can apply to a maximum of 2 projects.
\n\nIncentives:
\n- \n
- Working/building innovating, exciting and positively impacting projects during their winter! \n
- Hands-on experience with open source and exposure to collaborativie ways of working! \n
- Understanding how global programs like Google Summer of Code work! \n
- An amazing opportunity to utilize the winter holidays through an impactful project \n
- Certificate issued by COSH NITK at the end of completion, both for mentors and students (Mentors can decide if students are eligible for certificates) \n
\n \n Guidelines for participating entities\n \n\n
\n
\n \n );\n}\n","import React from \"react\";\nimport { Link } from \"react-router-dom\";\nimport styled from \"styled-components\";\nimport logo from \"../../assets/logo-min.png\";\n\nconst Brand = () => {\n return Contributors/Mentees
\nTo participate in Winter of Code NITK 2023, mentees/contributors are required to adhere to the following guidelines for the smooth conduction of the program.
\nApplication
\n \n- \n
- Any student, currently enrolled in an accredited institute, willing to contribute to open source is eligible to apply as a contributor to this Program. \n
- The mentee must agree to the guidelines applicable for mentees/contributors under the NITK Winter of Code. The mentee must submit the Google form shared by the NITK Winter of Code organizing committee to be considered eligible for applying to organizations. \n
- The Google form for organizations/mentors (a.k.a, Contributor/Mentee Application) must be submitted by the mentee available on the Program Website during the application period for organizations/mentors described in the Program Timeline. \n
- The Google form for organizations/mentors must be submitted by by mentees for the project(s) they are applying to. A mentee may apply for a maximum of 2 projects but will be selected as a contributor for a maximum of 1 project only. \n
- The mentees/contributors are expected to submit a detailed project proposal conforming to the template shared by the NITK Winter of Code organizing committee. Certain organizations/mentors may be permitted to accept applications in a particular format of their choice. \n
- The mentors/organizations in the NITK Winter of Code reserve the right to decide to accept or reject a mentee at their sole discretion. In case of any grievances, the applicant is instructed to reach out to the organizing committee of NITK Winter of Code. \n
- The NITK Winter of Code organizing committee will announce the selected mentees on the Program Website. \n
Responsibilities
\n \n- \n
- Providing Evaluation of their Mentor(s). \n
- Work with complete diligence to ensure the project objectives are met(which may be subject to change but only after the consent of the mentor in context). \n
- Ensure good coding & documentation practices are followed as deemed fit by the organization/mentor. \n
- Publish a final report documenting the work done during the project(carried out during NITK Winter of Code alone). No work done outside the duration of NITK Winter of Code, will be considered for evaluations or final report submissions and if violated, may lead to disqualification from the program immediately. \n
- If the organizing committee of NITK Winter of Code reasonably believes that a Contributor has failed to meet the foregoing responsibilities, the organizing committee may remove such Contributor from the Program. \n
Evaluations
\n \n- \n
- The organizing committee of NITK Winter of Code shall conduct two evaluations during the course of the program, namely - \n
- \n
- \n Mid Evaluation: On completion of 4 weeks of the program, an evaluation of both mentors and mentees shall be done by obtaining feedback from each entity of the other. It is mandatory that all entities fill out the evaluation form before the stipulated deadline.\n \n
- \n Final Evaluation: On completion of 8 weeks(end of the program), an evaluation of both mentors and mentees shall be done by obtaining feedback from each entity of the other. As part of this evaluation, the mentee is expected to submit a report documenting the work done as part of the program. It is mandatory that all entities fill out the evaluation form before the stipulated deadline.\n \n
\n - Evaluation results are strictly kept confidential and disclosed only to the organizing committee of the NITK Winter of Code. Specific questions are intended to be shared with the other entity and will be specifically called out in the evaluation form. \n
- If a mentee/contributor is failed in the mid-evaluation, they will be disqualified with immediate effect from the program. In case of any grievances, the mentees/contributors are instructed to reach out to the organizing committee of NITK Winter of Code. \n
- On successful completion(submission of the evaluation form before the deadline), the certificates of each individual shall be generated and shared. \n
- Failing to complete evaluations before the stipulated deadline, may lead to revoking of the project and the benefits associated with the completion of the project. No deadline extension shall be granted, except in genuine cases(considered by the organizing committee of NITK Winter of Code). \n
Participating organizations
\nTo participate in Winter of Code NITK 2023, participating organizations are required to adhere to the following guidelines for the smooth conduction of the program.
\nApplication
\n \n- \n
- Any organization willing to build an open source project or intend to work on an existing project is eligible to apply to NITK Winter of Code. The organization must have the source code of the project made open source that is built during the duration of the program. The previous clause shall not be applicable for organizations mentoring from the National Institute of Technology Karnataka (NITK). \n
- The organization administrator/project mentor must agree to the guidelines applicable for organizations under the NITK Winter of Code. The organization administrator/project mentor must submit the Google form shared by the NITK Winter of Code organizing committee to be considered eligible as a mentoring organization. \n
- The Google form for organizations/mentors (a.k.a, Organization Application) must be submitted by an Organization Administrator/project mentor available on the Program Website during the application period for organizations/mentors described in the Program Timeline. \n
- The Google form for organizations/mentors must be submitted by individual mentors for each project of an organization/self. \n
- The NITK Winter of Code organizing committee reserves the right to decide to accept or reject an organization at its sole discretion. \n
- The NITK Winter of Code organizing committee will announce the selected organizations/projects on the Program Website. \n
Responsibilities
\n \n- \n
- In NITK Winter of Code, an organization is considered responsible for appointing mentors for projects and ensuring that mentors fill in the application form for every project independently. \n
- An organization shall receive a mention on the Program Website on having at least one project proposal accepted by the NITK Winter of Code organizing committee. \n
Mentors
\nTo participate in NITK Winter of Code 2023, mentors are required to adhere to the following guidelines for the smooth conduction of the program.
\nApplication
\n \n- \n
- All rules & regulations applicable to the mentors of an organization are applicable to any mentor participating in NITK Winter of Code. \n
- The application process is common for all mentors, irrespective of their affiliation with any organization. The project mentors need to fill out the organization/mentor form independently for every project they wish to propose and fill in the details of the corresponding mentoring organization (if any). \n
Responsibilities
\n \n- \n
- The mentor(s) mentioned in the project proposal and organization/mentor form for the project will only be considered responsible for the project and will serve as the point of contact. \n
- All mentors and mentoring organizations will be required to follow the timeline proposed by the NITK Winter of Code organizing committee. \n
- The mentor shall be solely responsible for helping the selected contributor get started in the organization &/or project as part of NITK Winter of Code. \n
- The mentor shall be responsible for regularly syncing up with the mentee regarding the project status, work completed, issues, etc. \n
- The mentor shall be responsible for guiding and helping the mentee during the entire course of NITK Winter of Code. We consider, similar to Google Summer of Code, that a mentor is the most valuable resource for a mentee during the course of their project. \n
- There shall be a project reviewal committee setup, as per the discretion of the NITK Winter of Code organizing committee, after the commencement of the program, and all mentors will have to submit their feedback of the mentees as per the timeline. Adhering to the timeline is a mandate for participation in the program and shall be strictly enforced by the organizing committee. \n
- Mentors will also be evaluated based on the mentee feedback and the decision of continuing the project will be decided by the NITK Winter of Code organizing committee. \n
- In the event that discrepancies arise the decision taken by the NITK Winter of Code organizing committee will be final. \n
\n
The decision taken by the organizing committee of Winter of Code shall be final in any case. The organizing committee of Winter of Code reserves the right to suspend, cancel, or modify the structure of the Program. The organizing committee also reserves the right to modify these Program Rules to reflect any modifications to the Program. Any changes made will be effective immediately upon notice which will be notified through the program page and/or email. Continued participation in the Program after such notice will be deemed acceptance of such changes.
\n\n \n \n \n
\n \n
\n\n \n More Details\n \n
\n );\n}\n\nexport default function Projects() {\n const [openModal, setModal] = React.useState(false);\n\n const [projectDetail, setProject] = React.useState({});\n\n const closeModal = () => {\n // setProject({});\n setModal(false);\n };\n\n const renderModal = (project) => {\n setProject(project);\n setModal(true);\n };\n return (\n {project.title}
\n{project.org}
\n\n
Mentors:
\n- \n {project.mentors.map((mentor, idx) => {\n return (\n
- \n
Selected candidates:
\n {Array.isArray(project.students) && project.students.length ?\n- \n {project.students.map((student, idx) => {\n return (\n
- \n {student.name}\n \n );\n })}\n
No one
\n }\n\n \n \n Projects\n \n
\n );\n}","import React from \"react\";\nimport styled from \"styled-components\";\nimport { Link } from \"react-router-dom\";\n\nexport default function OrganizationCard(props) {\n return (\n \n \n ×\n \n
\n \n \n {projectList.length===0 ? (\n
\n \n New projects are to be announced soon!\n
\n ) : (\n\n {projectList.map((project, idx) => {\n return (\n renderModal(project)}\n key={idx}\n org={project.org}\n title={project.title}\n desc={project.summary}\n openToAll={project.openToAll}\n />\n );\n })}\n
\n ) }\n Loading...
;\n // }\n // if (error) {\n // console.log(error);\n // returnError fetching organizations
;\n // }\n\nreturn (\n\n \n Organizations\n \n
\n);\n}\n\n// export default function Organizations() {\n// return (\n// \n {orgsList.length===0 ? (\n
\n \n Organizations coming soon!\n
\n ) : (\n\n {orgsList.map((organization,idx) => {\n let url=organization.name.replace(/ /g,'_');\n return (\n
\n )}\n \n// \n// Organizations\n// \n//
\n// );\n// }\n","import React from \"react\";\n// import { useQuery } from \"@apollo/react-hooks\";\n// import { getOrganizationQuery } from \"../../queries\";\nimport ProjectCard from \"../cards/ProjectCard\";\nimport Modal from \"react-modal\";\nimport projectsList from '../../assets/projects.json';\nimport orgsList from '../../assets/organizations.json';\nimport { ProjectDetail } from '../projectspage/Projects';\n\nModal.setAppElement('#root');\n\n\nexport default function Organization({ match }) {\n const {\n params: { orgId },\n } = match;\n // const { loading, data, error } = useQuery(getOrganizationQuery, {\n // variables: { org_id: orgId },\n // });\n // if (loading) {\n // return No organizations available
\n\n//Loading...
;\n // }\n // if (error) {\n // console.log(error);\n // returnError fetching organization details
;\n // }\n\n const [openModal, setModal] = React.useState(false);\n\n const [projectDetail, setProject] = React.useState({});\n\n const closeModal = () => {\n // setProject({});\n setModal(false);\n };\n\n const renderModal = (project) => {\n setProject(project);\n setModal(true);\n };\n\n let orgName = orgId.replace(/_/g, ' ');\n\n const organization = orgsList.find(org => org.name === orgName);\n\n let projects;\n\n if (orgName === \"Miscellaneous\")\n projects = projectsList.filter(p => !p.org)\n // NeST expanded is too big on mobile devices\n else if (orgName === \"Network Stack Tester (NeST)\")\n projects = projectsList.filter(p => p.org === \"NeST\");\n else\n projects = projectsList.filter(p => p.org === orgName);\n\n\n return (\n\n \n
\n );\n}\n","import React from \"react\";\nimport ProjectCard from \"../cards/ProjectCard\";\nimport Modal from \"react-modal\";\nimport { ProjectDetail } from '../projectspage/Projects';\n\nModal.setAppElement('#root');\n\nexport default function ArchivedProject({ match }) {\n const {\n params: { year },\n } = match;\n\n let projectList;\n if (year === '2021') {\n projectList = require('../../assets/2021/projects.json');\n } else {\n projectList = require('../../assets/2022/projects.json');\n }\n\n const [openModal, setModal] = React.useState(false);\n\n const [projectDetail, setProject] = React.useState({});\n\n const closeModal = () => {\n setModal(false);\n };\n\n const renderModal = (project) => {\n setProject(project);\n setModal(true);\n };\n return (\n \n \n ×\n \n
\n \n\n {/* This condition is only for TEDxNITKSurathkal as the name is too big for small devices */}\n {organization.name === \"TEDxNITKSurathkal\" ? TEDx NITKSurathkal
:{organization.name}
}\n{organization.description}
\n\n Projects under {organization.name}\n
\n\n {projects.map((project, idx) => {\n return (\n renderModal(project)}\n key={idx}\n org={project.org}\n title={project.title}\n desc={project.summary}\n openToAll={project.openToAll}\n />\n );\n })}\n
\n \n \n \n Projects\n \n
\n );\n}\n","import React from 'react'\nimport { Link } from \"react-router-dom\";\n\nfunction Archive(props) {\n\n const years = ['2022', '2021'];\n\n return (\n \n \n ×\n \n
\n \n \n {projectList.map((project, idx) => {\n return (\n renderModal(project)}\n key={idx}\n org={project.org}\n title={project.title}\n desc={project.summary}\n openToAll={project.openToAll}\n />\n );\n })}\n
\n \n {years.map(year => (\n
\n )\n}\n\nexport default Archive\n","import React from \"react\";\nimport OrganizationCard from \"../cards/OrganizationCard\";\n\nexport default function ArchivedOrganizations({ match }) {\n\n const {\n params: { year },\n } = match;\n\n let orgsList;\n if (year === '2021') {\n orgsList = require('../../assets/2021/organizations.json');\n } else {\n orgsList = require('../../assets/2022/organizations.json');\n }\n\n\nreturn (\n \n \n Year {year}\n \n \n
\n
\n ))}\n \n \n \n Projects\n \n \n
\n
\n \n \n Organizations\n \n
\n);\n}","import React from 'react'\nimport {\n Chart as ChartJS,\n CategoryScale,\n LinearScale,\n BarElement,\n Title,\n Tooltip,\n Legend,\n } from 'chart.js';\nimport { Bar } from 'react-chartjs-2';\n\nChartJS.register(\n CategoryScale,\n LinearScale,\n BarElement,\n Title,\n Tooltip,\n Legend\n);\n\nfunction optionGenerator(txt) {\n const opts = {\n responsive: true,\n plugins: {\n legend: {\n position: 'top',\n },\n title: {\n display: true,\n text: txt,\n \n },\n },\n }\n return opts;\n}\n\nconst labels = ['2019', '2020', '2021', '2022'];\n\nexport const data = {\n labels,\n datasets: [\n {\n label: 'Projects',\n data: [15,13,21,20],\n backgroundColor: 'rgba(255, 99, 132, 0.5)',\n },\n {\n label: 'Mentors',\n data: [24,31,43,27],\n backgroundColor: 'rgba(53, 162, 235, 0.5)',\n },\n {\n label: 'Mentees',\n data: [31,12,14,22],\n backgroundColor: '#ebcb8b',\n },\n ],\n };\n\nfunction Statistics() {\n return (\n \n {orgsList.map((organization,idx) => {\n let url=organization.name.replace(/ /g,'_');\n return (\n
\n \n \n Statistics\n \n
\n
\n
\n )\n}\n\nexport default Statistics","import React, { useState, useEffect } from \"react\";\nimport { Router, Route } from \"react-router-dom\";\nimport { createHashHistory } from \"history\";\nimport { wrapHistory } from \"oaf-react-router\";\n// import { useToasts } from 'react-toast-notifications'\n\n\nimport { ThemeContext } from \"../store/ThemeContext\";\nimport { UserContext } from \"../store/UserContext\";\nimport Home from \"./homepage/Home\";\nimport About from \"./aboutpage/About\";\nimport Guidelines from \"./guidelinespage/Guidelines\";\nimport Nav from \"./navbar/Navbar\";\nimport { useCookies } from \"react-cookie\";\nimport { useMutation } from \"@apollo/react-hooks\";\nimport { refreshMutation } from \"../queries\";\nimport Footer from \"./footer/footer\";\nimport Projects from \"./projectspage/Projects\";\n// import Project from \"./projectspage/Project\";\nimport Organizations from \"./organizationspage/Organizations\";\nimport Organization from \"./organizationspage/Organization\";\nimport ArchivedProject from \"./archivedprojects/ArchivedProject\";\nimport Archive from \"./archive/Archive\";\nimport ArchivedOrganizations from \"./archivedorganizations/ArchivedOrganizations\";\nimport Statistics from \"./statistics/Statistics\";\n// import ProjectApplications from \"./profilepage/views/ProjectApplications\";\n// import OrganizationProjects from \"./profilepage/views/OrganizationProjects\";\n// import Login, { Logout } from \"./login/Login\";\n// import SignUp from \"./signup/applicant\";\n// import Profile from \"./profilepage/Profile\";\n\nconst history = createHashHistory();\nwrapHistory(history);\n\nfunction App() {\n // const { addToast } = useToasts();\n const [theme, setTheme] = useState(\"light\");\n const [user, setUser] = useState({\n id: \"\",\n type: \"\",\n auth: \"\",\n refresh: \"\",\n });\n const [cookies, setCookie] = useCookies([\"refresh\", \"access\"]);\n const [navbarOpen, setNav] = useState(false);\n const handleNavbar = () => {\n setNav(!navbarOpen);\n };\n\n // The mutation to be called every hour to keep the user logged in\n const [refresh] = useMutation(refreshMutation, {\n onCompleted({ renewAuth }) {\n const now = new Date().getTime();\n\n // Update the global user on data return\n setUser(renewAuth);\n\n // Set the refresh cookie for 7 hours from current time\n setCookie(\"refresh\", renewAuth.refresh, {\n path: \"/\",\n expires: new Date(now + 7 * 3600 * 1000),\n });\n\n // Set the access cookie for 1 hour from current time\n setCookie(\"access\", renewAuth.auth, {\n path: \"/\",\n expires: new Date(now + 1 * 3600 * 1000),\n });\n },\n onError(err) {\n console.log(err);\n },\n });\n\n // useEffect(() => {\n // const content = [\n // \"Guidelines for mentees have been added. Read through them on the guidelines page!\",\n // \"Applications open for students. View all projects at the projects page and apply by 10 Nov!\"\n // ];\n // content.forEach(information => {\n // addToast(information, {\n // appearance: 'info',\n // autoDismiss: true,\n // });\n // })\n // }, [addToast]);\n\n useEffect(() => {\n // First time when thge page loads, call the mutation\n refresh({ variables: { refresh: cookies.refresh || \"asd\" } });\n\n // Call the mutation every 1 hour because every one hour, the access token becomes invalid\n const interval = setInterval(() => {\n refresh({ variables: { refresh: cookies.refresh } });\n }, 3600000);\n return () => clearInterval(interval);\n // eslint-disable-next-line\n }, []);\n\n return (\n \n NITK has been a forerunner in contributing to open source owing to the initiatives such as Winter of Code NITK. NITK has a proven track record of competing on the global stage in open-source contributions. NITK has had record-breaking selections of 23 in Google Summer of Code, 2020 edition, and 17 in Google Summer of Code, 2021 edition. NITK is the only Asian institute to be part of the ns-3(one of the most famous, open-source, and widely used network simulator) consortium due to the immense amount of open-source contributions made by students of NITK to ns-3. NeST(Network Stack Tester) is a network emulator designed, implemented, and maintained by the students of NITK. The students of NITK have hosted sessions on codebase walkthrough of the Linux kernel and have also contributed to the mainline Linux kernel on various occasions. These numbers and quality contributions to the world of open source are a testimony to the open source culture thriving at NITK owing to initiatives such as Winter of Code NITK.\n
\n\n
\n
\n \n \n \n \n \n \n
\n );\n}\n\nexport default App;\n","const getCookie = (cname) => {\n const name = cname + \"=\";\n let decodedCookie = decodeURIComponent(document.cookie);\n let ca = decodedCookie.split(\";\");\n for (let i = 0; i < ca.length; i++) {\n let c = ca[i];\n while (c.charAt(0) === \" \") {\n c = c.substring(1);\n }\n if (c.indexOf(name) === 0) {\n return c.substring(name.length, c.length);\n }\n }\n return \"\";\n};\n\nconst setCookie = (cName, cValue, hours) => {\n let d = new Date();\n d.setTime(d.getTime() + hours * 60 * 60 * 1000);\n const expires = \"expires=\" + d.toUTCString();\n document.cookie = `${cName}=${cValue};${expires};path=/`;\n};\n\n// export default getCookie;\nexport { getCookie, setCookie };\n","import React from \"react\";\nimport ReactDOM from \"react-dom\";\nimport \"./index.css\";\nimport App from \"./components/App\";\nimport ApolloClient from \"apollo-boost\";\nimport { ApolloProvider } from \"@apollo/react-hooks\";\nimport { getCookie } from \"./cookieFunctions\";\nimport { CookiesProvider } from \"react-cookie\";\n\nimport { DefaultToast, ToastProvider } from 'react-toast-notifications';\nexport const MyCustomToast = ({ children, ...props }) => (\n \n
\n \n \n
\n {children}
\n \n
\n );\n });\n}\n\n","import React from \"react\";\nimport {Link} from 'react-router-dom';\nimport Timeline from \"./Timeline\";\nimport NITKLogo from '../../assets/NITK_Logo_1.png'\n\nconst timeline = [\n { event: \"Deadline to submit project proposals by organizations in NITK. Submit by 6th October to get the project proposals reviewed!\", date: \"October 6\" },\n { event: \"List of selected projects released. Students start discussing project details with mentors\", date: \"October 10\" },\n { event: \"Students can start submitting project proposals\", date: \"October 12\" },\n { event: \"Last day for students to submit project proposals\", date: \"November 12\" },\n { event: \"List of selected students for projects released\", date: \"November 24\" },\n { event: \"Coding phase begins\", date: \"December 9\" },\n { event: \"Mid evaluation\", date: \"January 9\" },\n { event: \"Final evaluation\", date: \"February 9\" }\n]\n\nconst Home = () => {\n return (\n <>\n \n
\n \n
\n {timeline.event}
\n{timeline.date}
\n\n
\n \n
\n
\n
NITK Winter of Code
\n Kickstart your open source journey
\n {/* View Projects */}\n {/* Apply as a mentor */}\n Apply as a mentee \n View Projects \n\n
Timeline
\n\n \n About NITK Winter of Code\n \n\n
\n \n );\n}\n","import React from \"react\";\n\n\n\nexport default function Guidelines() {\n return (\n <>\n Aim
\nNITK Winter of Code aims at helping students get started with open source projects that directly impact peoples' lives.
\nWinter of Code has a philosophy very similar to larger programs like GSoC and Outreachy. Winter of Code is designed to acclimatize people to the steps involved in taking up various projects in large organizations like VLC, Mozilla, and others through GSoC and other similar programs.
\nThe participants will learn how to prepare a project application, work in teams, understand the importance of effective communication, and most importantly, work with large codebases. They will also learn the intricate workflows and good coding practices.
\n\nProgram Overview
\nWinter of Code is a program organized by the Centre for Open-Source Software and Hardware (COSH) at NITK Surathkal with a focus on introducing the student developers across the world to open source software and hardware development. The students can work with projects proposed by the Technical clubs, Open Source Organizations and Faculty Members of NITK over the winter break. This program also plans to introduce to students the rigorous process of developing a project proposal similar to that of GSoC.
\nA team of students will act as an organizing committee for the Winter of Code. The organizing committee will ensure that the program is conducted smoothly and will also maintain a website for the event. The organizing committee is responsible for creating a basic filter for project proposals.
\nFor the first time in the year 2021, we have opened the NITK Winter of Code program for the students other than NITK to submit proposals and participate in this program. They will be mentored by the organizations from NITK Surathkal.
\n\nTarget Audience
\nAnyone who is interested in contributing to open source! There will be students from all years and so projects of varying difficulty are needed.
\n\nProjects
\nProjects of different levels of difficulty, catering to different skill sets and expertise, will be available. The projects will cover different domains, as much as possible. The projects can be proposed by students (Bachelors, Masters and Ph.D.), faculty members, administrative offices (for example, HODs, Chairman, Deans, Deputy Director and Director), and by the various clubs at NITK willing to mentor students. The projects will be accepted by the organizing committee based on their merit and feasibility for the duration of the Winter of Code program. New projects, as well as projects with an existing codebase, are allowed.
\nMentors must submit projects which can be worked on for a minimum period of 8 weeks. Each project must have 2 mentors. If an organization (any club) proposes projects, the organization must have an organization coordinator. Projects should be divided into small tasks/issues. The mentors should also include some tasks to judge the candidate prior to selecting them for the progra,. The mentors are free to conduct any kind of evaluation (interviews, patch requirements, etc) required to select the candidates before the deadline.
\nThe students can apply to projects either by filling a Google form or completing a small task, which is at the discretion of the mentors. A student can apply to a maximum of 2 projects.
\n\nIncentives:
\n- \n
- Working/building innovating, exciting and positively impacting projects during their winter! \n
- Hands-on experience with open source and exposure to collaborativie ways of working! \n
- Understanding how global programs like Google Summer of Code work! \n
- An amazing opportunity to utilize the winter holidays through an impactful project \n
- Certificate issued by COSH NITK at the end of completion, both for mentors and students (Mentors can decide if students are eligible for certificates) \n
\n \n Guidelines for participating entities\n \n\n
\n
\n \n );\n}\n","import React from \"react\";\nimport { Link } from \"react-router-dom\";\nimport styled from \"styled-components\";\nimport logo from \"../../assets/logo-min.png\";\n\nconst Brand = () => {\n return Contributors/Mentees
\nTo participate in Winter of Code NITK 2023, mentees/contributors are required to adhere to the following guidelines for the smooth conduction of the program.
\nApplication
\n \n- \n
- Any student, currently enrolled in an accredited institute, willing to contribute to open source is eligible to apply as a contributor to this Program. \n
- The mentee must agree to the guidelines applicable for mentees/contributors under the NITK Winter of Code. The mentee must submit the Google form shared by the NITK Winter of Code organizing committee to be considered eligible for applying to organizations. \n
- The Google form for organizations/mentors (a.k.a, Contributor/Mentee Application) must be submitted by the mentee available on the Program Website during the application period for organizations/mentors described in the Program Timeline. \n
- The Google form for organizations/mentors must be submitted by by mentees for the project(s) they are applying to. A mentee may apply for a maximum of 2 projects but will be selected as a contributor for a maximum of 1 project only. \n
- The mentees/contributors are expected to submit a detailed project proposal conforming to the template shared by the NITK Winter of Code organizing committee. Certain organizations/mentors may be permitted to accept applications in a particular format of their choice. \n
- The mentors/organizations in the NITK Winter of Code reserve the right to decide to accept or reject a mentee at their sole discretion. In case of any grievances, the applicant is instructed to reach out to the organizing committee of NITK Winter of Code. \n
- The NITK Winter of Code organizing committee will announce the selected mentees on the Program Website. \n
Responsibilities
\n \n- \n
- Providing Evaluation of their Mentor(s). \n
- Work with complete diligence to ensure the project objectives are met(which may be subject to change but only after the consent of the mentor in context). \n
- Ensure good coding & documentation practices are followed as deemed fit by the organization/mentor. \n
- Publish a final report documenting the work done during the project(carried out during NITK Winter of Code alone). No work done outside the duration of NITK Winter of Code, will be considered for evaluations or final report submissions and if violated, may lead to disqualification from the program immediately. \n
- If the organizing committee of NITK Winter of Code reasonably believes that a Contributor has failed to meet the foregoing responsibilities, the organizing committee may remove such Contributor from the Program. \n
Evaluations
\n \n- \n
- The organizing committee of NITK Winter of Code shall conduct two evaluations during the course of the program, namely - \n
- \n
- \n Mid Evaluation: On completion of 4 weeks of the program, an evaluation of both mentors and mentees shall be done by obtaining feedback from each entity of the other. It is mandatory that all entities fill out the evaluation form before the stipulated deadline.\n \n
- \n Final Evaluation: On completion of 8 weeks(end of the program), an evaluation of both mentors and mentees shall be done by obtaining feedback from each entity of the other. As part of this evaluation, the mentee is expected to submit a report documenting the work done as part of the program. It is mandatory that all entities fill out the evaluation form before the stipulated deadline.\n \n
\n - Evaluation results are strictly kept confidential and disclosed only to the organizing committee of the NITK Winter of Code. Specific questions are intended to be shared with the other entity and will be specifically called out in the evaluation form. \n
- If a mentee/contributor is failed in the mid-evaluation, they will be disqualified with immediate effect from the program. In case of any grievances, the mentees/contributors are instructed to reach out to the organizing committee of NITK Winter of Code. \n
- On successful completion(submission of the evaluation form before the deadline), the certificates of each individual shall be generated and shared. \n
- Failing to complete evaluations before the stipulated deadline, may lead to revoking of the project and the benefits associated with the completion of the project. No deadline extension shall be granted, except in genuine cases(considered by the organizing committee of NITK Winter of Code). \n
Participating organizations
\nTo participate in Winter of Code NITK 2023, participating organizations are required to adhere to the following guidelines for the smooth conduction of the program.
\nApplication
\n \n- \n
- Any organization willing to build an open source project or intend to work on an existing project is eligible to apply to NITK Winter of Code. The organization must have the source code of the project made open source that is built during the duration of the program. The previous clause shall not be applicable for organizations mentoring from the National Institute of Technology Karnataka (NITK). \n
- The organization administrator/project mentor must agree to the guidelines applicable for organizations under the NITK Winter of Code. The organization administrator/project mentor must submit the Google form shared by the NITK Winter of Code organizing committee to be considered eligible as a mentoring organization. \n
- The Google form for organizations/mentors (a.k.a, Organization Application) must be submitted by an Organization Administrator/project mentor available on the Program Website during the application period for organizations/mentors described in the Program Timeline. \n
- The Google form for organizations/mentors must be submitted by individual mentors for each project of an organization/self. \n
- The NITK Winter of Code organizing committee reserves the right to decide to accept or reject an organization at its sole discretion. \n
- The NITK Winter of Code organizing committee will announce the selected organizations/projects on the Program Website. \n
Responsibilities
\n \n- \n
- In NITK Winter of Code, an organization is considered responsible for appointing mentors for projects and ensuring that mentors fill in the application form for every project independently. \n
- An organization shall receive a mention on the Program Website on having at least one project proposal accepted by the NITK Winter of Code organizing committee. \n
Mentors
\nTo participate in NITK Winter of Code 2023, mentors are required to adhere to the following guidelines for the smooth conduction of the program.
\nApplication
\n \n- \n
- All rules & regulations applicable to the mentors of an organization are applicable to any mentor participating in NITK Winter of Code. \n
- The application process is common for all mentors, irrespective of their affiliation with any organization. The project mentors need to fill out the organization/mentor form independently for every project they wish to propose and fill in the details of the corresponding mentoring organization (if any). \n
Responsibilities
\n \n- \n
- The mentor(s) mentioned in the project proposal and organization/mentor form for the project will only be considered responsible for the project and will serve as the point of contact. \n
- All mentors and mentoring organizations will be required to follow the timeline proposed by the NITK Winter of Code organizing committee. \n
- The mentor shall be solely responsible for helping the selected contributor get started in the organization &/or project as part of NITK Winter of Code. \n
- The mentor shall be responsible for regularly syncing up with the mentee regarding the project status, work completed, issues, etc. \n
- The mentor shall be responsible for guiding and helping the mentee during the entire course of NITK Winter of Code. We consider, similar to Google Summer of Code, that a mentor is the most valuable resource for a mentee during the course of their project. \n
- There shall be a project reviewal committee setup, as per the discretion of the NITK Winter of Code organizing committee, after the commencement of the program, and all mentors will have to submit their feedback of the mentees as per the timeline. Adhering to the timeline is a mandate for participation in the program and shall be strictly enforced by the organizing committee. \n
- Mentors will also be evaluated based on the mentee feedback and the decision of continuing the project will be decided by the NITK Winter of Code organizing committee. \n
- In the event that discrepancies arise the decision taken by the NITK Winter of Code organizing committee will be final. \n
\n
The decision taken by the organizing committee of Winter of Code shall be final in any case. The organizing committee of Winter of Code reserves the right to suspend, cancel, or modify the structure of the Program. The organizing committee also reserves the right to modify these Program Rules to reflect any modifications to the Program. Any changes made will be effective immediately upon notice which will be notified through the program page and/or email. Continued participation in the Program after such notice will be deemed acceptance of such changes.
\n\n \n \n \n
\n \n
\n\n \n More Details\n \n
\n );\n}\n\nexport default function Projects() {\n const [openModal, setModal] = React.useState(false);\n\n const [projectDetail, setProject] = React.useState({});\n\n const closeModal = () => {\n // setProject({});\n setModal(false);\n };\n\n const renderModal = (project) => {\n setProject(project);\n setModal(true);\n };\n return (\n {project.title}
\n{project.org}
\n\n
Mentors:
\n- \n {project.mentors.map((mentor, idx) => {\n return (\n
- \n
Selected candidates:
\n {Array.isArray(project.students) && project.students.length ?\n- \n {project.students.map((student, idx) => {\n return (\n
- \n {student.name}\n \n );\n })}\n
No one
\n }\n\n \n \n Projects\n \n
\n );\n}","import React from \"react\";\nimport styled from \"styled-components\";\nimport { Link } from \"react-router-dom\";\n\nexport default function OrganizationCard(props) {\n return (\n \n \n ×\n \n
\n \n \n {projectList.length===0 ? (\n
\n \n New projects are to be announced soon!\n
\n ) : (\n\n {projectList.map((project, idx) => {\n return (\n renderModal(project)}\n key={idx}\n org={project.org}\n title={project.title}\n desc={project.summary}\n openToAll={project.openToAll}\n />\n );\n })}\n
\n ) }\n Loading...
;\n // }\n // if (error) {\n // console.log(error);\n // returnError fetching organizations
;\n // }\n\nreturn (\n\n \n Organizations\n \n
\n);\n}\n\n// export default function Organizations() {\n// return (\n// \n {orgsList.length===0 ? (\n
\n \n Organizations coming soon!\n
\n ) : (\n\n {orgsList.map((organization,idx) => {\n let url=organization.name.replace(/ /g,'_');\n return (\n
\n )}\n \n// \n// Organizations\n// \n//
\n// );\n// }\n","import React from \"react\";\n// import { useQuery } from \"@apollo/react-hooks\";\n// import { getOrganizationQuery } from \"../../queries\";\nimport ProjectCard from \"../cards/ProjectCard\";\nimport Modal from \"react-modal\";\nimport projectsList from '../../assets/projects.json';\nimport orgsList from '../../assets/organizations.json';\nimport { ProjectDetail } from '../projectspage/Projects';\n\nModal.setAppElement('#root');\n\n\nexport default function Organization({ match }) {\n const {\n params: { orgId },\n } = match;\n // const { loading, data, error } = useQuery(getOrganizationQuery, {\n // variables: { org_id: orgId },\n // });\n // if (loading) {\n // return No organizations available
\n\n//Loading...
;\n // }\n // if (error) {\n // console.log(error);\n // returnError fetching organization details
;\n // }\n\n const [openModal, setModal] = React.useState(false);\n\n const [projectDetail, setProject] = React.useState({});\n\n const closeModal = () => {\n // setProject({});\n setModal(false);\n };\n\n const renderModal = (project) => {\n setProject(project);\n setModal(true);\n };\n\n let orgName = orgId.replace(/_/g, ' ');\n\n const organization = orgsList.find(org => org.name === orgName);\n\n let projects;\n\n if (orgName === \"Miscellaneous\")\n projects = projectsList.filter(p => !p.org)\n // NeST expanded is too big on mobile devices\n else if (orgName === \"Network Stack Tester (NeST)\")\n projects = projectsList.filter(p => p.org === \"NeST\");\n else\n projects = projectsList.filter(p => p.org === orgName);\n\n\n return (\n\n \n
\n );\n}\n","import React from \"react\";\nimport ProjectCard from \"../cards/ProjectCard\";\nimport Modal from \"react-modal\";\nimport { ProjectDetail } from '../projectspage/Projects';\n\nModal.setAppElement('#root');\n\nexport default function ArchivedProject({ match }) {\n const {\n params: { year },\n } = match;\n\n let projectList;\n if (year === '2021') {\n projectList = require('../../assets/2021/projects.json');\n } else {\n projectList = require('../../assets/2022/projects.json');\n }\n\n const [openModal, setModal] = React.useState(false);\n\n const [projectDetail, setProject] = React.useState({});\n\n const closeModal = () => {\n setModal(false);\n };\n\n const renderModal = (project) => {\n setProject(project);\n setModal(true);\n };\n return (\n \n \n ×\n \n
\n \n\n {/* This condition is only for TEDxNITKSurathkal as the name is too big for small devices */}\n {organization.name === \"TEDxNITKSurathkal\" ? TEDx NITKSurathkal
:{organization.name}
}\n{organization.description}
\n\n Projects under {organization.name}\n
\n\n {projects.map((project, idx) => {\n return (\n renderModal(project)}\n key={idx}\n org={project.org}\n title={project.title}\n desc={project.summary}\n openToAll={project.openToAll}\n />\n );\n })}\n
\n \n \n \n Projects\n \n
\n );\n}\n","import React from 'react'\nimport { Link } from \"react-router-dom\";\n\nfunction Archive(props) {\n\n const years = ['2022', '2021'];\n\n return (\n \n \n ×\n \n
\n \n \n {projectList.map((project, idx) => {\n return (\n renderModal(project)}\n key={idx}\n org={project.org}\n title={project.title}\n desc={project.summary}\n openToAll={project.openToAll}\n />\n );\n })}\n
\n \n {years.map(year => (\n
\n )\n}\n\nexport default Archive\n","import React from \"react\";\nimport OrganizationCard from \"../cards/OrganizationCard\";\n\nexport default function ArchivedOrganizations({ match }) {\n\n const {\n params: { year },\n } = match;\n\n let orgsList;\n if (year === '2021') {\n orgsList = require('../../assets/2021/organizations.json');\n } else {\n orgsList = require('../../assets/2022/organizations.json');\n }\n\n\nreturn (\n \n \n Year {year}\n \n \n
\n
\n ))}\n \n \n \n Projects\n \n \n
\n
\n \n \n Organizations\n \n
\n);\n}","import React from 'react'\nimport {\n Chart as ChartJS,\n CategoryScale,\n LinearScale,\n BarElement,\n Title,\n Tooltip,\n Legend,\n } from 'chart.js';\nimport { Bar } from 'react-chartjs-2';\n\nChartJS.register(\n CategoryScale,\n LinearScale,\n BarElement,\n Title,\n Tooltip,\n Legend\n);\n\nfunction optionGenerator(txt) {\n const opts = {\n responsive: true,\n plugins: {\n legend: {\n position: 'top',\n },\n title: {\n display: true,\n text: txt,\n \n },\n },\n }\n return opts;\n}\n\nconst labels = ['2019', '2020', '2021', '2022'];\n\nexport const data = {\n labels,\n datasets: [\n {\n label: 'Projects',\n data: [15,13,21,20],\n backgroundColor: 'rgba(255, 99, 132, 0.5)',\n },\n {\n label: 'Mentors',\n data: [24,31,43,27],\n backgroundColor: 'rgba(53, 162, 235, 0.5)',\n },\n {\n label: 'Mentees',\n data: [31,12,14,22],\n backgroundColor: '#ebcb8b',\n },\n ],\n };\n\nfunction Statistics() {\n return (\n \n {orgsList.map((organization,idx) => {\n let url=organization.name.replace(/ /g,'_');\n return (\n
\n \n \n Statistics\n \n
\n
\n
\n )\n}\n\nexport default Statistics","import React, { useState, useEffect } from \"react\";\nimport { Router, Route } from \"react-router-dom\";\nimport { createHashHistory } from \"history\";\nimport { wrapHistory } from \"oaf-react-router\";\n// import { useToasts } from 'react-toast-notifications'\n\n\nimport { ThemeContext } from \"../store/ThemeContext\";\nimport { UserContext } from \"../store/UserContext\";\nimport Home from \"./homepage/Home\";\nimport About from \"./aboutpage/About\";\nimport Guidelines from \"./guidelinespage/Guidelines\";\nimport Nav from \"./navbar/Navbar\";\nimport { useCookies } from \"react-cookie\";\nimport { useMutation } from \"@apollo/react-hooks\";\nimport { refreshMutation } from \"../queries\";\nimport Footer from \"./footer/footer\";\nimport Projects from \"./projectspage/Projects\";\n// import Project from \"./projectspage/Project\";\nimport Organizations from \"./organizationspage/Organizations\";\nimport Organization from \"./organizationspage/Organization\";\nimport ArchivedProject from \"./archivedprojects/ArchivedProject\";\nimport Archive from \"./archive/Archive\";\nimport ArchivedOrganizations from \"./archivedorganizations/ArchivedOrganizations\";\nimport Statistics from \"./statistics/Statistics\";\n// import ProjectApplications from \"./profilepage/views/ProjectApplications\";\n// import OrganizationProjects from \"./profilepage/views/OrganizationProjects\";\n// import Login, { Logout } from \"./login/Login\";\n// import SignUp from \"./signup/applicant\";\n// import Profile from \"./profilepage/Profile\";\n\nconst history = createHashHistory();\nwrapHistory(history);\n\nfunction App() {\n // const { addToast } = useToasts();\n const [theme, setTheme] = useState(\"light\");\n const [user, setUser] = useState({\n id: \"\",\n type: \"\",\n auth: \"\",\n refresh: \"\",\n });\n const [cookies, setCookie] = useCookies([\"refresh\", \"access\"]);\n const [navbarOpen, setNav] = useState(false);\n const handleNavbar = () => {\n setNav(!navbarOpen);\n };\n\n // The mutation to be called every hour to keep the user logged in\n const [refresh] = useMutation(refreshMutation, {\n onCompleted({ renewAuth }) {\n const now = new Date().getTime();\n\n // Update the global user on data return\n setUser(renewAuth);\n\n // Set the refresh cookie for 7 hours from current time\n setCookie(\"refresh\", renewAuth.refresh, {\n path: \"/\",\n expires: new Date(now + 7 * 3600 * 1000),\n });\n\n // Set the access cookie for 1 hour from current time\n setCookie(\"access\", renewAuth.auth, {\n path: \"/\",\n expires: new Date(now + 1 * 3600 * 1000),\n });\n },\n onError(err) {\n console.log(err);\n },\n });\n\n // useEffect(() => {\n // const content = [\n // \"Guidelines for mentees have been added. Read through them on the guidelines page!\",\n // \"Applications open for students. View all projects at the projects page and apply by 10 Nov!\"\n // ];\n // content.forEach(information => {\n // addToast(information, {\n // appearance: 'info',\n // autoDismiss: true,\n // });\n // })\n // }, [addToast]);\n\n useEffect(() => {\n // First time when thge page loads, call the mutation\n refresh({ variables: { refresh: cookies.refresh || \"asd\" } });\n\n // Call the mutation every 1 hour because every one hour, the access token becomes invalid\n const interval = setInterval(() => {\n refresh({ variables: { refresh: cookies.refresh } });\n }, 3600000);\n return () => clearInterval(interval);\n // eslint-disable-next-line\n }, []);\n\n return (\n \n NITK has been a forerunner in contributing to open source owing to the initiatives such as Winter of Code NITK. NITK has a proven track record of competing on the global stage in open-source contributions. NITK has had record-breaking selections of 23 in Google Summer of Code, 2020 edition, and 17 in Google Summer of Code, 2021 edition. NITK is the only Asian institute to be part of the ns-3(one of the most famous, open-source, and widely used network simulator) consortium due to the immense amount of open-source contributions made by students of NITK to ns-3. NeST(Network Stack Tester) is a network emulator designed, implemented, and maintained by the students of NITK. The students of NITK have hosted sessions on codebase walkthrough of the Linux kernel and have also contributed to the mainline Linux kernel on various occasions. These numbers and quality contributions to the world of open source are a testimony to the open source culture thriving at NITK owing to initiatives such as Winter of Code NITK.\n
\n\n
\n
\n \n \n \n \n \n \n
\n );\n}\n\nexport default App;\n","const getCookie = (cname) => {\n const name = cname + \"=\";\n let decodedCookie = decodeURIComponent(document.cookie);\n let ca = decodedCookie.split(\";\");\n for (let i = 0; i < ca.length; i++) {\n let c = ca[i];\n while (c.charAt(0) === \" \") {\n c = c.substring(1);\n }\n if (c.indexOf(name) === 0) {\n return c.substring(name.length, c.length);\n }\n }\n return \"\";\n};\n\nconst setCookie = (cName, cValue, hours) => {\n let d = new Date();\n d.setTime(d.getTime() + hours * 60 * 60 * 1000);\n const expires = \"expires=\" + d.toUTCString();\n document.cookie = `${cName}=${cValue};${expires};path=/`;\n};\n\n// export default getCookie;\nexport { getCookie, setCookie };\n","import React from \"react\";\nimport ReactDOM from \"react-dom\";\nimport \"./index.css\";\nimport App from \"./components/App\";\nimport ApolloClient from \"apollo-boost\";\nimport { ApolloProvider } from \"@apollo/react-hooks\";\nimport { getCookie } from \"./cookieFunctions\";\nimport { CookiesProvider } from \"react-cookie\";\n\nimport { DefaultToast, ToastProvider } from 'react-toast-notifications';\nexport const MyCustomToast = ({ children, ...props }) => (\n \n
\n \n \n
\n {children}
\n