Historic: ProjectStatus_2011_09_16

TOC(ProjectList,ProjectStatus*,titleindex)

#!rst
--------------------------------------------------------------------------------
Status for the Alternate Streams Project: 26 Aug 2011 - 02 Sep 2011
--------------------------------------------------------------------------------


Summary
=======

In acceptance phase, but no comments from potential users.

Developer on vacation last week.

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

n/a

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

Wait for feedback.

Time plan
=========

Depends on acceptance tests.

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

No reaction from users.


--------------------------------------------------------------------------------
Status for the ID Tracking Project: 26 Aug 2011 - 02 Sep 2011
--------------------------------------------------------------------------------


Summary
=======

No change; developer on vacation last week.


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

n/a

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

Beta server deployment

Time plan
=========

Project to be ready for acceptance testing week of Sep. 19

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

Nothing to mention.


--------------------------------------------------------------------------------
Status for the DB Conversion Project: 09 Sep 2011 - 16 Sep 2011
--------------------------------------------------------------------------------


Summary
=======

Working on submit tool, still stalled on wgchairs on feedback from you
on how to deal with states.

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

Ported more of the submit views/forms, expanding tests. Fixed name
handling in import to use full name and did a new test run, fixing
some problems. Revamped submit author handling slightly to allow
editing full name properly, also put some stuff in a Javascript file
instead of stuffing it inside inline attributes.

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

Get a decision on state management, finish submit views.

Time plan
=========

Not much further with wgchairs, on the other hand the submit tool is
beginning to look good. Actually, I think most of the work may be
writing more tests to ensure I got all views covered.

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

Now that I've ported the author lookup in the submit tool, it's
evident there are some holes in the corner cases of automatic
registering of authors from the drafts. For instance, two different
persons with the same name or same email address will be registered as
one (it seems unlikely but plausible), or similarly if an author has a
new email address and spells the name differently, he/she may end up
as a different person. Not that it probably matters much.

Another comment on Email: there's an "active" field on it. I'm
currently using it as a "where do I email this guy if I don't have a
better clue from the context". There issue here is, what do I do when
I create a new email address - is it active or not? I'm currently
importing email addresses from people who have an account as active,
and treat the rest (authors) as not active. Hm, should probably check
that I actually do that properly.

Of course, one could also just treat them all as active. But I think
the problem is that we generally don't get a notice when an address
stops being active, so it's probably easier to try to track which one
is for sure active rather than having to inactivate them manually.


Ole

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


Summary
=======

Except for dependencies the changes are as in the RFC.

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

All the requested functionality in the RFC, except for the following:

Changes relating to alternate stream (since this is part of Oles current 
work)

Changes relating to /submit/, i.e. events occuring on new_revision 
(since this hasn't been ported yet).

and these two 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
===========

Implement the above when possible, and connect with IANA.

Time plan
=========

The remaining work shouldn't take too long. The changes in /submit/ are 
just some DocEvents, and the alternate streams stuff doesn't appear to 
be too heavy either.

Best,
Martin

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


Summary
=======

Feedback from mailing list. Most changes implemented.

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

A number of changes based on feedback on the mailing list. UI 
adjustments, some workflow changes (abandon effort button, etc.), 
Editing charters without uploading file.

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

Most of the changes have been implemented. The ones missing are: how to 
show the current revision when abandoning effort (RjS had a suggestion 
here), and ballot issuing.

Time plan
=========

I expect to finish the above today. Any eventual additional feedback 
would also be handled asap during this week.

Best,
Martin

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


Summary
=======

With the final installer almost complete, we will begin cross-platform testing over the next few weeks. At that point, we will respond to any feedback that your team members might have.


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

Help documentation system is complete for the GUI application.

Installers. Currently we have installers complete for Windows, OSX, Debian/Ubuntu. 


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

1) Finish the Fedora/Redhat installer.

2) Perform some extensive cross-platform tests. 



Time plan
=========

Our goal is to finish these cross-platform tests the week of 9/26.



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

Still some open questions:

1) Is there any official text or statements the IETF would like to include on the about page, and if there are any icons and/or logos to be used for this project?

2) 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.

Thanks!

Mike