<br><br><div><span class="gmail_quote">On 8/30/06, <b class="gmail_sendername">Raphael Ritz</b> <<a href="mailto:r.ritz@biologie.hu-berlin.de">r.ritz@biologie.hu-berlin.de</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi folks,<br><br>first, with respect to the process: I agree with Martin that<br>each of us should take responsibility for about three PLIPs.<br>I also support the proposal to have a comment trail in the<br>bundle. Let's agree on a common name for the file: I propose
<br>to call it: REVIEW-COMMENTS.txt (or stx?) and have it<br>in plain text (or rather structured text?). Other suggeetions?<br><br>Now, here is what's most appealing to me (i.e., which I offer to take<br>responsibility for):
<br><br> - PLIP 112 - XML Import / Export<br> - PLIP 148 - Move to CMF 2.1<br> - PLIP 172 - Wiki syntax support for all content</blockquote><div><br>+1 - up your alley. <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
furthermore I offer Martin to help review in detail<br><br> - PLIP 119 - Contextual help</blockquote><div><br>Please - I was beginning to think I may have taken on a bit much. ;) Let's look at this together.<br></div><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Other comments from me at the moment: I think<br><br> - PLIP 8 - Versioning<br> - PLIP 122 - Edit-in-place mode for all basic field types
<br> - PLIP 145 - Locking<br> - PLIP 168 - integrate iterate for checkin/checkout/staging<br><br>should be looked at in concert if possible because I'm afraid there<br>might be some incompatiblities to deal with (at least Kapil told me
<br>once that he had problems in iterate with my locking approach)</blockquote><div><br>Ah - could you take the lead on talking to Kapil about this? I'm guessing you're the one who understands the locking work the best at this point.
<br><br>CMFEditions, Iterate and your locking work from Norway would be things to be incredibly proud of in 3.0. I'm quite sick of making the "Plone kinda supports versioning/locking/staging, well, er..." argument. :)
<br></div><br>In a similar vein, I think it'd be useful if we had one person who took a look at the versioning, locking, and iterate bundles, since they are likely to require some co-ordination.<br><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Last but not least, I agree with what has been said about Bling/KSS/AZAX,<br>namely that we should strive for an early decision and merger. Basically<br>all UI improvements are stuck at the moment because it's not clear what
<br>to base an implementation upon (e.g., our locking stuff could benefit a lot<br>from more responsiveness/asynchronous updates but the only AJAX part<br>we've put in there up to now was implemented at the lowest possible
<br>level which I would not like to repeat).</blockquote><div><br>I'll make this a priority. I doubt I can get anything together before the weekend, but expect a detailed email from me then. :)<br><br>Martin<br></div><br>
</div><br>