Group: pgsql.advocacy


Subject: Change the name
From: greg@turnstep.com ("Greg Sabino Mullane")
Date: 9/4/2007 7:09:22 PM
-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 <p>PostgreSQL is pronounced <i>Post-Gres-Q-L</i>, and is also sometimes ! referred to as just <i>Postgres</i>. ! The unofficial pronunciations of <i>Post-gree</a> and ! <i>Post-gray</a> are also acceptable and should not be ! objected to when used by new users or customers. ! An audio file is available in <a href="http://www.postgresql.org/files/postgresql.mp3">MP3 format</a> for those would like to hear the pronunciation.</p> Uh, no, the idea is to simplify things, not make them worse. We don't need four different ways to refer to the project. For the record, I've never heard "Post-gray" and "Post-gree" used in the wild. "Postgres" is simple, unambiguous, easy to remember, and is already used quite widely verbally. The other alternatives will simply remind people of the original ill-fated decision. I've already put forth my own FAQ patch earlier in this thread. > But I do disagree with the 150-250 hours amount of work. As do I. I think it would be about 4 hours of 'work'. We change the FAQ, write a press release stating the name is changing, stop scolding people in various forums for using Postgres instead of PostgreSQL, and slowly start moving things over. If the domain name stays at postgresql.org for six years, or more, that's okay. People can use the name PostgreSQL for as long as they want, and nobody in the community should yell at them. - -- Greg Sabino Mullane greg@turnstep.com PGP Key: 0x14964AC8 200709041503 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iD8DBQFG3a0JvJuQZxSWSsgRA0jXAKCtFCFR4n297l5jVEVBDiLpHTLWQgCgtSls DFlkSnLOHCKIyPiBlev/tGE= =5fzB -----END PGP SIGNATURE----- ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings

Subject: Change the name
From: greg@turnstep.com ("Greg Sabino Mullane")
Date: 9/4/2007 7:38:21 PM
-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 > The next step of this process is NOT a poll. The next step of "should we > do it or not" is a rough draft of a plan which shows all of the "costs" of > changing the name and how we're going to meet them, as well as the Pros > and Cons of changing vs. not changing. Excellent point, Josh, I think we've outgrown a mailing list. I made a quick wiki page. Pleae let Neil or myself know if anyone needs editing privs: http://developer.postgresql.org/index.php/Postgres - -- Greg Sabino Mullane greg@turnstep.com PGP Key: 0x14964AC8 200709041537 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iD8DBQFG3bQLvJuQZxSWSsgRAy4mAJwMNTqbcFou2LdMuoJ5XP2qZNn3TwCfeEfM UHp5rrEF0qGLkMJuJ69pyPA= =/gHX -----END PGP SIGNATURE----- ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq

Subject: Change the name
From: greg@turnstep.com ("Greg Sabino Mullane")
Date: 9/14/2007 6:06:22 PM
-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 Josh Berkus writes: > What are you planning to ask -general, exactly? > > Unless it's a call for volunteers, anything you ask -general at this point > will be nothing but a straw poll. You can't even regard it as a vote, > because the folks on -general don't have enough information to make an > informed decision. I see -general as our user base, not as a bunch of uninformed 'folks' who wouldn't know advocacy from a hole in the ground. This is supposed to be a transparent project, and something like this should be put to the community at large. The most effective way we have to do that right now is the - -general list. Consider it a way to talk to the community, and see if anyone has any pros and cons that this list may not have thought of yet. > I've been waiting for the main proponents of changing the name to step up > and do that research. This will be a good litmus test of whether those > people will actually follow through to do the work required to change the > name. So far, I've seen nothing but e-mail posts. You are presupposing that your list of "research/work required" is the same as everyone elses, especially those in the "Postgres" camp. I, for example, have always advocated a gradual approach - a FAQ item, a news release, and we're done. Graphics, etc. can come at their own pace. The project has been living on two names for a long time now (more, if you count all the misspellings), it can surely survive with the same top two names swapped in officialness for a little while. Joshua D. Drake wrote: > Probably not. Consider the number of projects out there with odd names > that are doing just fine. Are they doing fine _despite_ their name? Let's be really honest, which project has a worse name than ours? > I still say we need to focus on our core strengths, the "Name" isn't > relevant in that argument. Instead of expending energy on that, we > should expending energy on doing everything we can to: > > Get windowing queries running ... > Seriously, let's focus on something really important versus something > that has zero technical ballast. It's not a zero-sum game. Certainly the number of people who can work on windowing queries are a very small percentage of our community. Nobody is advocating that we stop Tom and Simon from coding and make them recreate our handful of graphics. - -- Greg Sabino Mullane greg@turnstep.com PGP Key: 0x14964AC8 200709141356 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iD8DBQFG6s1YvJuQZxSWSsgRA6FwAJ4zPNesRevBXuZ2ehO/v4fK/KeejACcCbzs O+rd+rEHGwhPO/i15MHyBZE= =0aVO -----END PGP SIGNATURE----- ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster