I updated the rules, because I honestly don't want this meeting to drag on forever, so I'm putting up more defined rules. Let's all be as effecient as possible, please.
* the meeting will be moderated, please behave yourself * if you cannot behave yourself, you will loose the right to participate by loosing your +v privledges * the topic is WebWork and XWork, nothing more opinions and topics not directly related to the items in the meeting agenda are not allowed * we will adress one agenda item at a time. If you have something to say about a different agenda item, wait until it is brought up. * the current agenda item will be in the chat channel title window * if an open forum is not working, everyone will loose their +v status and all comments must be messaged to the moderator who will then give +v status only after each issue/agenda item has been brought up. Hopefully we can avoid this, but if it does happen, this is how order will be maintained. * lastly, _think_ before actually saying anything. Make sure that what you are about to say doesn't break any of the rules. This will make everything run much smoother. -Pat ----- Original Message ----- From: "Erik Beeson" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, February 04, 2003 9:42 AM Subject: [OS-webwork] Agenda Again > For those who can't see the link due to snipsnap running on a freaky port, > here's the agenda: > > The meeting will be at 14:00 GMT on Febuary 5th. If you have problems with > converting the timezone, click here, or search google for help. It will > cover both XWork and WebWork 2.0. > > RULES: > nobody is allowed to say how great they are > nobody is allowed to throw in random mean comments > random opinions about the world are also considered offtopic. It should > strictly be webwork related. > > AGENDA: > ThreadLocal > documentation > compatability > taglibs > 1. using velocity for all the UI widgets > 2. expanding the number of taglibs (ww:hidden, ww:form, etc) > 3. having more standard velocity macros > dependencies > configuration > 1. programmatic configuration > supported views > forms allow one-submit-only > validation > 1. formproc > define sample app > 1. wiki > 2. wafer project > 3. rss reader > 4. petstore > pull the Action instantiation out and into an Interceptor > consider different approaches on implementing actions > map dynamic elements to a given action > > NOTES: > > <Epesh> I'd say scope is the first thing (docs) > > <Epesh> along with "process" -- how do you decide what's an acceptable > change to scope? > > <jcarreira>Well, that's important, but I'd vote for ThreadLocal first... > that's the most important to keep me working (since I'm stuck on that now > and don't want to make a decision for everyone). > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
