Sean (Dec 24 2019 at 04:31): Sean (Dec 24 2019 at 04:31):@Sahibpreet Kaur here's the second feedback received from saberz52:
Sean (Dec 24 2019 at 04:31):Keep
What should we CONTINUE doing? What's going well? What's worthwhile?
Something I really liked was the explanations of each command, such as the Clone command or the creation of shapes. It became very simple to understand what individual command did in the command window.
Improve
What should we CHANGE? What should we improve? What could be better?
Something that should be changed is the ordering of the pieces. I feel as though the knight is one of the easier pieces to create and understand as opposed to the pawn where the torus is subtracted.
Stop
What should we STOP doing? What's not working well? What's a waste of time?
I definitely think that the queen piece was a waste of time, as it was just a list of commands to be put into the command prompt. I feel as though it would have been better if the user made the queen themselves with a little bit of guidance.
Start
What should we START doing? What would add value? What new process might help?
A process that I personally think would be useful is adding together all of the different databases of pieces together on the board. It would help my understanding of creating different parts and then combing them.
Sean (Dec 24 2019 at 04:32):task https://codein.withgoogle.com/dashboard/task-instances/4881519617769472/
Sahibpreet Kaur (Dec 24 2019 at 04:51):Thank you @Sean , this is really helpful; I'll note these points down. :)
Sahibpreet Kaur (Dec 30 2019 at 07:14):Can I get the other feedbacks? @Sean
Sean (Dec 30 2019 at 08:34):you should now have access to all the feedbacks received
Sahibpreet Kaur (Dec 30 2019 at 08:39):Yeah, got it! Thank you @Sean :)
Sean (Jan 13 2020 at 06:39):Got another good one! https://codein.withgoogle.com/dashboard/task-instances/4956312111153152/
Sean (Jan 13 2020 at 06:43):@Sahibpreet Kaur do you have a table of the feedback received and/or actions to consider in the tutorial next? or somewhere where the feedback can at least be itemized and tracked?
Sahibpreet Kaur (Jan 21 2020 at 06:24):Not yet, but I will set that up soon.
Sahibpreet Kaur (Jan 24 2020 at 07:35):@Sean I have created a Trello board for the feedback/changes to be made in the chess tutorial and sent an invitation to brlcad@gmail.com.
Sean (Jan 25 2020 at 05:28):@Sahibpreet Kaur I did see and signed up. Interesting (and organized) approach for addressing all of the feedback. I like it!
Sean (Jan 25 2020 at 05:30):One suggestion I would add to the list from a development and long-term management side of things would be to convert the document to a form that can live in the main source repository. Even better if it can be fully generated by it.
Sean (Jan 25 2020 at 05:30):That will help it stay up to date as well as give us a mechanism for collaborating together on it, for tracking who makes what changes, why changes are made, and more.
Sean (Jan 25 2020 at 05:31):If that's something you'd like to work on, I can give you some pointers, otherwise, it can get added to the Trello cards for someone to work on soon.
Sean (Jan 25 2020 at 05:35):The general idea with the existing setup will be to encode the document as Docbook XML in doc/docbook/lessons, possibly as a chess.xml or chess/ subdir
Sahibpreet Kaur (Jan 25 2020 at 06:39):I like this idea too! Can we discuss more about it?
Last updated: Jan 10 2025 at 00:48 UTC