Kenneth: TWikiFns. Ask Meredith if she is committed to drive it further - and when. It takes a driver to continue this further. There is still full support for the idea.
No answer from Meredith to the last minutes. Kenneth will send email.
Rafael: Take a stab at defining the scope of finishing the work of implementing TWikiFns including docs, t.o. code, testcases etc
All: Configure on DEVELOP: "as a general statement, there is no need to tell CDot anything else than - go ahead - and here is our additional wishlist." More of us will try to test further.
The new feature is now in the TWiki4 branch and being matured.
PreInstallSmartEditAddOn looks promissing but does not work on Safari. So needs more work. But could be TWiki distribution candidate.
Arthur: will try and look at code as time allows
Anyone: Can we get the developer access to a MacOS machine with Safari? (does he have access to one already - and is his sponser OK with spending time on this aspect?)
Update: Reports indicate that the performance on anything but very small topics is unacceptable. See PreInstallSmartEditAddOn.
2. Modify ChangeProposal for new TWiki Release 4.1 Process
Form Change Process to accept change proposals
Desired outcome: Brainstorm on how the ChangeProposals need to be modified so support the new TWikiRelease04x01Process; identify owner to implement the modifications
The process was discussed. The next step is to modify the Codev TWiki Application in a way that we can separate the wishes from users that are not committed from the proposals from people that are committed to implement the proposed feature. The discussion continues but we soon need the changes implemented to be able to use the new process because we cannot separate the committed feature proposals from the more than 250 proposals.
Current process: ChangeProposal, ChangeProposalForm. There was agreement that the process should be simplified and that we need the field for committed developer back.
Sam Hasler will take a stab at implementing what was discussed.
3. Review proposed items
Desired outcome: Identify action items for proposed items in WhatIsIn04x01 that have open questions
We did not have participants to do this.
4. Profiling framework for TWiki
Desired outcome: Try to define roadmap for easy to use profiling tool
HaraldJoerg has proposed a good start at BenchmarkFramework. Harald should ask for which parts of the work others can help on.
Harald has already checked in the first part of the work in collaboration with Crawford. The issue is currently that the basic profiling does not tell us enough and the more detailed kind will tell us too much. We will need a tool to handle the large quantity of data the detailed tool will give us.
Harald is still asking for more feedback. Harald will describe a bit more when is available now so we can provide better feedback.
Action Items
KennethLavrsen: Send email to Meredith to ask for status on commitment to finish TwikiFns
SamHasler: Draft the changes to the ChangeProposal process in Codev based on the brainstorming info from today
I moved SmartEditAddOn discussion to PreInstallSmartEditAddOn.
-- PeterThoeny - 15 Sep 2006
Kenneth, if you have time could you finish the notes of this meeting? It was my understanding that you would take the notes. We need the action items for EdinburghReleaseMeeting2006x09x18.
-- PeterThoeny - 16 Sep 2006
Done. I had made some preliminary notes during the meeting in an open text editor on my Windows machine and the plan was to copy paste that in the next morning. Next morning Microsoft had decided to send us all an update which rebooted the machine at the end. So my text was lost. And then the focus changed to getting the hotfix 4 out. But I have read through the log now and recaptured the action items.
-- KennethLavrsen - 16 Sep 2006