Historic: ProjectStatus_2011_09_09

TOC(ProjectList,ProjectStatus*,titleindex)

#!rst
--------------------------------------------------------------------------------
Status for the DB Conversion Project: 02 Sep 2011 - 09 Sep 2011
--------------------------------------------------------------------------------


Summary
=======

Got stuck on state decision on wgchairs, started up on submit app instead.

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

Not much to report, added a test to submit, changed the role model as
discussed. Rest of week went into unrelated (IOLA) issues.

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

Planning to work on submit until we get a decision on state.

Time plan
=========

Not much progress.

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

Nothing interesting.


Ole

--------------------------------------------------------------------------------
Status for the Rfc-ed/IANA Sync Project: 02 Sep 2011 - 09 Sep 2011
--------------------------------------------------------------------------------


Summary
=======

Major functionality there. Minor stuff and testing are left. Some parts 
depend on Ole's current work assignment.

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

IANA/RFC-editor authorization (for updating), bugtracker (discrepancies 
feature), some tests, events recorded in History log.

Some questions:

Have I correctly read the evaluation message in the following as being 
the ballot writeup?

"Information providing the status of the IANA review (one of the 5
  substates listed above) should be included as part of the evaluation
  message (sent to the IESG) so that IANA can determine if, and what,
  further action is required."

Regarding section 2.1 (RFC Publication): I read this (possibly wrongly) 
as: make a history entry for when the (newly assigned) RFC number 
appears on iana's protocols page (http://www.iana.org/protocols/). Is 
this correct?

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

New fields on Documents, some notifications, and testing.

Some more questions:

What is meant by Publication Status (as defined in [RFC2026]) (in 
section 4.2)? I read RFC2026, but there is no mention of publication 
status. Is it just the iesg_state?

Do you have any additional checks to add in section 4.3?

Time plan
=========

The alternate streams stuff (section 4.2.2) is part of Ole's current 
work assignment. Additionally, he also has to port /submit/, in which I 
need to add some changes for when a new revision is submitted 
(notification to IANA and so forth).

Except for these two parts I'll have the rest finished on wednesday. I 
implemented the communication with IANA as suggested in previous status 
update. The parse function is split from the rest of the functionality, 
so any changes needed would be quick to implement (if e.g. you prefer XML).

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

I'm having problems committing. I get the following error:

/home/svn/tools/ietfdb/hooks/pre-commit: 62: 
/home/svn/tools/ietfdb/hooks/pre-commit: Syntax error: "(" unexpected


--------------------------------------------------------------------------------
Status for the WG Charter Tool Project: 02 Sep 2011 - 09 Sep 2011
--------------------------------------------------------------------------------


Summary
=======

Demo site updated, waiting for feedback.


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

I updated the demo site with the changes noted in the last status mail. 
I didn't proceed with the changes in the charter modelling (separate 
Document objects), yet.


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

More changes based on feedback. Past wednesday I'll have more time, and 
the changes are quick to implement, so we can have (if needed) a new 
demo up by the end of the week.

Time plan
=========

Depends on changes.

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

None.


--------------------------------------------------------------------------------
Status for the Xml2rfc V2 Project: 02 Sep 2011 - 09 Sep 2011
--------------------------------------------------------------------------------


Summary
=======

Command-line application is complete unless we hear back from Tony soon. And the GUI app is almost complete.


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

We're finished with the command line program and waiting to hear back from Tony about the caching problem on his web server. 

The GUI program is mostly complete and we are currently testing it on different environments.


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

What we need to do next with the command line program is put it in the python package index. I can't remember if you said you'd like us to handle this submission or whether you wanted to do this.

The GUI will be complete by the end of this week. We are planning on testing on as many OS installers as possible on various machines and also to create a Fedora installer.


Time plan
=========

(see above)


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

None