8. Response Posts (5-6)

Topic 5 – User Testing & Community Feedback

What methods can you make use of for testing your code and hearing feedback on your contribution? How do you communicate with your community and audience while developing work in progress or sharing the final outcome?

As mentioned in earlier blog posts, most of the testing and iterative development for my project, both code and curriculum-wise, happened during the teaching itself; it served as a kind of test flight for the first round of improvements. When I explained basic concepts and the student didn’t understand, they would ask for clarification, and I would add comments live. If they felt my speech needed to be clearer, I would adjust my delivery in real time. When they were confused, I walked them through the material step by step. This immediate feedback loop helped shape the content quickly and responsively. I also took note of longer-term feedback to implement when I have more time, such as restructuring and extending the curriculum, as I could not do them now itself. I also ensured to show the student the changes they had proposed, so that they know their feedback was taken into account and implemented as a priority.

For longer-term feedback from the student collected after classes, and in line with my own goals, I have several points for future improvement. These points are also informed by several resources on community feedback. I wanted to implement this soon, so I could initiate a PR with a more professional project next time.

Improvement Plan

  1. Improve Communication for Teaching
    • I was told I mumble and skip stuff sometimes, or assume a knowledge basis students don’t have, so I strived to improve this for each lesson, and will continue to do so.
  2. Expand Participation
    To increase peer feedback and engagement, I want to invite more animation students to join this collaborative learning process, encouraging a diverse range of perspectives and active involvement, as more critique = more opportunity improvement.
  3. Encourage Peer Critique
    I want to foster a supportive environment where students actively engage and feel free to say any shortcomings of this project. To do this, I may use Padlet as a platform where students can give feedback anonymously if they prefer. As well as this, students should be able to join dedicated discussion channels around the workshop, like on Discord or Slack, so we can get together and discuss next steps. This safe space will encourage honest and constructive critique without fear of judgment. In the very next lesson, I will show students how their feedback was implemented or explain the reasons for rejecting certain suggestions, reinforcing the value of their input.
  4. Gauge Student Engagement and Motivation
    After each class, I plan to measure key indicators of student engagement using Google Forms or Padlet:
    • How motivated students feel to complete their homework assignments
    • How well they understand the material presented, and what additional support or resources could enhance their comprehension
    • How much they retain and can recall from the example demonstrations
  5. Assess Understanding and Retention
    To deepen this insight, I will ask student/s to recall examples from class during follow-up sessions. This will help me gather heuristics on their knowledge retention and comprehension, as I noticed that they had usually forgotten what happened in the previous lesson by the time the next one came. This can be at the very start of the next lesson. For this, regularly scheduled classes is also important.
  6. Standardise Lesson Timing & Duration
    • This was of course important, as long gaps meant forgetting material and unfamiliarity, short gaps make i overwhelming, long lessons are no fun, and too short means there are few takeaways.
    • I did not have this in place yet as it was still in development stages, but the curriculum on the site will be changed accordingly once this has been decided.

On the p5.js community side, from my research, the usual process is that community reviewers either provide feedback or reject the contribution. In the latter case, I would follow up through the appropriate channel to understand why and improve accordingly.

References

https://docs.github.com/en/github/site-policy/github-community-forum-code-of-conduct

Resources

Topic 6 – Contributing Beyond Code

What other forms beyond code can complement your contribution? How can you improve the outreach and accessibility by considering other non- code related contributions?

Beyond code, there are many non-technical contributions that can significantly enhance my project’s outreach, accessibility, and overall impact. I could create video tutorials to support different learning styles and work on refining the user interface and visual design to make the platform more intuitive, as I have seen people do on the p5.js Education Resources website. I am interested in doing this, but only once I am confident in my class materials – when I improve them, and extend them, and gain feedback until feedback is few, I could work on this.

Accessibility improvements; such as adding screen reader support, alt text, and keyboard navigation; would make the project more inclusive. I can also contribute through more thorough documentation, more engaging website with more depth, user guides, and translations to reach a broader audience, or even one day, making my project a big enough community such that others can contribute their translations. Engaging with the student community through Q&A sessions, feedback forums, and social media updates can also create a sense of collaboration and belonging. Additionally, I could run user testing to identify usability issues and incorporate their feedback. Developing branding materials, and even integrating the project into lesson plans can further broaden its reach and value. These non-code efforts are vital to ensuring the project grows in a sustainable, inclusive, and community-driven way.

I aim to make this project more professional and with better outreach, step by step. I found some good suggestions from opensource.stackexchange, some of which I tweaked for relevance, namely:

  1. Try looking for a forum which have people who can be a part of this workshop, and ensure it is free, with clear rules for sign-up and partaking.
  2. Writing a blog post illustrating my project in more detail, and attempt to publish it.

Resources

https://dev.to/mattdark/a-non-coders-guide-to-open-source-contributions-13ji

https://opensource.stackexchange.com/questions/2933/how-can-i-grow-my-open-source-project#:~:text=The%20average%20end%20user%20isn,a%20site%20for%20the%20project.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *