What Can You Expect from Chingu?
We provide information to help our members on their path to success:
- We maintain the Chingu.io website, which contains general information about the Chingu organization and the sign-up forms for our programs.
- We use and moderate Discord to answer questions and concerns. We are a very small team of volunteers building the Chingu platform, so please remember that when reaching out to us!
- We publish a weekly newsletter to provide relevant Cohort information and to recognize your successes.
- We maintain this website containing information about the Chingu organization the Cohort and our flagship Voyage program.
We facilitate Cohorts by:
- Pairing people together and giving you as many resources as possible so you can complete your project. Once the cohort starts, it’s on you as an individual to successfully reach the end!
- Establishing structure, a team environment, deadlines, and check-ins to keep you accountable and motivated so you and your team can complete your goals.
We work to make Chingu a friendly, supportive, and safe environment by:
- Not tolerating harassment, trolling, or any other behavior that violates our community standards.
- Helping you with serious conflicts like teammates that have disappeared after numerous attempts to contact them. If they haven’t responded in 5 days, reach out to us so we can note it in our systems. Then you should continue to finish that project regardless!
- You can find out more by reading our Community Standards.
Items NOT handled by the Chingu-X Team:
- Conflicts within teams should be handled by the team.
- Teams are self-organizing. This means each team is responsible for scheduling meetings, deciding which project they’ll be working on, organizing assignments, and completing the project.
We are continuously growing & improving, which means things will sometimes break.
We apologize for when things don't always work perfectly 🙏, but we believe that continuously improving in order to offer more opportunities for tech-learners is worth it.
Our goal is to listen, quickly resolve issues if/when they arise, and above all, "fail forward".
While we can guarantee all of the above, we CANNOT guarantee you a full team that completes a project and cohort with you. We try our best to match you with others of similar backgrounds, but unfortunately, we cannot stop a user from disappearing.
Unfortunately, we can’t force people to follow through on their commitments.
There are many reasons that can cause people to give up on their Chingu commitment, like getting a job, family emergencies, etc. Circumstances will change in teams and it’s best to go into the team ready to adapt.
Start your Chingu project with a resilient mindset and acknowledge the likely possibility that your team will look different at the end than it did at the beginning; you’ll have to overcome roadblocks throughout your Voyage.
In every cohort we have teams where members dropped out but one person showed grit and finished the project themselves. These people gain confidence (for tech-learners with imposter syndrome, this is invaluable), skills, and earn spots in top teams for future cohorts (we’re a meritocracy). Even when teams don’t work out, the resilient find a way to succeed!
We all encounter questions or problems from time-to-time. One of the strengths of the Chingu organization is you don't have to feel like you are alone when this happens to you. Your fellow Chingu's have a wide variety of exposure to different technologies and one or more have most likely encountered the same situation you are facing.
The best place to ask for help is in the
in Discord. This is the best place to ask questions about Chingu or questions
of a technical nature. Like questions about your favorite programming language,
a framework, a library, or a technique.
Getting help starts with how you phrase your question.
Bad: My React component isn't returning what I want. What gives?
Good: I have a React component (
Locations.jsx) that should be returning a list of location names based on the text entered through a search component (
Search.jsx), but is instead returning
undefined. These are located in the repo
https://github.com/jdmedlock/meteorite. Would someone have time to look at this to see if I've missed something obvious?
A good question has these parts:
- It's actionable and contains contextual information the reader needs.
- It states what is wrong, but also what the desired result should be.
- Key elements, like the component names in the example above, are formatted so they are easy to identify.
- It contains a link to supporting documentation. In this case the project repo.
- It ends with the ask. In other words, what do you need?
The first step in getting an answer is to post your question! That might sound obvious, but it takes a bit of courage to do this since you might feel that your issue is something that everyone else already knows about.
Pfffftttt!!! This is just the impostor syndrome coming out. While there most certainly are Chingu's who already have the answer there are just as many who don't. When you ask a question you aren't just helping yourself, you are also helping others who may be too shy to ask the same thing.
Once you've posted your question be patient if you don't get an answer right away. It may take a few minutes to get a response, but it might also take longer depending on the time of day, day of the week, etc.
If you don't get an answer within a few hours feel free to repost your question.
We love finding and fixing errors and omissions! We also love hearing your ideas for how to improve this wiki to help make it more relevant not just for you, but for future Chingu Voyagers.
Tickets are for problems, not for questions or advice. Continue to post questions in the channels like #community-chat and #code-help. But, please open a ticket if you are experiencing a problem like a permissions issue preventing you from being able to access to your GitHub repo.
You can open and view issues in the Voyage Wiki Issue Log.
The result of having the complete, accurate, and appropriate information is the issue can be resolved faster and more correctly. The key information that should be entered into the issue are:
Issues should be entered by the individual experiencing the issue. One tip is to include error messages and screenshots when describing issues since they provide the most accurate information and are quicker than typing text.
When the issue is resolved the Chingu-X team will update the issue to describe how it was resolved, along with any supplemental information that may be useful if the issue should reoccur in the future.