trial phase

[serapath]

@todo 🛠️

• tasks here are to be done by our team. candidate(s) please skip and read @info section
  • @input 📦 list of selected candidate(s) from application form #2
  • write trial phase description and share a recorded screencast to explain it
    • write trial phase description in @info section below
      • @output 🏭 see @info section below
    • add materials to describe the website project
      • @output ❓ see @info section below
    • add screencast to explain our project management system to chosen candidates
  • @input 📦 dat-ecosystem project screencast
    • next trial phase task for @Hornet004 #9
    • next trial phase task for @CodeLawd #10
    • next trial phase task for @Helenphina #11
  • @input 📦 github issue management system
    • next trial phase task for @Hornet004 #9
    • next trial phase task for @CodeLawd #10
    • next trial phase task for @Helenphina #11
  • @input 📦 example project screencast "wizardamigos"
    • next trial phase task for @Hornet004 #9
    • next trial phase task for @CodeLawd #10
    • next trial phase task for @Helenphina #11
  • @input 📦 example project screencast "datdot-ui"
    • next trial phase task for @Hornet004 #9
    • next trial phase task for @CodeLawd #10
    • next trial phase task for @Helenphina #11
  • @input 📦 little checklist and summary
    • next trial phase task for @Hornet004 #9
    • next trial phase task for @CodeLawd #10
    • next trial phase task for @Helenphina #11
  • introduce chosen candidates to the trial phase tasks
    • trial phase task for @Hornet004 #9
    • trial phase task for @CodeLawd #10
    • trial phase task for @Helenphina #11
  • work with candidates during trial phase towards trial phase results
  • evaluate trial phase results to choose partner(s)
  • make final initial project plan and inform chosen partner(s) to proceed with the gig
    * @output 📦 final initial project plan
    * @output ❓ list of chosen partner(s)

---

@info 👇

• the trial phase candidates and their issues to work on during the next 48 hours are
  • trial phase task for @Hornet004 #9
  • trial phase task for @CodeLawd #10
  • trial phase task for @Helenphina #11
• all participatants who submit a well defined project roadmap will be payed 20 USD

dat-ecosystem project input resources 🐝

• see dat-ecosystem website roadmap #49

evaluation of trial phase 📊

• ❔ did candidates deliver a proper plan to earn the trial phase reward of 💲20 USD 💰
• ❔ is the plan well structured and understandable by us
  • ❔ is the main issues linked in a comment of the candidate's given trial phase issue for easy discovery by us
  • ❔ are all the issues the candidate made directly or indirectly linked to their main issue
  • ❔ are all issues organized in the style of our github issues project task management system
  • ❔ did the candidate estimate times for their tasks
  • ❔ does the main issue list high level tasks to provide a good overview
  • ❔ are inputs and outputs properly linked
  • ❔ do all inputs lead to outputs which are used in other tasks as inputs until eventually the final outputs are produced
  • ❔ do outputs and inputs fit well together or are there missing steps or missing intermediate output documents
  • ❔ is each task well described in the info section in terms of what will happen or does it leave us with many open questions
  • ❔ did the candidate record a screencast to explain their plan well
• ❔ does the plan reflect a similar understanding of the dat-ecosystem that we have based on the input resources including 8 years of history
  • ❔ are all trial phase input resources included as task inputs in the candidate's plan
  • ❔ did the candidate provide additional thoughts/notes/links/screenshots/sketches/etc... or any other inspiration for specific parts of the project plan
  • ❔ did the candidate include all the ❓ outputs mentioned in the trial phase issue or adapted them to something similarly useful
    • the outputs mentioned were:
      • @output ❓ website UI/UX specification & wireframes
      • @output ❓ dat-ecosystem design system
      • @output ❓ list of re-usable web components
      • @output ❓ implemented website
      • @output ❓ link to one or multiple final screencasts (each 3-5 minutes max) where the candidate walks us through the entire project plan
  • ❔ does the proposed website structure represent all aspects of the dat-ecosystem input resources
• ❔ did the candidate work with us during the trial phase and used our feedback to improve the plan
  • ❔ did they use worklog issue comments to post their questions
  • ❔ did they improve the plan structure based on our feedback
  • ❔ did the candidate mention time spent working on the task when posting a worklog
• ❔ does it seem as if the plan can be executed in 4-8 weeks

[serapath]

Checklist

ABSTRACT EXAMPLE: https://hackmd.io/wTuH5UPLRdi214RDjRwWGQ?view

CHECKLIST: https://hackmd.io/OzSDw7a6ShS78ZS6ITnZuA?view

1. DISCORD: We use discord chat about our work on projects

• every time we finish a work effort at the end of our day or sometimes in between
• we post the latest worklog video links to the worklog chat on discord

2. ISSUES: creating a new issue can be done with the "new issue" button

• but also by clicking on a textual todo in the todolist can convert it into a sub issue
• no issue should have more than 10-20 todos
• if a todo list grows larger, some todos need to be grouped and put into a linked sub issue
• a sub issue todo can be marked as done only if all todos inside the sub issues are marked as done

3. ISSUE @todo: each project has a main issue with a task list and info section

• the task list shows all open and finished high level todos
• next to every todo you can link input documents and/or output documents
• some tasks can be links to sub issue with sub task lists and inputs/outputs
• the comments contain worklog comments and feedback comments
• issues can be assigned to you or others to indicate who is working on the task lists
• a todo should only be started once all inputs are marked as finished (= 📦)

4. ISSUE @INFO: section can describe an issue with todos in more detail

5. RESULTS: each todo can have multiple inputs links or outputs links

• each output link references not an issue, but a document
  • e.g. (files/links/wireframes/moodboards/documents/...)
• the symbol ❓ result name means an input or output is planned
  • result name is not a link
• the symbol 🏭 result name means an input or output is work in progress
  • result name is a link to a final or temporary document
• the symbol 📦 result name means an input or output is done
  • result name is a link to a final document added to the repository
• a worklog introduces an output
• the output is then linked under the finished todo that produced the output
• the suffix from [comment](link to worklog comment) is added to the output
• a sub bullet point list can list other issues where the output is used as input
  • just add one bullet point per usage as input like: next #<issue number>
• an input document link in an issue needs a suffix (from link to issue that produced the output)

6. WORKLOGS: After every work effort, we record a screencast worklog video

   • publish the screencast worklog video to youtube
   • add links to all github issues mentioned to the video description
   • post the video link in a worklog comment in all related github issues
   • link all produced finished or work-in-progress results in that issue too
   • add our video to our personal worklog playlist on youtube
   • also link all outputs next to the finished todos which produced them

7. FEEDBACKS: We will watch results and videos and write a feedback comment

   • the feedback might contain more requests to create and refine existing todos
   • the feddback can also answer questions from your worklog video
   • a feedback issue might contain task labels
     • which means you should take the feedback and create or update todos from the feedback

8. STRUCTURE: we try to structure all issue and sub issue todos lists

   • by components/parts and inputs/outputs
   • sometimes this can also include phases
   • structuring an issue so it helps with overview is an art form and comes with practice
   • the goal is to help all of us to keep track of progress and all results
   • the initial main issue is for overview
   • each sub issue is for a group of tasks that belong to a part of the project

9. WORK: working with issues means to constantly update and change the structure a bit

   • e.g. creating or updating issues and todo lists
   • e.g. marking todos as finished
   • e.g. linking more inputs and outputs or change their status