Yeah -- I was thinking we could start with the list of people who would
like to attend and then try to schedule (possibly using Doodle) around that.
So, to all: let us know if you would like to attend!
Mike
On 08/02/2013 04:36 AM, Phil Elson wrote:
Sounds like a good idea to me.
In terms of when - I think the IPython guys have picked a good time
(10am US Pacific time, or 5pm GMT/UTC) to have the meeting to maximise
the attendance from the Americas and Europe, though I appreciate that
no time is perfect for everybody. For instance, I know Eric being in
Hawaii–Aleutian Time Zone that time would mean a 7am start, and for
JJ, should he wish to join in, it would be a 2am meeting... (for a
clock of the places that may need consideration see
http://www.timeanddate.com/worldclock/converted.html?iso=20130802T17&p1=0&p2=1358&p3=235&p4=263&p5=137&p6=103).
Did you want to put a date on it Mike? How about we go for a week on
Tuesday, say the 2013-08-13 17:00Z (in your time:
http://goo.gl/OnWHBq) - though I'm open to moving it, if that doesn't
fit with some of the core contributors who would like to attend. If
anybody who knows they would like to attend could notify us here
(along with their time zone), we could also try to optimise the time
to reduce unsociable hours :-) though we have to acknowledge that
there is no such thing as the perfect time...
Cheers,
On 1 August 2013 19:58, Michael Droettboom <md...@stsci.edu
<mailto:md...@stsci.edu>> wrote:
(Apologies for cross-posting).
matplotlib has a dire need to improve its continuous integration
testing. I've drafted MEP19 and solicited comments, but there hasn't
been a lot of feedback thus far.
As an alternative to mailing list discussion, where this sort of
upfront
planning can sometimes be difficult, I'm considering holding a Google
Hangout in the next few weeks on the subject. It's ok to participate
even if you don't have the time to work on matplotlib -- I would also
like feedback from advice from those that have configured similar
systems for other projects. matplotlib's needs are somewhat more
complex in terms of dependencies, cpu, ram and storage, so we're
pushing
things pretty far here.
If there's enough people with an interest in participating in the
discussion, I'll send around a Doodle poll to find a good time.
Mike
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
<mailto:Matplotlib-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
