Thread: Time to update list of contributors
All, Time for the annual update of this list: http://www.postgresql.org/developer/bios Here's the list of people I gleaned from the release notes (btw, if people have countries for the folks who aren't attributed, I'd appreciate them). Of course, there are many contributors to essential non-core code who should be listed as well: Tom Lane, USA Peter Eisentraut, Germany Bruce Momjian, USA Simon Riggs, England Pavan Deolasee, India Itagaki Takahiro, Japan Greg Smith, USA David Fetter, USA Pavel Stehule, Czech Greg Stark, USA Heikki Linnakangas Oleg Bartunov, Russia Florian Pflug Jeff Davis, USA Trevor Hardcastle Nikhil S Holdger Schurig D'Arcy Cain, Canada Gevik Babakhani, Netherlands Teodor Sigaev, Russia Alvaro Herrera, Chile Mark Kirkwood, New Zealand Joachim Wieland Henry Hotz, USA Magnus Haeglander, Sweden Tatsuo Ishii, Japan Victor Wagner Bill Moran, USA Andrew Dunstan, USA Arul Shaji Nickolay Samokhvalov, Russia Neil Conway, Canada Marc Fournier, Canada Jaime Casanova, Venezuala Albert Cervera Bernd Helmle Glen Parker Jan Wieck, USA Steve Marshall Paul Bayer Doug Knight Greg Sabino Mullane, USA Chad Wagner Brendan Jurd Euler Taviera de Oliveira, Brazil Joe Conway, USA Michael M., Germany Guillaume Smet, France Mark Cotner Chris Marcellino, Italy Dave Cramer, Canada Devrim Gunduz, Turkey Jeremy Drake Marko Kreen, Estonia Kris Jurka, Finland Tom Dunstan, USA -- --Josh Josh Berkus PostgreSQL @ Sun San Francisco
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 27 Nov 2007 16:08:36 -0800 Josh Berkus <josh@agliodbs.com> wrote: > All, > > Time for the annual update of this list: > http://www.postgresql.org/developer/bios > > Here's the list of people I gleaned from the release notes (btw, if > people have countries for the folks who aren't attributed, I'd > appreciate them). Of course, there are many contributors to essential > non-core code who should be listed as well: It would be useful to know the requirements to be listed... Joshua D. Drake > > Tom Lane, USA > Peter Eisentraut, Germany > Bruce Momjian, USA > Simon Riggs, England > Pavan Deolasee, India > Itagaki Takahiro, Japan > Greg Smith, USA > David Fetter, USA > Pavel Stehule, Czech > Greg Stark, USA > Heikki Linnakangas > Oleg Bartunov, Russia > Florian Pflug > Jeff Davis, USA > Trevor Hardcastle > Nikhil S > Holdger Schurig > D'Arcy Cain, Canada > Gevik Babakhani, Netherlands > Teodor Sigaev, Russia > Alvaro Herrera, Chile > Mark Kirkwood, New Zealand > Joachim Wieland > Henry Hotz, USA > Magnus Haeglander, Sweden > Tatsuo Ishii, Japan > Victor Wagner > Bill Moran, USA > Andrew Dunstan, USA > Arul Shaji > Nickolay Samokhvalov, Russia > Neil Conway, Canada > Marc Fournier, Canada > Jaime Casanova, Venezuala > Albert Cervera > Bernd Helmle > Glen Parker > Jan Wieck, USA > Steve Marshall > Paul Bayer > Doug Knight > Greg Sabino Mullane, USA > Chad Wagner > Brendan Jurd > Euler Taviera de Oliveira, Brazil > Joe Conway, USA > Michael M., Germany > Guillaume Smet, France > Mark Cotner > Chris Marcellino, Italy > Dave Cramer, Canada > Devrim Gunduz, Turkey > Jeremy Drake > Marko Kreen, Estonia > Kris Jurka, Finland > Tom Dunstan, USA > - -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240 PostgreSQL solutions since 1997 http://www.commandprompt.com/ UNIQUE NOT NULL Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate PostgreSQL Replication: http://www.commandprompt.com/products/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHTLMdATb/zqfZUUQRApmWAKCn35/NMsxIPbb0zVOEOIPwBftthQCdE5bH 0KRAB/zHwywwy0hVZx2f1zg= =7QdJ -----END PGP SIGNATURE-----
On Tue, 27 Nov 2007, Josh Berkus wrote: > Kris Jurka, Finland USA actually. Kris Jurka
Gregory Stark <stark@enterprisedb.com> writes:
> "Josh Berkus" <josh@agliodbs.com> writes:
>> Time for the annual update of this list:
>> Greg Stark, USA
> I'm not sure what the countries are supposed to signify but that's
> neither the country I hail from nor where I'm currently living.
Just tell us how you want to be listed ...
regards, tom lane
On Nov 27, 2007 7:08 PM, Josh Berkus <josh@agliodbs.com> wrote: > Jaime Casanova, Venezuala Ecuador > Bernd Helmle and he's from germany http://www.oopsware.de/private/bernd.html -- regards, Jaime Casanova "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs and the universe trying to produce bigger and better idiots. So far, the universe is winning." Richard Cook
Hi, On Wed, 2007-11-28 at 11:44 +0530, Pavan Deolasee wrote: > Nikhil S > > Nikhil is from India, EnterpriseDB. What is his surname? I think we need that for adding to web page. Regards, -- Devrim GÜNDÜZ , RHCE PostgreSQL Replication, Consulting, Custom Development, 24x7 support Managed Services, Shared and Dedicated Hosting Co-Authors: plPHP, ODBCng - http://www.commandprompt.com/
<br /><br /><div class="gmail_quote">On Nov 28, 2007 5:38 AM, Josh Berkus <<a href="mailto:josh@agliodbs.com">josh@agliodbs.com</a>>wrote:<br /><blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br />Nikhil S<br /><br /></blockquote></div><br/>Nikhil is from India, EnterpriseDB.<br /><br /><br />Thanks,<br />Pavan<br clear="all" /><br />--<br />Pavan Deolasee<br />EnterpriseDB <a href="http://www.enterprisedb.com">http://www.enterprisedb.com </a>
"Josh Berkus" <josh@agliodbs.com> writes: > All, > > Time for the annual update of this list: >... > Greg Stark, USA I'm not sure what the countries are supposed to signify but that's neither the country I hail from nor where I'm currently living. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support!
Josh Berkus wrote: > All, > > Time for the annual update of this list: > http://www.postgresql.org/developer/bios > > Here's the list of people I gleaned from the release notes (btw, if people > have countries for the folks who aren't attributed, I'd appreciate them). > Of course, there are many contributors to essential non-core code who > should be listed as well: Hiroshi Saito has made a number of smaller but important contributions this cycle. Heikki is from Finland, but currently living in the UK. You also missed my name despite it being attributed to 3 items in the release notes, but I don't suppose that matters as I'm in the core section anyway. /D
On Tue, Nov 27, 2007 at 04:08:36PM -0800, Josh Berkus wrote: > All, > > Time for the annual update of this list: > http://www.postgresql.org/developer/bios > > Here's the list of people I gleaned from the release notes (btw, if people > have countries for the folks who aren't attributed, I'd appreciate them). > Of course, there are many contributors to essential non-core code who > should be listed as well: The mentioned page has a split in "core", "major" and "other" developers. The first part is easy, but a difference is needed between the other two I think. As for those we don't have info for, we could always email them and ask? For major developers, we also list company name if they're working on company time... > Magnus Haeglander, Sweden Cool new spelling. Maybe I should start using that one :-) Did you just come up with it, or is that actually in some document somewhere? //Magnus
Dave Page wrote: > Josh Berkus wrote: >> All, >> >> Time for the annual update of this list: >> http://www.postgresql.org/developer/bios >> >> Here's the list of people I gleaned from the release notes (btw, if people >> have countries for the folks who aren't attributed, I'd appreciate them). >> Of course, there are many contributors to essential non-core code who >> should be listed as well: > > Hiroshi Saito has made a number of smaller but important contributions > this cycle. > > Heikki is from Finland, but currently living in the UK. > > You also missed my name despite it being attributed to 3 items in the > release notes, but I don't suppose that matters as I'm in the core > section anyway. yeah well - the release notes do not make that good a reference on the "who submitted patches" question anyway because the do not contain stuff that are mere compile failures or add support for additional platforms/cleanups) of new features (ie my patches to add GSSAPI support to OpenBSD/Solaris or things full text command/tabcomplete support in psql). So in effect that list might more correctly be called a "feature contributor list" Stefan
Stefan Kaltenbrunner wrote: > yeah well - the release notes do not make that good a reference on the > "who submitted patches" question anyway because the do not contain stuff > that are mere compile failures or add support for additional > platforms/cleanups) of new features (ie my patches to add GSSAPI support > to OpenBSD/Solaris or things full text command/tabcomplete support in > psql). > So in effect that list might more correctly be called a "feature > contributor list" Agreed - and that's exactly why Hiroshi got left off I think. His work included lots of testing and subsequent platform specific build fixes and code cleanup/fixes. I should also point out that the contributor list has always included people who have contributed to non-core community projects in the past as well - psqlODBC, the JDBC driver, pgInstaller, pgAccess, pgAdmin, infrastructure/web etc. so Josh's update should not necessarily remove those people (though an argument could be made for giving those people their own section). /D
"Gregory Stark" <stark@enterprisedb.com> writes: > "Josh Berkus" <josh@agliodbs.com> writes: > >> All, >> >> Time for the annual update of this list: >>... >> Greg Stark, USA > > I'm not sure what the countries are supposed to signify but that's neither the > country I hail from nor where I'm currently living. Sorry, forgot to say what to put instead. I'll go with "Canada" -- it's more exotic :) -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce Momjian - ask me about EnterpriseDB'sPostgreSQL training!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 28 Nov 2007 09:46:36 +0000
Dave Page <dpage@postgresql.org> wrote:
> I should also point out that the contributor list has always included
> people who have contributed to non-core community projects in the past
> as well - psqlODBC, the JDBC driver, pgInstaller, pgAccess, pgAdmin,
> infrastructure/web etc. so Josh's update should not necessarily
> remove those people (though an argument could be made for giving
> those people their own section).
This list seems to be oddly designed anyway. Who is a developer? Is a
developer different than a -hacker?
Not to mention there don't seem to be any defined rules. I asked Berkus
and his reply was, "It has always been a little fuzzy". I asked Devrim
and he gave me 5 bullet points that don't quite make sense.
Further I think this list is in the wrong place. It is
under /developers which to mean is most intuitive to information "for"
developers not a listing of them.
I think the listing should probably go under about/contributors and
under contributors would be:
Core <-- this is obvious Committers <-- this is obvious the only question is it only
committers to the source tree or do we want to give equal billing to
the -www guys (I think yes to equal billing) Members (really I think this should be contributors but then it is
duplicative) Hacker Emeritus Special Thanks (not sure about this, but basically this is "others")
Sincerely,
Joshua D. Drake
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/ UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHTZU3ATb/zqfZUUQRAoHMAJ4gwAkOshe9+PbusrcaECb2HgGr2wCeOzQX
nY1eWHCq+NdV6F3DXvO3QXI=
=4Jri
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 28 Nov 2007 13:58:27 +0000
Gregory Stark <stark@enterprisedb.com> wrote:
> "Gregory Stark" <stark@enterprisedb.com> writes:
>
> > "Josh Berkus" <josh@agliodbs.com> writes:
> >
> >> All,
> >>
> >> Time for the annual update of this list:
> >>...
> >> Greg Stark, USA
> >
> > I'm not sure what the countries are supposed to signify but that's
> > neither the country I hail from nor where I'm currently living.
>
> Sorry, forgot to say what to put instead. I'll go with "Canada" --
> it's more exotic :)
I believe the list is where you are actually at. Aren't you in the UK
right now?
Joshua D. Drake
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/ UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHTZXYATb/zqfZUUQRAmHiAKCtbqqBKQTMuA8jn0J/Kl+B357dLwCgp312
awpJs8KeGYnWVM+mQXyAVls=
=/Lqi
-----END PGP SIGNATURE-----
Joshua D. Drake wrote: > Not to mention there don't seem to be any defined rules. I asked Berkus > and his reply was, "It has always been a little fuzzy". I asked Devrim > and he gave me 5 bullet points that don't quite make sense. Not sure what Devrim is referring to, but most often in the past Rob (or someone else) has proposed changes to -core which we've said yay or nay to. > Further I think this list is in the wrong place. It is > under /developers which to mean is most intuitive to information "for" > developers not a listing of them. Maybe. Where else would it go? > I think the listing should probably go under about/contributors and > under contributors would be: > > Core <-- this is obvious > Committers <-- this is obvious the only question is it only > committers to the source tree or do we want to give equal billing to > the -www guys (I think yes to equal billing) Actually we've previously agreed (in -core) that we do not want to list committers for various reasons. Yeah, I know the list isn't too hard to figure out, but we don't want to advertise it. > Members (really I think this should be contributors but then it is > duplicative) Why not Hackers? Noone is a 'member' of anything except core or mayber the web/infrastructure team. /D
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 28 Nov 2007 16:27:42 +0000
Dave Page <dpage@postgresql.org> wrote:
> Actually we've previously agreed (in -core) that we do not want to
> list committers for various reasons. Yeah, I know the list isn't too
> hard to figure out, but we don't want to advertise it.
Oh right, I actually recall that...
>
> > Members (really I think this should be contributors but then it
> > is duplicative)
>
> Why not Hackers? Noone is a 'member' of anything except core or mayber
> the web/infrastructure team.
Define Hacker. And I could argue that some are members of PGDG. What
about those who provide just as much time and energy in advocacy as
others do on -heackers? What about people that are working on external
projects only such as Slony or PLproxy?
Sincerely,
Joshua D. Drake
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/ UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHTZgrATb/zqfZUUQRAnS1AKCc/Nv3HmC+oX47GwBrXK9ChfoTaQCgitNG
sGbIf6/G87bgwSiGEVCcacQ=
=3StH
-----END PGP SIGNATURE-----
"Joshua D. Drake" <jd@commandprompt.com> writes: > On Wed, 28 Nov 2007 13:58:27 +0000 > Gregory Stark <stark@enterprisedb.com> wrote: > >> "Gregory Stark" <stark@enterprisedb.com> writes: >> >> > "Josh Berkus" <josh@agliodbs.com> writes: >> > >> >> All, >> >> >> >> Time for the annual update of this list: >> >>... >> >> Greg Stark, USA >> > >> > I'm not sure what the countries are supposed to signify but that's >> > neither the country I hail from nor where I'm currently living. >> >> Sorry, forgot to say what to put instead. I'll go with "Canada" -- >> it's more exotic :) > > I believe the list is where you are actually at. Aren't you in the UK > right now? Yep. That's fine with me too. Perhaps it's even better if there's any thought of using this list to drive the advocacy or user group efforts. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's RemoteDBA services!
Joshua D. Drake wrote: > On Wed, 28 Nov 2007 16:27:42 +0000 > Dave Page <dpage@postgresql.org> wrote: > >> Why not Hackers? Noone is a 'member' of anything except core or mayber >> the web/infrastructure team. > > Define Hacker. And I could argue that some are members of PGDG. Says he who only the other day muttered something about how PGDG wasn't a defined entity :-) > What > about those who provide just as much time and energy in advocacy as > others do on -heackers? What about people that are working on external > projects only such as Slony or PLproxy? The latter are still hackers using the definition we're likely to agree on (ie. not a cracker). Both groups are 'Contributors' though. Maybe just use 'Regular contributors' and 'Occasional contributors'. Or major and minor. Or something entirely different. /D
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 28 Nov 2007 16:53:43 +0000
Dave Page <dpage@postgresql.org> wrote:
> Joshua D. Drake wrote:
> > On Wed, 28 Nov 2007 16:27:42 +0000
> > Dave Page <dpage@postgresql.org> wrote:
> >
> >> Why not Hackers? Noone is a 'member' of anything except core or
> >> mayber the web/infrastructure team.
> >
> > Define Hacker. And I could argue that some are members of PGDG.
>
> Says he who only the other day muttered something about how PGDG
> wasn't a defined entity :-)
I believe the term was "legal" entity (If it wasn't that is what I
should of wrote). Which is true. We are however a "community".
>
> > What
> > about those who provide just as much time and energy in advocacy as
> > others do on -heackers? What about people that are working on
> > external projects only such as Slony or PLproxy?
>
> The latter are still hackers using the definition we're likely to
> agree on (ie. not a cracker). Both groups are 'Contributors' though.
> Maybe just use 'Regular contributors' and 'Occasional contributors'.
> Or major and minor. Or something entirely different.
>
Now that seems reasonable.
Core
Regular contributors
Occasional contributors
Past contributors
Core and Regular should be on the same page.
Occasional and Past on another? (At a minimum we can't have Past on
the same page it would get too large).
I don't like major and minor because a one line patch that saves
someone from loosing all there data is a major contribution but we may
never hear from the person again.
Sincerely,
Joshua D. Drake
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/ UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHTZ3+ATb/zqfZUUQRAs0PAJ4nui/SBGaALAYQPGo5fN9SgQXnigCgpWGD
t+lyk7oDx54Cz+6W4PjFwHI=
=qsPR
-----END PGP SIGNATURE-----
Joshua D. Drake wrote: > On Wed, 28 Nov 2007 16:53:43 +0000 > Dave Page <dpage@postgresql.org> wrote: > >> Joshua D. Drake wrote: >>> On Wed, 28 Nov 2007 16:27:42 +0000 >>> Dave Page <dpage@postgresql.org> wrote: >>> >>>> Why not Hackers? Noone is a 'member' of anything except core or >>>> mayber the web/infrastructure team. >>> Define Hacker. And I could argue that some are members of PGDG. >> Says he who only the other day muttered something about how PGDG >> wasn't a defined entity :-) > > I believe the term was "legal" entity (If it wasn't that is what I > should of wrote). Which is true. We are however a "community". > >>> What >>> about those who provide just as much time and energy in advocacy as >>> others do on -heackers? What about people that are working on >>> external projects only such as Slony or PLproxy? >> The latter are still hackers using the definition we're likely to >> agree on (ie. not a cracker). Both groups are 'Contributors' though. >> Maybe just use 'Regular contributors' and 'Occasional contributors'. >> Or major and minor. Or something entirely different. > > > Now that seems reasonable. > > Core > Regular contributors > Occasional contributors > Past contributors > > Core and Regular should be on the same page. > Occasional and Past on another? (At a minimum we can't have Past on > the same page it would get too large). Man, I'm glad I DB:ified that page a couple of months back :-P Do we really need separate pages, though? We already have the distinction that major developers (in your case, that would be Regular ones, I guess) are listed in full details, and other contributors are just listed with name. I still think we should keep "Hackers Emeritus" (you may rename it). The people on that list are way more than just "past contributors" IMHO. > I don't like major and minor because a one line patch that saves > someone from loosing all there data is a major contribution but we may > never hear from the person again. We don't generally add anybody who just provides a single patch, ever. They go in the release notes, but we only add people who've been around for a while to this list at all. I think, at least, but as has already been told there are no strict policies... //Magnus
Kris Jurka wrote: > > > On Tue, 27 Nov 2007, Josh Berkus wrote: > >> Kris Jurka, Finland > > USA actually. Where in the US? We generally list at least the state for ppl int he US - most often both city+state. (shows up only for people listed as major developers for the time being, which is why nobody asked for it before) //Magnus
Devrim GÜNDÜZ wrote: > Hi, > > On Wed, 2007-11-28 at 11:44 +0530, Pavan Deolasee wrote: > >> Nikhil S >> >> Nikhil is from India, EnterpriseDB. > > What is his surname? I think we need that for adding to web page. Yes, agreed. We had someone else who wanted to be listed by alias some time back (year+, don't remember whom it was) and that was turned down. //Magnus
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 28 Nov 2007 18:34:57 +0100
Magnus Hagander <magnus@hagander.net> wrote:
> > Now that seems reasonable.
> >
> > Core
> > Regular contributors
> > Occasional contributors
> > Past contributors
> >
> > Core and Regular should be on the same page.
> > Occasional and Past on another? (At a minimum we can't have Past on
> > the same page it would get too large).
>
> Man, I'm glad I DB:ified that page a couple of months back :-P
Me too... I wasn't looking forward to writing the patch ;)
>
> Do we really need separate pages, though? We already have the
> distinction that major developers (in your case, that would be Regular
> ones, I guess) are listed in full details, and other contributors are
> just listed with name.
I would be fine with that.
>
> I still think we should keep "Hackers Emeritus" (you may rename it).
> The people on that list are way more than just "past contributors"
> IMHO.
*shrug* I don't really have a better name and I agree that we should
give props so...
Core
Regular contributors
Hackers Emeritus
Occasional contributors
Past contributors
???
>
>
> > I don't like major and minor because a one line patch that saves
> > someone from loosing all there data is a major contribution but we
> > may never hear from the person again.
>
> We don't generally add anybody who just provides a single patch, ever.
> They go in the release notes, but we only add people who've been
> around for a while to this list at all. I think, at least, but as has
> already been told there are no strict policies...
Fair enough but I think the point is still relevant, in that we really
don't want to state specifically what a "Major" contributor is, I think
it opens us up to more bad mojo than just saying you are either a
regular contributor, or not :)
Sincerely,
Joshua D. Drake
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/ UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHTakTATb/zqfZUUQRAjVDAJ4qhlxToVRJ25jn0pumr9u4ZgX1tQCglFrv
FY3HgczRhQwqzDcHPJuA5xk=
=s+FQ
-----END PGP SIGNATURE-----
Joshua D. Drake wrote: > Committers <-- this is obvious the only question is it only > committers to the source tree or do we want to give equal billing to > the -www guys (I think yes to equal billing) > > I don't have a problem with that, but I think core code committers and www maintainers should be indentified separately. On a closely related note: last time I looked there was no way for anyone to discover on the web site who the committers actually are. That would also probably be useful. cheers andrew
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 28 Nov 2007 13:15:52 -0500
Andrew Dunstan <andrew@dunslane.net> wrote:
>
>
> Joshua D. Drake wrote:
> > Committers <-- this is obvious the only question is it only
> > committers to the source tree or do we want to give equal billing to
> > the -www guys (I think yes to equal billing)
> >
> >
>
> I don't have a problem with that, but I think core code committers
> and www maintainers should be indentified separately.
Why? Then we have to also separate advocacy which is just as important
and pgfoundry... as well as possibly a host of others. We all have our
job in the community :).
> On a closely
> related note: last time I looked there was no way for anyone to
> discover on the web site who the committers actually are. That would
> also probably be useful.
See Dave's response about core not wanting committers that easily
identified. I actually recall this argument, basically there are times
when commit access might be revoked temporarily etc... IIRC..
Sincerely,
Joshua Drake
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/ UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHTbGmATb/zqfZUUQRAucRAJ9Xc3Rg7/rbyKD2BjuKJDOeIQaYBwCfbH31
xuLvWYGSfuM7O1DnI8HHK4k=
=SrRN
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 28 Nov 2007 12:33:52 -0600 "Kevin Grittner" <Kevin.Grittner@wicourts.gov> wrote: > >>> On Wed, Nov 28, 2007 at 11:34 AM, in message > >>> <474DA6C1.4070605@hagander.net>, > Magnus Hagander <magnus@hagander.net> wrote: > > > We don't generally add anybody who just provides a single patch, > > ever. They go in the release notes, but we only add people who've > > been around for a while to this list at all. > > I'm not sure what the point of the list is, but I had assumed that > one reason for publishing it was to show the scope of the community. > Wouldn't advocacy be better served by listing all the contributors, > even those who have contributed for the first time in that release? > > Is there some risk there that I'm missing, a matter of the effort > to gather the information, or to avoid offending more regular > contributors? Well to me, it is to acknowledge active community members which can be used as a tool for advocacy. A list that contains 3000 names does no one any good, we might as well just dump the mailing list subscribers :). However a reasonably managed list that shows strength in not only numbers but a solid base of frequent contributors, show duration and maturity within the project. Sincerely, Joshua D. Drake > > -Kevin > > > > > ---------------------------(end of > broadcast)--------------------------- TIP 7: You can help support the > PostgreSQL project by donating at > > http://www.postgresql.org/about/donate > - -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240 PostgreSQL solutions since 1997 http://www.commandprompt.com/ UNIQUE NOT NULL Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate PostgreSQL Replication: http://www.commandprompt.com/products/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHTbX9ATb/zqfZUUQRAkLRAJ0Z7tuxKPA1iBvI2I3l7Yvp10tl5QCgjFaO PEMjG6fWqdqXMY1RPnzWMhY= =ISYJ -----END PGP SIGNATURE-----
Joshua D. Drake wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Wed, 28 Nov 2007 13:15:52 -0500 > Andrew Dunstan <andrew@dunslane.net> wrote: > > >> Joshua D. Drake wrote: >> >>> Committers <-- this is obvious the only question is it only >>> committers to the source tree or do we want to give equal billing to >>> the -www guys (I think yes to equal billing) >>> >>> >>> >> I don't have a problem with that, but I think core code committers >> and www maintainers should be indentified separately. >> > > Why? Then we have to also separate advocacy which is just as important > and pgfoundry... as well as possibly a host of others. We all have our > job in the community :). > You are being overly sensitive. I never suggested otherwise. I simply suggested that the roles people do in fact play should be public. > >> On a closely >> related note: last time I looked there was no way for anyone to >> discover on the web site who the committers actually are. That would >> also probably be useful. >> > > See Dave's response about core not wanting committers that easily > identified. I actually recall this argument, basically there are times > when commit access might be revoked temporarily etc... IIRC.. > > > When I was made a committer, someone, I forget who, but I'm fairly sure it was some member of core, told me explicitly that it was intended to assist me professionally (and it has). That seems strangely at odds with a reluctance to publish the list of names of committers. It's not something I care deeply about, but it seems more than strange given that the list of active committers at least is not too hard to discover. cheers andrew
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 28 Nov 2007 13:50:02 -0500
Andrew Dunstan <andrew@dunslane.net> wrote:
> You are being overly sensitive. I never suggested otherwise. I simply
> suggested that the roles people do in fact play should be public.
And I was only pointing to a logistical problem with that thought
process. You are a hacker, you are also a pgfoundry admin and buildfarm
maintainer...
Which list would you like to be under?
Joshua D. Drake
P.S. I know that answer, that isn't the point.
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/ UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHTbnnATb/zqfZUUQRAuIQAJ0fA5EEywJYT9dT2ymR2dzpDNvuigCdHAE2
oM8Byrl8TbB0P/Z6AcnFU1g=
=hLFJ
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - --On Wednesday, November 28, 2007 08:20:04 -0800 "Joshua D. Drake" <jd@commandprompt.com> wrote: > Core <-- this is obvious > Committers <-- this is obvious the only question is it only > committers to the source tree or do we want to give equal billing to > the -www guys (I think yes to equal billing) Equal billing, but categorized ... for instance, Dave Page might be something like: Dave Page (core, www) (where core reflects core server, not Core member) > Hacker Emeritus Past contributions? Most definitely ... - ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHTbxS4QvfyHIvDvMRAq4sAKDoUAhKsrHYPys7oeLyexUMyzHXewCffvZI D9i/ZWv84u5LBoXbSSv1ywI= =gBvn -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 28 Nov 2007 15:06:58 -0400
"Marc G. Fournier" <scrappy@hub.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
> - --On Wednesday, November 28, 2007 08:20:04 -0800 "Joshua D. Drake"
> <jd@commandprompt.com> wrote:
>
> > Core <-- this is obvious
> > Committers <-- this is obvious the only question is it only
> > committers to the source tree or do we want to give equal billing to
> > the -www guys (I think yes to equal billing)
>
> Equal billing, but categorized ... for instance, Dave Page might be
> something like:
>
> Dave Page (core, www) (where core reflects core server, not Core
> member)
I am trying to make an evolutionary step that will work within the
existing infrastructure. Based on Magnus's reply my solution requires
heading changes and moving names around without anything else.
Sincerely,
Joshua D. Drake
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/ UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHTb1vATb/zqfZUUQRAmDtAJ4pJjKr/b1p+2bnZ6TW/hQgaZ2VTQCgoz9r
0nrCvbM+2bXpSG3jU8AKFrg=
=JupM
-----END PGP SIGNATURE-----
Joshua D. Drake wrote: > > I don't have a problem with that, but I think core code committers > > and www maintainers should be indentified separately. > > Why? Then we have to also separate advocacy which is just as important > and pgfoundry... as well as possibly a host of others. We all have our > job in the community :). > > > On a closely > > related note: last time I looked there was no way for anyone to > > discover on the web site who the committers actually are. That would > > also probably be useful. > > See Dave's response about core not wanting committers that easily > identified. I actually recall this argument, basically there are times > when commit access might be revoked temporarily etc... IIRC.. I believe the reason we don't publicise who is a committer is that we have non-committers who do a lot more for the project. Commit rights are usually given to people who do a lot of patches (perhaps small ones) while people who develop larger patches are less likely to get commit rights rapidly. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
Marc G. Fournier wrote: > > > --On Wednesday, November 28, 2007 08:20:04 -0800 "Joshua D. Drake" > <jd@commandprompt.com> wrote: > >> Core <-- this is obvious >> Committers <-- this is obvious the only question is it only >> committers to the source tree or do we want to give equal billing to >> the -www guys (I think yes to equal billing) > > Equal billing, but categorized ... for instance, Dave Page might be something > like: > > Dave Page (core, www) (where core reflects core server, not Core member) erm ? last i looked dave seemed to be a core member but not a (core) commiter ? :-) Stefan
Bruce Momjian wrote: > Joshua D. Drake wrote: > > > I don't have a problem with that, but I think core code committers > > > and www maintainers should be identified separately. > > > > Why? Then we have to also separate advocacy which is just as important > > and pgfoundry... as well as possibly a host of others. We all have our > > job in the community :). > > > > > On a closely > > > related note: last time I looked there was no way for anyone to > > > discover on the web site who the committers actually are. That would > > > also probably be useful. > > > > See Dave's response about core not wanting committers that easily > > identified. I actually recall this argument, basically there are times > > when commit access might be revoked temporarily etc... IIRC.. > > I believe the reason we don't publicize who is a committer is that we > have non-committers who do a lot more for the project. Commit rights > are usually given to people who do a lot of patches (perhaps small ones) > while people who develop larger patches are less likely to get commit > rights rapidly. Of course the next question is why core is split out, especially since core's role is mostly for confidential company contacts and discipline. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 28 Nov 2007 14:16:16 -0500 (EST)
Bruce Momjian <bruce@momjian.us> wrote:
> > I believe the reason we don't publicize who is a committer is that
> > we have non-committers who do a lot more for the project. Commit
> > rights are usually given to people who do a lot of patches (perhaps
> > small ones) while people who develop larger patches are less likely
> > to get commit rights rapidly.
>
> Of course the next question is why core is split out, especially since
> core's role is mostly for confidential company contacts and
> discipline.
*shrug* I have always considered core a steering committee type of
deal. Not "in charge" persay but there as a focal point when needed
(like the name change decision that was finally made).
It seems to me that it makes sense, based on that to break it out.
However there is another consideration in that at least two core
members seem to have zero interest in being involved in a very public
way like you suggest above. So perhaps it makes sense for core to be
inclusive of the list and instead push all "contacts" to a contacts
page.
Sincerely,
Joshua D. Drake
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/ UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHTb9OATb/zqfZUUQRArpyAJ9H4ANMkcYvvQ/EkmL9ZySSM1PNJQCfaEFi
kEFgzu+0FjRgA+i2RdxbxIE=
=BGTr
-----END PGP SIGNATURE-----
>>> On Wed, Nov 28, 2007 at 11:34 AM, in message <474DA6C1.4070605@hagander.net>, Magnus Hagander <magnus@hagander.net> wrote: > We don't generally add anybody who just provides a single patch, ever. > They go in the release notes, but we only add people who've been around > for a while to this list at all. I'm not sure what the point of the list is, but I had assumed that one reason for publishing it was to show the scope of the community. Wouldn't advocacy be better served by listing all the contributors, even those who have contributed for the first time in that release? Is there some risk there that I'm missing, a matter of the effort to gather the information, or to avoid offending more regular contributors? -Kevin
Greg, > Perhaps it's even better if there's any thought of using this list to drive > the advocacy or user group efforts. Yeah, I assembled that list for FOSS.In. In some countries, like India and Brazil, there's the perception that you have to be American to be an OSS contributor. I'm trying to show people otherwise. -- Josh Berkus PostgreSQL @ Sun San Francisco
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 28 Nov 2007 11:53:45 -0800
Josh Berkus <josh@agliodbs.com> wrote:
> Greg,
>
> > Perhaps it's even better if there's any thought of using this list
> > to drive the advocacy or user group efforts.
>
> Yeah, I assembled that list for FOSS.In. In some countries, like
> India and Brazil, there's the perception that you have to be American
> to be an OSS contributor. I'm trying to show people otherwise.
Weird... considering how many of our contributors are not in the US.
Joshua D. Drake
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/ UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHTcedATb/zqfZUUQRAlBgAJ9TfVhNTqRm2TdM1zZFLGjSmZ+LoQCfZ23J
WlsoAp6g5H8SQdmNCYKoHgQ=
=E/8K
-----END PGP SIGNATURE-----
Dave, > Hiroshi Saito has made a number of smaller but important contributions > this cycle. Thanks. I was being surprised to see only one Japanese contributor this cycle. > Heikki is from Finland, but currently living in the UK. Thanks! > You also missed my name despite it being attributed to 3 items in the > release notes, but I don't suppose that matters as I'm in the core > section anyway. Damn. I think I kept skipping it because I thought I'd already put it in. I'll bet I missed another core member too. -- Josh Berkus PostgreSQL @ Sun San Francisco
Josh Berkus wrote: > Greg, > >> Perhaps it's even better if there's any thought of using this list to drive >> the advocacy or user group efforts. > > Yeah, I assembled that list for FOSS.In. In some countries, like India and > Brazil, there's the perception that you have to be American to be an OSS > contributor. I'm trying to show people otherwise. oh wow ... Stefan
Josh Berkus wrote: > Greg, > > > Perhaps it's even better if there's any thought of using this list to drive > > the advocacy or user group efforts. > > Yeah, I assembled that list for FOSS.In. In some countries, like India and > Brazil, there's the perception that you have to be American to be an OSS > contributor. I'm trying to show people otherwise. Can we use one of those "web 2.0" websites that allow you to set up a world map with pins over where people is supposed to be? ... what, are Pg developers scarabs or something? -- Alvaro Herrera http://www.PlanetPostgreSQL.org/ "La conclusión que podemos sacar de esos estudios es que no podemos sacar ninguna conclusión de ellos" (Tanenbaum)
WWW, > > Yeah, I assembled that list for FOSS.In. In some countries, like > > India and Brazil, there's the perception that you have to be American > > to be an OSS contributor. I'm trying to show people otherwise. > > Weird... considering how many of our contributors are not in the US. Could we consider putting countries in the Contributors list at some point? I think it would encourage more people from outside the US to become contributors. Currently the project is imbalanced, with 2/3 of our users outside the US (or more) and 1/2 our contributors inside the US. A lot of that has to do with employers, of course, but we should give all the encouragement we can. -- Josh Berkus PostgreSQL @ Sun San Francisco
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 28 Nov 2007 12:24:42 -0800
Josh Berkus <josh@agliodbs.com> wrote:
> WWW,
>
> > > Yeah, I assembled that list for FOSS.In. In some countries, like
> > > India and Brazil, there's the perception that you have to be
> > > American to be an OSS contributor. I'm trying to show people
> > > otherwise.
> >
> > Weird... considering how many of our contributors are not in the US.
>
> Could we consider putting countries in the Contributors list at some
> point? I think it would encourage more people from outside the US to
> become contributors. Currently the project is imbalanced, with 2/3
> of our users outside the US (or more) and 1/2 our contributors inside
> the US. A lot of that has to do with employers, of course, but we
> should give all the encouragement we can.
>
postgres=# select .5 + .66;?column?
- ---------- 1.16
(1 row)
??
:)
Other than that... sure I don't see a problem with it but one step at a
time :)
Sincerely,
Joshua D. Drake
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/ UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHTdF1ATb/zqfZUUQRAhlqAJ4jgjvrn6Sx53JXHGDCu0Ca7njr1gCfdMQZ
d0nDylYheo+4/u44XHI11fo=
=CHHs
-----END PGP SIGNATURE-----
On Wednesday 28 November 2007 04:21, Magnus Hagander wrote: > On Tue, Nov 27, 2007 at 04:08:36PM -0800, Josh Berkus wrote: > > All, > > > > Time for the annual update of this list: > > http://www.postgresql.org/developer/bios > > > > Here's the list of people I gleaned from the release notes (btw, if > > people have countries for the folks who aren't attributed, I'd appreciate > > them). Of course, there are many contributors to essential non-core code > > who should be listed as well: > > The mentioned page has a split in "core", "major" and "other" developers. > The first part is easy, but a difference is needed between the other two I > think. > A major contributor is differentiated from other contributors based on 1) longevity in the community, 2) number of areas they work on, 3) signifigance of the contributions that have been made. To become an other contributor, you have to have contributed something of sginifcance to the community; this has typically meant some new feature for a release, but could also mean being a package maintainer for one of the open source platforms; it was something specific to the postgresql core project though; ie. something likely discussed on the postgresql mailing lists, or involving the central project. -- Robert Treat Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
Josh Berkus wrote: > WWW, > > > > Yeah, I assembled that list for FOSS.In. In some countries, like > > > India and Brazil, there's the perception that you have to be American > > > to be an OSS contributor. I'm trying to show people otherwise. > > > > Weird... considering how many of our contributors are not in the US. > > Could we consider putting countries in the Contributors list at some point? I > think it would encourage more people from outside the US to become > contributors. Currently the project is imbalanced, with 2/3 of our users > outside the US (or more) and 1/2 our contributors inside the US. A lot of > that has to do with employers, of course, but we should give all the > encouragement we can. This also says to me that it could be more useful to display country of origin instead of country where the developer is currently living (i.e. Canada in Greg's case). -- Alvaro Herrera Developer, http://www.PostgreSQL.org/ "No hay ausente sin culpa ni presente sin disculpa" (Prov. francés)
Josh, > postgres=# select .5 + .66; > ?column? > ---------- > 1.16 > (1 row) Users != contributors -- Josh Berkus PostgreSQL @ Sun San Francisco
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
- -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
- - -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 28 Nov 2007 12:48:22 -0800
Josh Berkus <josh@agliodbs.com> wrote:
> Josh,
>
> > postgres=# select .5 + .66;
> > ?column?
> > ----------
> > 1.16
> > (1 row)
>
> Users != contributors
Oh sorry missed that :) It was still funny though .
Joshua D. Drake
- - - --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/ UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
- - -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHTdSvATb/zqfZUUQRArNHAKCih8tCcC1cYD8RujHL8Cg4ggC0IQCgkYBw
4+1PKkY124RVskL0FsqkdRY=
=u67Y
- - -----END PGP SIGNATURE-----
- -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHTdS3ATb/zqfZUUQRAjCXAKCWezM9PJQ6nQ7rjdqnufX8haLpPACglwoZ
1YR8zSo66WXnG+WIoTx5HjQ=
=0RSG
- -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHTdTAATb/zqfZUUQRAhhWAJoDGnUv+KKBll1tWTYIejzWMxD2gQCcCzN7
fpkRXqIxOPUvAfh8c7ETDl4=
=t1fU
-----END PGP SIGNATURE-----
Alvaro Herrera wrote: > Josh Berkus wrote: >> Greg, >> >>> Perhaps it's even better if there's any thought of using this list to drive >>> the advocacy or user group efforts. >> Yeah, I assembled that list for FOSS.In. In some countries, like India and >> Brazil, there's the perception that you have to be American to be an OSS >> contributor. I'm trying to show people otherwise. > > Can we use one of those "web 2.0" websites that allow you to set up a > world map with pins over where people is supposed to be? > > ... what, are Pg developers scarabs or something? We could probably do that fairly easily by just using the google maps API. We used to have a dev map, but it was individually updated. Might be easier to do now that there are services out there to do it for us.. //Magnus
Magnus, > We could probably do that fairly easily by just using the google maps API. > > We used to have a dev map, but it was individually updated. Might be > easier to do now that there are services out there to do it for us.. Yeah. Too bad we don't have access to some kind of GIS database or something which we could use to generate a map. ;-) -- Josh Berkus PostgreSQL @ Sun San Francisco
Josh Berkus wrote: > Magnus, > >> We could probably do that fairly easily by just using the google maps API. >> >> We used to have a dev map, but it was individually updated. Might be >> easier to do now that there are services out there to do it for us.. > > Yeah. Too bad we don't have access to some kind of GIS database or something > which we could use to generate a map. ;-) Well, we have a GIS database, but we don't have the mapping data :-P //Magnus
Magnus Hagander wrote: > > Where in the US? We generally list at least the state for ppl int he US > - most often both city+state. (shows up only for people listed as major > developers for the time being, which is why nobody asked for it before) > Denver, CO Kris Jurka
Josh Berkus wrote: > Peter Eisentraut, Germany Please change my city to Cologne. -- Peter Eisentraut http://developer.postgresql.org/~petere/
Hi, <br /><br /><div class="gmail_quote">On Nov 28, 2007 11:10 PM, Magnus Hagander <<a href="mailto:magnus@hagander.net">magnus@hagander.net</a>>wrote:<br /><blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">DevrimGÜNDÜZ wrote:<br />> Hi,<br />><br />> On Wed, 2007-11-28 at 11:44 +0530, Pavan Deolasee wrote:<br/>><br />>> Nikhil S<br />>><br />>> Nikhil is from India, EnterpriseDB. <br />><br/>> What is his surname? I think we need that for adding to web page.<br /><br /></div>Yes, agreed. We had someoneelse who wanted to be listed by alias some<br />time back (year+, don't remember whom it was) and that was turneddown. <br /><font color="#888888"></font></blockquote></div><br />Agreed :), for the record, my name is "Nikhil Sontakke".<br/><br />Regard,<br />Nikhils<br />-- <br />EnterpriseDB <a href="http://www.enterprisedb.com">http://www.enterprisedb.com</a>
On Wed, Nov 28, 2007 at 04:21:56PM -0700, Kris Jurka wrote: > Magnus Hagander wrote: > > > >Where in the US? We generally list at least the state for ppl int he US > >- most often both city+state. (shows up only for people listed as major > >developers for the time being, which is why nobody asked for it before) > > > > Denver, CO Ok, I've updated the current database. (It doesn't show where you're listed, but it'll automatically get there if that's changed) //Magnus
On Thu, Nov 29, 2007 at 08:33:19AM +0100, Peter Eisentraut wrote: > Josh Berkus wrote: > > Peter Eisentraut, Germany > > Please change my city to Cologne. Updated on the website, will be on the next site build. //Magnus
On Wednesday 28 November 2007 16:09, Magnus Hagander wrote:
> Josh Berkus wrote:
> > Magnus,
> >
> >> We could probably do that fairly easily by just using the google maps
> >> API.
> >>
> >> We used to have a dev map, but it was individually updated. Might be
> >> easier to do now that there are services out there to do it for us..
> >
> > Yeah. Too bad we don't have access to some kind of GIS database or
> > something which we could use to generate a map. ;-)
>
> Well, we have a GIS database, but we don't have the mapping data :-P
Well, it is easy to do it via google maps API. I did this once before on my
old dev installed, which I'm pretty sure was trashed, but could be redone.
You need to store everyones lat/lon, and then generate an xml file with the
proper info, but it's not to tricky. Granted using a service based on
PostGIS would be cooler, but I've not yet seen one as simple to use as
google's stuff.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
"Robert Treat" <xzilla@users.sourceforge.net> writes: > On Wednesday 28 November 2007 16:09, Magnus Hagander wrote: >> Well, we have a GIS database, but we don't have the mapping data :-P > > Well, it is easy to do it via google maps API. I did this once before on my > old dev installed, which I'm pretty sure was trashed, but could be redone. > You need to store everyones lat/lon, and then generate an xml file with the > proper info, but it's not to tricky. Granted using a service based on > PostGIS would be cooler, but I've not yet seen one as simple to use as > google's stuff. Aren't these two sides of the same coin? First you add postgis columns to the database to gather latitude and longitude for each developer in the database. Then you have the web site use Postgres's xml support to generate the xml document that you use with google maps to actually generate the map. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's On-Demand Production Tuning
On Thu, Nov 29, 2007 at 03:45:51PM +0000, Gregory Stark wrote: > "Robert Treat" <xzilla@users.sourceforge.net> writes: > > > On Wednesday 28 November 2007 16:09, Magnus Hagander wrote: > >> Well, we have a GIS database, but we don't have the mapping data :-P > > > > Well, it is easy to do it via google maps API. I did this once before on my > > old dev installed, which I'm pretty sure was trashed, but could be redone. > > You need to store everyones lat/lon, and then generate an xml file with the > > proper info, but it's not to tricky. Granted using a service based on > > PostGIS would be cooler, but I've not yet seen one as simple to use as > > google's stuff. > > Aren't these two sides of the same coin? First you add postgis columns to the > database to gather latitude and longitude for each developer in the database. > Then you have the web site use Postgres's xml support to generate the xml > document that you use with google maps to actually generate the map. Don't need postgis columns to do that. Just store the coordinates in float columns. Google does all the GIS stuff on them. //Magnus
"Magnus Hagander" <magnus@hagander.net> writes: > Don't need postgis columns to do that. Just store the coordinates in float > columns. Google does all the GIS stuff on them. Sure, you don't need the xml support to generate an text document with xml tax in it either. But it isn't as interesting that way. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support!
Robert Treat wrote: > On Wednesday 28 November 2007 16:09, Magnus Hagander wrote: > > Josh Berkus wrote: > > > Magnus, > > > > > >> We could probably do that fairly easily by just using the google maps > > >> API. > > >> > > >> We used to have a dev map, but it was individually updated. Might be > > >> easier to do now that there are services out there to do it for us.. > > > > > > Yeah. Too bad we don't have access to some kind of GIS database or > > > something which we could use to generate a map. ;-) > > > > Well, we have a GIS database, but we don't have the mapping data :-P > > Well, it is easy to do it via google maps API. I did this once before on my > old dev installed, which I'm pretty sure was trashed, but could be redone. > You need to store everyones lat/lon, and then generate an xml file with the > proper info, but it's not to tricky. Granted using a service based on > PostGIS would be cooler, but I've not yet seen one as simple to use as > google's stuff. I have a map of my Postgres trips using Google: http://momjian.us/main/trips.html Robert is right you just have a javascript file with longitude/latutude and city name. Here is the javascript I use: http://momjian.us/main/js/google_map_api.js I downloaded a location longitude/latutudes from: http://www.maxmind.com/download/worldcities/ -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
On Thu, Nov 29, 2007 at 04:29:41PM +0000, Gregory Stark wrote: > "Magnus Hagander" <magnus@hagander.net> writes: > > > Don't need postgis columns to do that. Just store the coordinates in float > > columns. Google does all the GIS stuff on them. > > Sure, you don't need the xml support to generate an text document with xml tax > in it either. But it isn't as interesting that way. THe difference is that (at least in 8.3) you don't need an addon product to remember to upgrade and such for the xml stuff, but you do for postgis.. //mha
On Thu, Nov 29, 2007 at 10:32:28AM -0500, Robert Treat wrote: > On Wednesday 28 November 2007 16:09, Magnus Hagander wrote: > > Josh Berkus wrote: > > > Magnus, > > > > > >> We could probably do that fairly easily by just using the google maps > > >> API. > > >> > > >> We used to have a dev map, but it was individually updated. Might be > > >> easier to do now that there are services out there to do it for us.. > > > > > > Yeah. Too bad we don't have access to some kind of GIS database or > > > something which we could use to generate a map. ;-) > > > > Well, we have a GIS database, but we don't have the mapping data :-P > > Well, it is easy to do it via google maps API. I did this once before on my > old dev installed, which I'm pretty sure was trashed, but could be redone. > You need to store everyones lat/lon, and then generate an xml file with the > proper info, but it's not to tricky. Granted using a service based on > PostGIS would be cooler, but I've not yet seen one as simple to use as > google's stuff. You can also use Googles API to get the lat/long of a city center as a good starting point, so you don't have to figure out peoples specific lat/long. Which helps to get things off the ground :-) //Magnus
All, First off, I wasn't suggesting that we take people off the list of contributors if they're not on "my" list. For one thing, I don't think we should take people off until they haven't contributed in a few years (the time should vary with the size of the original contribution, with big contributors eventually going on the "former contributor" list). Second, the list I made does not include drivers, GUIs, replication, and other "essential add-ons" which we've conventionally included with the list of contribs. Second, for those of you who noticed spelling errors in your names ... that's probably me but I *might* have pasted it from the release notes. You might want to check the release notes to seeif your name is spelled correctly there. --Josh
At 1:27p -0500 on 01 Dec 2007, Josh Berkus wrote: > First off, I wasn't suggesting that we take people off the list of > contributors if they're not on "my" list. For one thing, I don't think > we should take people off until they haven't contributed in a few years > (the time should vary with the size of the original contribution, with > big contributors eventually going on the "former contributor" list). > Second, the list I made does not include drivers, GUIs, replication, and > other "essential add-ons" which we've conventionally included with the > list of contribs. If I might chime it, it sounds like you're saying "if code they've written is still around and in use, then they should be counted as contributors." May be that won't exactly work because of "active" and "inactive" contributors, but this information is basically an annotized diff is, isn't it? Kevin
On Sunday 02 December 2007 14:05, Kevin Hunter wrote: > At 1:27p -0500 on 01 Dec 2007, Josh Berkus wrote: > > First off, I wasn't suggesting that we take people off the list of > > contributors if they're not on "my" list. For one thing, I don't think > > we should take people off until they haven't contributed in a few years > > (the time should vary with the size of the original contribution, with > > big contributors eventually going on the "former contributor" list). > > Second, the list I made does not include drivers, GUIs, replication, and > > other "essential add-ons" which we've conventionally included with the > > list of contribs. > > If I might chime it, it sounds like you're saying "if code they've > written is still around and in use, then they should be counted as > contributors." May be that won't exactly work because of "active" and > "inactive" contributors, but this information is basically an annotized > diff is, isn't it? > We don't really label as active or inactive, but rather contributors and past contributors, which in the past was diferentiatied as being an active community member (or not). A good example is Chris Kings-Lynne. He did the work for drop column, which is code that will likely be around forever, but he started his own consulting business (http://kkl.com.au/) and no longer focuses on PostgreSQL development (and does not particpate in the mailing lists); so he is on the "past contributor" list. -- Robert Treat Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL