@fuzzycz@jer_s@robertmhaas@mikeklaas 3) nothing happens for long periods of time; waiting for court dates, and response deadlines etc.
4) sometimes it's preferable to "not feed the trolls" as it were, by ignoring irrelevant and distracting arguments in blogs.
We are working on improving transparency where we can.
@fuzzycz@jer_s@robertmhaas@mikeklaas There are various reasons for this, though we are trying to do more where we can:
1) every update costs as we have to get counsel to review.
2) we don't make disputes public automatically, as we don't want to "shame" the other party while an agreement is still possible.
...
@samokhvalov@PostgreSQL If you feel you are unable to present your talk without recording it please let us know and we will schedule one of our backup talks for the slot. We hope that we do not need to do this however, as we believe your presentation will be of value to our attendees.
8/8
@pypi - is there anyone that can be nudged to increase a project limit? My ticket has been open for weeks now, and pgAdmin4 users are getting restless because new releases aren't on PyPI :-(. Thanks!
Very disappointed with @Ampeg. Both my original order for a PN-115HLF and it's replacement arrived damaged and had to be returned, with no visible damage to the packaging - and the only place that seems to have more is Yamaha themselves, for an extra ~£500.
My colleague @tjkincaid wrote a piece on NORM, or No-ORM. I'm one of the people he mentions were unconvinced; ORMs like the awesome #django give various ways to solve the issues raised. What do you think? https://t.co/ExXhxF7hph #postgresql#EDBPostgres
As part of my R&D on #postgresql and #machinelearning, I started a blog series on regression analysis with #tensorflow in PostgreSQL. Part 1 covers getting everything setup (and also makes a nice pl/python3 primer I think). https://t.co/7glKSC5YSA