WSoC-TestRepo2

Repository used for Shortlisting Candidates for the WSOC2001 Project

About

Winter Season of Code

Winter Season of Code is an Initiative by the Open Source community at VIT-AP to help increase Open source activity. To know more about WSoC, click here.

Repository

This repository was created to shortlist candidates for the WSOC2001 project.

Note : This repository was made only to test you on your Python programming skills (Back End development).

For developers who are looking to contribute for the front end aspect of the project, redirect to this repository.

Prerequisites

Languages and tools you are expected to know before working on the project :

• Git.
• GitHub.
• Python (Intermediate level).

Getting Started

To start working on the challenges provided, you must first fork this repository. Just press the fork button present in the top right corner of your screen.

Once done, you must be having your own copy of this repository in your GitHub page, just head over to your profile and open WSoC-TestRepo2.

Now, clone your copy of the repository to your local system.

For more details on forking and cloning the repository, click here (follow steps 1 and 2).

Once the repository is on your local system, you need to create a separate branch to start working.

To do this, open your console and "cd/" to the repository. Once done, use the command,

git checkout -b branchname

where, branchname is the name of your branch. It is advised that you name the branch after your registration number.

You can also branch directly from GitHub, click here for more info on that.

Once done, you are all set to get started.

Things to remember

• All the questions and programs are present in the directory called "core" within the repository.
• Each level has different challenges and different points awarded for each.
• You will be judged based on a total of 100 points, 20 for level 1, 30 for level 2 and 40 for level 3. The rest 10 depends on how you solve the problems given.
• Further details about the challenges in each level will be mentioned in their respective README files.
• You do not necessarily have to add comments for each line, but a short description could gain you a few extra points.
• It is not compulsory to do all the challenges. Do as many as you can before sending us a pull request. However, people who have solved more have a higher edge over others.
• Earlier the submission, higher the priority.
• If you have any queries regarding any of the challenges or the event itself, feel free to create a GitHub issue.
• Have fun💥✨!

Submission

If you are completed with the challenges or think you are ready to submit your work. Follow the steps below :

• Push all your changes to your remote repository, use command git push.
• Now, you need to send us a pull request. If you are not sure how to do that, click here.
• Make sure you fill out the final form present in the description of your pull request.
• Once you submit your pull request, you are done!

There exist two deadlines for submission.
September 25th. For the early birds.
October 10th. For the perfectionists.
(The earlier, the better 😄)

If you've done your best with the branch and have sent it in for merging already, you're on the right track.
Don't worry about the results, take a break.

We'll contact you if you're in. 😉