From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Jean-Paul Argudo <jean-paul(at)postgresql(dot)fr> |
Cc: | pgsql acdvocacy <pgsql-advocacy(at)postgresql(dot)org> |
Subject: | Re: New PostgreSQL Sponsorship Criteria |
Date: | 2013-10-14 17:02:54 |
Message-ID: | 525C23BE.9020201@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy |
JPA,
> So calculating for Dalibo's time contribution is quite a nightmare,
> including for myself. So I don't even think about anyone on this
> list :-D
We don't need to calculate the exact hours. We know that Dalibo has at
least two people who spend a LOT of time on community contribution
stuff, and have for years; that's good enough to decide the
sponsor/major sponsor split (plus Dalibo as a company does other stuff).
This is why the two-level system is nice: less hairsplitting.
My purpose here is to distiguish this from, for example, Aster Data or
Google, each of whom have one staff member who spends less than 20% of
their worktime contributing to PostgreSQL, which makes them "sponsors"
as opposed to "major sponsors". And as others have pointed out, in
borderline cases we can just ask the contributor themselves.
> So basically my objection is that we drop the examples, and let the
> general rules apply, as the Committee can freely decide ?
Well, I think we need *some* examples, or the rules are going to be
pretty unclear.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2013-10-14 17:56:26 | Re: New PostgreSQL Sponsorship Criteria |
Previous Message | Jonathan S. Katz | 2013-10-14 16:36:14 | Re: New PostgreSQL Sponsorship Criteria |