Skip to content
This repository has been archived by the owner on Apr 12, 2023. It is now read-only.

Latest commit

 

History

History
51 lines (32 loc) · 3 KB

README.md

File metadata and controls

51 lines (32 loc) · 3 KB
Raw

JBoss Google Code In Student Handbook

Thank you for participating in Google Code In with JBoss! We are really excited to have you :)

Before you begin with tasks, let's go over some information which is crucial.

Requirements

  • Make sure you signed up to Google Code In
  • Make sure you signed up to Github as we are going to use it for all kind of coding work. It is also necessary for Gitter (details below).
  • Also read how Git and Github works. Here is a good document for that. You can also try the Git tutorial, an interactive tutorial to learn Git in 15 minutes by GitHub.

Communication

We're here to help you!

While you can post your queries related to your task directly on the GCI web portal, we recommend using Gitter to contact mentors.

Use the public channel JBossOutreach/gci for asking questions, instead of finding mentors there and asking privately. This way, you would also help other students who have the same problems, which is the open source way! (we are aware that GCI is a contest, but your efforts that help others won't be unnoticed by the mentors and GCI admins).

Your friendly mentors will be around in that channel to answer any questions you may have.

Quick note, it is considered a good practice to use Google before contacting mentors, as many problems you encounter will have been solved on the web.

For any troubles you're having with the organization, mentors or other students, feel free to contact the GCI admins (details below).

Don’t do these things

  • Don't use foul language to any student or mentor in any case. Always be polite to other community members and mentors.
  • Try to avoid arguing with mentors regarding your task submission.
  • At times there might be delay in reviewing a task. You should NOT be constantly texting them to respond.
  • WARNING Never try to copy someone else’s work.Plagiarism is strictly prohibited, you will be banned from the program.

Do these things

  • When Stuck in a task you should always try to find out the solution to the problem by googling it out before pinging mentors.
  • Always squash your commits when sending the pull request.
  • Always try to attach necessary screenshots or gifs with your pull request.
  • When sending the pull request do mention the corresponding issue number.

Github Repositories

We created forks of the relevant projects in JBossOutreach Github organization.

We ask you to send your pull requests (PRs) to the forks there. This way, we can merge your PRs to the clones and later on the project owners can merge your code back to the original repositories.

GCI admins

  • Ali Ok (aliok AT redhat DOT com; Gitter username: aliok)
  • Anuj Garg (anujgargcse AT gmail DOT com; Gitter username: KeenWarrior)
  • Georgios Zaronikas-Karagiannis (gzaronik AT redhat DOT com; Gitter username: gzaronikas )