Skip to content

Commit 6bff689

Browse files
Update main menu to display 'Dashboards' for consistency (#4453) (#4506)
* Update main menu to display 'Dashboards' for consistency. Fixes #4296 This resolves the inconsistency highlighted in issue #4296 (#4296). The decision to make this change was made in issue #68 (opensearch-project/ux#68)." * Update OpenSearch Dashboard to OpenSearch Dashboards for consistence * CHANGELOG.md update --------- Signed-off-by: Danila Gulderov <gulderov@ya.ru> (cherry picked from commit bbf8dfb) Co-authored-by: gulderov <gulderov@ya.ru>
1 parent 401e383 commit 6bff689

File tree

3 files changed

+86
-1
lines changed

3 files changed

+86
-1
lines changed

CHANGELOG.md

+2
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,8 @@ Inspired from [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
2121
- Remove `lmdb-store` to fix backport issue ([#4266](https://github.com/opensearch-project/OpenSearch-Dashboards/pull/4266))
2222
- [Chore] Update deprecated url methods (url.parse(), url.format()) ([#2910](https://github.com/opensearch-project/OpenSearch-Dashboards/pull/2910))
2323
- Cleanup unused url ([#3847](https://github.com/opensearch-project/OpenSearch-Dashboards/pull/3847))
24+
- [Saved Objects Management] Fix relationships header overflow ([#4070](https://github.com/opensearch-project/OpenSearch-Dashboards/pull/4070))
25+
- Update main menu to display 'Dashboards' for consistency ([#4453](https://github.com/opensearch-project/OpenSearch-Dashboards/pull/4453))
2426

2527
### 🚞 Infrastructure
2628

COMMUNICATIONS.md

+83
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,83 @@
1+
# OpenSearch Dashboards Communication
2+
3+
- [Overview](#overview)
4+
- [Slack](#slack)
5+
- [Forum](#forum)
6+
- [Developer Office Hours](#developer-office-hours)
7+
- [What it is](#what-it-is)
8+
- [When](#when)
9+
- [How to sign up](#how-to-sign-up)
10+
- [FAQ](#faq)
11+
12+
## Overview
13+
14+
The purpose of this document is to provide information regarding the communication channels for OpenSearch Dashboards. All communication is subject to the [OpenSearch Code of Conduct](CODE_OF_CONDUCT.md). Please see [CONTRIBUTING](CONTRIBUTING.md) if you're interested in contributing to the project.
15+
16+
## Slack
17+
18+
The OpenSearch project has a public workspace on [Slack](https://opensearch.slack.com). See the [Getting Started guide]() for steps to register and setup the workspace.
19+
20+
Once registered, check out these channels for discussion of OpenSearch Dashboards topics:
21+
22+
- [#dashboards](https://opensearch.slack.com/archives/C01QENNTGUD)
23+
- [#dashboards-ux](https://opensearch.slack.com/archives/C05389T9LJC)
24+
25+
## Forum
26+
27+
Slack conversations are not searchable outside the workspace. For this reason we encourage using the [OpenSearch Dashboards category](https://forum.opensearch.org/c/opensearch-dashboards/57) of the forum for technical support discussions or summarizing findings for the rest of the community.
28+
29+
## Developer Office Hours
30+
31+
### What it is
32+
33+
A recurring 1-hour virtual meeting for community developers to chat with [OpenSearch Dashboards project maintainers](MAINTAINERS.md). Priority will be given to topics that are signed-up in advance, but ad-hoc discussions are welcome in any remaining time.
34+
35+
While we'll always prioritize asynchronous communication, sometimes a community call is the most effective and efficient venue to share information and knowledge. Some reasons to sign up:
36+
37+
1. Review a proposal or technical design for a new feature in OpenSearch Dashboards or an OpenSearch Dashboards plugin
38+
2. Learn more about how to build and extend OpenSearch Dashboards - which APIs, plugins, resources, and services are available to speed development
39+
3. Discuss OpenSearch Dashboards roadmap and technical initiatives
40+
41+
Signing up isn't required to attend - all OpenSearch Dashboards contributors or interested developers are welcome as participants.
42+
43+
Bring your ideas and projects early, while you still have time and flexibility to make significant changes.
44+
45+
### When
46+
47+
Every other Thursday, 10AM-11AM PT.
48+
49+
### How to sign up
50+
51+
There will be a forum post for each iteration of the meeting, with pre-defined slots. To sign-up, simply reply in the forum thread with the following template:
52+
53+
* Topic: [a brief description of what you'd like to discuss]
54+
* Requested by: [provide GitHub aliases of attendees]
55+
* GitHub issues or PRs: [before signing up, make sure to create an issue, whether in the OpenSearch Dashboards repository or your own plugin repository]
56+
* Time required [choose 15, 30, 45, or 60 minutes]
57+
* Requested maintainer: [optional; provide GitHub alias of any particular maintainer you’d like to attend]
58+
59+
### FAQ
60+
61+
#### Will the meetings be recorded?
62+
63+
Yes, we plan to record each office hours session and post to our YouTube channel so the information can be more easily shared and referenced.
64+
65+
#### Will all maintainers attend?
66+
67+
Generally no, but there will always be at least one maintainer. We'll review the sign-ups ahead of time to make sure the right subject-matter experts will attend, depending on the topics.
68+
69+
#### What happens if there are no sign-ups for a particular session?
70+
71+
The session will still occur, and the maintainers will present a brief knowledge-sharing session or demo. We'll also hold ad-hoc discussions, but the session may end early.
72+
73+
#### Is it first come first serve or do we get to decide which topics we discuss in a session?
74+
75+
For sign-ups, it’s first-come first served, until we decide we need another method.
76+
77+
#### Will there also be meeting notes? or is the recording the only available transcript?
78+
79+
No. But we’ll also post the chat transcript and any slides shared (see https://forum.opensearch.org/t/opensearch-community-meeting-2023-0131/11892/5 as example)
80+
81+
#### How can I cancel or reschedule?
82+
83+
Just leave another forum reply, as early as possible so other folks have the opportunity to sign-up for the same spot.

src/plugins/dashboard/public/plugin.tsx

+1-1
Original file line numberDiff line numberDiff line change
@@ -360,7 +360,7 @@ export class DashboardPlugin
360360

361361
const app: App = {
362362
id: DashboardConstants.DASHBOARDS_ID,
363-
title: 'Dashboard',
363+
title: 'Dashboards',
364364
order: 2500,
365365
euiIconType: 'inputOutput',
366366
defaultPath: `#${DashboardConstants.LANDING_PAGE_PATH}`,

0 commit comments

Comments
 (0)