Collin Fair the main developer wrote most of the code during his first year of undergrad. I contacted him and he is happy with contributions. He was very responsive. This is worth mention as not all the communities are easy to contact with straight away.
Few things he thought might be worth doing:
If they want to write fresh code with a minimum of legacy, there are a number of often-requested new services like Runtastic (https://github.com/cpfair/tapiriik/issues/95), MovesCount (https://github.com/cpfair/tapiriik/issues/68), etc. that would be quite popular if implemented. This is just a matter of following the pattern of the existing services.
If they want pure legacy-software-maintenance experience, the Dropbox integration is currently running using an API that's scheduled for shutdown this coming summer, and at some point needs to be rewritten for the new Dropbox API. I was thinking about finally pulling in https://github.com/cpfair/tapiriik/pull/93 at the same time, so other cloud storage platforms like Google Drive could be snapped in more easily.
And, finally, if they want a sisyphean task with no easy way to prove success, any of the "X data not syncing properly from service Y to Z" issues on Github would be a good fit.
First things first, in order to contribute we first need to find a project.
I suggested https://github.com/cpfair/tapiriik
Collin Fair the main developer wrote most of the code during his first year of undergrad. I contacted him and he is happy with contributions. He was very responsive. This is worth mention as not all the communities are easy to contact with straight away.
Few things he thought might be worth doing:
If they want to write fresh code with a minimum of legacy, there are a number of often-requested new services like Runtastic (https://github.com/cpfair/tapiriik/issues/95), MovesCount (https://github.com/cpfair/tapiriik/issues/68), etc. that would be quite popular if implemented. This is just a matter of following the pattern of the existing services.
If they want to look more into the underlying architecture, stuff like https://github.com/cpfair/tapiriik/issues/208 (involving modifications to how fitness activities are represented internally) and https://github.com/cpfair/tapiriik/issues/290 (has non-trivial privacy/security & data storage considerations) might fit.
If they want pure legacy-software-maintenance experience, the Dropbox integration is currently running using an API that's scheduled for shutdown this coming summer, and at some point needs to be rewritten for the new Dropbox API. I was thinking about finally pulling in https://github.com/cpfair/tapiriik/pull/93 at the same time, so other cloud storage platforms like Google Drive could be snapped in more easily.
And, finally, if they want a sisyphean task with no easy way to prove success, any of the "X data not syncing properly from service Y to Z" issues on Github would be a good fit.