Skip to content

Commit

Permalink
update ticket link to the new titan link
Browse files Browse the repository at this point in the history
  • Loading branch information
@cherylli
cherylli committed Aug 17, 2024
1 parent 17b3b82 commit dc3665a
Show file tree
Hide file tree
Showing 2 changed files with 141 additions and 138 deletions.
263 changes: 133 additions & 130 deletions .gitignore
View file
Original file line number Diff line number Diff line change
@@ -1,130 +1,133 @@
# Logs
logs
*.log
npm-debug.log*
yarn-debug.log*
yarn-error.log*
lerna-debug.log*
.pnpm-debug.log*

# Diagnostic reports (https://nodejs.org/api/report.html)
report.[0-9]*.[0-9]*.[0-9]*.[0-9]*.json

# Runtime data
pids
*.pid
*.seed
*.pid.lock

# Directory for instrumented libs generated by jscoverage/JSCover
lib-cov

# Coverage directory used by tools like istanbul
coverage
*.lcov

# nyc test coverage
.nyc_output

# Grunt intermediate storage (https://gruntjs.com/creating-plugins#storing-task-files)
.grunt

# Bower dependency directory (https://bower.io/)
bower_components

# node-waf configuration
.lock-wscript

# Compiled binary addons (https://nodejs.org/api/addons.html)
build/Release

# Dependency directories
node_modules/
jspm_packages/

# Snowpack dependency directory (https://snowpack.dev/)
web_modules/

# TypeScript cache
*.tsbuildinfo

# Optional npm cache directory
.npm

# Optional eslint cache
.eslintcache

# Optional stylelint cache
.stylelintcache

# Microbundle cache
.rpt2_cache/
.rts2_cache_cjs/
.rts2_cache_es/
.rts2_cache_umd/

# Optional REPL history
.node_repl_history

# Output of 'npm pack'
*.tgz

# Yarn Integrity file
.yarn-integrity

# dotenv environment variable files
.env
.env.development.local
.env.test.local
.env.production.local
.env.local

# parcel-bundler cache (https://parceljs.org/)
.cache
.parcel-cache

# Next.js build output
.next
out

# Nuxt.js build / generate output
.nuxt
dist

# Gatsby files
.cache/
# Comment in the public line in if your project uses Gatsby and not Next.js
# https://nextjs.org/blog/next-9-1#public-directory-support
# public

# vuepress build output
.vuepress/dist

# vuepress v2.x temp and cache directory
.temp
.cache

# Docusaurus cache and generated files
.docusaurus

# Serverless directories
.serverless/

# FuseBox cache
.fusebox/

# DynamoDB Local files
.dynamodb/

# TernJS port file
.tern-port

# Stores VSCode versions used for testing VSCode extensions
.vscode-test

# yarn v2
.yarn/cache
.yarn/unplugged
.yarn/build-state.yml
.yarn/install-state.gz
.pnp.*
# Logs
logs
*.log
npm-debug.log*
yarn-debug.log*
yarn-error.log*
lerna-debug.log*
.pnpm-debug.log*

# Diagnostic reports (https://nodejs.org/api/report.html)
report.[0-9]*.[0-9]*.[0-9]*.[0-9]*.json

# Runtime data
pids
*.pid
*.seed
*.pid.lock

# Directory for instrumented libs generated by jscoverage/JSCover
lib-cov

# Coverage directory used by tools like istanbul
coverage
*.lcov

# nyc test coverage
.nyc_output

# Grunt intermediate storage (https://gruntjs.com/creating-plugins#storing-task-files)
.grunt

# Bower dependency directory (https://bower.io/)
bower_components

# node-waf configuration
.lock-wscript

# Compiled binary addons (https://nodejs.org/api/addons.html)
build/Release

# Dependency directories
node_modules/
jspm_packages/

# Snowpack dependency directory (https://snowpack.dev/)
web_modules/

# TypeScript cache
*.tsbuildinfo

# Optional npm cache directory
.npm

# Optional eslint cache
.eslintcache

# Optional stylelint cache
.stylelintcache

# Microbundle cache
.rpt2_cache/
.rts2_cache_cjs/
.rts2_cache_es/
.rts2_cache_umd/

# Optional REPL history
.node_repl_history

# Output of 'npm pack'
*.tgz

# Yarn Integrity file
.yarn-integrity

# dotenv environment variable files
.env
.env.development.local
.env.test.local
.env.production.local
.env.local

# parcel-bundler cache (https://parceljs.org/)
.cache
.parcel-cache

# Next.js build output
.next
out

# Nuxt.js build / generate output
.nuxt
dist

# Gatsby files
.cache/
# Comment in the public line in if your project uses Gatsby and not Next.js
# https://nextjs.org/blog/next-9-1#public-directory-support
# public

# vuepress build output
.vuepress/dist

# vuepress v2.x temp and cache directory
.temp
.cache

# Docusaurus cache and generated files
.docusaurus

# Serverless directories
.serverless/

# FuseBox cache
.fusebox/

# DynamoDB Local files
.dynamodb/

# TernJS port file
.tern-port

# Stores VSCode versions used for testing VSCode extensions
.vscode-test

# yarn v2
.yarn/cache
.yarn/unplugged
.yarn/build-state.yml
.yarn/install-state.gz
.pnp.*

# idea
/.idea
16 changes: 8 additions & 8 deletions README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -51,14 +51,14 @@ importance of the various evaluation conditions.
| Condition | Feedback |
|-----------|----------|
| Passed | Hi @ Congratulations on your hard work and dedication. Your Voyage 51 Solo Project has been accepted and you are advancing to the Voyage Phase starting on September 2nd. Watch the <#1026584387569078373> channel for more information. <br/><br/> ```**_If you haven't yet signed up for this Voyage please complete this form so you don't miss out _** ``` —> https://forms.gle/DajSfXQCX4qbMAu8A <br/><br/>I’m looking forward to seeing what you and your team will be creating in your Voyage! <br/><br/>https://c.tenor.com/bDxOr4tSm7kAAAAC/spongebob-high-five.gif <br/><br/>Here is some more specific feedback which I hope will be helpful: </br> |
| Requested changes | Hi @ Your app shows that you’ve invested a considerable amount of thought and effort in its design & implementation. <br/><br/>Please make the following change and then open a ticket in <#1105911757177888908> when you are ready for me to look at it again. ``` **_This is the only change you are required to make._** ``` <br/><br/> ```__**Requested changes**__``` <br/> 1. ... <br/><br/>```**__Here’s additional feedback that I hope will be helpful__**```. |
| Requested changes - no GH repo URL or deployed URL | Hi @ I started to review your Solo Project, but you haven’t provided a valid URL for a specific GitHub repo or the URL where it’s deployed on the Internet. <br/><br/> Your GitHub repo URL generates a page not found error. This can happen if your repo is private instead of public. <br/><br/> We ask for this so we can not only look at your code, but also the running application and its UI/UX. In addition, knowing how to deploy to a web host like GitHub Pages, Netlify, Vercel, Render, etc. is a skill you’ll need in your Voyage. <br/><br/> Please open a ticket in <#1105911757177888908> when you have these URL's and we'll start the evaluation. Thanks! |
| Requested changes - PO: Invalid or inaccessible backlog URL |Hi @ I started to review your Solo Project, but you haven’t provided a valid or publicly accessible URL for your product backlog site on the Internet. <br/><br/>We ask for this so we can evaluate your current expertise as a Product Owner. This will help both you and us validate that you've chosen the right tier before you start a Voyage.<br/><br/>If you have questions about what's required take a look at our [Solo Project Guide](https://github.com/chingu-voyages/Handbook/blob/main/docs/guides/soloproject/soloproject.md#solo-project-guide).<br/><br/>Please open a ticket in <#1105911757177888908> when you have this URL and we'll start the evaluation. Thanks! |
| Requested changes - PO/SM: Quiz below 80% |Hi @ You missed a few questions in the quize which dropped your score below the 80% minimum required to pass.<br/><br/>The questions you've missed are listed below. Please open a ticket in the <#1105911757177888908> channel to update your answers for these questions. We'll then re-evaluate them and will provide you with an update on your status. <br/><br/>If you have questions about what's required take a look at our [Solo Project Guide](https://github.com/chingu-voyages/Handbook/blob/main/docs/guides/soloproject/soloproject.md#solo-project-guide). |
| Requested changes - no deployed URL | I started to review your Solo Project, but you haven’t provided a valid URL for where it’s deployed on the Internet. <br/><br/>We ask for this so we can not only look at your code, but also the running application and its UI/UX. In addition, knowing how to deploy to a web host like GitHub Pages, Netlify, Vercel, Render, etc. is a skill you’ll need in your Voyage. <br/><br/>Please open a ticket in <#1105911757177888908> when you have this URL and we'll start the evaluation. Thanks! |
| Repo URL not found | I started to review your Solo Project, but the URL you’ve provided for your repo is not found (HTTP/404). <br/><br/>This often happens if the repo is marked as private in GitHub instead of public. <br/><br/>Please open a ticket in <#1105911757177888908> when you have this URL and we'll start the evaluation. Thanks! |
| Requested changes - old project ( last change over 12 months ago) | I started to review your Solo Project, but the project you provided was not developed within the last 12 months, or have a significant number of commits made to it by you within the last year. It's likely that you have learnt a lot more in the last 12 months and this project is not an accurate reflection of your current ability, Or you have not been coding for the last 12 months and likely to have forgotten how to code. <br/><br/>Please open a ticket in <#1105911757177888908> when you have a newer project and we'll start the evaluation. Thanks! |
| Requested changes - submitted project tier is lower than applied tier | Hi @ I started to review your Solo Project, but this Solo Project is a Tier 2, rather than a Tier 3 app. Would you like to submit another tier 3 project or continue with this tier 2 project? Which means you'll be eligible to join a tier 2 team if the project is accepted. You can learn more about our tiers and the requirements of each here —> https://github.com/chingu-voyages/Handbook/blob/main/docs/guides/soloproject/soloproject.md#1-choose-your-tier<br/><br/>Please open a ticket in <#1105911757177888908> and lets us know. Thanks! |
| Requested changes | Hi @ Your app shows that you’ve invested a considerable amount of thought and effort in its design & implementation. <br/><br/>Please make the following change and then open a ticket in <#1193342042080817323> when you are ready for me to look at it again. ``` **_This is the only change you are required to make._** ``` <br/><br/> ```__**Requested changes**__``` <br/> 1. ... <br/><br/>```**__Here’s additional feedback that I hope will be helpful__**```. |
| Requested changes - no GH repo URL or deployed URL | Hi @ I started to review your Solo Project, but you haven’t provided a valid URL for a specific GitHub repo or the URL where it’s deployed on the Internet. <br/><br/> Your GitHub repo URL generates a page not found error. This can happen if your repo is private instead of public. <br/><br/> We ask for this so we can not only look at your code, but also the running application and its UI/UX. In addition, knowing how to deploy to a web host like GitHub Pages, Netlify, Vercel, Render, etc. is a skill you’ll need in your Voyage. <br/><br/> Please open a ticket in <#1193342042080817323> when you have these URL's and we'll start the evaluation. Thanks! |
| Requested changes - PO: Invalid or inaccessible backlog URL |Hi @ I started to review your Solo Project, but you haven’t provided a valid or publicly accessible URL for your product backlog site on the Internet. <br/><br/>We ask for this so we can evaluate your current expertise as a Product Owner. This will help both you and us validate that you've chosen the right tier before you start a Voyage.<br/><br/>If you have questions about what's required take a look at our [Solo Project Guide](https://github.com/chingu-voyages/Handbook/blob/main/docs/guides/soloproject/soloproject.md#solo-project-guide).<br/><br/>Please open a ticket in <#1193342042080817323> when you have this URL and we'll start the evaluation. Thanks! |
| Requested changes - PO/SM: Quiz below 80% |Hi @ You missed a few questions in the quize which dropped your score below the 80% minimum required to pass.<br/><br/>The questions you've missed are listed below. Please open a ticket in the <#1193342042080817323> channel to update your answers for these questions. We'll then re-evaluate them and will provide you with an update on your status. <br/><br/>If you have questions about what's required take a look at our [Solo Project Guide](https://github.com/chingu-voyages/Handbook/blob/main/docs/guides/soloproject/soloproject.md#solo-project-guide). |
| Requested changes - no deployed URL | I started to review your Solo Project, but you haven’t provided a valid URL for where it’s deployed on the Internet. <br/><br/>We ask for this so we can not only look at your code, but also the running application and its UI/UX. In addition, knowing how to deploy to a web host like GitHub Pages, Netlify, Vercel, Render, etc. is a skill you’ll need in your Voyage. <br/><br/>Please open a ticket in <#1193342042080817323> when you have this URL and we'll start the evaluation. Thanks! |
| Repo URL not found | I started to review your Solo Project, but the URL you’ve provided for your repo is not found (HTTP/404). <br/><br/>This often happens if the repo is marked as private in GitHub instead of public. <br/><br/>Please open a ticket in <#1193342042080817323> when you have this URL and we'll start the evaluation. Thanks! |
| Requested changes - old project ( last change over 12 months ago) | I started to review your Solo Project, but the project you provided was not developed within the last 12 months, or have a significant number of commits made to it by you within the last year. It's likely that you have learnt a lot more in the last 12 months and this project is not an accurate reflection of your current ability, Or you have not been coding for the last 12 months and likely to have forgotten how to code. <br/><br/>Please open a ticket in <#1193342042080817323> when you have a newer project and we'll start the evaluation. Thanks! |
| Requested changes - submitted project tier is lower than applied tier | Hi @ I started to review your Solo Project, but this Solo Project is a Tier 2, rather than a Tier 3 app. Would you like to submit another tier 3 project or continue with this tier 2 project? Which means you'll be eligible to join a tier 2 team if the project is accepted. You can learn more about our tiers and the requirements of each here —> https://github.com/chingu-voyages/Handbook/blob/main/docs/guides/soloproject/soloproject.md#1-choose-your-tier<br/><br/>Please open a ticket in <#1193342042080817323> and lets us know. Thanks! |
---

[Back to TOC](#evaluation-conditions--feedback)
Expand Down

0 comments on commit dc3665a

Please sign in to comment.