Skip to content

Commit 76d35e5

Browse files
Add CoC and naming conventions
1 parent 7da0323 commit 76d35e5

File tree

1 file changed

+37
-0
lines changed

1 file changed

+37
-0
lines changed

en/README.md

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
# Lambda I/O Meetup Guidelines
2+
3+
## Table of Contents
4+
5+
- []()
6+
7+
## Code of Conduct
8+
9+
It is very important to state that any Lambda I/O Meetup, *regardless of where
10+
it occurs, when it occurs or who organizes* **MUST** follow the [Lambda I/O
11+
Foundation Code of Conduct](https://github.com/lambda-io/code-of-conduct). The same **MUST* be taken seriously by all members
12+
and staff, always considering the welfare and the inclusive and diverse
13+
environment that we aim to have.
14+
15+
## Naming Conventions
16+
17+
Since the meetings are scheduled based on regionality, it is interesting to have
18+
a name that refers to the city where it will happen.
19+
20+
Given this, the name is formed by:
21+
22+
**`Lambda I/O` + `< City Name >` + `Meetup`**
23+
24+
e.g.
25+
26+
- The meetup will take place in *Fortaleza, CE* -> `Lambda I/O Fortaleza Meetup`
27+
- The meetup will take place in *Salvador, BA* -> `Lambda I/O Salvador Meetup`
28+
29+
> Note: In order to keep a *nicer name*, it can be used, instead of the city
30+
name, any contraction or slang to represent it.
31+
32+
> e.g.
33+
34+
> - The meetup will take place in *São Paulo, SP* -> `Lambda I/O Sampa Meetup`
35+
> - The meetup will take place in *Rio de Janeiro, RJ* -> `Lambda I/O Rio Meetup`
36+
37+
##

0 commit comments

Comments
 (0)