>From Jesse Kuhnert <[EMAIL PROTECTED]>: > It seems like the timing sort of makes sense now. We still have to get > approval from tapestry-dev and any other sort of entities, but I don't see > why anyone would be against it. > The thing is that I don't want to have to manage the process of doing it.
I guess i could help here. > There are also a few additional items I'm not sure about: > > -) We don't want this looking like a tacos only sort of thing, there are a > lot of other people developing cool tapestry components. We should try and > get these people involved in the process as well. (Esp Ron Piterman) +1. There are one-two more i have in mind but the general spirit is that this is a tapestry thing, not tacos-only... > -) Someone needs to sit down and think about how this sub-project should > look in tapestry :) Just spin contrib off into it's own project? (If that's > the case we should probably kill off the unused contrib components as well) Actually, I was talking to Brain Wallace about this. Our initial idea was to keep contrib but also add effect and ajax (or tacos). Of course these libraries will exist under the same project. Ajax (or tacos) will mainly be tacos. Effect will be client-only dhtml stuff. Leonardo's + mine ideas are at http://tacoscomponents.jot.com/ToolBar/Developers. Some components from Tapfx will also endup there. > -) We can't move the new DatePicker into apache as that widget is LGPL. The > component is still very useful though. Do we leave it here in tacos along > with other items we can't put on apache for one reason or another? Yep, leave those here. Can't we have [EMAIL PROTECTED] play some other role in Tapestry - have some other scope? It has served us well till now. Recently it came up to top-700 sf projects which is better than it looks. Also, it has its own community. There are a lot of people here that I don't see in tapestry's ML. And its obvious that they're more skilled than tap's subscribers + this makes talking here more fun. I mean there are a few tap subscribers who just drive me [EMAIL PROTECTED]>$%!@ > -) What do we do about commit access? As much as I love what we have going > here, as well as the ability of other component developers for tapestry I'm > not thrilled with the idea that we can't control commit access on a project > level. How do other projects do this? Is this sort of a gentlemans agreement > where everyone knows more or less where they should and shouldn't be > developing and only stray off the path if they really feel comforatable with > it? How do other apache projects handle this? (Like maven? ) Don't know how this can be enforced. Can we ask at tap's dev list or perhaps have someone contact maven's? > -- > Jesse Kuhnert > Tacos/Tapestry, team member/developer > > Open source based consulting work centered around > dojo/tapestry/tacos/hivemind. > -- ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Tacos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tacos-devel
