generated from chingu-voyages/voyage-template
-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1 from uajanth/development
Development
- Loading branch information
Showing
51 changed files
with
4,101 additions
and
242 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,14 +1,10 @@ | ||
# voyage-tasks | ||
# Chingu Collaborate | ||
|
||
Your project's `readme` is as important to success as your code. For | ||
this reason you should put as much care into its creation and maintenance | ||
as you would any other component of the application. | ||
This project aims to streamline and address some of the main issues associated with the primary offering of Chingu, known as Voyages. | ||
|
||
If you are unsure of what should go into the `readme` let this article, | ||
written by an experienced Chingu, be your starting point - | ||
[Keys to a well written README](https://tinyurl.com/yk3wubft). | ||
Firstly, with self-taught developers emerging daily, we wanted to create a platform where Chingus don't have to wait for the next available voyage that may sometimes be months away. | ||
|
||
And before we go there's "one more thing"! Once you decide what to include | ||
in your `readme` feel free to replace the text we've provided here. | ||
Secondly, while Chingus may initially be able to commit to a Voyage there may be commitments along the way that lead them to abandoning Voyages before completion. Unfortunately, this can directly impact other Chingus and their experience with Voyages too. For example, teams can quickly go from having 5 members assigned to their voyage, to 2 members. The main problem here is that with 2 members in a voyage, Chingus aren't able to develop their collaborative learning skills that they intended to develop through their Voyage. | ||
|
||
For these reasons, we decided to create a platform to help Chingus. Using Chingu Collaborate, Chingus will be able to collborate with other decicated Chingus in the event they miss the deadline to join a Voyage or the next Voyage is months away. Additionally, Voyage teams can leverage Chingu Collaborate to gain help with their Voyages. | ||
|
||
> Own it & Make it your Own! |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.