# Community Meeting - Jan 26, 2021

**URL:** <https://forum.opensearch.org/t/community-meeting-jan-26-2021/4727>\
**Category:** OpenDistro\
**Created:** [January 25, 2021, 10:21pm UTC](https://forum.opensearch.org/t/community-meeting-jan-26-2021/4727 "2021-01-25T22:21:30Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![searchymcsearchface](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/searchymcsearchface/32/868_2.png) [@searchymcsearchface](https://forum.opensearch.org/u/searchymcsearchface)\
**Post date:** [January 25, 2021, 10:21pm UTC](https://forum.opensearch.org/t/community-meeting-jan-26-2021/4727/1 "2021-01-25T22:21:31Z")

</div>

We’ll be discussing the new forks and the project as a whole during the community meeting tomorrow (Jan 26). We’d be glad to have you!

> **[Login to Meetup | Meetup](https://www.meetup.com/Open-Distro-for-Elasticsearch-Meetup-Group/events/thmcwrycccbhc/)**
>
> Find groups that host online or in person events and meet people in your local community who share your interests.

---

<div class="post-metadata">

**Author:** ![frotsch](https://avatars.discourse-cdn.com/v4/letter/f/839c29/32.png) [@frotsch](https://forum.opensearch.org/u/frotsch)\
**Post date:** [January 26, 2021, 9:22pm UTC](https://forum.opensearch.org/t/community-meeting-jan-26-2021/4727/2 "2021-01-26T21:22:22Z")

</div>

@searchymcsearchface How can I write you a PM?

---

<div class="post-metadata">

**Author:** ![searchymcsearchface](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/searchymcsearchface/32/868_2.png) [@searchymcsearchface](https://forum.opensearch.org/u/searchymcsearchface)\
**Post date:** [January 26, 2021, 9:29pm UTC](https://forum.opensearch.org/t/community-meeting-jan-26-2021/4727/3 "2021-01-26T21:29:07Z")

</div>

If you click on my name it should give you the option to “Message.”

---

<div class="post-metadata">

**Author:** ![frotsch](https://avatars.discourse-cdn.com/v4/letter/f/839c29/32.png) [@frotsch](https://forum.opensearch.org/u/frotsch)\
**Post date:** [January 26, 2021, 9:31pm UTC](https://forum.opensearch.org/t/community-meeting-jan-26-2021/4727/4 "2021-01-26T21:31:21Z")

</div>

No, sadly not. I can not even PM the moderators (maybe my trust level is too low?). Can you PM me so that we have an open thread?

---

<div class="post-metadata">

**Author:** ![searchymcsearchface](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/searchymcsearchface/32/868_2.png) [@searchymcsearchface](https://forum.opensearch.org/u/searchymcsearchface)\
**Post date:** [January 26, 2021, 10:49pm UTC](https://forum.opensearch.org/t/community-meeting-jan-26-2021/4727/5 "2021-01-26T22:49:54Z")

</div>

Relevant slides from the community meeting:

 ![Slide5](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/6/6a40b98e6300b287e650602dde3635bae1adf3f5.png) ![Slide6](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/5/53031d2c801c669258db3a9fce3b2b4974f8fe96.png) ![Slide7](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/b/b7ff27fce340c0b62e470ac95167ae9d4b131a15.png) ![Slide8](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/3/398cc273f5b1f78200d56491ef3c48d9a414f557.png) ![Slide9](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/8/891330ea7b570e4ea7071118d4451b704b272809.png) ![Slide10](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/3/3a48e0db71807845796e0e37db81af5d2e3608a7.png) ![Slide11](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/5/55364a8ee16947491673c8f8d69ea6960215b4e9.png)

---

<div class="post-metadata">

**Author:** ![fabide](https://avatars.discourse-cdn.com/v4/letter/f/8e8cbc/32.png) [@fabide](https://forum.opensearch.org/u/fabide)\
**Post date:** [January 27, 2021, 9:14am UTC](https://forum.opensearch.org/t/community-meeting-jan-26-2021/4727/6 "2021-01-27T09:14:38Z")

</div>

I couldn’t make it yesterday. Did you record the Meetup too? We are highly interested in the ongoing Development.  
Thanks

---

<div class="post-metadata">

**Author:** ![GoodMirek](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/goodmirek/32/94_2.png) [@GoodMirek](https://forum.opensearch.org/u/GoodMirek)\
**Post date:** [January 27, 2021, 11:29am UTC](https://forum.opensearch.org/t/community-meeting-jan-26-2021/4727/7 "2021-01-27T11:29:19Z")

</div>

Do you plan to fork also logstash and beats?

---

<div class="post-metadata">

**Author:** ![frotsch](https://avatars.discourse-cdn.com/v4/letter/f/839c29/32.png) [@frotsch](https://forum.opensearch.org/u/frotsch)\
**Post date:** [January 27, 2021, 2:13pm UTC](https://forum.opensearch.org/t/community-meeting-jan-26-2021/4727/8 "2021-01-27T14:13:05Z")

</div>

And the [docs](https://github.com/elastic/elasticsearch/tree/master/docs)? Seems they are also ASLv2 licensed.

---

<div class="post-metadata">

**Author:** ![searchymcsearchface](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/searchymcsearchface/32/868_2.png) [@searchymcsearchface](https://forum.opensearch.org/u/searchymcsearchface)\
**Post date:** [January 27, 2021, 2:18pm UTC](https://forum.opensearch.org/t/community-meeting-jan-26-2021/4727/9 "2021-01-27T14:18:23Z")

</div>

Currently, we don’t record these sessions for a non-technical reason (a story for another time) but trying to get an exception due to interest.

---

<div class="post-metadata">

**Author:** ![searchymcsearchface](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/searchymcsearchface/32/868_2.png) [@searchymcsearchface](https://forum.opensearch.org/u/searchymcsearchface)\
**Post date:** [January 27, 2021, 2:21pm UTC](https://forum.opensearch.org/t/community-meeting-jan-26-2021/4727/10 "2021-01-27T14:21:00Z")

</div>

Right now, we don’t have any plans to fork logstash nor beats. AFAIK they aren’t changing licenses and while there are some feature parity issues they should still be usable. Also, we have our hands full with Elasticsearch and Kibana.

---

<div class="post-metadata">

**Author:** ![searchymcsearchface](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/searchymcsearchface/32/868_2.png) [@searchymcsearchface](https://forum.opensearch.org/u/searchymcsearchface)\
**Post date:** [January 27, 2021, 2:40pm UTC](https://forum.opensearch.org/t/community-meeting-jan-26-2021/4727/11 "2021-01-27T14:40:19Z")

</div>

I was told that the docs were not eligible for forking, but looking at it myself I have questions. 🧐 I’m seeking further guidance.

If it is eligible there are definitely some hoops to jump through (different format and organization) and it would not be a small task to divide out x-pack specific stuff.

And if we could, the other question is if it’s better to just start fresh and build from the Open Distro docs? To be clear, this is not my decision to make, but my personal assessment of the first party docs is that they are wide but not deep and a tad unclear. Could we do better?

So, **tl;dr** Not sure. I would guess ‘no’, but now I’m double checking.

---

<div class="post-metadata">

**Author:** ![frotsch](https://avatars.discourse-cdn.com/v4/letter/f/839c29/32.png) [@frotsch](https://forum.opensearch.org/u/frotsch)\
**Post date:** [January 27, 2021, 3:12pm UTC](https://forum.opensearch.org/t/community-meeting-jan-26-2021/4727/12 "2021-01-27T15:12:50Z")

</div>

anyway, but at least we should make sure to not commingle the docs for the fork with open distro docs especially with the fact in mind to later put the fork (incl. docs) into a decentrally governed organization.

---

<div class="post-metadata">

**Author:** ![searchymcsearchface](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/searchymcsearchface/32/868_2.png) [@searchymcsearchface](https://forum.opensearch.org/u/searchymcsearchface)\
**Post date:** [January 27, 2021, 3:17pm UTC](https://forum.opensearch.org/t/community-meeting-jan-26-2021/4727/13 "2021-01-27T15:17:35Z")

</div>

Open Distro plugins/tools are also destined for governance as well AFAIK.

---

<div class="post-metadata">

**Author:** ![frotsch](https://avatars.discourse-cdn.com/v4/letter/f/839c29/32.png) [@frotsch](https://forum.opensearch.org/u/frotsch)\
**Post date:** [January 27, 2021, 3:21pm UTC](https://forum.opensearch.org/t/community-meeting-jan-26-2021/4727/14 "2021-01-27T15:21:57Z")

</div>

ah, ok, didn’t know. Thats great and a strong commitment from AWS to OSS!

---

<div class="post-metadata">

**Author:** ![tvc\_apisani](https://avatars.discourse-cdn.com/v4/letter/t/74df32/32.png) [@tvc\_apisani](https://forum.opensearch.org/u/tvc_apisani)\
**Post date:** [January 28, 2021, 9:46am UTC](https://forum.opensearch.org/t/community-meeting-jan-26-2021/4727/15 "2021-01-28T09:46:31Z")

</div>

Just a question: as in the ELK stack all the components gets released ‘all togheter’ by version number in order to ensure compatibility, how do you plan to ensure compatibility between the new ES fork and the remaining elastic oss components (in primis logstash and beats), expecially if a new versioning scheme is used ?

---

<div class="post-metadata">

**Author:** ![searchymcsearchface](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/searchymcsearchface/32/868_2.png) [@searchymcsearchface](https://forum.opensearch.org/u/searchymcsearchface)\
**Post date:** [January 28, 2021, 2:17pm UTC](https://forum.opensearch.org/t/community-meeting-jan-26-2021/4727/16 "2021-01-28T14:17:07Z")

</div>

That’s a great question. I have thoughts, but I would be speaking without full knowledge if I responded now. Let me take this up with the team and get back with you.

---

<div class="post-metadata">

**Author:** ![frotsch](https://avatars.discourse-cdn.com/v4/letter/f/839c29/32.png) [@frotsch](https://forum.opensearch.org/u/frotsch)\
**Post date:** [January 28, 2021, 2:40pm UTC](https://forum.opensearch.org/t/community-meeting-jan-26-2021/4727/17 "2021-01-28T14:40:41Z")

</div>

IMHO the question from @tvc_apisani is two fold:

1. API compatibility (ES Rest API/Kibana Rest Api)
2. ECS compatibility ([Overview | Elastic Common Schema (ECS) Reference [8.4] | Elastic](https://www.elastic.co/guide/en/ecs/current/ecs-reference.html))

Right?

See also the comments from @igorid70 [About the OpenDistro category - #2 by igorid70](https://forum.opensearch.org/t/about-stepping-up-elasticsearch-kibana-forks/4726/2)

---

<div class="post-metadata">

**Author:** ![searchymcsearchface](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/searchymcsearchface/32/868_2.png) [@searchymcsearchface](https://forum.opensearch.org/u/searchymcsearchface)\
**Post date:** [January 28, 2021, 4:17pm UTC](https://forum.opensearch.org/t/community-meeting-jan-26-2021/4727/18 "2021-01-28T16:17:44Z")

</div>

@frotsch Good breakdown (also responded to @igorid70 in that thread)

To answer your questions

1. We have no appetite to break the API. If subsequent versions of Elasticsearch come out (not this fork) that break with 7.10, then that is a different issue.
2. I can’t see us breaking anything to do with ECS as long as it stays open source, which seems like a fairly safe bet.

Normal disclaimers that these are crystal balls but I can tell you where the team is at on these issues today.

---

<div class="post-metadata">

**Author:** ![hagayg](https://avatars.discourse-cdn.com/v4/letter/h/eada6e/32.png) [@hagayg](https://forum.opensearch.org/u/hagayg)\
**Post date:** [January 28, 2021, 5:45pm UTC](https://forum.opensearch.org/t/community-meeting-jan-26-2021/4727/19 "2021-01-28T17:45:57Z")

</div>

Will there be any possible impact from the possible outcome of Oracle v Google in the USSC as far as API compatability goes? Obviously not now, but future versions might get hit.

---

<div class="post-metadata">

**Author:** ![searchymcsearchface](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/searchymcsearchface/32/868_2.png) [@searchymcsearchface](https://forum.opensearch.org/u/searchymcsearchface)\
**Post date:** [January 28, 2021, 5:59pm UTC](https://forum.opensearch.org/t/community-meeting-jan-26-2021/4727/21 "2021-01-28T17:59:08Z")

</div>

I think the whole open source community will be upset if that case goes sideways. I _doubt_ it would apply to anything that is already released as open source. After the decision, we will need to figure out how it applies in our circumstance.

[Next page](https://forum.opensearch.org/t/community-meeting-jan-26-2021/4727.md?page=2)
