Re: summer of code - next steps
It would require 2 new entries in the avail document in CVSROOT - so while its possible - I'm not sure if infrastructure would wish to deal with that. -Tim Yoav Shapira wrote: Hi, Would this work? Or request restricted access to only - jakarta-tomcat-jasper - jakarta-tomcat-catalina/webapps/balancer The user id id would be prefixed or suffixed with soc. This also assumes no binding voting rights. Thoughts? - Drop the soc from the userid ? - Let them be full committers ? - Other? Since tomcat seems to be one of the last ones in cvs - I am not sure how using svn will work with respect to this. Do we need a vote so we can make the appropriate requests to infrastructure? We're in a bit of a bind. I don't want to let them be full committers: that's a hard-earned privilege. Same thing for the @apache.org address, so I want to keep the soc prefix. But we use CVS, and I don't think CVS supports directory-specific commit privileges. We'd have to make a branch for them, assuming CVS supports branch-specific commit privileges? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: summer of code - next steps
Thank-you for your e-mail. Please note that i will be away from the office starting Wednesday June 29th, returning Thursday July 7th, with no access to email. In my absence, kindly contact Cheri Dueck at [EMAIL PROTECTED] Kind Regards, Natasha Hasmani Senior Event Manager - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: summer of code - next steps
Thank-you for your e-mail. Please note that i will be away from the office starting Wednesday June 29th, returning Thursday July 7th, with no access to email. In my absence, kindly contact Cheri Dueck at [EMAIL PROTECTED] Kind Regards, Natasha Hasmani Senior Event Manager - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: summer of code - next steps
Would this work? Or request restricted access to only - jakarta-tomcat-jasper - jakarta-tomcat-catalina/webapps/balancer The user id id would be prefixed or suffixed with soc. This also assumes no binding voting rights. Thoughts? - Drop the soc from the userid ? - Let them be full committers ? - Other? Since tomcat seems to be one of the last ones in cvs - I am not sure how using svn will work with respect to this. Do we need a vote so we can make the appropriate requests to infrastructure? -Tim Yoav Shapira wrote: Hey, How should code be accepted for these? - Create a new sandbox? - Place on SF then have the mentor commit as needed SF CVS doesn't work well enough IMO. Maybe the ASF will have a repository that can be used as a staging area. - Full commit for the student I suspect it could happen fairly quickly. We've been planning to give the students commit access to just their section of code, or an entirely separate repository. Remy's suggestion of SVN first is good, because SVN allows configuring commit access to users on a directory level. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: summer of code - next steps
Hi, Would this work? Or request restricted access to only - jakarta-tomcat-jasper - jakarta-tomcat-catalina/webapps/balancer The user id id would be prefixed or suffixed with soc. This also assumes no binding voting rights. Thoughts? - Drop the soc from the userid ? - Let them be full committers ? - Other? Since tomcat seems to be one of the last ones in cvs - I am not sure how using svn will work with respect to this. Do we need a vote so we can make the appropriate requests to infrastructure? We're in a bit of a bind. I don't want to let them be full committers: that's a hard-earned privilege. Same thing for the @apache.org address, so I want to keep the soc prefix. But we use CVS, and I don't think CVS supports directory-specific commit privileges. We'd have to make a branch for them, assuming CVS supports branch-specific commit privileges? Yoav Shapira System Design and Management Fellow MIT Sloan School of Management / School of Engineering Cambridge, MA USA [EMAIL PROTECTED] / [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: summer of code - next steps
Tim Funk wrote: It appears that 2 (or 3) tomcat related projects have been accepted.. - reverse proxy - jsp compilation speed As I understand it, the above two are a done deal. I'll mentor the second one. - JSTL tag plugins (Unless this belongs to the jakarta taglib folks) Oviously it's taglib related, but I don't think taglibs have business shipping Tomcat proprietary code. How should code be accepted for these? - Create a new sandbox? - Place on SF then have the mentor commit as needed SF CVS doesn't work well enough IMO. Maybe the ASF will have a repository that can be used as a staging area. - Full commit for the student I suspect it could happen fairly quickly. - Other This was talked about on the other mailing lists. For those using svn - it seems a temporary account can be given to svn without needing to provide a shell account. Since we are using cvs - thats not possible. That's what I understood (more or less). I propose we take the code in SVN, and put it in our CVS when it gets ready. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: summer of code - next steps
Hey, How should code be accepted for these? - Create a new sandbox? - Place on SF then have the mentor commit as needed SF CVS doesn't work well enough IMO. Maybe the ASF will have a repository that can be used as a staging area. - Full commit for the student I suspect it could happen fairly quickly. We've been planning to give the students commit access to just their section of code, or an entirely separate repository. Remy's suggestion of SVN first is good, because SVN allows configuring commit access to users on a directory level. Yoav - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Summer of code - next steps?
I re-re-read the FAQ and here is what I interpret: Anyone may submit to Google a proposal (any meaning a student). Google will then take their favorite 200 and pass these along to the mentoring organizations. The mentoring organizations can give a thumbs up or down because they need to approve that the work was done at the end of the time period. Its up to the discretion of each project to incorporate the code produced by the student. But if the code is not worthy to be accepted, the student can still be paid (by Google) if the mentor says its OK. [I would imagine there could be cases where code is produced but not committed for a variety of reasons.] So it seems the wiki was a communication vehicle to let folks know what project mentoring organizatoins were interested in since it was up the mentoring organizations to say yes or no to whether they wish to mentor a specific proposal. I have no idea of the ramifications if multiple folks are interested in the same project and it they should submit competing or complementary proposals. I guess the google group dedicated to this has more information there. -Tim Remy Maucherat wrote: Tim Funk wrote: For those interested in Summer of code what do we need to do next? Is having the Wiki up to date enough? And we sit back while participants submit their proposals and Google chooses whom will get the stipend, while the folks listed on the Wiki mentor? http://code.google.com/soc_application.html Very good questions :) I'm interested too. I added the JSTL tag plugins for Jasper as another project, BTW. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Summer of code - next steps?
Tim Funk wrote: For those interested in Summer of code what do we need to do next? Is having the Wiki up to date enough? And we sit back while participants submit their proposals and Google chooses whom will get the stipend, while the folks listed on the Wiki mentor? http://code.google.com/soc_application.html Very good questions :) I'm interested too. I added the JSTL tag plugins for Jasper as another project, BTW. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Summer of code - next steps?
For those interested in Summer of code what do we need to do next? Is having the Wiki up to date enough? And we sit back while participants submit their proposals and Google chooses whom will get the stipend, while the folks listed on the Wiki mentor? http://code.google.com/soc_application.html -Tim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Summer of code
I was thinking of using HttpClient. Configuration - I am somewhat undecided. I like urlrewrite. Its also a BSD licence - so if we use their rules as a starting point - are we legally OK? (I think the answer is yes) -Tim Peter Rossbach wrote: Hey Tim, Have you see this fine mod_rewrite filter at http://tuckey.org/urlrewrite/. What you mean, can we use the common httpclient for backend proxy implementation? It has a stable pooling with keepalive handling and http/https support. Peter Tim Funk schrieb: Here is more detail of what I was pondering with the reverse proxy. Topic - Extend the balancer webapp to allow for reverse proxy Description - Write a 2.4 compliant Servlet Filter which will allow tomcat (or any other compliant engine) to act as a reverse proxy. Constraints --- - Use no tomcat internal specific api's - Allow for other filters to wrap this so caching would be allowed - Allow for pluggable proxy rules much like the balancer is implemented Rules to create --- - simple match rule which is one-to-one mapping back to a single server based on a URL prefix Nice to haves - - Use a pool of connections to take advantage of keep-alive capabilitites - A partner caching filter which can cache to memory/disk/??? - A partner filter which can provide rudimentary content rewriting for hosts which return an incorrect hostname - cluster rule - So tomcat fronts a cluster of servers for the following scenarios 1) round robin 2) random 3) sticky Remy Maucherat wrote: I think there should be proposals, like this one which seems good, then have a vote on all these. Please be quick for the proposals as there's a deadline, apparently, so I'd say this needs to be wrapped up and the wiki edited by the end of next week. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Summer of code
Out of curiosity, is a mod_jk 1.2.14 vote set to occur at some point? Or are there known issues with 1.2.13 at this point? [My understanding is that the odd-even release # model is now being followed -- correct?] -- Jess Holle - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Summer of code
Here is more detail of what I was pondering with the reverse proxy. Topic - Extend the balancer webapp to allow for reverse proxy Description - Write a 2.4 compliant Servlet Filter which will allow tomcat (or any other compliant engine) to act as a reverse proxy. Constraints --- - Use no tomcat internal specific api's - Allow for other filters to wrap this so caching would be allowed - Allow for pluggable proxy rules much like the balancer is implemented Rules to create --- - simple match rule which is one-to-one mapping back to a single server based on a URL prefix Nice to haves - - Use a pool of connections to take advantage of keep-alive capabilitites - A partner caching filter which can cache to memory/disk/??? - A partner filter which can provide rudimentary content rewriting for hosts which return an incorrect hostname - cluster rule - So tomcat fronts a cluster of servers for the following scenarios 1) round robin 2) random 3) sticky Remy Maucherat wrote: I think there should be proposals, like this one which seems good, then have a vote on all these. Please be quick for the proposals as there's a deadline, apparently, so I'd say this needs to be wrapped up and the wiki edited by the end of next week. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Summer of code
Hey Tim, Have you see this fine mod_rewrite filter at http://tuckey.org/urlrewrite/. What you mean, can we use the common httpclient for backend proxy implementation? It has a stable pooling with keepalive handling and http/https support. Peter Tim Funk schrieb: Here is more detail of what I was pondering with the reverse proxy. Topic - Extend the balancer webapp to allow for reverse proxy Description - Write a 2.4 compliant Servlet Filter which will allow tomcat (or any other compliant engine) to act as a reverse proxy. Constraints --- - Use no tomcat internal specific api's - Allow for other filters to wrap this so caching would be allowed - Allow for pluggable proxy rules much like the balancer is implemented Rules to create --- - simple match rule which is one-to-one mapping back to a single server based on a URL prefix Nice to haves - - Use a pool of connections to take advantage of keep-alive capabilitites - A partner caching filter which can cache to memory/disk/??? - A partner filter which can provide rudimentary content rewriting for hosts which return an incorrect hostname - cluster rule - So tomcat fronts a cluster of servers for the following scenarios 1) round robin 2) random 3) sticky Remy Maucherat wrote: I think there should be proposals, like this one which seems good, then have a vote on all these. Please be quick for the proposals as there's a deadline, apparently, so I'd say this needs to be wrapped up and the wiki edited by the end of next week. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Summer of code
Hi, Correct Servlet Specification violation in reading manifests, aka bug 34993, is quite inappropriate for a full fledged summer project. The bug is actually invalid, but more generally the project would be far too short (see o.a.c.util.ExtensionValidator for the implementation of the extension check mechanism mandated by the specification). OK, good. Thanks for pointing that out and resolving the bug. If you haven't edited the wiki page yet, I'll do so in a moment. The intent on these projects is not necessarily for them to take 3 months of intense work: it's to get some students to write some code which will get them familiar and excited with open-source development. That's it: a low bar. Similarly, Tune Jasper Performance for Multiple JSPs should IMO be a more general Tune Jasper Compilation Performance :) Good point, will change. Enhance Tomcat to support one-to-many mapping of security roles might be also too short. We'll see. The idea is again to get them excited, maybe starting small, and then continuing to contribute with other stuff. I'd like to propose adding the following things to the summer of code: - tag plugins implementation for JSTL (finally) - improve admin/management tools (?) Sure. Feel free to edit the wiki page accordingly. Anyway, we need a community discussion on summer of code proposals. OK. My intent was to kick-start the process by posting some ideas to the wiki page, and that seems to have worked ;) Everyone, please take a look at http://code.google.com/summerofcode.html and the linked Apache ideas page (which is currently down for me ;(), and comment as you see fit. Anyone willing to be a mentor or help out, that's great. Any ideas for projects are also welcome. Yoav - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Summer of code
Yoav Shapira wrote: Hi, Correct Servlet Specification violation in reading manifests, aka bug 34993, is quite inappropriate for a full fledged summer project. The bug is actually invalid, but more generally the project would be far too short (see o.a.c.util.ExtensionValidator for the implementation of the extension check mechanism mandated by the specification). OK, good. Thanks for pointing that out and resolving the bug. If you haven't edited the wiki page yet, I'll do so in a moment. Don't know, the page is locked for me. The intent on these projects is not necessarily for them to take 3 months of intense work: it's to get some students to write some code which will get them familiar and excited with open-source development. That's it: a low bar. Makes sense. Where's the document on what summer of code ASF projects should be ? Similarly, Tune Jasper Performance for Multiple JSPs should IMO be a more general Tune Jasper Compilation Performance :) Good point, will change. Enhance Tomcat to support one-to-many mapping of security roles might be also too short. We'll see. The idea is again to get them excited, maybe starting small, and then continuing to contribute with other stuff. I think the current security is somewhat a dead end. Adding to the list of questions, I don't know yet if it will be touched up in the upcoming Servlet spec. So I'd rather not plan to base new work on the current code until we know more. I'd like to propose adding the following things to the summer of code: - tag plugins implementation for JSTL (finally) - improve admin/management tools (?) Sure. Feel free to edit the wiki page accordingly. Well, we'd need consensus on tasks, I think. Most of the time, I don't like it when a random piece of code pops out of thin air. Anyway, we need a community discussion on summer of code proposals. OK. My intent was to kick-start the process by posting some ideas to the wiki page, and that seems to have worked ;) Everyone, please take a look at http://code.google.com/summerofcode.html and the linked Apache ideas page (which is currently down for me ;(), and comment as you see fit. Anyone willing to be a mentor or help out, that's great. Any ideas for projects are also welcome. Ok, from what I understand from Google's documents, pay is rather decent (for French standards, at least ;) ), so it seems project's length should be around 1 - 1.5 months. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Summer of code
Yoav Shapira wrote: Hi, Yeah, that *is* a great idea. Feel free to edit to the wiki page (wiki.apache.org/general/SummerOfCode2005), please ;) I removed two of the projects, so it's ready for new additions. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
