Movement Analysis Code for Everyone

[dblana]

Project Lead:
dblana

Mentor:
ottagit

Welcome to OL7, Cohort C! This issue will be used to track your project and progress during the program. Please use this checklist over the next few weeks as you start Open Leadership Training 🎉.

---

Before Week 1 (Jan 30): Your first mentorship call

• Complete the OLF self-assessment (online, printable). If you're a group, each teammate should complete this assessment individually. This is here to help you set your own personal goals during the program. No need to share your results, but be ready to share your thoughts with your mentor.
• Make sure you know when and how you'll be meeting with your mentor.

Before Week 2 (Feb 6): First Cohort Call (Open by Design)

• Complete Assignment 'Write Your Vision or Mission Statement'. Leave a comment on this issue with your draft vision statement & be ready to share this on the call.
• Watch 'Mozilla & Working Open'.
• Check the Syllabus for notes and connection info for all the cohort calls.

Before Week 3 (Feb 13): Mentorship call

• Look up two other projects and comment on their issues with feedback on their vision statement.
• Complete your Open Canvas (instructions, canvas). Comment on this issue with a link to your canvas.
• Start your Roadmap. Comment on this issue with your draft Roadmap.

Before Week 4 (Feb 20): Cohort Call (Build for Understanding)

• Look up two other projects and comment on their issues with feedback on their open canvas.
• Pick an open license for the work you're doing during the program.
• Use your canvas to start writing a README, or landing page, for your project. Link to your README in a comment on this issue.

Week 5 and more

• Create a repository for your project. New to GitHub? You can fork our templates.
• Add Contributing Guidlines
• Add a Code of Conduct
• Submit your project to Mozilla Pulse, add the tag #mozsprint
• Invite new contributors to into your work!

This issue is here to help you keep track of work as you start Open Leaders. Please refer to the OL7 Syllabus for more detailed weekly notes and assignments past week 4.

[dblana]

Draft mission statement: I am working with clinicians and researchers in motion analysis labs to share coding resources, so that they can improve and accelerate their analyses.

[dblana]

Open Canvas

[dblana]

Roadmap

The use of computer code can greatly benefit clinical movement analysis. It can save time and reduce errors by automating routine tasks, and it can produce new insights by enabling complex calculations. However, not everyone has the skills or time to learn how to develop their own code.

We are proposing to develop a free online platform for sharing code, which will also include step-by-step tutorials on how to develop and use it. People with technical skills will be able to collaborate, create new tools, and easily share them among all motion analysis labs. Beginners who are keen to develop coding skills will find a library of tutorials and example code to support their learning. Researchers and clinicians working on motion analysis who would like to use code but do not have time or interest in developing it themselves, will be able to easily find relevant resources, with instructions and examples of use.

Milestone: Clinical Movement Analysis Society (CMAS) annual meeting
It would be great to have a website by the CMAS annual meeting, April 25-26 2019!

• Create github repository
• Add readme
• Add code of conduct
• Add contributor guidelines
• Add FAQ

Milestone: Example code
The example code we will provide initially will be in Python and focus on how to work with C3D files (the de facto standard for movement analysis data).

• Add Python code to extract different types of information from C3D files and visualise it
• Add tutorial to explain the code
• Add a ready-to-use application: Python code to calculate the gait profile score and movement analysis profile

Milestone: Workshop for CMAS labs
We will have a one-day coding workshop for UK CMAS labs (sometime in the summer 2019). We already have funding for one travel grant per CMAS-accredited lab, to encourage participation from as many members of the CMAS community as possible.

• Arrange speakers
• Create workshop material

[annefou]

Nice roadmap. I still need to finalize mine... I think I'll steal your idea to have a workshop as a milestone! That's a very motivating target!

[ottagit]

@dblana Good job on both your open canvas and project roadmap; I like the clarity and precision of the former, and just enough detail provided in the roadmap at this stage of the project. Thanks @annefou for your feedback. Hope to see more interactions on this issue 👍 👍

[mrpandey]

That's a good mission statement - clear and concise. And that's an even better roadmap! I am looking forward to contribute if my skill-set matches the requirements.

[ottagit]

@mrpandey many thanks for your feedback. Would be glad to have you on board @dblana

[theo-bech]

Very concise vision statement, and a great project overall! Agree with @annefou, the workshop as a milestone is an excellent idea.

[balicea]

Mission statement is very to the point. A few clarifications:

1. under "key metrics": what's more important in terms of code shared, quality or quantity? Are there annotation or formatting standards that the community must meet?

2. under "solution": will your tutorials be stylized as a Wiki, a set of YouTube videos, or as a more standard technical doc? What is most accessible to your community?

[dblana]

Mission statement is very to the point. A few clarifications:

1. under "key metrics": what's more important in terms of code shared, quality or quantity? Are there annotation or formatting standards that the community must meet?
2. under "solution": will your tutorials be stylized as a Wiki, a set of YouTube videos, or as a more standard technical doc? What is most accessible to your community?

These are excellent points! 😃

1. On quality vs quantity: I am keen to get as many people involved as possible, and most of them do not have any formal computer science training... so I guess quantity is more important. But we should include guidelines for writing good software that can be shared, thank you for pointing that out!

2. My thought was that the tutorials would be simple documents, because I don't know how to make YouTube videos myself - but other contributors might! I will add that to the list of ways people can contribute 👍

[dblana]

Busy week, but I managed to make a repository for the project, and started the README.md file. A lot of construction signs 🚧 everywhere...

[annefou]

Nice! I also created my README.md but should definitely use this construction sign 🚧 (Thanks I did not know it!!!) to show it is not finalized.

[dblana]

So many emojis... https://gist.github.com/rxaviers/7360908

[annefou]

👏 So cool!!! Thanks for sharing!

[theo-bech]

A very clear open canvas, it helped me figure out how to make mine more comprehensive!

[scottkildall]

Wow, good work here. At first I got a little tripped up in the specifics, e.g. does "clinical movement analysis" mean? Then, when reading more deeply, it's all there. So, perhaps an example in the ReadMe for a more general audience, if you want to serve that community (which is where you're getting feedback) would be helpful. Thanks!

[dblana]

Wow, good work here. At first I got a little tripped up in the specifics, e.g. does "clinical movement analysis" mean? Then, when reading more deeply, it's all there. So, perhaps an example in the ReadMe for a more general audience, if you want to serve that community (which is where you're getting feedback) would be helpful. Thanks!

Thank you! That's a great idea 👍

[dblana]

@scottkildall As I am learning how github works, I added your suggestion as the first issue: https://github.com/cmasuki/open-code/issues

[dblana]

I updated the contributing guidelines and I'd love some feedback! I've tried to make it easy enough for beginners, but not too long... Is there sufficient information there to get people started? How much info should I provide about Git? 😬 Any comments/suggestions would be greatly appreciated! 🙏