-
Notifications
You must be signed in to change notification settings - Fork 365
Historic: ProjectStatus_2011_09_23
Robert Sparks edited this page May 1, 2023
·
1 revision
TOC(ProjectList,ProjectStatus*,titleindex)
#!rst
--------------------------------------------------------------------------------
Status for the Alternate Streams Project: 16 Sep 2011 - 23 Sep 2011
--------------------------------------------------------------------------------
Summary
=======
Project is in acceptance phase.
What's done
===========
What's next
===========
Time plan
=========
Problems and Possibilities
==========================
No new features neither bugs have appeared this week. The project is
ready to be accepted and deployed in production.
--------------------------------------------------------------------------------
Status for the ID Tracking Project: 16 Sep 2011 - 23 Sep 2011
--------------------------------------------------------------------------------
Summary
=======
Project is ready to be deployed in the beta server.
What's done
===========
What's next
===========
Time plan
=========
Problems and Possibilities
==========================
Developer was ill so the project was on hold.
--------------------------------------------------------------------------------
Status for the Rfc-ed/IANA Sync Project: 16 Sep 2011 - 23 Sep 2011
--------------------------------------------------------------------------------
Summary
=======
Waiting on dependencies
What's done
===========
Not much. Ole was porting the /submit/ and is still working on the
alternate streams assignment.
What's next
===========
Ole indicated today that the above is far enough along that I can start
injecting code in the right places. I'll do so on monday (and expect to
finish it on monday).
Time plan
=========
The rest that is needed is what needs to happen with IANA. Should I send
the proposal (a little more formally written) that I gave you a while
back? Or should I send it to you?
Problems and Possibilities
==========================
None, so far.
Best,
Martin
--------------------------------------------------------------------------------
Status for the WG Charter Tool Project: 16 Sep 2011 - 23 Sep 2011
--------------------------------------------------------------------------------
Summary
=======
A couple of more changes made.
What's done
===========
I made some minor changes based on feedback from RjS.
What's next
===========
Baring any additional changes, nothing else is planned.
Problems and Possibilities
==========================
Regarding your thoughts on showing the charters as regular document
pages I think it could be done. There are, however, some differences
betweeen documents and charters that we would have to account for:
* The charter pages also show some information from the associated Group
* There are snapshots on the charter page
* The ballot process is slightly different (other positions can be held)
* The history page shows more information (e.g. from the history of the
Group) than the history page for a document
* The announcements are different
We could probably make templates that could be used for both charters
and documents (and any eventual new types of documents), and we could go
even further and make an abstract view that could contain both types. It
would entail being able to specify how the history of a (generic)
document is assembled, what additional meta information would be
displayed, and somehow account for the different processes the documents
go through.
Depending on how many new document types you expect I'm not sure where
to use common (abstract) code and where to use specialised code, which
would be easier to change in the event the process for that document
type changes.
Best,
Martin
--------------------------------------------------------------------------------
Status for the Xml2rfc V2 Project: 16 Sep 2011 - 23 Sep 2011
--------------------------------------------------------------------------------
Summary
=======
The command line client is now in the Python Package Index, and the GUI installers are complete.
What's done
===========
- Fedora/RPM installer finished
- Submitted command line application to the package index
- Fixed a text formatting bug from the mailing list
What's next
===========
- Continued cross platform testing
- Ensuring the IETF has proper access to the Python Package Index package
Time plan
=========
Finish cross platform testing this next week.
Problems and Possibilities
==========================
- Will xml2rfc-gui be submitted to the Debian/Fedora package repositories? And if so, would you like us to dot his submission?