4 ms·

(I'm the VPE at Influxdata). I appreciate this sentiment. We've been focused on a building a SaaS version of Influxdata and are committed to a paired open sour

by rbetts 6y ago

(I'm the VPE at Influxdata). I appreciate this sentiment. We've been focused on a building a SaaS version of Influxdata and are committed to a paired open source version of that. The open source version has been lagging as we work on the SaaS side. However, we are committed to shipping a GA version of the OSS 2.0 stack around the end of Q3 that offers an in-place data migration capability from 1.x OSS. We've spoken about this publicly in other forums. You can google "influxdays London talks" to hear Paul Dix (CTO/Founder) talk more about our OSS plans.

edoceo 6y ago
Classic "two masters" problem.
- santafen 6y ago
  This was from the CTO last week: "This work won't be landing anywhere until sometime next year and it'll be landing in our Cloud 2 offering first." So the OSS is definitely a second-class citizen. And now that they've dropped all DevRel activity, don't expect much attention for OSS Developers and users.
  - mhall119 6y ago
    Quite the contrary, we're finishing up packaging of the OSS version now to make it as easy as possible for you to get it and we're assembled a new team focused on getting OSS 2.0 released. We continue to support all users, including OSS users, in our public Slack and Discourse, as well as Github. We have not "dropped all DevRel" activity.
    - santafen 6y ago
      ¯\_(ツ)_/¯ Influx laid off pretty much the entire DevRel team in the last 6 months, but ok.
      - mhall119 6y ago
        This is true, and has certainly been painful for us and puts more work on those of us who are still working on community and devrel, but we're still doing it.
        mhall119 6y ago
        In fact we've got one of our Developer Advocates doing a live broadcast right now over at https://www.influxdata.com/time-series-meetup/virtual-2020 https://www.influxdata.com/time-series-meetup/virtual-2020
rattray 6y ago
Well, guess I know to never use Influx as a startup
- mhall119 6y ago
  Why is that? It takes minimal effort to get it up and running and you can either self-host or use the SaaS offering on any of the major clouds. There's even a free tier on the SaaS your startup can use that won't cost you a dime until your usage becomes significant.
  - rattray 6y ago
    Because the VPE sounds like the corporate sort of person who would not prioritize the things I'd want them to as a customer.
    - mhall119 6y ago
      I don't think anybody who knows Ryan would describe him as "the corporate sort of person" :) He was giving you an honest assessment of what was going on, not sugar-coated or wrapped in corporate speak. The work he described on our SaaS offering was directly tied to what our current and potential customers wanted.
    - threeseed 6y ago
      Your issue is that they are prioritizing paying customers over giving you a free product. I don't think that's fair given they are still a startup.
    - rbetts 6y ago
      That kinda hurts. There are 100k's of happy InfluxDB users -- untold millions of completely open source Telegraf deployments doing meaningful work for people -- integrated into our products and our competitors' products. We make the vast majority of our codebase public under liberal OSS licenses. And we'll keep listening and learning how to do more. ... off to see if I can change my internal slack handle to @corporatetool. Unless there's a policy against that ;-)

by rbetts 6y ago

edoceo 6y ago

Classic "two masters" problem.

santafen 6y ago
This was from the CTO last week: "This work won't be landing anywhere until sometime next year and it'll be landing in our Cloud 2 offering first." So the OSS is definitely a second-class citizen. And now that they've dropped all DevRel activity, don't expect much attention for OSS Developers and users.
- mhall119 6y ago
  Quite the contrary, we're finishing up packaging of the OSS version now to make it as easy as possible for you to get it and we're assembled a new team focused on getting OSS 2.0 released. We continue to support all users, including OSS users, in our public Slack and Discourse, as well as Github. We have not "dropped all DevRel" activity.
  - santafen 6y ago
    ¯\_(ツ)_/¯ Influx laid off pretty much the entire DevRel team in the last 6 months, but ok.
    - mhall119 6y ago
      This is true, and has certainly been painful for us and puts more work on those of us who are still working on community and devrel, but we're still doing it.
      - mhall119 6y ago
        In fact we've got one of our Developer Advocates doing a live broadcast right now over at https://www.influxdata.com/time-series-meetup/virtual-2020 https://www.influxdata.com/time-series-meetup/virtual-2020

rattray 6y ago

Well, guess I know to never use Influx as a startup

mhall119 6y ago
Why is that? It takes minimal effort to get it up and running and you can either self-host or use the SaaS offering on any of the major clouds. There's even a free tier on the SaaS your startup can use that won't cost you a dime until your usage becomes significant.
- rattray 6y ago
  Because the VPE sounds like the corporate sort of person who would not prioritize the things I'd want them to as a customer.
  - mhall119 6y ago
    I don't think anybody who knows Ryan would describe him as "the corporate sort of person" :) He was giving you an honest assessment of what was going on, not sugar-coated or wrapped in corporate speak. The work he described on our SaaS offering was directly tied to what our current and potential customers wanted.
  - threeseed 6y ago
    Your issue is that they are prioritizing paying customers over giving you a free product. I don't think that's fair given they are still a startup.
  - rbetts 6y ago
    That kinda hurts. There are 100k's of happy InfluxDB users -- untold millions of completely open source Telegraf deployments doing meaningful work for people -- integrated into our products and our competitors' products. We make the vast majority of our codebase public under liberal OSS licenses. And we'll keep listening and learning how to do more. ... off to see if I can change my internal slack handle to @corporatetool. Unless there's a policy against that ;-)