On Thu, May 12, 2016 at 09:47:02AM +0200, Michael Banck wrote: > On Thu, May 12, 2016 at 08:57:34AM +0800, Craig Ringer wrote: > > On 11 May 2016 at 22:20, Bruce Momjian <br...@momjian.us> wrote: > > > I am giving a keynote at an IEEE database conference in Helsinki next > > > week (http://icde2016.fi/). (Yes, I am not attending PGCon Ottawa > > > because I accepted the Helsinki conference invitation before the PGCon > > > Ottawa date was changed from June to May). > > > > > > As part of the keynote, I would like to mention areas where academia can > > > help us. The topics I can think of are: > > > > > > Any others? > > > > > > > When publishing work, publish source code somewhere stable that won't just > > vanish. And build on the latest stable release, don't build your prototype > > on Pg 8.0. Don't just publish a tarball with no information about what > > revision it's based on, publish a git tree or a patch series. > > > > While academic prototype source is rarely usable directly, it can serve a > > valuable role with helping to understand the changes that were made, > > reproducing results, exploring further related work, etc > > > > Include your dummy data or data generators, setup scripts, etc. > > That is all sound advise, but if they do all of the above, then they > should also make sure the source (or parts of it) is potentially usable > by the project, i.e. (joint?) PGDG copyright, if their academic > institution allows that.
I have incorporated suggestions from this email thread into my IEEE talk for next week: http://momjian.us/main/writings/pgsql/ieee.pdf You will see most of it in the new slides toward the end. Please let me know if it needs more additions/changes. Thanks. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription + -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers