Skip to content

Historic: ProjectStatus_2011_08_05

Robert Sparks edited this page May 1, 2023 · 1 revision

TOC(ProjectList,ProjectStatus*,titleindex)

#!rst

--------------------------------------------------------------------------------
Status for the Alternate Streams Project: 29 Jul 2011 - 05 Aug 2011
--------------------------------------------------------------------------------



Summary
=======

Code refactored to avoid group replication in stream model. Generic 
delegate system for streams almost finished.

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

Fixed group replication bug. 
http://trac.tools.ietf.org/tools/ietfdb/ticket/694

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

* Finish delegate system. The requirement tells that IAB chair must 
  be able to designate delegates. The implemented delegate system will 
  allow the chair of any existing stream (or future one) to designate 
  delegates in a stream.

* Add new states and delete the ones not needed. Update their 
  descriptions.

Time plan
=========

* 12 Aug: States updated to the last document revision
* 19 Aug: Authorization for IAB stream
* 22 Aug: Development finished and start acceptance

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

No problems at the moment.

--------------------------------------------------------------------------------
Status for the ID Tracking Project: 29 Jul 2011 - 05 Aug 2011
--------------------------------------------------------------------------------


Summary
=======

The user registration system is almost complete (only lacks the 
ability to write to the apache password file).

The application to manage lists of I-Ds is in early development 
stages (basic app structure and models defined).

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

User registry system http://trac.tools.ietf.org/tools/ietfdb/ticket/688

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

In this week it's planned:

Extend the I-D list application with:

* Ability to add/delete individual drafts
* Ability to add drafts using predefined rules
* Ability to update lists that have added draft using some rules

Time plan
=========

12 Aug: I-D list almost functional
19 Aug: List export and list display customization
26 Aug: Notifications
29 Aug: Development finished and start acceptance

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

At the moment we just need to now if the apache password file is r/w 
by the user that runs the webserver process or if we have to call an 
external script/program to update that file.

--------------------------------------------------------------------------------
Status for the DB Conversion Project: 29 Jul 2011 - 05 Aug 2011
--------------------------------------------------------------------------------


Summary
=======

Import of most meeting data done, still missing the materials though.
Currently working on getting the proxy code set up correctly for the
agenda view, hopefully the other views will be easy afterwards.

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

- Merging with trunk (again) to get new meeting code.
- Understanding how the old and new meeting models are working.
- Import of meetings, meeting times and sessions.
- Proxy support for meeting models.
- Agenda view half-way working.

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

- Model link to materials (agendas, slides, minutes).
- Import materials.
- Finish proxy and agenda view.
- Finish rest of meeting views (don't seem to be exercising the models much).
- Start porting liaison code.

Time plan
=========

Assuming meeting is done August 9/10, there's 1.5 week to port
liaison, August 19th.

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

The meeting code is an interesting hodgepodge of Javascript, template
and Python code designed to work around the oddities in the old
schema. It was somewhat of a puzzle to figure out how to proxy the old
schema, and there is plenty of opportunity for simplifying the view
code (much of which is methods on the models) once the new schema is
live - it's currently querying the data in a naive way, wasting lots
of cycles on overhead.


Ole

--------------------------------------------------------------------------------
Status for the WG Charter Tool Project: 29 Jul 2011 - 05 Aug 2011
--------------------------------------------------------------------------------


Summary
=======

WG Record modeling, overview, and state change logic (without 
annoucements) 90% done. Initial searching of the charter datebase 
working and editing of WG record attributes.


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


The modeling of the WG records, as discussed with Ole, is done, as well 
as the WG record view. This includes viewing the associated charter text 
(if available). There are some minor details that may need tweaking, but 
this shouldn't take much time later on. Additionally, changing of state 
is working and nearly completed, although without the associated 
announcements.

Searching the WG records is in the initial phases, as is editing of the 
WG record attributes.


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


Finishing the searching and editing elements. When this is done, the 
plan is to prepare a demo site you (and eventually Russ Housley), so 
that any UI tweaks and other changes can be made. I expect this to be 
ready tomorrow or wednesday.


Time plan
=========


As noted the searching and editing elements are planned until approx. 
wednesday, barring any complications. After this I plan on working on 
announcements and balloting towards the end of the week, followed by 
Atom feed and diff'ing of charters. 90% completion is expected early 
next week.


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


There was more work than expected after the merge that Ole did of 
conversion, and as a result the schedule has been pushed a little closer 
to the deadline than I wished.


--------------------------------------------------------------------------------
Status for the Xml2rfc V2 Project: 29 Jul 2011 - 05 Aug 2011
--------------------------------------------------------------------------------


Summary
=======

There are two major components:
1) Command-Line Tool. We have been responding to and soliciting feedback from the xml2rfc mailing list. 
2) GUI App. We plan to send you an alpha that we have working on Windows and Linux at this point.


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

Command line: As much as possible, we've have been trying to respond to feedback from the xml2rfc feedback list. 

GUI: Alpha of the GUI app; to deliver this coming week.


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

Command line: respond to feedback from the xml2rfc feedback list. Query the list about several details.

GUI: Solidify the GUI application and installation. Ensure installation on Mac. Smooth the install.


Time plan
=========

At this point the beta of the command-line application has been complete for a number of weeks and we have providing polish and modifications based on recommendations.

For the GUI application, we never solidified specific dates. If you have desires with this now, please do let us know and we will do our best to hit those -- and also confirm our abilities to do so.



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

None.



Clone this wiki locally