<div dir="ltr">Super helpful, Frank. Thanks for this detailed roundup of your experience... couldn't have asked for a more perfect response.<div><br></div><div>As we move forward with this, I think we should take these words of wisdom into consideration. </div>
<div><br></div><div>One thing that Frank brings up here that I think is important and that we've maybe overlooked is the amount of work that is involved </div><div>with getting the sponsorship going and maintaining it. I assume that among the PSC, we should be able to get all the wikis and necessary documentation set up, but it sounds like it would be good for us to 'elect' someone to be in charge of managing the sponsorship program. For now, it sounds like Chris is interested to do that and I doubt that anyone would balk at his nomination, but it might be good to vote him in, make it an official title nonetheless. What do people think?</div>
<div><br></div><div>The other issue that Chris brought up earlier and Frank delved into a bit more is this issue of the credits page. In the interest of threaded email clients, I'd like to bring up that discussion in a separate mail. </div>
<div><br></div><div>Again, thanks Frank for sharing this. It's awesome to have this experience to draw from and but moreover the buena-vibra of a fellow project sticking out an arm to help us out. OpenLayers has been really fortunate to have so many big siblings around to show us the way -- we are indebted. Thanks!</div>
<div><br></div><div>Erik</div><div><br></div><div><br><br><div class="gmail_quote">On Fri, Oct 17, 2008 at 7:19 PM, Frank Warmerdam <span dir="ltr"><<a href="mailto:warmerdam@pobox.com">warmerdam@pobox.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="Ih2E3d">Paul Spencer wrote:<br>
> Frank,<br>
><br>
> In relation to OpenLayers pursuing sponsorship via OSGeo, could you<br>
> provide us with a brief summary of your experience with OSGeo<br>
> sponsorship program as it relates to GDAL/OGR? I think this would help<br>
> us crystalize our thoughts on how OpenLayers would like to proceed.<br>
<br>
</div>Paul,<br>
<br>
I'm not sure the experience will be all that similar for OpenLayers, but<br>
I'll make a few observations with regard to GDAL, and perhaps editorialize<br>
a bit.<br>
<br>
First, please be aware that participating in the sponsorship program<br>
involves some effort. Beyond setting up initial documents, and soliciting<br>
sponsors, it is expected that any project that participates in the sponsorship<br>
program will produce an annual report to sponsors summarizing at least how<br>
the sponsorship funds have been used over they year. This isn't onerous,<br>
but someone has to get this done.<br>
<br>
Second, I would observe that Tyler takes care of the invoices for sponsorship,<br>
and the collection of money. So generally speaking once I have a verbal<br>
(or email) agreement from an organization to sponsor GDAL I pass on the<br>
contact details, the start date, and the sponsorship level to Tyler who<br>
prepares the invoice, and takes care of contact with the sponsor. This is<br>
a huge help and without Tyler handling this professionally the whole effort<br>
might well be too much for me pursue.<br>
<br>
For GDAL it is considered allowed to sponsor for any amount of above<br>
$500, but the invoicing and other hassles involved in small sponsorships have<br>
resulted in me only actively pursuing sponsorships of $3000 or more (a<br>
silver sponsorship). I accept smaller sponsorships (gracefully I hope),<br>
but I don't pursue smaller sponsors for annual renewals.<br>
<br>
An items that has proven a bit challenging for GDAL is that sponsors are<br>
permitted a logo and block of text on our sponsor page.<br>
<br>
<a href="http://www.gdal.org/credits.html" target="_blank">http://www.gdal.org/credits.html</a><br>
<br>
It has proven surprisingly hard to get an appropriately sized logo, and<br>
appropriate text from sponsors. Sometimes they don't respond. Sometimes<br>
they give me huge or otherwise inappropriate logos. And they give me<br>
highly variable text for inclusion. So I've had to set fairly specific<br>
rules for the maximum number of pixels in the logo (I take care of resizing<br>
and confirm with the sponsor) and an upper limit on the descriptive text<br>
(50 words at silver). I still have some sponsors I've not been able to get<br>
the logo and text from and they go uncredited. In retrospect I wonder if I<br>
would have been better off with a simplier scheme - at least perhaps no text.<br>
<br>
As for actually soliciting sponsors, I have (I think) been responsible for<br>
soliciting all the GDAL sponsors so far. I generally don't try to hard, but<br>
I do have to make some effort. I don't recall any stepping up and volunteering<br>
their interest just based on the sponsor solicitation page. I've directly<br>
approached a few organizations I knew were heavy users of GDAL and that I<br>
know well. I also will often mention GDAL and OSGeo sponsorship opportunities<br>
to folks when I answer technical questions about the project and related<br>
software if they look like they might be getting significant value from the<br>
software. I generally just approach companies under the assumption that<br>
sponsorship is pretty hard to arrange for a government organization. My<br>
pitch normally goes something like:<br>
<br>
"""<br>
If you find you are getting substantial value from GDAL/OGR and you<br>
would like to help sustain the project you might consider becoming<br>
a sponsor:<br>
<br>
<a href="http://www.gdal.org/sponsorship.html" target="_blank">http://www.gdal.org/sponsorship.html</a><br>
<br>
Sponsorship helps us fund bug fixing and other efforts to sustain<br>
the project. Sponsors get some degree of priority in getting<br>
bug fixes, and receive credit on our credits page. Let me know<br>
if you might be interested, or have any questions about sponsorship.<br>
"""<br>
<br>
In a few cases I've offered to waive an hourly fee to fix some bug or<br>
implement some small feature if an organization would like to become<br>
a sponsor. I've turned what might have been a personal invoice for<br>
$500 into a $3000 silver sponsorship a couple times this way, though<br>
generally these organizations might already have been well disposed<br>
to sponsorship without my sweetening the pot.<br>
<br>
I do avoid situations where sponsors are offered specific promises<br>
in return for sponsorship unless it is something I'd be doing out of<br>
my own time. For instance I discussed possible sponsorship options with<br>
a large company who seemed to want to tie it to efforts to incorporate<br>
or do work on a particular library of theirs and I stressed that<br>
sponsorship would need to be distinct from any efforts in that regard.<br>
<br>
Well - thats the collection side.<br>
<br>
The other side is making productive use of the money.<br>
<br>
In the GDAL project we have only used the money for two things so far.<br>
One has been funding a contract paid maintainer position which is focused<br>
on bug fixing, though it also takes on some other project tasks. We have<br>
also used it to purchase project t-shirts handed out at the 2007 code<br>
sprint.<br>
<br>
We have been very lucky to have Mateusz Loskot available as our paid<br>
maintainer. He is a skilled self-starter and does not require much<br>
direction, though he has responded well to my priority setting. We have<br>
a written up RFC describing how the paid maintainer role works:<br>
<br>
<a href="http://trac.osgeo.org/gdal/wiki/rfc9_maintainer" target="_blank">http://trac.osgeo.org/gdal/wiki/rfc9_maintainer</a><br>
<br>
My main problem so far in this regard has been Mateusz' limited<br>
availability, and in fact we have accumulated a significant amount of<br>
money in the project fund as he hasn't had enough time available to<br>
consume it all.<br>
<br>
With regard to paid maintenance I will note a couple things about the<br>
GDAL project.<br>
<br>
1) I have deliberately kept the remuneration fairly modest for this role.<br>
$20/hr or so. This is for a couple reasons. First, it helps avoid a<br>
sense amoung the unpaid developers that someone is getting rich off the<br>
project. The maintainer pay isn't enough to make anyone particular<br>
jealous though it may still cause some existing contributors to "leave<br>
it to the paid guy" for some things. The other reason is I want the<br>
sponsors to feel that their money is being stretched fairly effectively.<br>
<br>
Actually, the third reason is that I like to see this maintainer role<br>
as a sort of stepping stone that could lead the maintainer to more<br>
lucrative private contracting related to the project.<br>
<br>
2) I have deliberately avoided having the funding go to the existing<br>
core team - especially to the PSC members who actually decide on the<br>
dispersement of the funds. In particular, I've never taken any GDAL<br>
project money for myself. I've been concerned about appearance of<br>
self-dealing or our profiteering off the project. I'm not sure how<br>
reasonable these concerns are - but to me it was important that the<br>
money be seen going to bring additional resources to the project<br>
that wouldn't have been their otherwise and to avoid any appearance<br>
of impropriety in the handling of the money.<br>
<br>
--<br>
<br>
Mateusz is no longer available for the maintainer role (he has accepted<br>
a related full time job), so now we are having to search for a new<br>
maintainer. It isn't so easy to find someone with good dev skills,<br>
a pre-apparent interest in GDAL and a willingness to work for modest<br>
financial returns. Our ability to find a new maintainer may well be<br>
a major test for our sponsorship program.<br>
<br>
Overall, the sponsorship program was one of the reasons I was interested<br>
in launching OSGeo and having GDAL join it. I wanted an orderly, transparent<br>
mechanism where organizations could help fund the project development in<br>
a way beyond funding specific new features. I think it has gone fairly<br>
well though I hope for a more stable maintainer role in the future.<br>
<br>
I will say that I think using some of the funding for team building<br>
activities is a good idea. We did the t-shirts from this fund, and in<br>
the future I could imagine using the funds to help support a GDAL<br>
code sprint, or perhaps cool prizes for the best bug report, best<br>
patch etc.<br>
<br>
--<br>
<br>
One other point I'll mention is that 25% of the sponsorship funds<br>
collected go to fund general OSGeo activities. I have not heard<br>
any complaints about this in the context of the GDAL project (from<br>
sponsors or developers) though I have heard resistance on this from<br>
other projects. I think it is important to see this as supporting<br>
the underlying infrastructure and community that OSGeo provides to<br>
projects.<br>
<br>
But if you see the project sponsorship program as a way to raise<br>
money to fund specific new developments then this cut may seem<br>
painful. I do think it is important to *not* treat project<br>
sponorship as a mechanism for an organization to fund a specific<br>
development. Direct contracting with a consultant is still better<br>
for that sort of thing.<br>
<br>
I hope this is somewhat helpful.<br>
<br>
Best regards,<br>
<font color="#888888">--<br>
---------------------------------------+--------------------------------------<br>
I set the clouds in motion - turn up | Frank Warmerdam, <a href="mailto:warmerdam@pobox.com">warmerdam@pobox.com</a><br>
light and sound - activate the windows | <a href="http://pobox.com/~warmerdam" target="_blank">http://pobox.com/~warmerdam</a><br>
and watch the world go round - Rush | Geospatial Programmer for Rent<br>
</font><div><div></div><div class="Wj3C7c"><br>
_______________________________________________<br>
Dev mailing list<br>
<a href="mailto:Dev@openlayers.org">Dev@openlayers.org</a><br>
<a href="http://openlayers.org/mailman/listinfo/dev" target="_blank">http://openlayers.org/mailman/listinfo/dev</a><br>
</div></div></blockquote></div><br></div></div>