It seems discussion has died down a bit. So to wrap up on the last issues discussed:
I think we should just keep the name. We have quite a bit of goodwill invested in the name already and it is certainly no worse than other names that have been accepted into incubation. So unless there is a direct objection to incubation because of the name, lets just table it as a concern to monitor and move on. The only other issue that has been floating around is the size of the initial committers. Scott and I detailed various contributions explicitly and for those we did not callout in this list, we did call out in the proposal itself. All of the committers listed are active contributors to Etch today. There have been more contributors in the past and plenty in our circle of friends here at Cisco that would like to be contributors. But as I mentioned originally, we culled the list based on active contributors today. I understand that starting with 14 may mean staying in incubation "longer", but I do not necessarily think that is a bad thing. I am not in any race to finish incubation "quickly". If there is true interest in Etch, there will be plenty of contributors and the project will be better for it. So again, unless there is a specific, direct objection to incubation because of the length of the committer list, lets just table it, like the name, as a concern to monitor and move on. Give that, is there anything else that prevents us calling for a vote? -- james On 8/15/08 7:27 AM, "Grant Ingersoll" <[EMAIL PROTECTED]> wrote: > FWIW, I'm +1 on the proposal, regardless of the name. > > > On Aug 13, 2008, at 12:58 PM, scott comer wrote: > >> the discussion about names seems somewhat done. it is easy to get the >> impression from the volume that there is a demand for name change. in >> my opinion there isn't. certainly names is a rich topic and the >> discussion >> would never die down on it's own because it is so much fun. it's a >> wonder >> anything gets done... >> >> here is a summary of who's responded to our proposal and an indication >> of the topic. >> >> [EMAIL PROTECTED] +1 >> [EMAIL PROTECTED] +1 (MENTOR) >> [EMAIL PROTECTED] +1 (TOOMANY, NAME) >> [EMAIL PROTECTED] +1 (NAME) >> [EMAIL PROTECTED] +1 (TOOGOOD, TOOMANY, NAME, MENTOR) >> [EMAIL PROTECTED] +1 >> [EMAIL PROTECTED] +1 (TOOMANY, MENTOR) >> >> [EMAIL PROTECTED] (TOOMANY) >> [EMAIL PROTECTED] (NAME) >> [EMAIL PROTECTED] (QUESTION) >> [EMAIL PROTECTED] (NAME) >> [EMAIL PROTECTED] (NAME) >> [EMAIL PROTECTED] (NAME) >> [EMAIL PROTECTED] (TOOMANY) >> [EMAIL PROTECTED] (TOOMANY) >> [EMAIL PROTECTED] (NAME) >> >> of the people that mention name (8), only 3 are voting: >> >> henning: concerned about confusion with debian. only says we need to >> be careful and explicit. >> niall: wants to see the q resolved. likes the name, sees no real >> objection. >> niclas: conflict with debian; only worries about it. >> >> of the rest, most like the name etch and seem to be just "tossing >> the ball around". >> >> the main other concern is that of confusion with Debian Etch vs. >> Apache Etch. There >> was some discussion about whether etch could get to the top of the >> google list. >> >> so, can we put the name question to bed? it was suggested that the >> podling could/should >> decide the issue for itself, later. is there a problem with that? >> >> are there any other concerns about the proposal which aren't >> addressed? >> >> scott out >> > > -------------------------- > Grant Ingersoll > http://www.lucidimagination.com > > Lucene Helpful Hints: > http://wiki.apache.org/lucene-java/BasicsOfPerformance > http://wiki.apache.org/lucene-java/LuceneFAQ > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- James Dixson Manager, Software Development CUAE Engineering, Cisco Systems (e) [EMAIL PROTECTED] (p) 512-336-3305 (m) 512-968-2116 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
