Skip to content

Conversation

@Asgoret
Copy link
Owner

@Asgoret Asgoret commented Nov 8, 2019

No description provided.

@Asgoret Asgoret requested a review from vizdrag as a code owner November 8, 2019 15:04
@Asgoret Asgoret added the Documentation Request for changing documentation label Nov 8, 2019
@Asgoret Asgoret mentioned this pull request Nov 8, 2019
Copy link

@DimmKirr DimmKirr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd add that titles should be written with proper capitalization rules.
Плюс, я бы добавил общий комментарий, что заголовки в английском языке пишутся по другим правилам (слова с большой буквы)

@@ -1,4 +1,6 @@
# Руководство по приятному общению (RUS)
# Руководство по приятному общению | Code od Conduct
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code of Conduct


## Code of conduct

1. It is not recommended to write many small messages in a row connected with one thought. State your thoughts in one big message. For large messages, it’s easier to track a thread. Otherwise, it can be considered by the administrator as a flood.
Copy link

@DimmKirr DimmKirr Apr 7, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is not advised to write multiple small messages in a row about the same matter. Express your thoughts in one larger message. It’s easier to keep track of a thread if the messages are larger, rather than smaller. Otherwise, it could be considered as flood by the administrator.

## Code of conduct

1. It is not recommended to write many small messages in a row connected with one thought. State your thoughts in one big message. For large messages, it’s easier to track a thread. Otherwise, it can be considered by the administrator as a flood.
2. Reply to messages. All official customers support this feature. When there are several threads in a chat at the same time, it is impossible to understand what message is addressed to whom.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reply to messages. All official Telegram clients support this feature. If there are several threads a in a chat at the same time, it is very hard to keep track of which message has been addressed to whom.


1. It is not recommended to write many small messages in a row connected with one thought. State your thoughts in one big message. For large messages, it’s easier to track a thread. Otherwise, it can be considered by the administrator as a flood.
2. Reply to messages. All official customers support this feature. When there are several threads in a chat at the same time, it is impossible to understand what message is addressed to whom.
3. Insulting chat participants and admins is undesirable. Offensive messages will be deleted, and in case of a malicious violation will be banned (but this is inaccurate).
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

and in case of a malicious violation, a user will be banned (but this is inaccurate).

1. It is not recommended to write many small messages in a row connected with one thought. State your thoughts in one big message. For large messages, it’s easier to track a thread. Otherwise, it can be considered by the administrator as a flood.
2. Reply to messages. All official customers support this feature. When there are several threads in a chat at the same time, it is impossible to understand what message is addressed to whom.
3. Insulting chat participants and admins is undesirable. Offensive messages will be deleted, and in case of a malicious violation will be banned (but this is inaccurate).
4. Advertising and outright spam we do not need. Violators will be instantly banned and advertising messages deleted.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't need advertising and outright spam.

#вакансия (a hashtag is required - without it, the bot will not work)
City and office address: ... (district or metro)
Work format: office or remote
Employment: full, partial, project
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Employment: full, part-time, project

City and office address: ... (district or metro)
Work format: office or remote
Employment: full, partial, project
Salary plug: from ... to ...
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Salary range: from ... to ...

Work format: office or remote
Employment: full, partial, project
Salary plug: from ... to ...
(amount after taxes or with reference to the calculator. “By agreement” or “by the results of the interview” is not suitable, only a specific plug )
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(amount after taxes or with reference to the calculator. “Depending on experience” or “based on the intervie result” is not suitable, only a specific range)

Employment: full, partial, project
Salary plug: from ... to ...
(amount after taxes or with reference to the calculator. “By agreement” or “by the results of the interview” is not suitable, only a specific plug )
Vacancy description: ...
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Job description

Contacts: ...
```
### Правила размещения резюме
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CV posting rules

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Documentation Request for changing documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants