Research Hackdays Zurich

[Bastian Greshake]

Hey there,

some of you might already know that I’ll be at the Research Hackdays in Zurich at the beginning of June (http://make.opendata.ch/wiki/event:2015-06). The organisers would like me to host a group (if people are interested in joining me) to work on/with openSNP/personal genomics data in general. 

The whole thing will be ~1 1/2 days, so there isn’t time for too large projects. But do you nevertheless have ideas of what we should tackle there? I know, Helge would like to get the test coverage up, but I do have some doubts on whether people would be willing to work on that, as it’s not shiny and there’s little to show at the end of the two days. ;-)  

So maybe we could do something fun and lure people into openSNP and maybe they will be willing to write tests later on? :D

Cheers,

Bastian

[Philipp Bayer]

It may be a good chance to make the old "stats" page -
https://github.com/gedankenstuecke/snpr/issues/102

It's not hard as all the numbers are there, there are many libraries to
do most of the plotting for you (even D3.js?), and you'll hopefully have
something nice and shiny to show at the end.... But this is against "no
new features until X% test coverage"

> --
> You received this message because you are subscribed to the Google
> Groups "SNPr development" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to snpr-developme...@googlegroups.com
> <mailto:snpr-developme...@googlegroups.com>.
> To post to this group, send email to snpr-dev...@googlegroups.com
> <mailto:snpr-dev...@googlegroups.com>.
> Visit this group at http://groups.google.com/group/snpr-development.
> For more options, visit https://groups.google.com/d/optout.

[Samantha Clark]

Or make the model for linking family members somehow on profile pages? :D :D

To unsubscribe from this group and stop receiving emails from it, send an email to snpr-developme...@googlegroups.com.
To post to this group, send email to snpr-dev...@googlegroups.com.

[Bastian Greshake]

On 26 May 2015, at 14:31, Samantha Clark <iov...@gmail.com> wrote:

Or make the model for linking family members somehow on profile pages? :D :D

You mean similar to Facebook’s family feature? So in the end we could pretty quickly find out where the expected relatedness != stated relatedness? ;-)

On Tue, May 26, 2015 at 5:12 AM, Philipp Bayer <phili...@gmail.com> wrote:

It may be a good chance to make the old "stats" page -
https://github.com/gedankenstuecke/snpr/issues/102

Also see https://github.com/gedankenstuecke/snpr/issues/166

It's not hard as all the numbers are there, there are many libraries to
do most of the plotting for you (even D3.js?), and you'll hopefully have
something nice and shiny to show at the end.... But this is against "no
new features until X% test coverage"

I don’t think that in 1 1/2 days we will necessarily build something that goes straight into openSNP, but working on some things that are fun to build and nice to look would be enough, so it’s not strictly against the proposed rule ;-)

What I did think about was making the Fitbit graphs a bit nicer and maybe adding similar features for two more trackers: Jawbone’s Up and Misfit’s Shine. 

Reasons for that: 

1. They both seem to have a subscription API similar to the one Fitbit offers, which would make it useful for production if it ever comes to it

2. Implementing it shouldn’t be too hard and is a nice exercise using OAuth etc. 

3. At the end you can again display data in a nice way

4. (I do happen to have a Shine & Jawbone Up, so we already would have real “test” data as showcases)

Cheers,

Bastian

[Helge Rausch]

> But this is against "no new features until X% test coverage"

How about we change this to "no decreasing of test coverage, ever"? If you only add tested code, coverage should increase, right? ;)

[Bastian Greshake]

Yep, sounds fine to me. :-) 

On 27.05.2015, at 12:01, Helge Rausch <he...@rausch.io> wrote:

> But this is against "no new features until X% test coverage"

How about we change this to "no decreasing of test coverage, ever"? If you only add tested code, coverage should increase, right? ;)

--