in the interest of Don not getting pitchforked, i was wondering how
people felt about starting weekly progress reports. just a sanity
check to show who is working on what and how its going as well as
offering a summary of community discussions. i get the feeling that
a lot of development/communication is taking place by email, which
is fine, but it makes it much harder for people to get involved when
they're is no visible sign of development or information about whats
going on. (yes, i'll volunteer for it). i'm actually curious if this
is an effect of trying to have track development on a bboard vs
using a mailing list.
personally i'm eager to help with the porting process, but what i
glean from these bboards seem a bit lean on info. so at the moment i
have no idea what i can do to help out.
my summary of whats concurrently out on the bboards and who working
on what.
1. ben's working on a query dispatcher, and hopefully some specs
will appear, that will explain what its going to do and why its not
going to be burden to do run time query dispatching.
2. don's working on getting the system to boot without oracle.
3. roberto's working on pl/pgsql porting guide.
4. the rest (whoever you are) are twiddling thumbs.
the community discussions summary.
1. some talk on using Pg's object inheritance features. they're was
some discussion back and forth regarding portability. no final say
was ever really explicitly stated. but based on the general
unwritten sentiment and some inferring (the query dispatcher taking
care of portability concerns) i guess pg extensions are in.
2. where is the cvs respository? (incidentally why not sourceforge?)
3. some interesting discussion in the guidelines thread about
automajically generating dml and dql, as well as the need for the
acs objects to have a higher level definitions (xml anyone?).
