(Local time zone is UTC+2 hours CEST) [08/05/12 18:45] *** peterthoeny (n=PeterTho@63.146.69.17) has joined channel #twiki_release [08/05/12 20:02] *** ArthurClemens (n=ArthurCl@natpool-1.lostboys.nl) has joined channel #twiki_release [08/05/12 20:03] *** ArthurClemens_ (n=ArthurCl@ip56507f6a.direct-adsl.nl) has joined channel #twiki_release [08/05/12 20:03] good evening [08/05/12 20:03] Hi there! :) [08/05/12 20:03] still doing the dishes [08/05/12 20:20] *** ArthurClemens (n=ArthurCl@natpool-1.lostboys.nl) has quit: Read error: 110 (Connection timed out) [08/05/12 20:30] *** ArthurClemens_ (n=ArthurCl@ip56507f6a.direct-adsl.nl) is now known as ArthurClemens [08/05/12 20:52] *** PeterThoeny_ (n=PeterTho@63.146.69.17) has joined channel #twiki_release [08/05/12 20:55] *** peterthoeny (n=PeterTho@twiki/founder/peterthoeny) has quit: Read error: 110 (Connection timed out) [08/05/12 21:01] *** OliverKrueger (n=okrueger@dslb-082-083-213-093.pools.arcor-ip.net) has joined channel #twiki_release [08/05/12 21:02] *** OliverKrueger (n=okrueger@dslb-082-083-213-093.pools.arcor-ip.net) has set the topic for #twiki_release: "http://twiki.org/cgi-bin/view/Codev/GeorgetownReleaseMeeting2008x05x12" [08/05/12 21:02] hi arthur, koen, oliver, (sven here?), markus! [08/05/12 21:02] Hi, Peter. :) [08/05/12 21:03] ... & all. ;) [08/05/12 21:03] Hi PT [08/05/12 21:03] := (all incl. Peter) ;) [08/05/12 21:04] kenneth might not join today, he is still traveling [08/05/12 21:05] We can do the minutes in german this time. ;) [08/05/12 21:05] nice to see you here again oliver! [08/05/12 21:06] arthur, sprichst du deutsch? [08/05/12 21:06] :-) [08/05/12 21:06] In that case, we should add a bablefish link, hm? ;) [08/05/12 21:06] s /bable/babel/ [08/05/12 21:06] and a BabelfishPlugin for the references topics. [08/05/12 21:07] ich speche swizertuetsch mit meinen kindern [08/05/12 21:07] I thought you were from Austria. [08/05/12 21:08] nop [08/05/12 21:08] grew up in graubuenden (near austria though) [08/05/12 21:09] Which Kanton is that? [08/05/12 21:09] graubuenden :-) [08/05/12 21:09] oops. :) [08/05/12 21:09] my mom still runs a bad and breakfast there [08/05/12 21:09] http://www.thoeny.com/peter/schuders/index.html [08/05/12 21:09] Havent heard of that one. [08/05/12 21:09] it is mainly mountains [08/05/12 21:09] the biggest canton [08/05/12 21:10] english name is grison [08/05/12 21:10] oh, nice colors on that page.. ;) [08/05/12 21:10] we go there next month for vacation [08/05/12 21:10] +10 min, shall we start? [08/05/12 21:11] Ok. Who takes the notes? [08/05/12 21:11] who is taking notes, who is facilitating? [08/05/12 21:11] i can facilitate unless someone would like to [08/05/12 21:11] I can take the notes (will edit the page afterwards, if that's ok?) [08/05/12 21:11] vilen dank markus [08/05/12 21:11] Im not really prepared... havent read the topic... :-( [08/05/12 21:12] makus, could you also attach the log afterwards? [08/05/12 21:12] yes, np. [08/05/12 21:12] yes, editing after meeting is certainly fine [08/05/12 21:12] hey, there you are [08/05/12 21:12] Hi Arthur [08/05/12 21:12] I was here at 1900 GMT [08/05/12 21:13] one hour ago [08/05/12 21:13] hi arthur [08/05/12 21:13] hi [08/05/12 21:13] sure about GMT? [08/05/12 21:13] According to the time zone converter, it's now 19:13 GMT ;) [08/05/12 21:13] *** MatthewMetzger (n=MatthewM@mnch-06-4066.dsl.iowatelecom.net) has joined channel #twiki_release [08/05/12 21:13] so you got extra time for dish washing $:-) [08/05/12 21:14] hi matthew, welcome here! [08/05/12 21:14] Thanks Peter [08/05/12 21:14] do you want to introduce yourself quickly? [08/05/12 21:14] proposed agenda: [08/05/12 21:15] # 1. Review Urgent Bugs with 4.2.1 scope [08/05/12 21:15] # 2. Feature requests for Georgetown Release [08/05/12 21:15] # 3. Proposal for new core team [08/05/12 21:15] anything to add? [08/05/12 21:15] Sure. I'm a sysadmin for a small private school that uses TWiki. I'm just sitting in on this meeting because I'm interested. [08/05/12 21:15] Hi Matthew [08/05/12 21:15] Hello OliverKrueger [08/05/12 21:15] ok, stick around and please feel free to voice your voice :-) [08/05/12 21:15] okay :) [08/05/12 21:15] do you know perl? [08/05/12 21:16] PeterThoeny_: not fluently. [08/05/12 21:16] ---++ 1. Review Urgent Bugs with 4.2.1 scope [08/05/12 21:16] I'll be trying to learn more later this year. All my favorite applications seem to be programed in perl. [08/05/12 21:17] we have made some progress with bug fixing [08/05/12 21:17] thanks to all who help out [08/05/12 21:17] we have still a number of release blockers [08/05/12 21:18] e.g. bugs to squish before we can release 4.2.1 [08/05/12 21:18] http://develop.twiki.org/~twiki4/cgi-bin/view/Bugs/ReleaseBlocker [08/05/12 21:18] kenneth is not here today to run through the bugs [08/05/12 21:18] Do we discuss all of them of just the "New" or "Confirmed" ones? [08/05/12 21:18] wondering if we should pick some, or run through all release blockers [08/05/12 21:19] I'd like to talk about Bugs:Item5511, too (Waiting for Feedback). [08/05/12 21:20] most confirmed bugs we don't need to discuss [08/05/12 21:20] they just need work [08/05/12 21:20] 5511 was voted on [08/05/12 21:20] http://develop.twiki.org/~twiki4/cgi-bin/view/Bugs/Item5511 [08/05/12 21:20] Bugs:Item5511 - Updated attachment gets renamed to attachment name: leads to read errors [08/05/12 21:21] all proposed solutions point to a feedback mechanism we don't have [08/05/12 21:21] Yes, but the vote was not unanonymous and (therefore) nobody picked it up since last meeting. [08/05/12 21:21] that makes the scope wider than a patch release [08/05/12 21:22] I'd suggest to document the change and mark it as "Deferred" at least for 4.2.1 [08/05/12 21:23] admins will have to train users that they first need to delete a file before they can update the old one [08/05/12 21:24] it looks like consensus is towards keeping current (e.g. new) spec and document it [08/05/12 21:24] i am fine with this even though i votes to revert [08/05/12 21:25] although it looks like a sensible thing to warn if the extension is differnet [08/05/12 21:25] uebera||: anything to add? [08/05/12 21:25] let's move on [08/05/12 21:26] Bugs:Item5602 - Web Rename not following ALLOWWEBRENAME Preference [08/05/12 21:27] http://develop.twiki.org/~twiki4/cgi-bin/view/Bugs/Item5602 [08/05/12 21:28] i think there is an issue that needs to be fixed [08/05/12 21:28] we have to test this [08/05/12 21:28] but it is also a doc issue [08/05/12 21:29] ALLOWWEBRENAME suggests permission to rename web, where in fact it is permissions to rename topics in a web [08/05/12 21:29] aha [08/05/12 21:29] Oh I was never aware of that. [08/05/12 21:29] this is probably a bug that is here since 4.0, e.g. the revampt permissions [08/05/12 21:29] (in 4 years of twiki) [08/05/12 21:29] so i think we should downgrade it to normal (not a release blocker for 4.2.1) [08/05/12 21:30] If the behaviour didn't change in the last month, that should be ok. [08/05/12 21:30] same doc issue with allowwebchange, it does not mean permission to change the name of the web, rather, permission to change topics in the web [08/05/12 21:31] ok, downgrade to normal, noting the reason [08/05/12 21:31] then how is the renaming of webs protected? [08/05/12 21:32] Bugs:Item5443 - Searches related to TOPICINFO don't work as expected [08/05/12 21:32] http://develop.twiki.org/~twiki4/cgi-bin/view/Bugs/Item5443 [08/05/12 21:33] Interesting question, ArthurClemens [08/05/12 21:33] on rename of webs: yes, it needs to be protected [08/05/12 21:33] e.g. bug needs to be fixed (not for 4.2.1) [08/05/12 21:34] so we split the bug report in 2? [08/05/12 21:34] 5443 is a tricky one [08/05/12 21:35] Arthur: (1) correct the documentation and (2) protect webs from getting renamed? [08/05/12 21:35] uebera||: yes [08/05/12 21:35] on 5602 i sugegst to leave as one bug until someone investigates on protecting web renames (there might be a way that needs to be documented) [08/05/12 21:36] if it turns out that there is no way to protect a web rename we should split it up into 2 bug items [08/05/12 21:37] ok, but we should add the suggestion above to Item5602. [08/05/12 21:38] until now, I never renamed a web using a non-admin account... I thought you need to be admin to do that ;) [08/05/12 21:38] yes markus, can you take the action item to update the bug item? [08/05/12 21:38] will do. [08/05/12 21:39] on 5443, crawford's suggestion is a sensible one [08/05/12 21:39] needs to be tested thoroughly, out of scope for 4.2.1 release [08/05/12 21:39] so, reprioritize to normal? [08/05/12 21:40] := "not a blocker for 4.2.1". [08/05/12 21:40] yes, we we agree on reprioritizing this to normal [08/05/12 21:42] no voices against, so let's do it :-) [08/05/12 21:42] ok... on to 5443? (can't say anything about it) [08/05/12 21:42] * Bugs:Item5529 - SEARCHes of type word do not work if word is non-English and with TWiki running utf-8 [08/05/12 21:42] http://develop.twiki.org/~twiki4/cgi-bin/view/Bugs/Item5529 [08/05/12 21:42] i18n issue [08/05/12 21:43] clearly a bug [08/05/12 21:44] I guess the regexes still use a-zA-Z [08/05/12 21:44] yes, or perl word boundaries [08/05/12 21:45] which is not aware of multi-byte utf-8 cahrs [08/05/12 21:45] the latter would be better [08/05/12 21:45] ah [08/05/12 21:45] would this be a simply (workaround) fix? : scan for punctuation and whitespace instead of perl word boundaries [08/05/12 21:45] (i just added this comment to the bug topic) [08/05/12 21:46] what about '<' and '>' and &#nbr; (semicolon)? [08/05/12 21:46] and the ampersand? [08/05/12 21:46] * Bugs:Item5485 - Attachments containing special characters (e.g. german umlauts: ä ö ü) can not be opened any more [08/05/12 21:47] http://develop.twiki.org/~twiki4/cgi-bin/view/Bugs/Item5485 [08/05/12 21:47] I'd like to close this particular item. [08/05/12 21:47] Reason: web server problem. [08/05/12 21:47] yep [08/05/12 21:48] on 5529, yes, those apply too, e.g. scan for a set of chars to exclude [08/05/12 21:48] Do you want to exclude umlauts from filenames? [08/05/12 21:49] there is something like 'use utf8'; [08/05/12 21:49] PeterThoeny_: sorry, I mixed up the items. [08/05/12 21:49] umlauts and multi-byte chars in file attachment names should be supported [08/05/12 21:49] yep [08/05/12 21:50] Item5485 looks like a real blocker? [08/05/12 21:50] who can work on it? [08/05/12 21:51] I was talking about 5485. There's nothing we could do for the very use case. [08/05/12 21:51] No, its just a webserver config issue. [08/05/12 21:51] The problem is that the webserver is unable to map the encoded umlauts 'onto' the local filenames. [08/05/12 21:51] The resulting GET 'bypasses' TWiki. [08/05/12 21:52] ah [08/05/12 21:52] perl + unicode: http://search.cpan.org/~rgarcia/perl-5.10.0/pod/perluniintro.pod [08/05/12 21:53] so is this a i18n doc issue? [08/05/12 21:53] about unicode in perl 5.8 [08/05/12 21:53] yes. [08/05/12 21:53] sorry [08/05/12 21:54] I guess there is a config option for Apache, maybe we should ask in #apache... (haven't tried IIS yet). [08/05/12 21:55] ok, so reprioritize to normal (doc work) [08/05/12 21:55] +1 [08/05/12 21:55] * Bugs:Item5447 - If =manage= requires login, impossible to change password [08/05/12 21:55] http://develop.twiki.org/~twiki4/cgi-bin/view/Bugs/Item5447 [08/05/12 21:56] this items bounces back and forth between sven and arthur [08/05/12 21:56] arthur, can you give an update? [08/05/12 21:58] arthur seems to have stepped out for a moment [08/05/12 21:58] change password is performed by manage [08/05/12 21:58] and that script requires a login [08/05/12 21:59] so change password should be performed by another script [08/05/12 21:59] yes, chicken and egg problem if you forgot the pwd [08/05/12 21:59] another option is to use manage and manageauth [08/05/12 22:00] have manageauth authenticated (like viewauth) [08/05/12 22:00] I see we decided on something [08/05/12 22:00] long ago [08/05/12 22:00] (1 month) [08/05/12 22:00] redirect from manage to manageauth if needed [08/05/12 22:00] I will get back to that [08/05/12 22:01] next [08/05/12 22:01] ok, there are a number of other bug items [08/05/12 22:01] time check: +60 min [08/05/12 22:02] I suggest we go to next action item unless someone would like to cover one or two bug items [08/05/12 22:02] ? [08/05/12 22:02] What about Item5608? [08/05/12 22:02] When was ScriptUrlPaths introduced? Is this really a blockeR? [08/05/12 22:02] * OliverKrueger just found https://issues.apache.org/bugzilla/show_bug.cgi?id=24333 which is interesting for Bugs.Item5485 [08/05/12 22:03] ok [08/05/12 22:03] * Bugs:Item5608 - =ScriptUrlPaths= is not documented [08/05/12 22:03] http://develop.twiki.org/~twiki4/cgi-bin/view/Bugs/Item5608 [08/05/12 22:04] no hint on what it does [08/05/12 22:04] agreed that it needs to be documented, but not a blocker for 4.2.1 [08/05/12 22:04] Someone could run grep on the repository and see who introduced it and whether it's commented. [08/05/12 22:04] +1 [08/05/12 22:05] any other bug item? [08/05/12 22:06] if not lets continue [08/05/12 22:06] k [08/05/12 22:06] ---++ 2. Feature requests for Georgetown Release [08/05/12 22:06] http://twiki.org/cgi-bin/view/Codev/TWikiFeatureProposals#ProposalsReadyForReleaseMeeting [08/05/12 22:07] two very old proposals that got discussed for a long time [08/05/12 22:07] should be cover today? possible to decide? [08/05/12 22:07] there has been no progress on ProcessAddToHeadAdds [08/05/12 22:07] http://twiki.org/cgi-bin/view/Codev/ProcessAddToHeadAdds [08/05/12 22:08] neither on TWikiFormInheritance [08/05/12 22:08] what is holding up the proposal? [08/05/12 22:08] I haven't spent any time on it [08/05/12 22:10] * OliverKrueger has no opinion on that since he did not follow the discussion. [08/05/12 22:10] you as the committed developer can come up with a refinement we can agree on [08/05/12 22:10] i think step by step approach is fine [08/05/12 22:11] personally i like tour proposal [08/05/12 22:11] if the concern on the simplifying the position ranges can be addressed we have a winner [08/05/12 22:11] (although i am fine as is) [08/05/12 22:13] one issue on process is that we are not that many people in the release meetings, which non participants take as a reason to say that we cannot decide at the meetings [08/05/12 22:13] I still need to review the proposals in http://twiki.org/cgi-bin/view/Codev/ProcessAddToHeadAddsTalk [08/05/12 22:13] where in fact we have a clearly stated process and _should_ and can decide on proposals waiting to be covered [08/05/12 22:14] Yes, me too. Haven't looked at the attached plugin yet. [08/05/12 22:15] ok, arthur, i suggest to review the talk page and tweak the proposal a bit to get the person who raised concern to agree [08/05/12 22:15] hopefully this happens before the next release meeting [08/05/12 22:15] if not we can decide in 2 weeks [08/05/12 22:15] Crawford's proposal looks fine, but I need to try it [08/05/12 22:15] ok [08/05/12 22:15] (i need to be offline for a few min, sorry) [08/05/12 22:16] btw: is there a topic which lists the changes 4.2.1 would bring if it was released tomorrow? [08/05/12 22:17] Peter: should we proceed to "3. Proposal for new core team" then? [08/05/12 22:18] http://develop.twiki.org/~twiki4/cgi-bin/view/Bugs/ReleaseNotes?type=n%2Fa%7Cpatch [08/05/12 22:18] Ah, thanks! [08/05/12 22:23] (sorry, i am back from phone call with our ceo) [08/05/12 22:24] anyone wants to quickly comment on http://twiki.org/cgi-bin/view/Codev/TWikiFormInheritance [08/05/12 22:24] ? [08/05/12 22:25] nope [08/05/12 22:25] no [08/05/12 22:25] gmc, are you here? [08/05/12 22:26] is t.o. down? [08/05/12 22:26] works for me. [08/05/12 22:26] hmm [08/05/12 22:27] the last time koen (the committed developer) addressed questions was two month ago [08/05/12 22:28] the spec of the proposal has not been updated for a long time [08/05/12 22:28] so i would give an action item to gmc to address the feedback and to tweak the proposal a bit [08/05/12 22:28] k [08/05/12 22:29] i am for a quick(er) decision, but concerns need to addressed as well [08/05/12 22:29] time check: +90 min [08/05/12 22:29] ---++ 3. Proposal for new core team [08/05/12 22:30] instead of proposing a new core team structure today i'd like to have an open ended discussion on the needs of the community [08/05/12 22:30] i will take this as input to propose a new structure [08/05/12 22:31] shall we spend 20 min on the discussion? [08/05/12 22:31] ok [08/05/12 22:31] ok. [08/05/12 22:32] (i wish i could present you with a proposal but i am very much late on everything lately) [08/05/12 22:32] What is the motivation behind this topic? [08/05/12 22:33] so first a question: how can we organize ourselfs to: make quick decisions, increase our community, have fun [08/05/12 22:33] I think we need to show we are an open community [08/05/12 22:33] at the second summit we discussed to revamp the core team in regards to governance [08/05/12 22:34] one key contributor stopped contributing until this is settled [08/05/12 22:34] the current core team devides 'team functions' between members [08/05/12 22:35] kenneth and i feel that the current process more or less works, but that we need to enhance the process so that we can scale better [08/05/12 22:35] currently we have a very open and democratic process to decide on features [08/05/12 22:35] 1. it looks as if we have special status, special meetings, and that we decide on twiki above the rest of the community [08/05/12 22:36] the current and open reality is not reflected in the 'core team' status [08/05/12 22:36] we can apply the same for strategic question, in addition to f2f meetings [08/05/12 22:36] yes, the main purpose of the core team at this time is to put on breaks if needed [08/05/12 22:36] with veto power [08/05/12 22:37] we never used it so far [08/05/12 22:37] I cannot foresee if this will be necessary [08/05/12 22:37] and it is not likely to be used unless someone tries to push somthing that is totally out of line with the core twiki mission [08/05/12 22:37] but have a look at http://twiki.org/cgi-bin/view/Codev/CoreTeam [08/05/12 22:38] we have people with a status, and we have roles [08/05/12 22:38] yes, and the community pushed back on the roles a long time ago [08/05/12 22:39] we can describe what we think is needed [08/05/12 22:39] hence almost the only real purpose is the vet power at this time [08/05/12 22:39] to keep the quality of twiki [08/05/12 22:40] I propose that we have an alternative setup for twiki 'tasks' (for lack of a better name) [08/05/12 22:41] arthur, please elaborate [08/05/12 22:42] for instance the 'TWiki Architect Role'. does it describe what we need? [08/05/12 22:42] others too, please help brainstorm how we can get organized so that your features/priorities get addressed [08/05/12 22:42] we have a roadmap for the next major release [08/05/12 22:42] we need help on architectural issues for sure [08/05/12 22:43] I feel we need the emphasis on this task: TWiki architecture related to the next release [08/05/12 22:44] and we need discussions that are above the feature requests [08/05/12 22:44] so we have the task and we need people for that [08/05/12 22:44] would focused teams help to make quick & good decisions? [08/05/12 22:45] yes, architecture discussions are best done interactively [08/05/12 22:45] I don't know. We did some restructuring work on twiki.org ourselves in a small team, with Kenneth [08/05/12 22:46] but it died out when the most important issues were resolved [08/05/12 22:46] we did not have a continous discussion on these things [08/05/12 22:47] same goes for usability. I think I could do a lot with Carlo [08/05/12 22:47] but we are lacking a framework [08/05/12 22:47] not necessarily a team, but at least to have a 'home' [08/05/12 22:48] may be i am wrong, but i have a hunch that small focused teams get things done quickly, they can "hire" new contributors [08/05/12 22:48] and with some cross functional things which could be the new core team? [08/05/12 22:49] for what kind of issues do we need a core team? [08/05/12 22:49] the term core team is overloaded, it needs a new name too [08/05/12 22:49] if we have, say 5 focus groups we need to coordinate [08/05/12 22:49] that could be the purpose of the new core team [08/05/12 22:50] coordination can still happen in release meetings [08/05/12 22:50] I would not favor 'secret' meetings [08/05/12 22:50] that is a good question [08/05/12 22:50] how many vetoes rights do we need? [08/05/12 22:51] could that be one circulating member? [08/05/12 22:51] to be voted upon once a year? [08/05/12 22:51] on meetings, one option is to have meetings per focus group, open to all who like to drop by, and a new core team to coordinate [08/05/12 22:51] or just one type of meeting? [08/05/12 22:51] a single member which holds the vetoes rights? [08/05/12 22:52] perhaps Peter as benevolent facilitator and one other member? [08/05/12 22:52] *** MatthewMetzger (n=MatthewM@mnch-06-4066.dsl.iowatelecom.net) has quit: [08/05/12 22:52] one release meeting should suffice [08/05/12 22:53] most people have a lot of meetings going on in their lives [08/05/12 22:53] the core team should be the TWikiFacilitatorTeam [08/05/12 22:53] what if a member of each focus group is representing the needs to the new core team, e.g. would be member of the new core team? [08/05/12 22:54] facilitating, not meeting to decide [08/05/12 22:54] that would imply that focus groups are fixed structures [08/05/12 22:54] I don't think it will work [08/05/12 22:54] perhaps for some, not for all [08/05/12 22:55] no, it would mean a committed lead for a certain period of time, such as one year [08/05/12 22:55] sounds good. plus one 'second in command' just in case... [08/05/12 22:56] mr spock [08/05/12 22:56] I think the TWiki community has shown to avoid these kind of structures [08/05/12 22:56] back to the roots of twiki: robot in sapce :-) [08/05/12 22:57] then we end up with a lot of groups without people [08/05/12 22:57] arthur, i am not sure, we have seen that core team roles are tired [08/05/12 22:57] but focus teams with leads could be wired [08/05/12 22:58] oliver, koen, markus, any other feedback? [08/05/12 22:59] not at the moment. I'll have to think about it. [08/05/12 22:59] time check: +120 min [08/05/12 22:59] good feedback so far [08/05/12 23:00] I think there is enough food to feed the community [08/05/12 23:00] i wish the release meetings would be better attended [08/05/12 23:00] neither from me, atm [08/05/12 23:00] especially this one where we have the new core team as an agenda item [08/05/12 23:00] people have been asking for ideas and comments not just from developers [08/05/12 23:00] so we could elaborate on Codev [08/05/12 23:01] time for me [08/05/12 23:01] PeterThoeny_: thanks, thanks everyone [08/05/12 23:01] bye, Arthur. :) [08/05/12 23:01] ciao [08/05/12 23:01] bye ArthurClemens [08/05/12 23:01] yes, i also need to sign off [08/05/12 23:01] thanks arthur! [08/05/12 23:02] *** ArthurClemens (n=ArthurCl@ip56507f6a.direct-adsl.nl) has quit: [08/05/12 23:02] bye Peter [08/05/12 23:02] feel free to continue the discussion [08/05/12 23:02] possibly in #twiki [08/05/12 23:02] yes. [08/05/12 23:03] thanks all for participating! [08/05/12 23:03] tty soon [08/05/12 23:03] Bye, Peter. :) [08/05/12 23:04] *** OliverKrueger (n=okrueger@dslb-082-083-213-093.pools.arcor-ip.net) has left channel #twiki_release: "Konversation terminated!" [08/05/12 23:05] Further comments that should go in today's log, anyone? ;) [08/05/12 23:08] If not, I'm going to clean it up a little (i.e., remove local reconnects and duplicate lines from my IRC bouncer) an attach it... ERC>