Community Bonding

[Lucas van Dijk]

Hi Guys!

Awesome, thanks for accepting me into the Google Summer of Code! I'm really excited right now! I've got a big presentation today, so this email will be a bit short, but things I would like to do this month:

- More detailed breakdown of milestones and tasks, and open issues for each task in my Github branch of Vispy
- Already start playing with the Vispy visual system, and try to make a start with arrows (which implies reading a lot of code and documentation)

What will be the main communication channels besides the mailing list? Do you guys have an IRC channel or something?

Regards,
Lucas

[Cyrille Rossant]

Hi Lucas,

Congrats! :)
We have a gitter chat room at https://gitter.im/vispy/vispy

Best,
Cyrille

> --
> You received this message because you are subscribed to the Google Groups
> "vispy-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vispy-dev+...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vispy-dev/6592d143-50db-4c05-abb3-a4e43c6b0e1e%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[jérémy viau trudel]

Hi Lucas,

Congratulation! I like your idea of breaking down you work and planning it using githubIssue's milestones and issues. I'd like to see how you work with it. What is your github name?

Best,

jvtrudel

[Lucas van Dijk]

My github username is sh4wn [1]. I'm planning to start creating the issues this thursday or friday, so you'll not find anything there yet!

[1]: https://github.com/sh4wn

Op zondag 3 mei 2015 18:40:47 UTC+2 schreef jérémy viau trudel:

[jeremy viau trudel]

Thanks Lucas, it’s noted. 

--
You received this message because you are subscribed to a topic in the Google Groups "vispy-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vispy-dev/SWRxW4V8jyE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vispy-dev+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vispy-dev/c2a8a315-50bf-41a4-932e-89fafe6390fb%40googlegroups.com.

[Lucas van Dijk]

Ok, I've added most tasks as Github issues [1], although the descriptions are often still a bit vague. These are of course subject to change as we progress through the GSoC, encountering bugs, develop new ideas, etc. But these will help tracking progress, and gives a nice overview what to do for the coming months.

I think I'll create a PR for each milestone on my own Github fork, so each milestone has a central point where we can discuss API's, implementations etc.

I'm currently working quite hard to finish my study assignments as fast as I can, but some of these assignments are a bit more work than expected, so I may need a few days off in the first official GSoC week, and maybe even the second week. But I'll work a few days extra in the weekends to make up for that.

[1]: https://github.com/sh4wn/vispy/issues?q=is%3Aopen+is%3Aissue

Regards,

Op zaterdag 9 mei 2015 22:45:27 UTC+2 schreef jérémy viau trudel:

[Eric Larson]

That looks like a good set of issues to me. It's good to have those for your own internal tracking, but it would be better as you go to open one issue at a time on the main `vispy` issue tracker, or open PRs from your fork into the main repo, so that everyone can comment there. Otherwise people might not get notified about discussions.

Eric

--
You received this message because you are subscribed to the Google Groups "vispy-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vispy-dev+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vispy-dev/40bb8b98-4468-4251-bdf8-5cc946f34a58%40googlegroups.com.