Hi, all

Here are some assorted things.

1. Unless someone beat me to it, I'll go about getting a fop-users mailing 
list set up. That appears to be the will of the majority (well, everyone 

2. We require a release plan for FOP 1. I propose a very simple one - a 
regular planned release the first week of every month, with a secondary 
bugfix release 1-2 weeks later (second or third week). That means that 
another will appear soon. Numbering of releases will _not_ be fixed; it will 
depend on how much got done in the intervening month. Comments?

3. We need volunteers to step in and take charge of documentation, including 
design and objectives, for FOP 1. We still want a revised Objectives 
statement on the FOP main page, for example. Takers?

4. I am pretty much set on spending 80-90% of _my_ time on FOP 2, even 
though we have neither formally defined FOP 2 nor actually kicked it off. 
However, that doesn't mean that I am abandoning FOP 1 - I'll continue to 
accept patches (I have one right now), plus do releases (unless somebody 
else wants to give that a shot), and otherwise support testing. I am 
currently doing some testing related to the CR->PR process.

I'd also like to lay claim to the pagination code for about a week - I want 
to get page-position="last" happening, plus review properties on 
page-sequence, and just in general tighten ship on FOP 1 pagination. If 
anyone else is already in there, maybe you could let me know - if somebody 
is doing stuff here already I don't want to re-invent the wheel.

Arved Sandstrom

Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to