Historic: ProjectStatus_2011_08_26

TOC(ProjectList,ProjectStatus*,titleindex)

#!rst

--------------------------------------------------------------------------------
Status for the Alternate Streams Project: 19 Aug 2011 - 26 Aug 2011
--------------------------------------------------------------------------------


Summary
=======

    Pending of acceptance tests and resolve the email issue

What's done
===========

    The beta server is available and updated on http://beta.wgchairs.yaco.es

What's next
===========

    Allow the community to test over the beta server.

Time plan
=========

    When acceptance ends we'll end the project.

Problems and Possibilities
==========================

    I hope that no great problems arise during acceptance :)


--------------------------------------------------------------------------------
Status for the ID Tracking Project: 19 Aug 2011 - 26 Aug 2011
--------------------------------------------------------------------------------


Summary
=======

    Still working on notifications

What's done
===========

    Beta server with redesigned database working on beta.community.yaco.es

What's next
===========

    Finish notifications.

Time plan
=========

    2 Sept. Finish development and start acceptance

Problems and Possibilities
==========================

    Nothing new.

--------------------------------------------------------------------------------
Status for the DB Conversion Project: 19 Aug 2011 - 26 Aug 2011
--------------------------------------------------------------------------------


Summary
=======

Finished liaison, started on porting wgchairs.

What's done
===========

Finished writing tests for liaison and porting the forms, fixing some
details and bugs. Worked a little bit on adding role overview to the
list of groups in admin, did a new test import run and fixed some
things, also spent some time contemplating states and looking into
dbsettings.

Then started on wgchairs/, so far half-way through delegate
management, adding tests as I go along; importing data was easy, just
a new role.

What's next
===========

Fix rest of delegate management, then tackle the rest of the of the
management interface, shepherds and workflows, the latter will require
some modeling, as we've discussed. I'll pick up the discussion again
when I get to the modeling.

Time plan
=========

Progressing nicely.

Problems and Possibilities
==========================

The wgchairs code looks a bit odd at places. In most places it's
absolutely fine, and not a big problem, but I'm not really happy about
the way everything is showed into the forms, as if views aren't
allowed to deviate from the simplest "if method = post: validate and
save form". It makes it hard to figure out what's happening, e.g. I
got quite a shock when I discovered that the innocently looking
delegate management view is actually triggering a long string of
somehow related forms. Phew. It was the same with liaison. I've
removed a little bit of code, but otherwise just did the changes
necessary for the port; now there are tests, it's probably a bit
easier to refactor it later on, though.


Ole

--------------------------------------------------------------------------------
Status for the Rfc-ed/IANA Sync Project: 19 Aug 2011 - 26 Aug 2011
--------------------------------------------------------------------------------


Summary
=======

Preparation for sending a detailed proposal to IANA/RFC-editor

What's done
===========

I wasn't in on Friday, but I am preparing the proposal, and will send it 
at the end of the day. I'll send it to you (with a couple of questions), 
and then we can send it to IANA/RFC-editor with any modifications you 
might have.

What's next
===========

Tomorrow, I'll begin implementing the minor changes which can be made 
without interaction with IANA/RFC-editor (e.g. AUTH48 links, etc.)

Time plan
=========

Given feedback from IANA/RFC-editor this week I should be able to have 
things wrapped up by the end of next week.


Problems and Possibilities
==========================

Nothing, so far.

--------------------------------------------------------------------------------
Status for the WG Charter Tool Project: 19 Aug 2011 - 26 Aug 2011
--------------------------------------------------------------------------------


Summary
=======

Functionality as in RFC. Ole's suggestions/corrections implemented.


What's done
===========

Ole had some corrections/suggestions which I implemented. More thorough 
testing, some template clean-up, and some stylistic changes. I also 
reset the beta.iola.dk:10003 server so that is uses the lastest version.


What's next
===========


Up to you.

--------------------------------------------------------------------------------
Status for the Xml2rfc V2 Project: 19 Aug 2011 - 26 Aug 2011
--------------------------------------------------------------------------------


Summary
=======

Making progress on the GUI application and did a almost final batch test and error analysis on the command line application. Please, let me know when we should plan to send the second milestone for completion of the command line tool.  Thanks Henrik!



What's done
===========

- Batch testing & error analysis
- Some minor bugfixes to parser/writer algorithms based on some of these results
- Improvements to GUI based on tonys feedback (prompt on unsaved XML document, better error messages for invalid references)
- Application exits with error code now
- Work done on help documentation for GUI (not connected to application yet, so we have not pushed this into the SVN repo yet)


What's next
===========

Continue working on the GUI application and work adding full installers to each platform.


Time plan
=========

I would imagine that over the next month or so, the GUI application will get wrapped up as we respond to feedback on the list, make small changes, and introduce the full installers.


Problems and Possibilities
==========================

a) The web version invoking xml2rfc2 is having issues resolving references. Josh agrees with tony that it is a permissions problem trying to create the cache.  We're looking into how to handle this; the current plan is to throw a warning if no valid write_cache directory can be found, and load the document without caching.

b) In response to your latest email about the problem installing the CLI tool under OSX, it seems as though the python package manager wants to compile the LXML library on the client machine.  If development tools are not installed on the client machine, which we believe is the case here, then it will fail.  Our GUI installers will, of course, be distributing these libraries as binary packages.  As far as installing the CLI from the python package, we're not sure if it is possible to default to a binary version of libxml2 but we will look into this this week.