FINAL REMINDER: Apache EU Roadshow 2018 in Berlin next week!
Hello Apache Supporters and Enthusiasts This is a final reminder that our Apache EU Roadshow will be held in Berlin next week on 13th and 14th June 2018. We will have 28 different sessions running over 2 days that cover some great topics. So if you are interested in Microservices, Internet of Things (IoT), Cloud, Apache Tomcat or Apache Http Server then we have something for you. https://foss-backstage.de/sessions/apache-roadshow We will be co-located with FOSS Backstage, so if you are interested in topics such as incubator, the Apache Way, open source governance, legal, trademarks or simply open source communities then there will be something there for you too. You can attend any of talks, presentations and workshops from the Apache EU Roadshow or FOSS Backstage. You can find details of the combined Apache EU Roadshow and FOSS Backstage conference schedule below: https://foss-backstage.de/schedule?day=2018-06-13 Ticket prices go up on 8th June 2018 and we have a last minute discount code that anyone can use before the deadline: 15% discount code: ASF15_discount valid until June 7, 23:55 CET You can register at the following link: https://foss-backstage.de/tickets Our Apache booth and lounge will be open from 11th - 14th June for meetups, hacking or to simply relax between sessions. And we will be posting regular updates on social media throughout next week so please follow us on Twitter @ApacheCon Thank you for your continued support and we look forward to seeing you in Berlin! Thanks Sharan Foga, VP Apache Community Development http://apachecon.com/ PLEASE NOTE: You are receiving this message because you are subscribed to a user@ or dev@ list of one or more Apache Software Foundation projects.
Re: Deprecating the Python bindings
> On May 9, 2018, at 11:51 AM, Andrew Schwartzmeyer > wrote: > > Hi all, > > There are two parallel efforts underway that would both benefit from > officially deprecating (and then removing) the Python bindings. The first > effort is the move to the CMake system: adding support to generate the Python > bindings was investigated but paused (see MESOS-8118), and the second effort > is the move to Python 3: producing Python 3 compatible bindings is under > investigation but not in progress (see MESOS-7163). > > Benjamin Bannier, Joseph Wu, and I have all at some point just wondered how > the community would fare if the Python bindings were officially deprecated > and removed. So please, if this would negatively impact you or your project, > let me know in this thread. Another approach could be to move the bindings from the `mesos` git repo to a separate repo (either the ASF or in the `mesos` GitHub org). This could decouple it from the main Mesos build infrastructure and create a project for a Python community to coalesce around. I think there's value in nominating an official Python binding, but maybe we don't have to carry that in the same git repo and build system. J
Re: Deprecating the Python bindings
Andrew, Is it one of the reasons for deprecating this binding the lack of interest of Mesos community? If the answer is yes, let me try to boost the maintenance of this biding. -- Javi Roman Twitter: @javiromanrh GitHub: github.com/javiroman Linkedin: es.linkedin.com/in/javiroman Big Data Blog: dataintensive.info Apache Id: javiroman On Thu, May 10, 2018 at 1:18 PM Heer, Christoph wrote: > > Hi, > > within SAP, we still use the Python bindings for our own productive Mesos > framework. There a multiple different pure Python implementations available > but especially this wide choice, different capabilities, unclear update > frequencies, available documentation and mixed quality makes the switch hard > and brings a lot of uncertainties. With the Python binding we had always a > reliable pice software that was part of Mesos and therefore covered somehow > with testing and included in release decisions. > > I understand the motivation behind the deprecation and removal. But I'm > afraid of the drop of the 'official' Python bind as it will probably deter > people to build Mesos frameworks with Python. Maybe it would make sense to > promote one implementation as recommended and include it into testing and > release decisions but I see also the point to give flexibility and choices. > > Best regards, > Christoph > > > > Christoph Heer, SAP SE, Dietmar-Hopp-Allee 16, 69190 Walldorf, Germany > Sitz der Gesellschaft/Registered Office: Walldorf, Germany > > Vorstand/SAP Executive Board: Bill McDermott (CEO), Robert Enslin, Adaire > Fox-Martin, Christian Klein, > Michael Kleinemeier, Bernd Leukert, Jennifer Morgan, Luka Mucic, Stefan Ries > Vorsitzender des Aufsichtsrats/Chairperson of the SAP Supervisory Board: > Hasso Plattner > Registergericht/Commercial Register Mannheim HRB 719915 > > This e-mail may contain trade secrets or privileged, undisclosed, or otherwise > confidential information. If you have received this e-mail in error, you are > hereby > notified that any review, copying, or distribution of it is strictly > prohibited. Please inform > us immediately and destroy the original transmittal. Thank you for your > cooperation.
