[mlpack] mlpack video meeting planning, next week

[Ryan Curtin]

Hello there everyone,

At the beginning of the summer I suggested that we should do more
regular video meetings, and everyone seemed to think this would be a
good idea.  We did one and I think it went well, but then unfortunately
my summer got away from me and I couldn't find the time to organize any
other ones.

Finally now I've recovered my schedule, so let's have another one!

This time we can use a free Zoom meeting, which will be able to handle
more people.  I think this will work a lot better---definitely it will
be better than Jitsi, and it should also be better than Hangouts which
had a 10 person limit.

The first thing to do is to find a time where everyone would like to
join.  So I set up a whenisgood:

http://whenisgood.net/ygz8psj

Since we are all over the world, I'll have to pick a "least bad" time,
so I'll do my best to make sure that everyone who wants to attend can
attend.  I'll pick a time for the meeting later on Friday (Aug. 23rd).

The second thing to do is to figure out what to talk about.  Here's an
idea for things to discuss:

 - How is everyone doing? :)  What is everyone up to?

 - mlpack development update
    * I'll put together some slides about what's happened since the last
      meeting, just like I did last time, and highlight developments and
      changes

 - Release planning:
    * what should go into the next release
    * when should the next release happen
    * should it be mlpack 3.2.0, 3.1.2, etc.?
    * what are the states of open PRs, and what do we want to do with
      them?

 - GSoC update/retrospective:
    * we can talk about the status of each project and what we're hoping
      for moving forward

 - Open mic topics (just some ideas):
    * What should we change (if anything) about how we develop software
      as a group?
    * Is there anything we could improve?  Is everyone having a good
      time?
    * Are there any big problems that we are overlooking that need to be
      addressed, but aren't on Github as issues?
    * Are there any big problems that we are overlooking that *are* on
      Github as issues?

If there's anything that I've overlooked there for an agenda, just let
me know!  It is easy to add. :)

Looking forward to seeing all of you again!

Thanks,

Ryan

-- 
Ryan Curtin    | "Long live the new flesh."
ryan at ratml.org |   - Max