Re:Following a Select Statement Through Postgres Internals (...
by egor83 on Sunday April 10, 2016 @08:52PM
(#11469002)
> If you were to produce something along the lines of that
> for open-source projects that need it, I wouldn't hesitate
> to pay a modest fee.
Try BountySource [1] maybe?There you can post a proposal for some improvement to an OSS project (a design doc, in your case) and pledge a bounty for it.
If other people have the same problem, they might chip in further, making it more visible/profitable to solve.
----
Re:Following a Select Statement Through Postgres Internals (...
by Denzel on Monday April 11, 2016 @10:53AM
(#11471876)
Thanks for the link! First time I've seen that marketplace. I'll look into it.
I can't say the same thing for ElasticSearch (or most large open-source projects). It's very difficult to get the high-level context without a well-written design doc explaining why things are the way they are. Some parts of ElasticSearch make sense, and other parts just seem hackneyed. Of course, I could pull together little bits and pieces of high-level insight from multiple disparate blog posts and forums and mailing lists here and there.
But what I would like is a design doc! If you were to produce something along the lines of that for open-source projects that need it, I wouldn't hesitate to pay a modest fee.