.. title: Dev call March 30th, 2011
.. slug: devcall_20110330
.. date: 2011-03-30 12:15:54
.. tags: miro, work


<p>Miro 4.0 status (<a href="http://bugzilla.pculture.org/roadmap.cgi?product=Miro&target=4.0">roadmap</a>)</p>
<ul>
<li>lots of flux in git-master, but the code is stabilizing
<li>working on metadata support, device syncing, performance enhancements,
  extensions, streaming to other devices (ipad, ...), ...
<li>working on project infrastructure: wiki, nightlies, nightly runs of
  unit tests, ...
<li>probably a release in May or June--we're working hard on it!
</ul>

<p>Will:</p>
<ul>
<li>Spent most of the time on BD.  Long drama, but it should be fine
  now.  I spent most of the time addressing privacy issues, but also
  did some restructuring as well.
<li>Worked on upsizing issues with conversions.  Pretty sure I have it
  fixed, but since the changes are pervasive, I want to do more
  testing.  I didn't have to do anything outlandish like I had feared last
  week, so that's good.
</ul>

<p>Paul:</p>
<ul>
<li>spent some time fixing Miro Guide issues, mostly django errors
<li>worked on P1 bugs, mostly ui stuff
</ul>

<p>Jonas:</p>
<ul>
<li>continued working on P1 bugs
<li>added support for hex-encoded magnet URIs
</ul>

<p>Geoffrey:</p>
<ul>
<li>working on P1 bugs, particularly ui bugs
</ul>

<p>Ben:</p>
<ul>
<li>working on P1 bugs
<li>finished up keyboard shortcut issues--should be pretty solid now
</ul>

<p>Janet:</p>
<ul>
<li>spent a bunch of time with sikuli tests and Miro
<li>worked on testing Universal Subtitles
<li>working on testing things and writing new tests so we continue to
  increase the regression tests
</ul>

<p>Order of business:</p>
<ul>
<li>Talked about where we're at with Miro 4.0.  Lot of newly created
  bugs over the last week, but we're pretty much done with new
  features.  Seems like we're just working on bugs now.  Getting close
  to a point where we could do a release candidate.

<li>git master is in pretty heavy flux right now and because of that
  nightlies are probably unstable--use them at your own risk.  This
  will sort itself over time when there are fewer massive changes
  being made.  If you're interested in testing, but don't want to test
  bleeding edge, then it's worth waiting until we hit the release
  candidate portion of the dev cycle.  We're currently thinking that'll
  be in a couple of weeks.

<li>Miro is developed by a community of people including you!  If you
  can't contribute your time and work to development, testing, and
  translations, please consider contributing funding
  by <a href="https://www.miroguide.com/donate">donating</a>.  Your
  money goes directly to ongoing development of Miro and related
  projects like <a href="http://mirocommunity.org/">Miro Community</a>
  and <a href="http://universalsubtitles.org/">Universal
  Subtitles</a>.
  See <a href="http://pculture.org/about/">http://pculture.org/about/</a>
  for more details on these projects.

<li>Did you know there's a Miro User Manual?  If you haven't looked at
  it yet, it's worth taking a look at.  You can find it
  at <a href="http://manual.getmiro.com/">http://manual.getmiro.com/</a>.
</ul>

<p><b>Bugzilla stats for Miro for the last week:</b></p>
<ul>
<li>80 bugs/feature-requests created
<li>3 bugs marked WORKSFORME
<li>3 bugs marked INVALID
<li>2 bugs marked ---
<li>12 bugs marked DUPLICATE
<li>2 bugs marked WONTFIX
<li>54 bugs marked FIXED
<li>2 bugs marked INCOMPLETE
</ul>