IrcLogDakarReleaseMeeting2005x12x17

IRC Log

[12:31] * #twiki_dakar: PeterThoeny Lavr MichaelDaum_
[12:31] * #twiki_dakar was created on Sat Dec 17 03:27:10 2005.
[12:55] * ArthurClemens has joined #twiki_dakar.
[12:56] * CDot has joined #twiki_dakar.
[12:57] CDot: Evening, all!
[12:57] * CDot has changed the topic on channel #twiki_dakar to Free
the Dakar 5!.
[12:57] ArthurClemens: hi - I am glad I can join after all, at a friend's place
[12:58] CDot: why did you get bennaed?
[12:58] CDot: banned?
[12:58] ArthurClemens: My provider noticed a Trojan on one of my computers
[12:58] CDot: Ouch
[12:59] ArthurClemens: It was on my pc that I use to check css with
[12:59] ArthurClemens: I've cleaned it, but they re-applied the ban
[12:59] CDot: You were lucky they noticed - it could have been there for ages
[12:59] ArthurClemens: just before the weekend
[13:00] ArthurClemens: But everything stops. Work is not just web browsing
[13:00] Lavr: Evening guys
[13:00] CDot: Hi Kenneth
[13:00] ArthurClemens: Hi
[13:03] CDot: Well, it would be good if Lynnwood could show up.....
[13:04] PeterThoeny: hi all, Peter here
[13:04] Lavr: Hi Peter
[13:04] * Lavr is KennethLavrsen
[13:04] PeterThoeny: sorry my ignorance, who is lavr?
[13:04] PeterThoeny: oh, thanks
[13:04] PeterThoeny: hi kenneth
[13:05] PeterThoeny: is anyone using skype?
[13:05] ArthurClemens: Hi Peter, I think we are still waiting for Lynnwood. Shall we give him 5 minutes?
[13:05] ArthurClemens: I don't have skype
[13:05] * terceiro has joined #twiki_dakar.
[13:06] terceiro: hi all
[13:06] CDot: I'm wondering if maybe Lynnwood got his times wrong
[13:06] PeterThoeny: highly recommended, especially for itnl calls
[13:06] Lavr: Hi Terceiro
[13:06] CDot: hey Antonio
[13:06] PeterThoeny: hi antonio
[13:06] Lavr: Skype has a limit of 5 so we are already too many.
[13:07] CDot: does anyne known Lynnwoods Skype address?
[13:07] * terceiro doesn't use skype
[13:07] PeterThoeny: not me
[13:07] PeterThoeny: lynwood mentined that he goes skiing with his son in the morning
[13:08] PeterThoeny: may be he is a bit late coming back
[13:08] ArthurClemens: I've just sent him an email
[13:08] PeterThoeny: ok, i'll shoot an e-mail
[13:08] ArthurClemens: too late
[13:08] CDot: arthur just did that....
[13:08] ArthurClemens: Will this conversation get logged?
[13:08] CDot: not at the moment
[13:09] CDot: need to be a channel op to invite logger
[13:09] CDot: it can be logged by someone taking a cat and paste easily enough
[13:09] PeterThoeny: ok e-mail to lynwood sent
[13:09] CDot: ^cat^cut
[13:10] ArthurClemens: Who will do the task of putting this online later this evening?
[13:10] CDot: anyway, I don;t want to hang around here all night, so let's get started. The big question is, what are we waiting for to release Dakar?
[13:10] CDot: ArthurClemens: I'll do that
[13:11] ArthurClemens: I think Peter can start off
[13:11] PeterThoeny: ok, i have several things
[13:11] ArthurClemens: CDot: ok
[13:11] PeterThoeny: the biggest thing is Item663
[13:11] PeterThoeny: TWiki.org doc merge
[13:11] PeterThoeny: frankly, the quality of the current doc is not up to the standard
[13:12] CDot: standard?
[13:12] PeterThoeny: so there are two issues
[13:12] PeterThoeny: out of sync with twiki.org
[13:12] PeterThoeny: and doc up to standards
[13:12] ArthurClemens: Peter, can you tell us what is missing before it lives up to the standard?
[13:13] PeterThoeny: http://twiki.org/cgi-bin/view/TWiki/TWikiDocsStyleGuide
[13:13] CDot: and can you tell us why all the work lynnwood and I did on mergeing the docs was apparently a waste of time?
[13:13] PeterThoeny: not a waste of time
[13:14] PeterThoeny: crawford closed Item663 at a point where i did agree that it can be closed
[13:14] PeterThoeny: hence i took it into my own hand
[13:14] PeterThoeny: and worked many days on the docs
[13:14] PeterThoeny: i have not been active in the last two weeks due to a busy schedule
[13:15] PeterThoeny: anyway, there 49 topics left i need to go through
[13:15] ArthurClemens: TWikiDocsStyleGuide lists many guidelines - what is generally missing?
[13:15] PeterThoeny: not just the guidlines
[13:16] PeterThoeny: content written in a place that is not intuitive for new users etc
[13:16] PeterThoeny: just see the changelogs of my doc work and you will see
[13:16] CDot: I can see a lot of formatting fixes
[13:17] ArthurClemens: Could you make a list of these docs?
[13:17] PeterThoeny: yes, that one too
[13:17] ArthurClemens: As a project leader, you are in the position to delegate these things.
[13:17] PeterThoeny: for example, TWikiVariables should have just bullets
[13:17] PeterThoeny: it had tables left aligned
[13:17] PeterThoeny: it had missing Related
[13:17] PeterThoeny: etc
[13:18] PeterThoeny: point two: Item958
[13:18] PeterThoeny: Upload incompatibility with Cairo
[13:18] ArthurClemens: Sorry Peter, not finished yet
[13:18] PeterThoeny: not too big change
[13:18] ArthurClemens: I would like to close this off
[13:18] ArthurClemens: The documentation issue
[13:18] PeterThoeny: i inteded to list the items first
[13:19] PeterThoeny: ok, if preferred to discuss one by one
[13:19] PeterThoeny: lets do that
[13:19] ArthurClemens: We're in the middle now
[13:19] PeterThoeny: so how to proceed on docs?
[13:19] ArthurClemens: I propose you make a list of topics]
[13:19] ArthurClemens: with a short line what should be changed
[13:20] ArthurClemens: and divide the list
[13:20] ArthurClemens: let other people finish it off
[13:20] ArthurClemens: 10 docs per person
[13:20] CDot: All that is required are Bug web entries
[13:20] CDot: that is the right way to track
[13:20] PeterThoeny: i can do that, although that is almost the same work as fixing since I have look at the diff and to read through the text
[13:20] CDot: Peter, this is very very frustrating
[13:20] Lavr: Maybe dividing the list of documents is not the best way to get to a release of Dakar? Maybe it is actually better to leave that to 1-2 people.
[13:20] ArthurClemens: I don't think a project leader should do this work
[13:21] PeterThoeny: not all developers are doc persons
[13:21] CDot: you are saying you won't let the release go because there is work remaining, but you won't tell us what work you think needs doing!
[13:21] PeterThoeny: i think it is good to divide the work
[13:21] ArthurClemens: You need to keep more distance from the nitty gritty
[13:21] PeterThoeny: possibly with lynwood
[13:22] ArthurClemens: Peter, you make the list, Lynnwood and 1 or 2 other people can do the work
[13:22] CDot: It is moot for me; clearly my documentation is not up to scratch, so it's pointless for me to be involved in further docs work.
[13:22] Lavr: I think documentation gets more consistant of addressed by a few that are good at it and have an idea how the end result is supposed to be. There is plenty to do on the testing and fixing to get Dakar ready.
[13:22] PeterThoeny: ok, here is the raw list of 49 topics i intend to go throuh:
- TWikiContributor
- TWikiHistory
- TWikiInstallationGuide
- TWikiPreferences
- TWikiRegistration
- TWikiUpgradeGuide
- TWikiUserAuthentication
- TWikiUsernameVsLoginUsername
- TWikiVariables
- TWikiVariablesAtoM
- TWikiVariablesNtoZ
- TWikiWebsTable
- TemplateWeb
- TextEditor
- TextFormattingFAQ
- TextFormattingRules
- TimBernersLee
- UnlockTopic
- WebBottomBar
- WebChangesAlert
- WebHome WebIndex
- WebLeftBar
- WebLeftBarCookbook
- WebLeftBarExample
- WebLeftBarPersonalTemplate
- WebRss
- WebRssBase
- WebSearch
- WebSearchAdvanced
- WebSiteTools
- WebTopBar
- WebTopicEditTemplate
- WebTopicList
- WebTopicNonWikiTemplate
- WebTopicViewTemplate
- WelcomeGuest
- WhatIsWikiWiki
- WikiCulture
- WikiName
- WikiNotation
- WikiReferences
- WikiSyntaxSummary
- WikiTopic
- WikiWikiClones
- WikiWord
- WindowsInstallCookbook
- WindowsInstallSummary
- YouAreHere
[13:22] * You have been disconnected. Sat Dec 17 13:22:41 2005.
[13:23] * Automatically rejoining channel...
[13:23] * Channel re-joined successfully.
[13:23] * Initial topic: Free the Dakar 5!
[13:23] * #twiki_dakar: PeterThoeny terceiro CDot ArthurClemens Lavr MichaelDaum_
[13:23] CDot: he's back!
[13:23] * #twiki_dakar was created on Sat Dec 17 03:27:10 2005.
[13:23] PeterThoeny: not sure what happend
[13:23] ArthurClemens: Peter, get more experience with IRC!
[13:23] ArthurClemens: Excess Flood error
[13:23] PeterThoeny: it is the first time i use irc
[13:23] PeterThoeny: oic
[13:24] Lavr: Welcome back. IRC network kicks flooders. Don't paste to many lines at a time.
[13:24] CDot: if you paste too much, you get kicked off
[13:24] CDot: anyway, here is not the best place for that list
[13:24] CDot: an item in Bugs web is the best place
[13:24] ArthurClemens: Peter, if you have more distance, you can just check how things are going even if you are busy yourself.
[13:24] PeterThoeny: ok, i'll post that in http://twiki.org/cgi-bin/view/TWiki/DakarMergeProgress
[13:25] ArthurClemens: How do you feel about delegating this?
[13:25] PeterThoeny: well, the reason why i pasted it was crawford comment that "you are saying you won't let the release go because there is work remaining, but you won't tell us what work you think needs doing!"
[13:25] ArthurClemens: (don't run away)
[13:26] ArthurClemens: So a doc editor, how should he get started on the docs?
[13:26] PeterThoeny: i know there is tention in the virtual room, everyone wants dakar released
[13:26] CDot: sure, I understand that. But paste to a topic in Bugs web.
[13:26] PeterThoeny: and i am the person holding it back as it seems like
[13:27] CDot: Tension? That's an understatement.
[13:27] Lavr: Peter, you are not alone in wanting to hold back the release.
[13:27] ArthurClemens: We haven't finished our list.
[13:27] Lavr: The major task - as I see it - is the rate that bugs still arrive.
[13:27] PeterThoeny: so shall we spend a bit of time on what is bugging people?
[13:27] CDot: I don;t have a problem with people holding back the release
[13:27] PeterThoeny: getting this out and cleared is important too
[13:28] CDot: what I have a problem with is people holding back the release for no apparent reason
[13:28] ArthurClemens: I would like to close off the documentation first.
[13:28] PeterThoeny: ok, back to docs
[13:28] ArthurClemens: Peter, anything to add or to answer?
[13:28] Lavr: I think it is important that some focus on documents, some on testing heavily, and some on fixing bugs. I think all agree that we are on a feature freeze.
[13:28] ArthurClemens: Lets get very concrete.
[13:29] ArthurClemens: Peter, your next steps on the docs are ... ?
[13:29] PeterThoeny: starting next week i have time again to work on docs
[13:29] ArthurClemens: Lavr, we get back to this later
[13:29] ArthurClemens: We just wanted the list...
[13:29] PeterThoeny: next steps: get in touch with lynwood to see if he can help out
[13:29] PeterThoeny: then work on the docs
[13:30] ArthurClemens: What other people can we ask?
[13:30] PeterThoeny: some experienced tech writer
[13:30] PeterThoeny: i am not aware we have one
[13:31] ArthurClemens: Side action: actively try to get a tech writer
[13:31] PeterThoeny: yes, mike mannix did an excellent job
[13:31] PeterThoeny: he was working very closely with the developers
[13:32] ArthurClemens: I would like to offer my help, but I am Dutch.
[13:32] PeterThoeny: and proactively probed the developers to understand new features
[13:32] PeterThoeny: this was smooth sailing with mike
[13:32] CDot: well, Mike Mannix isn't available now, so if you want a TA, you will have to look elsewhere.
[13:32] PeterThoeny: for cairo i palyed that role
[13:32] PeterThoeny: which increased my workload
[13:33] PeterThoeny: for dakar nobody took that role
[13:33] PeterThoeny: until i stepped in two month ago
[13:33] PeterThoeny: so action item for all
[13:33] PeterThoeny: look for a tech writer
[13:34] ArthurClemens: Can we make this a notification in Codev and twiki.org homepage?
[13:34] PeterThoeny: it is in CodevHelpWanted i think
[13:34] CDot: now we are going to delay the release until we have a tech author on board?
[13:34] PeterThoeny: wondering where to get more exposure
[13:34] PeterThoeny: possibly sf.net?
[13:35] PeterThoeny: no, that is not the idea crawford
[13:35] CDot: then what is the idea?
[13:35] PeterThoeny: if lynwood agrees, lynwood and i are working on the docs
[13:35] CDot: ok - so no delay waiting for a TA
[13:35] PeterThoeny: correct
[13:36] ArthurClemens: ok, not ideal, but lets proceed for the time being
[13:36] ArthurClemens: Next point
[13:36] ArthurClemens: Any questions left for the docs?
[13:36] CDot: yes
[13:36] CDot: how long will this take?
[13:36] ArthurClemens: fair point
[13:37] PeterThoeny: still many hours left
[13:37] PeterThoeny: i estimate about 60% done
[13:37] CDot: many? is that 5? 10? 100? 1000?
[13:37] PeterThoeny: easily 40 hours
[13:38] PeterThoeny: any other things to discuss on docs?
[13:39] PeterThoeny: just a comment
[13:39] ArthurClemens: Are we talking about a period of about 2 weeks?
[13:39] PeterThoeny: the reason why i push for the doc merge is to not lose contributions done by other folks
[13:40] ArthurClemens: Did we reach agreement on what happens to the docs on twiki.org/TWiki?
[13:40] PeterThoeny: it is impolite to simply delete the hundreds of doc fixes done on twiki.org on upgrading twiki.org to dakar
[13:40] Lavr: Don't forget xmas, family, vacation stress at work, new year. Don't over-commit.
[13:40] CDot: Peter, Lynnwood already did a topic-by-topic trawl of the docs to that end
[13:41] PeterThoeny: well, my workday is already 14-16 hours a day (all together)
[13:41] PeterThoeny: i know that lynwood did that
[13:42] CDot: but?
[13:42] PeterThoeny: he makked many as "Revised", e.g topic was significantly revised in Dakar making direct comparison to Cairo version difficult.
[13:42] * SvenDowideit has joined #twiki_dakar.
[13:42] PeterThoeny: hence the work left to actually do teh work of merging
[13:42] ArthurClemens: Sven, we are talking about the documention process.
[13:43] PeterThoeny: which is the timeconsuming part
[13:43] SvenDowideit: ah
[13:43] PeterThoeny: hi sven!
[13:43] SvenDowideit: holla
[13:43] ArthurClemens: The idea was offered to create a 'Cairo' web for the older TWiki docs.
[13:43] PeterThoeny: that is a good idea
[13:43] CDot: I find it hard to believe that there is 40 hours work remaining on the few docs that were revised for Dakar
[13:43] PeterThoeny: but something else
[13:44] PeterThoeny: the "cairo" doc web should be plain cairo docs
[13:44] PeterThoeny: not the contribs done since then
[13:44] SvenDowideit: y
[13:44] SvenDowideit: definatly
[13:44] PeterThoeny: hence the current TWiki web on twiki.org is not the cairo doc web
[13:44] ArthurClemens: Wouldn't a separate Cairo doc web make the merging easier?
[13:44] SvenDowideit: i have an idea that i want to explore anyway
[13:45] terceiro: maybe the TWiki web should be always the next versions's doc web
[13:45] CDot: SvenDowideit: see email for log
[13:45] SvenDowideit: thanks CDot
[13:45] CDot: terceiro: the trouble with that is that it breaks when there are multiple branches
[13:45] PeterThoeny: restructuring the doc process is another subject
[13:46] PeterThoeny: an important one
[13:46] PeterThoeny: but not relevant for the purpose of this meeting
[13:46] SvenDowideit: personally i thing we should have one docco web on twiki.org per release / branch, and that they are read only.
[13:46] terceiro: CDot, PeterThoeny: ok
[13:46] PeterThoeny: of organizing dakar release
[13:46] SvenDowideit: but that we should write an annotation / editing plugin
[13:47] PeterThoeny: that sounds like a good idea
[13:47] Lavr: Read only web is the murder of the Wiki way.
[13:47] SvenDowideit: no
[13:47] SvenDowideit: its not Lavr
[13:47] PeterThoeny: also useful for twiki world domination
[13:47] CDot: ok; checkpoint. What we have arrived at so far, is that Peter wants to do another 40 hours work, over an unspecified period, before he will accept that the release is ready to go.
[13:47] CDot: correct?
[13:47] PeterThoeny: correct
[13:48] SvenDowideit: buti should expand on the idea on codev soon
[13:48] PeterThoeny: actually, not unspecified time
[13:48] PeterThoeny: we should shoot for a 01 jan 2006 release
[13:48] PeterThoeny: a nice number
[13:48] SvenDowideit: can't we go for a 2005 release?
[13:48] SvenDowideit: as 2 'years' between drinks is terrible
[13:49] Lavr: I would like to talk bug arrival rate before we settle on a release date.
[13:49] PeterThoeny: we would if i work 36 hours a day
[13:49] * Lynnwood has joined #twiki_dakar.
[13:49] PeterThoeny: no, more serously
[13:49] ArthurClemens: Lynnwood is coming
[13:49] PeterThoeny: i think it is better not to release around xmas
[13:50] PeterThoeny: because there is little attention span
[13:50] Lynnwood: Hey there folks. My sincere apologies!!! I got stranded on the ski mountain with a flat tire
[13:50] PeterThoeny: more impact if we release in teh first few days of january
[13:50] PeterThoeny: everyone fresh at work
[13:50] Lavr: Hy Lynnwood and thanks for the initiative.
[13:50] PeterThoeny: wondering what's new
[13:50] ArthurClemens: Let's not make this a big point.
[13:50] Lynnwood: could anymore email the a copy of log to catch up?
[13:50] PeterThoeny: hi lynwood, welcome here!
[13:50] CDot: I really, really, really, strongly, want a 2005 release
[13:51] Lynnwood: lynnwood@skyloom.com
[13:51] CDot: a whole year without a release stinks
[13:51] Lynnwood: or maybe just copy and paste into a irc to me
[13:51] PeterThoeny: ok i mail it now
[13:51] ArthurClemens: And in january 2006, 2005 is already old
[13:51] CDot: right
[13:52] ArthurClemens: We need to talk about releasing more quickly another time
[13:53] ArthurClemens: Lynnwood, the question is: could you run through the docs another time with Peter to make them final?
[13:53] Lynnwood: absolutely
[13:53] ArthurClemens: About 40 docs left.
[13:53] Lynnwood: ok
[13:53] ArthurClemens: How is your time the next week/weeks?
[13:53] PeterThoeny: crawford, we also had a gap between athens and beijing
[13:53] PeterThoeny: http://twiki.org/cgi-bin/view/Codev/TWikiProductionRelease
[13:54] CDot: and that makes it ok?
[13:54] SvenDowideit: yes, and we are a laughing stock because of it
[13:54] PeterThoeny: TWikiRelease01Dec2001 and TWikiRelease01Feb2003, respectively
[13:54] SvenDowideit: oss wise
[13:54] ArthurClemens: Come on, we are a small developer group
[13:54] PeterThoeny: you can laugh at it oss wise
[13:54] Lynnwood: I can make some time this week
[13:54] ArthurClemens: Great
[13:55] CDot: all the more reason to release early, release often
[13:55] SvenDowideit: thats true, but does not change the fact that in the oss world thats too long
[13:55] PeterThoeny: on corporate level it does not matter that much
[13:55] SvenDowideit: correct
[13:55] MichaelDaum_ is now known as MichaelDaum
[13:55] CDot: small developer groups have a hard time coming to completion, like now
[13:55] SvenDowideit: thats why i keep acting like a pain
[13:55] PeterThoeny: actually, corporations do not want too frequent upgrades
[13:55] SvenDowideit: i'm trying to drive the oss part
[13:55] PeterThoeny: frequent betas is the key
[13:55] PeterThoeny: that is what oss folks like to work with
[13:55] MichaelDaum: (kids are sleeping)
[13:56] ArthurClemens: Peter and Lynnwood, I would like to have a monitor how things are going 7 days from now.
[13:56] ArthurClemens: Hi Michael
[13:56] SvenDowideit: while for oss reguar actual releases are needed
[13:56] CDot: ok, here's an alternative proposal.
[13:56] CDot: Let's not release
[13:56] Lynnwood: ArthurClemens - sounds good
[13:56] CDot: Let's just keep releasing betas
[13:56] PeterThoeny: the cisco model?
[13:56] CDot: at regular intervals - say every month
[13:56] Lavr: Corporations want less bigs release and small incremental bugs fix releases that can be patched on a running server without having to spend 2 days making it work again.
[13:57] CDot: Lavr: spot on, that's my experience as well
[13:57] PeterThoeny: good point kenneth
[13:57] CDot: small releases, often
[13:57] PeterThoeny: that is the idea of automated upgrades
[13:57] ArthurClemens: Are we talking about betas or about dot dot releases?
[13:57] SvenDowideit: ArthurClemens, in the end its just a label for the same thing
[13:57] CDot: PeterThoeny: I don't know the cisco model (never dealt with them directly myself)
[13:58] SvenDowideit: if they are often enough and inremental its good
[13:58] Lynnwood: I agree in general about focusing more on frequent betas but I think it's still worthwhile getting out a Dakar soon - just becuase we said we would.
[13:58] Lavr: Dakar will be a big one. We should plan a patch release 2 months after to close all the bugs that will arrive once Dakar is exposed to users, lusers and PHBs.
[13:58] PeterThoeny: if you look at cisco routers, all of them run a beta version of ios (their os)
[13:58] CDot: ok
[13:59] ArthurClemens: So Dakar = TWiki4.0 ?
[13:59] SvenDowideit: i agree that we should plan a service pack for dakar
[13:59] SvenDowideit: y
[13:59] CDot: I don't
[13:59] Lynnwood: service pack in a month or two is good
[13:59] PeterThoeny: a service pack is a sensible thing to do
[13:59] CDot: "service pack" assumes some kind of planning
[13:59] SvenDowideit: not publicly
[13:59] SvenDowideit: just mentally
[14:00] Lynnwood: It just makes sense to provide patch for bugs that will inevitably show up after release.
[14:00] SvenDowideit: (i mean i agree with Lavr )
[14:00] PeterThoeny: the TWikiReleaseNamingConvention account for that, http://twiki.org/cgi-bin/view/Codev/TWikiReleaseNamingConvention
[14:00] Lavr: A service release for sure does not mess up WebPreferences, TWikiPreferences etc etc. One I can install on a Monday and not on a Saturday morning if you know what I mean.
[14:00] SvenDowideit: y
[14:00] ArthurClemens: Ok, I think we are off to all kinds of interesting discussions. What other things are holding off Dakar now?
[14:01] Lavr: The thing that makes me nervous is the bug arrival rate.
[14:01] PeterThoeny: fist, lets ask if we can agree on a 01 jan 2006 release date
[14:01] SvenDowideit: Lavr, is saying no..
[14:01] Lynnwood: Thanks ArthurClemens - I was trying to gauge that.
[14:01] SvenDowideit: i'm suggesting its too late..
[14:02] ArthurClemens: Do we know enough to say we can make it?
[14:02] CDot: let's find out
[14:02] Lavr: Each time I spend 2-3 hours testing I find 3-4 bugs. If I demo Dakar at work we always find a compatibility bug. Something that does not work on old topics.
[14:02] Lynnwood: how about the "official" release on the 1st but have our internal release a week before.
[14:02] Lynnwood: allow us to catch any minor "gotchas"
[14:02] PeterThoeny: no, don't look from the developers perspective, please consider the marketing side of the release
[14:02] Lavr: So power testing and fixing is needed. Can we make it for 1st of January. Yes. If more starts testing.
[14:03] PeterThoeny: s/release/release timing/
[14:03] CDot: we lost all the testers we had, I think, because of the delays up to now
[14:03] SvenDowideit: yes, please consider the marketing we need to attract open source developers
[14:03] SvenDowideit: the delays are killing that
[14:03] PeterThoeny: if if we were redady next friday it is not good to timing
[14:03] CDot: why not?
[14:03] SvenDowideit: wrt oss it is
[14:04] ArthurClemens: I would like to hear how much work is involved in other things
[14:04] Lynnwood: Can we have the marketing side of things ready for the 1st?
[14:04] Lavr: Well. Lately the bug arrival rate as decreased a little and it mainly on Wysiwyg.
[14:04] CDot: we are already burning the XMas holidays as "get familiar" time for upgraders
[14:04] PeterThoeny: on markeing: i am basically ready
[14:04] MichaelDaum: twiki.org itself is confusing most
[14:04] PeterThoeny: i got a good testimonial from novell for the press release
[14:05] ArthurClemens: Michael: good point. The homepage needs a makeover
[14:05] Lynnwood: MichaelDaum - I agree with you but I can't see redoing twiki.org before release!
[14:05] CDot: Lavr: yes. I don;t agree with tying the release to Wysiwyg availability.
[14:05] MichaelDaum: can we just relaunch a fresh twiki.org
[14:05] ArthurClemens: Peter has suggested to have Wysiwyg as beta
[14:05] PeterThoeny: back to release date please
[14:05] Lavr: What is the killer feature of Dakar? What will make people upgrade?
[14:05] PeterThoeny: do we agree on a 01 jan 2005 release date?
[14:06] CDot: MichaelDaum: interesting idea, but a huge amount of work
[14:06] Lavr: My users are waiting for one thing only. WYSIWYG.
[14:06] SvenDowideit: no PeterThoeny we don't
[14:06] CDot: PeterThoeny: no. I want a 2005 date, if we can do it.
[14:06] CDot: I will not be here anyway, so it's purely from a marketing perspective
[14:06] PeterThoeny: even if this hurts twiki from the markeing perspective (little attention span)?
[14:07] CDot: I want people to see a regular release cycle
[14:07] PeterThoeny: please be realistic
[14:07] SvenDowideit: ie a twiki day
[14:07] Lynnwood: Sounds like there's some symbolic or personal feeling behind choice between 12/24 and 1/1
[14:07] CDot: yes, symbolic
[14:07] SvenDowideit: like the patch tuesday microsoft have
[14:07] PeterThoeny: 01 sep 2004 to 24 dec 2005
[14:07] PeterThoeny: vs 01 sep 2004 to 01 jan 2006
[14:07] SvenDowideit: is much better
[14:07] CDot: the magic is in the "2004->2005"
[14:08] CDot: versus "2004->2006"
[14:08] SvenDowideit: i'd be happier with 31/12/2005 than 1/1/2006
[14:08] SvenDowideit: as from an oss marketing angle
[14:08] Lavr: From a marketing perspective: What sells Dakar? What is the reason for people to upgrade? What do I get that I don't have in Cairo? And is that worth releasing?
[14:08] MichaelDaum: can we get the date out of the release name , please
[14:08] SvenDowideit: its hugly different
[14:08] CDot: Lavr: good question
[14:08] SvenDowideit: i concure
[14:08] SvenDowideit: never liked the naming system
[14:09] CDot: I tried to address that in DakarReleaseNotes
[14:09] CDot: (the "what do I get" question)
[14:09] ArthurClemens: Lavr: indeed these things should go on the release homepage, and on the twiki.org homepage
[14:09] terceiro: at least for my users (and people in Brazil in general), user interface i18n is a great reason ro upgrade
[14:09] Lavr: No. Not the long release notes. What are the top 3 features?
[14:10] ArthurClemens: Peter, do you think 31 dec is bad for publicity? People will read the news the day later anyway.
[14:10] CDot: Security, Internationalisation, mod_perl
[14:10] MichaelDaum: yep
[14:10] SvenDowideit: and configure, registration, sessions(for admin)
[14:10] CDot: he said top three
[14:11] CDot: I was trying to summarise
[14:11] MichaelDaum: security, security, security
[14:11] SvenDowideit: y, which are different depending on who it is
[14:11] ArthurClemens: So, we have a top 10!
[14:11] Lavr: If you have Cairo you do not care for configure. Registration is a good one. Sessions was already in Cairo in a plugin.
[14:11] SvenDowideit: y, dakar has alot of killer features, we've just forgotten over time
[14:11] SvenDowideit: Lavr, some of us do care for configure on upgrade
[14:12] Lynnwood: I'd say expand the list to 5 or 6. or top 3 features in a couple categories.
[14:12] SvenDowideit: especially those that change their setup alot
[14:12] SvenDowideit: to demo things
[14:12] Lynnwood: Some speak to admins, some to uses.
[14:12] Lavr: My point is that there is really no top 3. There are many small incremental improvements.
[14:12] PeterThoeny: for the press release we need a bullet list of top 5 features
[14:12] MichaelDaum: hierarchical webs
[14:12] CDot: anyway, I'm getting drunk, so can we focus on the key questions please?
[14:12] CDot: what do we need to release?
[14:12] Lavr: If I don't upgrade I don't need configure-
[14:12] ArthurClemens: Lets make the killer list on DakarRelease, and practice the marketing texts.
[14:12] CDot: so far we established 40 hours of Peter and Lynnwood
[14:12] Lynnwood: sounds good.
[14:13] Lynnwood: I'm ready to burn the midnight oil if I see a release coming out of it.
[14:13] CDot: what else? Is a killer-list a requirement? If so, who will do it? And when?
[14:13] Lavr: Hierachical webs, WYSIWYG, registration. That is the real top 3.
[14:13] Lynnwood: what about a poll among developers and core users.
[14:13] Lynnwood: ?
[14:13] ArthurClemens: We need to continue this on DakarRelease
[14:13] Lavr: Those are the 3 features that matters.
[14:14] CDot could care a farthing for hierarchical webs
[14:14] CDot: cound'nt
[14:14] ArthurClemens: What else we have that holds up the release? Peter?
[14:14] CDot: Lynnwood: all the key people are here, now
[14:15] Lynnwood: perhaps - I just feel it's worth arguing about the key features.
[14:15] Lynnwood: not worth
[14:15] MichaelDaum: ok, so we need a good feature list as part of the announcement
[14:15] Lynnwood: there some personal preference involved
[14:15] Lynnwood: yep
[14:15] PeterThoeny: ok, i will create topic in codev to discuss the top features that should be listed in the press relrease
[14:15] MichaelDaum: but there's more in the marketing corner
[14:15] Lavr: The reason I mention the 3 key features is that 2 of them are not ready for release.
[14:15] CDot: PeterThoeny: good, thanks
[14:16] Lynnwood: ditto
[14:16] terceiro: thanks, god
[14:16] ArthurClemens: Peter, what else we have that is holding up the release?
[14:16] PeterThoeny: ok, shall we move to other things that need to be done for the release?
[14:16] terceiro: PeterThoeny: please
[14:16] MichaelDaum: yes
[14:17] ArthurClemens: we are waiting
[14:17] PeterThoeny: http://twiki.org/cgi-bin/view/Codev/AddWysiwygPluginToDakar
[14:17] PeterThoeny: this is a competitive necessity
[14:17] ArthurClemens: What is the status, CDot?
[14:17] PeterThoeny: since many other wikis already ship with a wysiwyg editor
[14:18] PeterThoeny: i do not worry about the quality of the plugin as long as we set the right expectation
[14:18] Lynnwood: I'm scanning the logs. Have we addressed which bugs are critical to close before release?
[14:18] CDot: my client has set mid jan as delivery date for the plugin
[14:18] MichaelDaum: hm, think micro kernel, that is keep things separate. TWikiFor is the right thing to do.
[14:18] CDot: I cannot guarantee anything stable before then
[14:18] CDot: however, it is continuously improving
[14:18] PeterThoeny: since this is a plugin it can be upgraded easily once a stable version is available
[14:19] CDot: I think it would be a mistake to bundle it, even as a beta
[14:19] PeterThoeny: by all means, ship it
[14:19] ArthurClemens: Lynnwood: this is item 2. We don't have the list yet.
[14:19] Lavr: I think that the feature set of Wysiwyg is adequate. The problem is how existing topics are handled if you open it and save it.
[14:19] PeterThoeny: and label it as alpha is needed
[14:19] Lynnwood: Thanks ArthurClemens
[14:20] PeterThoeny: crawford, what are you concerns about not shipping it with dakar?
[14:20] CDot: If we ship it, even as beta, people will assume that the "killer feature" is available
[14:20] Lynnwood: I agree with CDot about bundling wysiwyg. If we give it too much emphasis, it might come back to bite us.
[14:20] CDot: so they will try it, and because it is beta, it will have problems
[14:21] Lavr: When my users ask me about next TWiki version all they ask about is Wysiwyg. Noone really ask for anything else.
[14:21] CDot: possibly even lost content is a risk
[14:21] ArthurClemens: Lost content is a problem.
[14:21] SvenDowideit: Lavr, that was similar with cairo
[14:21] MichaelDaum: burned area if it does not hold up
[14:21] CDot: exactly
[14:21] SvenDowideit: there were few 'user' desired things then too
[14:21] PeterThoeny: lost content befind older rev?
[14:21] SvenDowideit: but for the power user
[14:21] PeterThoeny: or lost forever?
[14:21] CDot: if it doesn't hold up, everything is burned
[14:21] SvenDowideit: it was a huge upgrade
[14:21] CDot: nothing is lost forever
[14:22] CDot: Colas characterises twoi type of Wysiwyg users:
[14:22] CDot: 1. Non-techies who are afraid of TML, and think Wysiwyg is their way to use TWiki
[14:22] CDot: 2. Techies who want to use it to edit massive tables, but otherwise have no probs with TML
[14:23] Lavr: If Dakar does not have Wysiwyg I will not even consider upgrading the Motorola server. I will wait for Wysiwyg. It is THE REASON to upgrade. I will however upgrade my Motion TWiki to Dakar right away because that is a different target audience and not a corporate thing.
[14:23] SvenDowideit: Lavr, that is excellent
[14:23] MichaelDaum: but why not upgrade and install it on top?
[14:23] SvenDowideit: as its one less problem that will bite an early dakar release
[14:23] CDot: Lavr: thank you, good point
[14:24] CDot: the point is, that for audience (1), it has to be perfect
[14:24] SvenDowideit: doesn't Wysiwyg work on cairo?
[14:24] CDot: because non-techies will not forgive if it fails
[14:24] CDot: yes, it works on Cairo
[14:24] PeterThoeny: i am not sold, i still do not see a convincing point not to ship dakar with the plugin
[14:24] SvenDowideit: so Lavr's problem is solved
[14:24] ArthurClemens: We can add Wysiwyg in the killer top 10, but on the download page offer is as alpha as separate download.
[14:25] ArthurClemens: And include it when it is ready
[14:25] CDot: ArthurClemens: that seems reasonable to me
[14:25] SvenDowideit: it does sound like we need to unbundle whatever we can from the core
[14:25] PeterThoeny: no, not like this
[14:25] Lynnwood: sounds like a reasonable compromise
[14:25] SvenDowideit: so that we can release each component when its ready
[14:25] PeterThoeny: twiki gets downlaoded 250 times a day
[14:25] CDot: anyway, there is a dreadful Firefox bug, that I can't guarantee to fix for Dec 31
[14:25] SvenDowideit: y, small chickens
[14:25] PeterThoeny: only a handfull will install additional plugins
[14:26] Lavr: The plugin is fine TODAY featurewise. It is fixing bugs so topic are not currupted that is the issue.
[14:26] PeterThoeny: if we ship without i can't even sell that as a key part of dakar in the press release
[14:26] CDot: You can ship it disabled, I suppose
[14:26] CDot: then the admin has to enable it explicitly
[14:26] SvenDowideit: the expectation will be the same
[14:26] CDot: that might be acceptable
[14:26] ArthurClemens: We need a welcome page for the download, with the killer top 10 that people will see once installed. They will get the link to the alpha download there.
[14:26] SvenDowideit: ie, its in the release, so it works..
[14:27] CDot: caveat emptor
[14:27] Lavr: And I still don't see the point of releasing Dakar without WYSIWYG.
[14:27] SvenDowideit: experienced twikiers of course know better
[14:27] MichaelDaum: people love firefox extensions because they are visible
[14:27] SvenDowideit: y, and last i looked alot of twiki's success is due to the plugins
[14:28] PeterThoeny: what is the firefox bug?
[14:28] CDot: PeterThoeny: http://develop.twiki.org/~develop/cgi-bin/view/Bugs/Item1189
[14:28] Lynnwood: Lavr - I can think of lots of small reasons for not delaying Dakar for wysiwyg (all the other features) plus one BIG one: it's overdue.
[14:29] PeterThoeny: is ff1.5 a production release?
[14:29] CDot: yes
[14:29] Lynnwood: Dakar is an awesome advance even without wysiwyg
[14:29] SvenDowideit: if we wnat to attract oss devs, we need to market to them
[14:29] SvenDowideit: and releasing often is one requirement
[14:29] MichaelDaum: dakar is a major step towards TWikiApplications
[14:29] SvenDowideit: please, tell me if you don't think we need more oss devs
[14:30] SvenDowideit: as i will stop pushing this barrow
[14:30] ArthurClemens: Do we have some agreement on disabling Wysiwyg by default, or do we offer it as a separate download?
[14:30] CDot: we need more devs, IMHO
[14:30] CDot: show of hands; SvenDowideit?
[14:30] Lynnwood: that's broadly agreed among the developers
[14:30] SvenDowideit: y
[14:30] PeterThoeny: we need more good developers, but i do not see a connection to 12/31 vs 01/01
[14:30] CDot: ArthurClemens?
[14:30] SvenDowideit: ah, you should though
[14:30] Lavr: How far are we in time to get WYSIWYG with current feature set stable and in a quality so it does not currupt topics?
[14:30] SvenDowideit: its the way oss devs work
[14:30] ArthurClemens: voting for what?
[14:30] CDot: read back
[14:31] Lynnwood: let's just think of it as a quick poll to see where we stand
[14:31] CDot: your question
[14:31] ArthurClemens: this was rethorical I presumed
[14:31] CDot: "Do we have some agreement on disabling Wysiwyg by default, or do we offer it as a separate download?"
[14:31] SvenDowideit: right now,its clear to oss devs that there is always a large foggy delay between doing dev work and a release
[14:31] ArthurClemens: as ok
[14:31] ArthurClemens: ah ok
[14:31] SvenDowideit: and so they simply stay away
[14:31] CDot: Lavr: ?
[14:31] SvenDowideit: like with cairo
[14:31] ArthurClemens: So voting on which part of the question?
[14:32] CDot: the first part
[14:32] Lavr: CDOT. Just your evaluation. DO you need 2 weeks, 1 months, 2 months to get Wysiwyg stable?
[14:32] CDot: I month
[14:32] ArthurClemens: As long as the information is clear: do not use it on production environment yet.
[14:32] SvenDowideit: where there is work done, with not enough feedback, then when we declare a set of betas suddenly everthing gets delayed
[14:32] Lynnwood: I'd go with 12/31 simply because CDot - who has been the lead developer for Dakar - is requesting it.
[14:32] Lavr: So Dakar could be release 1 Feb 2006 with Wysiwyg?
[14:32] SvenDowideit: without the devs being involved in the process
[14:33] CDot: I am out until 22nd Dec, back for one day, out until 28th, back for one day, out until 3rd Jan.....
[14:33] PeterThoeny: we could shoot for 01 feb 2006
[14:33] MichaelDaum: that's more reasonable
[14:33] PeterThoeny: but this does not make the oss folks happy
[14:33] SvenDowideit: ok, so you basically don't see getting more devs involved as important
[14:33] Lynnwood: imo, he's earned enough "karma" in the past year to get that.
[14:33] SvenDowideit: compared to marketing to bussiness
[14:34] MichaelDaum: they are bringing back christmas presents anyway
[14:34] CDot: If I have any say in this matter, then hear me. I want Dakar to go in 2005. Without Wysiwyg. Period.
[14:34] SvenDowideit: i agree with Lynnwood on that too
[14:34] SvenDowideit: also
[14:34] CDot: Wysiwyg will follow mid Jan, or people can download a dev version "caveat emptor"
[14:34] ArthurClemens: Dakar, with Wysiwyg as alpha: yes.
[14:34] SvenDowideit: please be aware that more delay will reduce the time and interest from those devs that did participate in dakar
[14:34] CDot: if it is really important to them, then that;'s what they will do
[14:34] terceiro: I'm with CDot
[14:34] SvenDowideit: have you seen raf / will recently?
[14:34] MichaelDaum: CDot, doing a release in Dec 2005 is not making TheSplash: bad timing
[14:35] SvenDowideit: its the big splash wrt developers
[14:35] CDot: MichaelDaum: sorry, I no longer care. I just want the bloody thing released.
[14:35] PeterThoeny: this is really a bad timing
[14:35] MichaelDaum: most come back Jan 2006 to their news readers
[14:35] PeterThoeny: i will not go for this
[14:35] SvenDowideit: no
[14:35] SvenDowideit: ok
[14:35] SvenDowideit: peter, we're at an impass
[14:35] Lavr: Well. If we release Dakar new year - and schedule a Dakar bug fix update including WYSIWYG - announced - that sounds like a good compromize.
[14:35] Lynnwood: I think we're giving a little too much weight to the "big splash" aspect of this release.
[14:35] SvenDowideit: me too
[14:36] Lynnwood: ANY release will renew attention.
[14:36] CDot: right; witness the interest in the beta
[14:36] CDot: betas
[14:36] SvenDowideit: PeterThoeny, if you want to run the marketing campain as though you are a private company with paid developers
[14:36] CDot: I really have to go very soon; can we finish the list of "what has to be done" please?
[14:37] SvenDowideit: then you will end up having to actually pay them
[14:37] ArthurClemens: Peter, what is the bad timing for 31 dec 2005?
[14:37] Lavr: I know from my Motion project - if I release a beta 100 people download it. If I make a real release - 100 people download it - PER DAY. People are afraid of betas.
[14:37] SvenDowideit: otherwise the focus needs to take oss devs into account more
[14:37] SvenDowideit: y
[14:37] MichaelDaum: Lavr, so we need to release alot more
[14:37] CDot: PeterThoeny: why is 31 dec bad timing?
[14:38] PeterThoeny: we all agree that we need to relase more
[14:38] SvenDowideit: and with less well polished stuff
[14:38] PeterThoeny: at least monthly betas
[14:38] PeterThoeny: better by-weekly
[14:38] Lavr: Big releases rarely. And easy to upgrade releases that can be "patched" often is the best OSS model.
[14:38] ArthurClemens: Peter?
[14:38] Lynnwood: as long as they are easily applied. e.g. having archive that includes only changed files.
[14:38] CDot: PeterThoeny: why is 31 dec bad timing?
[14:38] MichaelDaum: every fix should be released as a minor one
[14:39] SvenDowideit: PeterThoeny: why is 31 dec bad timing?
[14:39] Lynnwood: easy guys. give him time to think
[14:39] Lynnwood: and type...
[14:39] PeterThoeny: we can release on 31 dec and label it as TWikiRelease2006x01x01x8954
[14:39] MichaelDaum: uh
[14:39] SvenDowideit: no, the label needs to say the same
[14:40] SvenDowideit: otherwise its obviously not a 2005 release
[14:40] CDot: why on earth would we do that? the whole point is to release in 2005! Why then label it 2006?????
[14:40] PeterThoeny: i do not want to change the release convention of 01 Somemonth Someyear
[14:40] SvenDowideit: while everyone else does?
[14:40] CDot: is that it? Is that the only reason?
[14:40] ArthurClemens: Why not?
[14:40] PeterThoeny: in the past we released mid month and labelled the release 01 Sep Someyear
[14:41] SvenDowideit: infact everyone else wants to remove the date totally?
[14:41] CDot: so let's label it 1 Dec 2005!
[14:41] SvenDowideit: y, and i wasn't happy about it
[14:41] MichaelDaum: no, please dont
[14:41] CDot: why not?
[14:41] MichaelDaum: call it twiki-4.0 (dakar)
[14:42] SvenDowideit: no, its confusing to use dates, and then not actually use the date that it was released on
[14:42] CDot: and why have we just spent a year installing TWiki 20050904?
[14:42] SvenDowideit: twiki 4 would be a huge improvement
[14:42] Lynnwood: The dates have been confusing in the past.
[14:42] MichaelDaum: exactly
[14:42] Lynnwood: as they didn't match the actual dates.
[14:42] CDot: which - if I'm still sober enough to parse it - is not the 1st of the month
[14:42] ArthurClemens: I am for twiki-4.0. You can see the dot releases and the dot dot releases.
[14:42] SvenDowideit: y, its actually twiki 3.3
[14:42] Lavr: If the release name is a date and it is released on another date - then that release scheme is more confusing than smart.
[14:42] SvenDowideit: y
[14:42] Lynnwood: So why not take this occasion to switch to some number as Sven suggests.
[14:43] CDot: I totally agree - I want the dat out of the release name
[14:43] PeterThoeny: this is a point where we disagree
[14:43] MichaelDaum: yes, please
[14:43] PeterThoeny: we do not need to solve that now
[14:43] MichaelDaum: I'm all with it
[14:43] PeterThoeny: this is not holding back the release
[14:43] SvenDowideit: PeterThoeny, there are alot of things where everyone seems to dissagree with you
[14:43] PeterThoeny: lets focus on what is holding us back
[14:43] MichaelDaum: this makes clear what 4.1 is
[14:44] MichaelDaum: if we can delay stuff for 4.1 then we are easier now
[14:44] SvenDowideit: and this is a huge barrier to oss devs
[14:44] MichaelDaum: can we also see the date for 4.1?
[14:44] PeterThoeny: on point 2, wysiwygplugin in release or not, where do we stand?
[14:45] MichaelDaum: not int 4.0
[14:45] CDot: see what I thought Peter and I had agreed in http://twiki.org/cgi-bin/view/Codev/TWikiReleaseNamingConvention
[14:45] CDot: (we hadn't agreed, but that's what I though we had agreed)
[14:46] Lavr: You cannot release Wysiwyg 1st Jan. If there is a release 1 Jan it should be default without and with an encouragement (with warning) to try the Wysiwyg plugin in non production environments. We need more to test it to get it stable and ready for 1st Feb.
[14:46] SvenDowideit: i didn't like it as its hard to tell the difference between 4.0 and 4.1 unless you remember magic numbers
[14:46] CDot: Lavr: that's my viewpoint as well
[14:47] SvenDowideit: thats why the build no isn't normally to prominenet in releases
[14:47] ArthurClemens: Peter, we haven't heard an argument for keeping the old naming scheme.
[14:48] PeterThoeny: please read TWikiReleaseNamingConvention
[14:48] MichaelDaum: this is a long topic ... any short version?
[14:49] PeterThoeny: "A naming like TWikiReleaseDakar7954 for a production release is developer centric. My goal was always to use a release name that is user centric, hence the date in the name and no code name."
[14:49] SvenDowideit: i can't see anything that supports the date naming
[14:49] SvenDowideit: especially over 4.1
[14:49] PeterThoeny: "A TWiki admin is more interested in knowing how old a release is, and where a release is in relation to other releases; (s)he does not care what the code name was for a release, and does not know that Cairo comes after Beijing. Hence the date in the release topic and package name."
[14:49] ArthurClemens: We agree that we need to name more user centric.
[14:49] PeterThoeny: "The date serves as an externally used release number. The internal build & release number can be based on the code name and SVN number."
[14:50] MichaelDaum: Peter, consider car naming
[14:50] ArthurClemens: These data can go into the documentation page.
[14:50] MichaelDaum: yes
[14:51] Lavr: The current date naming is confusing - and in some cases dangerous. If I downloaded Cairo in October - And I see there is a security update calles 04Sep2005 I think I am OK because I downloaded mine after 4th of September. We have seen many confused newbies here on IRC.
[14:51] MichaelDaum: every other oss project has a release scheme based on the major.minor.patch pattern
[14:51] SvenDowideit: well, most anyway
[14:51] CDot: hold on; if this is going to degenerate into a session explaining to Peter why he is wrong, then count me out. So far he has been totally inflexible in this discussion, and I can't see anything here that has not been argued already. So let's focus on what needs to be done to generate a release, please.
[14:51] MichaelDaum: this is jsut a point of growing up
[14:51] SvenDowideit: y, sadly i agree with CDot
[14:52] CDot: so far we have 40 hours work on docs
[14:52] MichaelDaum: delay stuff for a minor release, that's why we discuss the naming scheme, please dont forget that
[14:52] PeterThoeny: ok, i am the young kid
[14:52] CDot: can we have agreement on wyswiyg please?
[14:52] PeterThoeny: lets focus on the release
[14:52] ArthurClemens: To conclude: the majority of people here think that TWiki 4.0 (dakar) is more user centric.
[14:52] Lavr: I am not religiously against the date versions as long the date is the date it is released.
[14:52] SvenDowideit: without selling to oss devs, my interest is minimal too
[14:53] ArthurClemens: Wysiwyg
[14:53] MichaelDaum: I vote: no
[14:53] Lynnwood: I vote no basically - or Arthur's earlier proposal.
[14:53] CDot: reminder: the question was: (21:44:53) PeterThoeny: on point 2, wysiwygplugin in release or not, where do we stand?
[14:53] PeterThoeny: i see a danger in voting here
[14:54] Lavr: We should commit a bug update release on 1st Feb 2006 and introduce WYSIWYG with that.
[14:54] PeterThoeny: if we want to vote we need also makrketing persons and end users, not just developers
[14:54] Lynnwood: let's not think of it as voting. we have no agreement of majority rules.
[14:54] ArthurClemens: Peter, what do you see?
[14:54] CDot: PeterThoeny: the people on this call are the only ones who do any work, so why is there a danger? We decide.
[14:54] MichaelDaum: I agree with Lavr
[14:54] CDot: there are no marketing people
[14:54] Lynnwood: it's really a consensus. the real question is: do you want to block an agreement.
[14:56] PeterThoeny: consensus is if all agree
[14:56] Lynnwood: In a consensus process, it the general will of the group as whole becomes apparent, the burden on the minority to either go along or try to sway.
[14:56] Lynnwood: agree to move forward.
[14:56] SvenDowideit: see current eu discussions for a great eg
[14:57] Lynnwood: consensus is not unanimous agreement. that is very rare.
[14:57] MichaelDaum: better any consensus than none (T.Blair)
[14:57] SvenDowideit: and its not a singular ruler either
[14:57] SvenDowideit: ok, left field q.
[14:57] Lavr: I have voiced by oppinion and have already moved my proposals towards what I think is consensus. I do not think we are that far apart from a compromise and concensus.
[14:57] PeterThoeny: ok, back to plugin or not
[14:57] SvenDowideit: it sounds like we have 2 'products' needed
[14:58] SvenDowideit: one for oss, and one for marketing to companies
[14:58] Lynnwood: y Lavr - you've demonstrated good consensus spirit there.
[14:58] SvenDowideit: for oss we need lots of actual releases, but some bugs are ok
[14:58] SvenDowideit: for big companies, no real bugs, and fewer releases
[14:58] PeterThoeny: sven: to be, betas are the production releases of oss folks
[14:59] SvenDowideit: not good enough unfortunalty
[14:59] CDot is rapidly running out of time on this call
[14:59] Lavr: We all have Lynnwood. And you guys are always great to chat with. That is why I chose Twiki in the first place
[14:59] PeterThoeny: that assumes that the quality of betas is "good enough"
[14:59] PeterThoeny: which it is
[14:59] SvenDowideit: as oss ppl ignore betas
[14:59] CDot: please get back to the topic
[14:59] SvenDowideit: its a marketing thing, but marketing at oss devs
[14:59] CDot: what needs to be done to release Dakar?
[14:59] PeterThoeny: ok, ship the plugin or not
[14:59] SvenDowideit: ok, sorry PeterThoeny can we continue after CDot is gone?
[15:00] CDot: majority says "no, ship in Feb"
[15:00] SvenDowideit: no for me, until the developer / sponsor is happy with it
[15:00] SvenDowideit: as pride and reputation is the only currency twiki can pay devs with
[15:00] PeterThoeny: that does not solve the competitive necessity question
[15:01] ArthurClemens: There have been several options offered: (1) list in the top 10 + offer as separate download; (2) include in release, but communicate clearly that it is an alpha and not meant for production sites
[15:01] PeterThoeny: unless we delay dakar to 01 feb 2006
[15:01] CDot: it is open source software
[15:01] PeterThoeny: (which i do not want)
[15:01] Lynnwood: but competitive necessity doesn't directly relate to the release schedule. It can be managed.
[15:01] CDot: I am not blocking anyone else fixing the last few bugs
[15:01] PeterThoeny: i am all for (2)
[15:02] Lynnwood: O
[15:02] PeterThoeny: "include in release, but communicate clearly that it is an alpha and not meant for production sites"
[15:02] Lynnwood: I'm sorry - where is "2"?
[15:02] Lynnwood: ah. thanks
[15:02] CDot: I don't see (2) as an option. It will be assumed to be 100%.
[15:03] Lynnwood: CDot - not if we explicity say what peter said there.
[15:03] ArthurClemens: CDot: I am not so sure about that either
[15:03] CDot: then ship it disabled
[15:03] CDot: as I said; caveat emptor
[15:03] PeterThoeny: it will be labelled as alpha in the press release and should be labelled as such in the plugin topic
[15:03] Lynnwood: that would be wise for an alpha feature anyway.
[15:03] ArthurClemens: yes
[15:03] CDot: but do not ship it as a default component
[15:03] ArthurClemens: (disabled)
[15:03] CDot: i.e. enabled
[15:04] MichaelDaum: is that looking professional?
[15:04] PeterThoeny: i see that we seem to agree to ship with dakar, label it as alpha, and disable it
[15:04] Lynnwood: yes
[15:04] CDot: yes
[15:04] PeterThoeny: good
[15:04] ArthurClemens: ok
[15:04] Lynnwood: awesome
[15:04] PeterThoeny: excellent!
[15:04] CDot: what else?
[15:04] MichaelDaum: not blocking
[15:04] CDot: what else?
[15:05] ArthurClemens: Lets ponder a while on our past achievements
[15:05] CDot: what else?
[15:05] MichaelDaum: the header art
[15:05] Lynnwood: an honorable position MichaelDaum
[15:05] CDot: what else?
[15:05] CDot badly needs another beer
[15:05] MichaelDaum: we need to polish the look a little, still
[15:05] Lynnwood needs his first.
[15:05] PeterThoeny: ok, we talked about point 1 (docs), point 2 (wysiwyg)
[15:06] PeterThoeny: point 3: missing classicskin
[15:06] PeterThoeny: http://develop.twiki.org/~develop/cgi-bin/view/Bugs/Item1190
[15:06] MichaelDaum: ArthurClemens, what about the header art we discussed on modernizing pattern
[15:06] CDot: Lynnwood: can you please take over the duty of logging this discussion somewhere public? thx
[15:06] ArthurClemens: This is waiting for feedback
[15:06] Lynnwood: CDot - yes
[15:06] MichaelDaum: ArthurClemens, put it in and see what people say
[15:07] Lynnwood: I was going to ask for suggestions where to post it.
[15:07] ArthurClemens: Peter, more items?
[15:07] Lynnwood: Perhaps one of our private installations for now.
[15:07] Lynnwood: or on DEVELOP
[15:07] terceiro: I have one item: finishing all current translations
[15:07] MichaelDaum: ntwiki
[15:07] MichaelDaum: yes
[15:07] ArthurClemens: point 4: translations
[15:07] PeterThoeny: i have a few smaller items
[15:08] PeterThoeny: perhaps lets ask participants for their "must have"
[15:08] ArthurClemens: Lets divide our time in 10 minutes each, max.
[15:08] CDot: what remains to be done on translations?
[15:08] SvenDowideit: rest - i'm working on the docs for it now
[15:08] ArthurClemens: Dutch needs to be done for a great part
[15:08] SvenDowideit: as in rest_cgi
[15:08] ArthurClemens: (and tested)
[15:08] terceiro: CDot: people need to complete the translations
[15:09] PeterThoeny: point 5: rest
[15:09] CDot: SvenDowideit: there are no open bugs for rest?
[15:09] MichaelDaum: mod_perl testing
[15:09] SvenDowideit: not that i could find, but i will make sure
[15:09] CDot: how is this being tracked? Why is it suddenly a requirement?
[15:09] PeterThoeny: sven: what about the security question?
[15:09] SvenDowideit: i've applied the patch raf made
[15:09] PeterThoeny: e.g. plugins need to declare rest-enabled functions
[15:10] SvenDowideit: all that ccrb required was better docs
[15:10] CDot: PeterThoeny: the patch deals with that
[15:10] CDot: SvenDowideit: ok
[15:10] PeterThoeny: ok, good
[15:10] ArthurClemens: Is rest discussed?
[15:10] PeterThoeny: look like
[15:10] SvenDowideit: i simply need it to do the ajax wrk i've got
[15:10] SvenDowideit: y
[15:10] ArthurClemens: Peter, classic skin?
[15:10] PeterThoeny: is rest a selling point for dakar?
[15:11] CDot: no
[15:11] CDot: it's too geeky
[15:11] ArthurClemens: What can you do with it?
[15:11] CDot: please can we concentrate on what needs doing? Whimper?
[15:11] Lavr: Will the code (excluding Wysiwyg) be stable enough end of this month? With stable I mainly mean that users can upgrade from Cairo to Dakar and 99.9% of all topics shows satisfactory.
[15:12] PeterThoeny: arthur: http://en.wikipedia.org/wiki/REST
[15:12] ArthurClemens: will read later, thanks
[15:12] CDot: Lavr: that depends on whether you uncover any more bugs or not
[15:12] Lavr: I continue testing natually.
[15:12] ArthurClemens: The list was: (3) classic skin, (4) translations
[15:13] PeterThoeny: (5) rest
[15:13] PeterThoeny: (why do I see a hand?)
[15:13] CDot: unfotunately, I cannot continue fixing, so any requirement or urgent level bugs will either be fixed by someone else, or the release cannot go.
[15:13] Lynnwood: quick note: I'm juggling some family stuff. I'll be tracking conversation here but in an out a bit for next few minutes.
[15:13] PeterThoeny: meant this: ( 5 ) rest
[15:13] Lavr: I think we need to get more large installations to try the new beta 5 against their existing webs.
[15:14] MichaelDaum: can we switch part of twiki.org to dakar?
[15:14] PeterThoeny: on rest, i do not see a reason why not to take it into dakar as long as security is ok
[15:14] terceiro: are we in a release freeze or not?
[15:14] Lavr: I have a SVN installation running at Motorola now with a selection of webs and I have asked the biggest TWiki geeks to use it whenever they have time. Many of my error reports come from there.
[15:14] PeterThoeny: michael: i think dakar is now ready for twiki.org
[15:15] terceiro: I mean, feature freeze
[15:15] PeterThoeny: missing part was installpassword
[15:15] CDot: terceiro: rest was already passed by CCRB
[15:15] terceiro: CDot: ok then
[15:15] Lavr: Twiki.org is a good idea. That is for sure a large installation.
[15:15] CDot: it's just running late due to SvenDowideit's hopeless inefficiency
[15:15] SvenDowideit: i though raf was doing it
[15:15] CDot: exactly
[15:15] CDot:
[15:15] PeterThoeny: on (4) anything to add?
[15:16] PeterThoeny: anybody needs help from other?
[15:16] PeterThoeny: item 940 : translations
[15:16] terceiro: PeterThoeny: I'll mail all people that have already translated to complete their translations
[15:16] PeterThoeny: s/940/(4)/
[15:16] terceiro: ArthurClemens: this means string freeze
[15:16] CDot: we need to have tracking items in bugs web, at Requirement level, fo all items discussed here as blocking
[15:16] CDot: Lynnwood: can you make sure that happens please?
[15:17] ArthurClemens: terceiro: understood
[15:17] terceiro: ArthurClemens: great
[15:17] ArthurClemens: Wait: I want to have one more thing: Show menu, Hide menu
[15:18] CDot: ArthurClemens: my gut says "no"
[15:18] CDot: too late, too risky
[15:18] PeterThoeny: arthur: is this a new point?
[15:18] Lavr: Feature freeze!
[15:18] ArthurClemens: ok, TWiki4.1 then
[15:18] CDot: yep, thx
[15:19] PeterThoeny: what other "must have" points?
[15:19] ArthurClemens: What items about classic skin?
[15:19] CDot: ?
[15:19] PeterThoeny: i do not see the classicskin in the twiki web
[15:19] CDot: because it is now a contrib
[15:19] ArthurClemens: I see Item1190
[15:19] PeterThoeny: it was there previously, but with an old screenshot
[15:20] ArthurClemens: That is a doc update
[15:20] PeterThoeny: it's not in today's beta
[15:20] CDot: ah - it is missing from the MANIFEST
[15:20] CDot: it is not in the MANIFEST for ClassicSkinContrib
[15:21] PeterThoeny: some more related issues on classicskin
[15:21] CDot: hum; yes it is
[15:21] CDot: hmmmm
[15:21] PeterThoeny: Item1190, Item736
[15:22] ArthurClemens: Problem is, there is no maintainer of that skin
[15:22] Lavr: I just tried ?skin=classic. Bottom menu is broken.
[15:22] PeterThoeny: there are many issues with the classicskin
[15:22] PeterThoeny: i18n is missing
[15:22] MichaelDaum: in Item1190: the natskin is not part of the release
[15:22] PeterThoeny: login/logout is missing
[15:22] PeterThoeny: screenshots are old
[15:22] PeterThoeny: and probably many new dakar elements are missing
[15:23] ArthurClemens: For sure
[15:23] SvenDowideit: so we should drop it as unmaintained
[15:23] terceiro: SvenDowideit: that's why I would say
[15:23] PeterThoeny: not all needs to be fixed for dakar
[15:23] PeterThoeny: i18n is deferred (ok)
[15:24] PeterThoeny: it is not a question to drop classic skin
[15:24] ArthurClemens: Screenshot is important (no robot), but that is docs I assume
[15:24] CDot: Lavr: I just tried http://develop.twiki.org/~develop/cgi-bin/view/Bugs/Item1190?skin=classic - bottom menu looks fine to me....
[15:24] SvenDowideit: then you'll simply have to fix it
[15:24] PeterThoeny: if you add ?skin=asdfasdfasd you will end up in classic skin
[15:24] CDot: no you won't
[15:24] MichaelDaum: I got the impression that fixing classicskin will delay the release.
[15:24] PeterThoeny: the skin is also used as a base for new skins (at least it is documented as such)
[15:24] SvenDowideit: personally i can't see any reason to keep it
[15:24] CDot: you will end up in the default templates, which happen to be a copy of classic skin, but should not be referred to as such
[15:25] CDot: since they will be simplified over time
[15:25] Lavr: Cdot: http://merlin.lavrsen.dk/dakar/bin/view/Main/WebHome?skin=classic
[15:25] PeterThoeny: sven: you stated earlier that you will work with the classicskin enabled
[15:25] PeterThoeny: what happened to that?
[15:25] CDot: proper "ClassicSkin" is in the contrib
[15:25] SvenDowideit: i did it, and it worked well enough
[15:25] SvenDowideit: and i fixed some stuff
[15:26] SvenDowideit: but without a true maintainer, it just gets too crufty to release
[15:26] CDot: Lavr: looks like you have old templates
[15:26] PeterThoeny: i think there is a low hanging fruit to ship classic
[15:26] SvenDowideit: and thus i suggest we remove it and focus on doing one thing well
[15:26] PeterThoeny: it dos not need to be perfect, just workable
[15:26] CDot: Lavr: I removed the last %_'s a few days ago
[15:26] ArthurClemens: But is it enough to include login/logout?
[15:26] Lavr: Cdot: Maybe I need to rerun pseudo-install
[15:26] PeterThoeny: sanity check needed
[15:27] PeterThoeny: but it seems like this is ok according to sven
[15:27] PeterThoeny: new screen shots
[15:27] SvenDowideit: it was a few months ago
[15:27] PeterThoeny: login/logout
[15:27] SvenDowideit: and i figured login / logout wasn't needed either
[15:27] SvenDowideit: as no one seems to use classic enough to maintain it
[15:27] SvenDowideit: (again, oss dev pov)
[15:28] MichaelDaum: (qual pov)
[15:28] PeterThoeny: as i said, i do not see an issue with shipping a buggy classic skin, it just needs to work somewhat
[15:28] SvenDowideit: why ship it at all
[15:28] SvenDowideit: it only diverts attention
[15:29] CDot: why not? it's there as a contrib, just leave it
[15:29] ArthurClemens: 1 minute left for this point
[15:29] PeterThoeny: there are probably some users who do not want / can't use css based skins
[15:30] CDot: in a spirit of compatibility
[15:30] Lavr: CDot: Pseudo-install did not fix things. Classic bottom many still broken. We will have to investigate tomorrow
[15:30] ArthurClemens: I will add the login/logout
[15:30] PeterThoeny: twiki.org has some users who enabled classic skin
[15:30] CDot: Lavr: k
[15:30] ArthurClemens: Peter: recently?
[15:30] SvenDowideit: but without developers who work on it, its just gathering cruft
[15:30] SvenDowideit: which is worse to a dev
[15:31] PeterThoeny: arthur: not recently
[15:31] ArthurClemens: I think the most important things on classic have been mentioned.
[15:31] MichaelDaum: I even agree more with SvenDowideit looking at 4.x releases with more template refactoring
[15:31] PeterThoeny: related to classicskin, mentioned in http://develop.twiki.org/~develop/cgi-bin/view/Bugs/Item1190
[15:32] PeterThoeny: - plainskin docs
[15:32] PeterThoeny: - natskin question
[15:32] MichaelDaum: why are the sceenshots too big for it?
[15:32] PeterThoeny: develop.twiki.org shows natskin
[15:33] ArthurClemens: Please continue the discussion in the topic
[15:33] PeterThoeny: small screenshot should be 600x130, linked to larger screenshot of arbitrary size
[15:33] ArthurClemens: Translations have been mentioned
[15:33] MichaelDaum: ok
[15:33] ArthurClemens: (point 4)
[15:33] PeterThoeny: yes, any help wanted on transaltions?
[15:34] ArthurClemens: Swiss German?
[15:34] CDot: Someone needs to work on Tibetan
[15:34] ArthurClemens: Please someone have a look at English
[15:34] ArthurClemens: Do we have point 6?
[15:34] terceiro: English is the harder one
[15:35] PeterThoeny: how about Rumantsch, the 4th swiss language?
[15:35] CDot: we don;t have French, which is an issue
[15:35] PeterThoeny: spoken by 1% of swiss population
[15:35] Lynnwood: Hey guys - I'm really sorry. I'm being drawn away. Let me just mention some follow-up I'm planning. I'll post notes with summary of major points of conclusion (including questions still open) and follow-up actions.
[15:35] PeterThoeny: oh, french
[15:35] PeterThoeny: that is almost a must
[15:35] SvenDowideit: how about we finish now, as i have to go move in more stuff
[15:35] PeterThoeny: is someone working on it?
[15:35] CDot: Lynnwood: don;t forget to create a log of this calkl
[15:36] Lynnwood: yes the summary will include the raw log also.
[15:36] ArthurClemens: Action point: we need to attract translators.
[15:36] Lynnwood: or I should say the recond.
[15:36] CDot: My only remaining point is this; whatever you are working on, PLEASE COMMUNICATE!
[15:36] terceiro: PeterThoeny: AFAICT, there is no one working on a french translation
[15:36] PeterThoeny: this is not a show stopper for release
[15:36] CDot: It is really painful to sit staring at open items, unable to close them, with no status.
[15:37] PeterThoeny: crawford, not sure if this is a new point, just woud like a clarification:
[15:37] PeterThoeny: Item1025 Flooded with warn messages from misc plugins
[15:38] CDot: CLassicSkin.txt disappeared due to an SVN problem on my machine. It's not in the release, but it is OK in the manifest now.
[15:38] CDot: PeterThoeny: what is your question?
[15:39] PeterThoeny: if a company has developed a plugin for inhouse use, wil they get warning messages if the plugin uses an deprecared api call?
[15:39] MichaelDaum: yes
[15:40] SvenDowideit: as they should
[15:40] CDot: yes
[15:40] SvenDowideit: it really nasty to have that sort of problem and not get told often
[15:40] Lynnwood: The other item I'd like folks to consider if a regularly scheduled session like this is worthwhile. Not as long but regular schedule.
[15:40] PeterThoeny: hmm, that is almost a point, but not for today
[15:41] Lavr: When I put Dakar in production I will have a gigabyte or so per month saying...
[15:41] Lavr: | 17 Dec 2005 - 23:28 | BlackListPlugin defines deprecated endRenderingHandler
[15:41] Lynnwood: so later...
[15:41] SvenDowideit: Lavr, can you fix it?
[15:41] Lynnwood: and thanks to all for trying this out.
[15:41] ArthurClemens: Thanks Lynnwood for setting this up.
[15:41] SvenDowideit: Lynnwood, thanks for organising it, its been educational
[15:41] MichaelDaum: endRenderingHandler is really easy to fix, Lavr give it a try
[15:41] CDot: Lavr: you are welcome to provide a patch
[15:41] CDot: it's easy
[15:41] Lavr: Yes. I will just comment out the line in the TWiki code that writes the warning
[15:42] PeterThoeny: so this is point 6 then
[15:42] ArthurClemens: Do we have an action list?
[15:42] CDot: Laver: do you paint the tyres on your car black when the tread wears thin as well?
[15:42] SvenDowideit: sounds like
[15:42] Lavr: Last time I tried to Fix soe perl code on TWiki noone could find their bugs for two hours.
[15:43] PeterThoeny: point 6: review Item1025
[15:43] Lavr: I am learning but I am still far
[15:43] ArthurClemens: MichaelDaum mentioned the header art - point 7?
[15:43] MichaelDaum: yep
[15:43] MichaelDaum: what about mod_perl testing
[15:43] PeterThoeny: could you explain point 7?
[15:44] CDot has had enough
[15:44] MichaelDaum: there's a bug item about that
[15:44] CDot: sorry, gang, I really have to go
[15:44] CDot: nice chatting to you
[15:44] ArthurClemens: See ya, CDot
[15:44] MichaelDaum: bye bye CDot
[15:44] Lavr: Thanks CDot. For tonight and for 10000+ lines of code.
[15:44] ArthurClemens: Point 7 = http://twiki.org/cgi-bin/view/Codev/ModernizePatternSkin
[15:44] CDot (n=crawford@crawfordcurrie.plus.com) has left #twiki_dakar
[15:45] MichaelDaum: see also http://ntwiki.ethermage.net/~develop/cgi-bin/view/Bugs/Item959
[15:46] PeterThoeny: is that a showstopper for release?
[15:46] Lavr: Item 959. I will shout FEATURE FREEZE again.
[15:46] MichaelDaum: but the header art is just not there in pattern.
[15:47] MichaelDaum: and it is a low hanging fruit
[15:47] MichaelDaum: ArthurClemens has made a nice proposal
[15:47] ArthurClemens: Its the idea, the image can be worked on
[15:47] Lavr: Each time we touch the PatternSkin we fight for days before it looks right in all browsers.
[15:47] SvenDowideit: does low hanging include someone to do the work, and fix all the bugs before commiting
[15:47] Lavr: I like the idea but it should be 1st Feb.
[15:48] SvenDowideit: as i'm also yellin CODE FREEZE
[15:48] PeterThoeny: seems like point 7 should be deferred
[15:48] terceiro: I think so
[15:49] Lavr: New year is two weeks from now. Bug fixing and documentation should be the only focus. I will even stop testing Wysiwyg the next 2 weeks.
[15:49] MichaelDaum: polish is so important. sorry to mention it again
[15:49] ArthurClemens: We also need something when twiki.org goes Dakar
[15:49] ArthurClemens: Why not this next 2 weeks?
[15:50] PeterThoeny: ok, i try to upgrade twiki.org between xmas and new years
[15:50] ArthurClemens: Putting an image is not a code change
[15:50] MichaelDaum: yep
[15:50] ArthurClemens: It has been documented already
[15:50] Lavr: No. But changing style sheets is often causing 2-3 new bugs. And Pattern looks good right now.
[15:51] PeterThoeny: sorry, i am lost, waht is the discussion now?
[15:51] ArthurClemens: Well, the header is bare bones
[15:52] ArthurClemens: Changing style sheets - that has been the case with significant changes
[15:52] ArthurClemens: This is a small change that has been documented
[15:52] Lavr: Could it go in your Pattern cook book?
[15:53] MichaelDaum: maybe you can convince the others if you are quick
[15:53] ArthurClemens: It is in there.
[15:53] ArthurClemens: The question is: is this kind of image right?
[15:53] PeterThoeny: ok, i have to leave soon
[15:54] MichaelDaum: yes
[15:54] PeterThoeny: can someone create the minutes of this meeting?
[15:54] PeterThoeny: in codev
[15:54] ArthurClemens: http://develop.twiki.org/~develop/cgi-bin/view/TWiki/PatternSkinCssCookbookTopBarBackgroundImage
[15:55] Lavr: I get an error when I view that page Arthur
[15:55] ArthurClemens: an error..
[15:55] MichaelDaum: me not
[15:55] Lavr: A Runtime Error has occured. Line 169. Error: "Insertion" is undefined.
[15:55] MichaelDaum: only the logo looks bad
[15:55] PeterThoeny: any other points to discuss?
[15:55] Lavr: IE.
[15:56] MichaelDaum: can we start the party now
[15:56] MichaelDaum:
[15:56] Lavr: It was good to see you here "live" Peter.
[15:56] ArthurClemens: Peter, please leave a comment on http://twiki.org/cgi-bin/view/Codev/ModernizePatternSkin
[15:56] ArthurClemens: Lavr: prototype.js is not installed on develop
[15:57] ArthurClemens: PatternSkin needs to be installed
[15:57] PeterThoeny: Arthur: ok, i will
[15:57] MichaelDaum: Peter, I hope to talk to you more often!!!
[15:57] MichaelDaum: Thanks.
[15:57] ArthurClemens: Thanks
[15:57] terceiro: thank you all. Thank you Lynnwood for the initiative
[15:57] PeterThoeny: it was a constructive discussion
[15:58] PeterThoeny: i like it because it is effective
[15:58] ArthurClemens: Please come by more often on IRC. It has changed my way of working on twiki.
[15:58] Lavr: Very. I enjoyed it. And good compromises.
[15:58] PeterThoeny: thanks all for participating on a saturday, very early, very late, or away from kids
[15:59] Lavr: Yeah the Freenode network is for geeks and nerds only We never really see trolls here.
[15:59] PeterThoeny: on #twiki, frankly, the few times i looked at the logs it was full of politics
[15:59] PeterThoeny: it did not look inviting to me, not at all i am affraid
[15:59] SvenDowideit: thats the reality of oss
[15:59] MichaelDaum: I willk always recommend an irc channel for an oss
[15:59] MichaelDaum: it is important for support also
[16:00] ArthurClemens: Not to mention the small things, that is the oil that keeps the machine running
[16:00] MichaelDaum: ... just to say hello
[16:01] Lavr: I have by IRC open 24 hours on #motion and #twiki. We all come and go. It may take 20 hours before I answer. Everybody does that. I think there is a good mood in the #twiki channel. I would not be there otherwise.
[16:01] PeterThoeny: ok, my son asks me to play with him for quite a while now
[16:02] ArthurClemens: I am heading home. See you all here next days!
[16:02] PeterThoeny: so, when is next meeting?
[16:02] PeterThoeny: next sat is 12/24
[16:02] PeterThoeny: not good to meet
[16:02] Lavr: Not really.
[16:02] PeterThoeny: possibly fri 12/23?
[16:03] ArthurClemens (n=ArthurCl@213-84-74-216.adsl.xs4all.nl) has left #twiki_dakar ("Leaving")
[16:03] Lavr: I could on 23rd
[16:03] MichaelDaum: I can only join mo+tue+wed next week
[16:03] PeterThoeny: lets lynwood coordinate
[16:03] MichaelDaum: then family rulez
[16:04] Lavr: SWMBO (She Who Must Be Obeyed)
[16:04] PeterThoeny: oh, i realize i am out 12/21 to 12/23
[16:04] PeterThoeny: ok, nice chat
[16:04] PeterThoeny: thanks all! ttyl
[16:04] Lavr: See you. Thanks again.
[16:05] MichaelDaum: ok I will leave too but will be on #twiki still
[16:05] MichaelDaum (n=micha@twiki/developer/MichaelDaum) has left #twiki_dakar ("irc client terminated")
[16:05] Lavr (i=Lavr@0x535b29eb.albnxx17.adsl-dhcp.tele.dk) has left #twiki_dakar