# OpenSearch Community Meeting - 2022-0516 - open office

Agenda:

- Open discussion

[Meeting Link](https://www.meetup.com/OpenSearch/events/285397453)
**Passcode:**
- **481312**

Feel free to comment on the agenda before the meeting if you want to add an item or have a question. During the meeting the agenda will be unlocked for collaborative editing / note taking. After the meeting the agenda will be set to read-only mode.

## Chat log

08:57:30 From Kris Freedain to Waiting Room Participants:
We'll be opening up in a few minutes. Thanks everyone.
09:01:15 From lukas.vlcek to Everyone:
Hello...
09:01:21 From Julien EL KHIATI to Everyone:
Hi everyone !
09:01:21 From Amitai Stern to Everyone:
Hi!
09:01:22 From Fred Hilpert to Everyone:
Hi
09:02:21 From Kris Freedain to Everyone:
Agenda today - open discussion: https://hackmd.io/@HmdZWaVnQU6M8icdvC5TwQ/ByxUkAaEq
09:04:04 From Fred Hilpert to Everyone:
Not here
09:04:14 From nateboot to Everyone:
I've played with it a bit -
09:06:27 From Amitai Stern to Everyone:
Sorry internet issues.. brb
09:06:32 From nateboot to Everyone:
Hi Hannes!
09:07:15 From nateboot to Everyone:
https://github.com/orgs/opensearch-project/projects/1
09:12:57 From nateboot to Everyone:
https://github.com/opensearch-project/documentation-website/
09:13:26 From nateboot to Everyone:
Correct - File an issue, it will ask you what kind, you probably want a "Feature"
09:14:41 From lukas.vlcek to Everyone:
I think there is related ticket: https://github.com/opensearch-project/documentation-website/issues/410
09:14:53 From nateboot to Everyone:
Good find Lukas!
09:15:07 From Ryan Paras to Everyone:
for someone looking to push a CSV into opensearch ... not drag and drop by any means ... but could use fluentd to pick up your CSV file, parse (https://docs.fluentd.org/parser/csv) and push to opensearch
09:18:21 From nateboot to Everyone:
Go ahead Julien!
09:19:02 From Andrew Ross to Everyone:
Just FYI, mapping types were already deprecated in OpenSearch 1.0 and have been removed in OpenSearch 2.0: https://github.com/opensearch-project/OpenSearch/issues/1940
09:19:24 From nateboot to Everyone:
Do you have a link to your issue, Julien?
09:19:32 From Julien EL KHIATI to Everyone:
https://github.com/opensearch-project/OpenSearch-Dashboards/issues/1403
09:19:37 From Julien EL KHIATI to Everyone:
https://github.com/opensearch-project/OpenSearch-Dashboards/issues/1022
09:19:41 From Julien EL KHIATI to Everyone:
https://github.com/opensearch-project/performance-analyzer/issues/77
09:20:45 From nateboot to Everyone:
I think the ongoing etiquette is for a developer to assign it to themselves.
09:23:38 From nateboot to Everyone:
I agree - nothing should be done in private.
09:24:37 From Kris Freedain to Everyone:
Agree - let's work to continue to have conversations in the open. Another current option is within the forum at: https://forum.opensearch.org/
09:25:24 From nateboot to Everyone:
You can always file an issue on the documentation website asking for a blog
09:25:59 From Terry Q to Everyone:
Hi, are there up-to-date guidelines for recommended topologies?
For example are separate, dedicated master-eligible nodes still recommended or should we use multi-purpose (master/data/coordinating) nodes?
09:26:37 From Amitai Stern to Everyone:
I think that highly depends on you use case
09:28:15 From nateboot to Everyone:
Looking forward to seeing you contribute! Thanks!
09:28:16 From Terry Q to Everyone:
Fair enough. We currently recommend a minimum of 3 master plus 3 data as recommended by Elastic. I was just wondering if there was any change as there appeared to be a drift towards multipurpose nodes
09:28:34 From Kris Freedain to Everyone:
For a new blog post, create an issue – we even have a blog post template: https://github.com/opensearch-project/project-website/issues/new?assignees=&labels=new+blog%2C+enhancement&template=blog_post.md&title=

We’ll see it and work with you to begin the process. You’ll also need an author bio for the post.

For reference, here is the pull request for a post a partner did: https://github.com/opensearch-project/project-website/pull/454
09:28:52 From lukas.vlcek to Everyone:
Speaking about the documentation, is there any ongoing work right now to do some major rework/redesign of it or can we expect that existing documentation site will stay as it is for some time? (I think there are some tickets proposing it some changes…)
09:29:07 From David Tippett to Everyone:
https://opensearchcon-cfp.splashthat.com
09:29:31 From Kris Freedain to Everyone:
OpenSearchCon
https://opensearch.org/blog/community/2022/05/opensearchcon/
Main event page: https://opensearchcon.splashthat.com/
CFP page: https://opensearchcon-cfp.splashthat.com/
Exhibit page: https://opensearchcon-exhibit.splashthat.com/
CFP form: https://airtable.com/shruYlSq21a7mZ9sK
09:29:58 From nateboot to Everyone:
Sorry. I totally interrupted.
09:30:58 From lukas.vlcek to Everyone:
Thanks for the answer! +1
09:31:28 From Andriy Redko to Everyone:
https://github.com/opensearch-project/documentation-website/issues/419
09:31:48 From nateboot to Everyone:
I'm actually not aware of a documentation roadmap - that would be an awesome idea.
09:32:32 From Joshua Bright to Everyone:
https://github.com/opensearch-project/opensearch-clients/issues/19
09:36:44 From nateboot to Everyone:
++moving so fast
09:37:14 From lukas.vlcek to Everyone:
Maybe start writing meeting minutes collab document?
09:38:50 From Kris Freedain to Everyone:
Lukas - absolutely! If you've taken notes, we’d be happy to have them added to the agenda itself https://hackmd.io/@HmdZWaVnQU6M8icdvC5TwQ/ByxUkAaEq
09:39:13 From lukas.vlcek to Everyone:
Let’s think about it...
09:39:41 From lukas.vlcek to Everyone:
See you next time.
09:39:44 From Fred Hilpert to Everyone:
Thanks all! See you!