.. title: Dev call 8/25/2010 minutes
.. slug: devcall_20100825
.. date: 2010-08-25 11:16:09
.. tags: miro, work


<p>Miro 3.5 status (<a href="http://bugzilla.pculture.org/roadmap.cgi?product=Miro&target=3.5">roadmap</a>)</p>
<ul>
<li>working on fixing up video conversion issues
<li>working on cleaning things up
</ul>

<p>Miro Community 1.1.1 status (<a href="http://bugzilla.pculture.org/roadmap.cgi?product=Miro+Community&target=1.1.1">roadmap</a>)</p>
<ul>
<li>Miro Community 1.1 was released last week
<li>working on some bug fixes targeted for 1.1.1
</ul>

<p>Paul:</p>
<ul>
<li>pushed Miro Community 1.1 out to the new servers
<li>looking at moving the db to another machine
</ul>

<p>Ben:</p>
<ul>
<li>continued working on bugs for Miro 3.5
<li>implemented font selection for subtitles on Windows
</ul>

<p>Will:</p>
<ul>
<li>implemented the PCF bug triage Firefox addon
<li>worked on database startup failure problems
</ul>

<p>Janet:</p>
<ul>
<li>working on Windows installer things
<li>and other things
</ul>

<p>Order of business</p>
<ul>
<li>We talked a little about what Miro 4 will entail.  We're going to
  try to plan it out in a wiki rather than plan it out in Bugzilla
  because Bugzilla is difficult to use for iterative design.  When
  tasks become sufficiently defined, we'll move them to Bugzilla and
  start implementing.
<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://getmiro.com/userguide/">http://getmiro.com/userguide/</a>.
<li>Priority is being put on finishing development work on Miro 3.5.
  Any help with this would be huge.  There are a series of bugs on the
  roadmap that need to be fixed.  If you want to help out but don't know
  where to start,
  see <a href="http://getmiro.com/userguide/contributing.html">http://getmiro.com/userguide/contributing.html</a>
<li>If you can't contribute work, 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.
</ul>

<p><b>Bugzilla stats for Miro:</b></p>
<p>
  Lot's of bug churn this week in part because of focus on regression
  testing and because of the creation (and heavy usage of) the PCF bug
  triage Firefox addon.
</p>
<ul>
<li>20 bugs/feature-requests created
<li>3 bugs marked WORKSFORME
<li>1 bugs marked INVALID
<li>3 bugs marked DUPLICATE
<li>1 bugs marked WONTFIX
<li>12 bugs marked FIXED
<li>30 bugs marked INCOMPLETE
</ul>