add: gitea tools
This commit is contained in:
35
Guide/Tasks/Task1.md
Normal file
35
Guide/Tasks/Task1.md
Normal file
@@ -0,0 +1,35 @@
|
||||
## Task 1
|
||||
|
||||
### In this task you have to do the following
|
||||
1. Analysis client's project description
|
||||
2. Determine if client's goal is achievable
|
||||
3. Take a name for this project
|
||||
4. Make comprehensive note of project description
|
||||
5. Create repo on gitea with gitea tool
|
||||
6. Post your note as wiki page to the repo, with title 'Initial Note'
|
||||
|
||||
|
||||
---
|
||||
### Rules to Analysis Project Description
|
||||
|
||||
---
|
||||
### Rules to Determine Goal Achievability
|
||||
|
||||
---
|
||||
### Project Naming Rules
|
||||
1. No white space
|
||||
2. No repo whose owner is you has the same name
|
||||
3. No preposition
|
||||
4. No numeric character
|
||||
5. No special character
|
||||
|
||||
---
|
||||
### Note Rules
|
||||
1. Short, direct.
|
||||
2. Cover every point in client's project description.
|
||||
3. List potential conflicts.
|
||||
4. Note possible technology stack.
|
||||
5. Expert can understand client's purpose by just reading your note.
|
||||
6. List codebase in our gitea server can be reused in this project.
|
||||
|
||||
---
|
||||
Reference in New Issue
Block a user