>One alternate solution is to remove all commercial links from the web >site and documentation. But, such a policy would be open to individual >interpretation and could have any number of unforeseen consequences.
Just my 2 cents, As a struts user and observer of this list, I think it would be unfortunate if some indication of community if not commercial use of Struts were removed (or at least not easily located somwhere). When many technology decisions are made in a project, and perhaps especially with open source technologies, an inevitable question is "Who else is using it?". If this information is removed, and perhaps replicated in one or more places, it becomes harder for new adopters to make a case to their respective management if they can't find the information easily. That said, given Struts strong history, It might not be the end of the world if it were removed. But I'd like to see it stay in some form somewhere. >Another alternative would be to remove the news and resources pages >completely, with the expectation that, if these pages are valuable to >the Community, then someone in the Community will undertake hosting >them. (I know I would.) Agreed. Thanks, Mike Jasnowski -----Original Message----- From: Ted Husted [mailto:[EMAIL PROTECTED] Sent: Friday, November 14, 2003 9:41 AM To: Struts Developers List Subject: Re: cvs commit: veto Please, let's *not* start rehashing the General list discussion here. Like Vegas, what goes on in General should stay in General. :) http://www.mail-archive.com/general%40jakarta.apache.org/ The topic here is that a Committer has requested a product change that another Committer has vetoed. It's been acknowledged that the veto has merit and is binding. But we do prefer that vetoes not be the end of a discussion, and we must always look for alternate solutions that everyone can live with. One alternate solution is to remove all commercial links from the web site and documentation. But, such a policy would be open to individual interpretation and could have any number of unforeseen consequences. It is also something that should be brought to the Jakarta PMC or ASF Board, since such a policy would seem to transcend our charter to maintain the Struts codebase and documentation on the foundation's behalf. Another alternative would be to remove the news and resources pages completely, with the expectation that, if these pages are valuable to the Community, then someone in the Community will undertake hosting them. (I know I would.) A valid argument would be that these pages have become a maintenance burden, just as the consultants and powered-by pages became a burden. But, personally, I'm good with the status quo, and leave it to other Committers to make whatever proposals they feel might be useful. -Ted. --------------------------------------------------------------------- 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]
