I'm tending towards the argument that if you can convince someone who has the right access to update the vendors.xml page, then you deserve to be on the list.
-- Howard M. Lewis Ship Creator, Tapestry: Java Web Components http://jakarta.apache.org/tapestry > -----Original Message----- > From: Steven Noels [mailto:[EMAIL PROTECTED] > Sent: Wednesday, July 02, 2003 8:37 AM > To: Jakarta General List > Subject: Re: The vendors page > > > On 2/07/2003 11:13 Santiago Gala wrote: > > > I would not say "you employ", but "just convince one > jakarta commiter > > to > > make the change". This would ensure at least some level of > communication > > (like sending it to the project -dev list and discussing it > there, etc.) > > +1 on being present on the list and discussing things > > <snip/> > > > the project committers should be aware of them existing and > > supporting the project. > > Yep - so basically this should be decided on a subproject-level in > Jakarta's case. I doubt *anyone* is able to support *all* Jakarta > subprojects on a level that he/she serves his customers well. > Suggestion: move this page away from the Jakarta main site, and > stimulate subprojects to host their own vendor pages. > > </Steven> > -- > Steven Noels http://outerthought.org/ > Outerthought - Open Source, Java & XML Competence Support Center > Read my weblog at http://blogs.cocoondev.org/stevenn/ > stevenn at outerthought.org stevenn at apache.org > > > --------------------------------------------------------------------- > 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]
