Magnus Hagander wrote:
> On Fri, May 13, 2011 at 23:08, Bruce Momjian <bruce@momjian.us> wrote:
> > I obviously freaked out too quickly. ?:-(
> >
> > And I have no problem linkking _to_ the sponsorship Wiki page from the
> > release notes.
>
> I may not be web-2.0-savvy enough.. But as a sponsor, I'd much rather
> see something like that as an appendix in the docs (even if it's well
> hidden), or as a page on the "actual" website. That gives it a much
> stronger "confidence level" than just a page on a wiki, that anybody
> can edit. (now, we know that we are fairly good at "policing" the
> content on our wiki, but an outsider does not know that)
I was thinking of a wiki so it could be popuplated by the developers.
We don't seem to be good at updating the main web site with content that
requires coordination.
> > I also liked the spreadsheet or SQL file idea where we could actually do
> > analysis of the companies and sponsored items. ?Yeah, why not use SQL
> > for this.
>
> SQL? I thought everything was supposed to be noSQL now?! Don't we just
> store it as a json file in the filesystem? That's so much more
> webscale!
Well, I imagine this could get pretty complex. For example, I assume
Tom's commits would show Red Hat, and 2nd Quadrants show 2nd Quadrant,
and there are some features that have multiple people associated with
the feature.
In fact, this is not going to fit in a single SQL table but will need to
join for multiple companies/contributors.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +