-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
merge, update & continue russian translation #167
Merged
Merged
Changes from 18 commits
Commits
Show all changes
25 commits
Select commit
Hold shift + click to select a range
463271c
Russian translation: layout-hoodieverse
0902b67
Russian `_config.yml`
2f6f048
Fix: russian lang label added to other lang descs
d5fb119
merge
11111000000 6544423
update & translate api
11111000000 81cb6ad
API hoodie.md completed
11111000000 78315f5
add russian to footer
11111000000 82b32c0
start tutorial translation
11111000000 bafedde
translate Installation guide
11111000000 65719a4
translate level 1;
11111000000 19bc672
traslate menu
11111000000 6725050
merge
11111000000 862e25d
fix
11111000000 52da8ee
fix menu
11111000000 3ec6550
fix menu
11111000000 a9b4e1f
fix menu
11111000000 929549d
fix menu
11111000000 91f3fb0
fix community section
11111000000 52c2779
translate say hi
mishin d6b436b
Merge branch 'gh-pages' of github.com:hoodiehq/documentation into gh-…
11111000000 f37a371
fix
11111000000 36b709a
Merge pull request #1 from mishin/gh-pages
11111000000 0e97459
fix
11111000000 cb35e01
update & translate techdocs index
11111000000 d8dd916
start translate store API
11111000000 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,131 @@ | ||
--- | ||
layout: layout-community | ||
locales: ru | ||
--- | ||
|
||
## Об этом документе | ||
|
||
> "Быть комиттером не значит коммитить код, это значит коммитить в проект." | ||
> – <a href="https://community.apache.org/contributors/" target="_blank">Apache Software Foundation</a> | ||
|
||
Здесь описывается как включиться в работу над проектом. | ||
|
||
Этот документ предназначен для членов сообщества. Это пошаговое руководство и описание нашего процесса взаимодействия. | ||
|
||
According to our [Code of Conduct](http://hood.ie/code-of-conduct.html), we are aiming to provide a safe space for everyone in this community. And we're happy to welcome everyone, including developers and people who want to become one of our non-coding contributors. | ||
|
||
This document is and will always be work in progress. We are constantly trying to improve our onboarding and community culture and always happy to get feedback! | ||
|
||
### Where and what can people contribute? | ||
|
||
Hoodie is a quite big project and we have various parts that need to be created and / or maintained. To find out where we need help, take a look at our [Contribute Site](http://hood.ie/contribute/). If you can't find anything you'd want to do or have further questions, please [contact us](http://hood.ie/contact/). | ||
|
||
--------------- | ||
|
||
### 1. Say hi! | ||
|
||
- As the first and frontmost contact for the new contributor, you are responsible for making them a part of community. | ||
- If this doesn't make sense or is just not possible because of any reason, e.g. your own obligations, lack of time or personal reasons, please talk to the community as early as possible to see who can be their contact person and guide in the next weeks and months. | ||
- Please also keep in mind that, ideally, the two people are sharing the same fields of work, interests or skills so both can learn from each other. | ||
- Once you found someone, give the two an introduction. | ||
|
||
Try to speak to the new contributor. We learned that this clears a lot of obstacles in communication and helps getting things going faster. Also, meeting new people is always fun! | ||
|
||
The easiest way to do this is a quick <a href="http://talky.io" target="_blank">Talky</a>, Skype call or Google Hangout with the person interested and at least one exsisiting contributer (this could be you already). If you happen to be in the same town, meeting for lunch, coffee or going on a walk is always the preferrable option. | ||
|
||
### 2. Get Started together | ||
|
||
1. Introduce them to our [Code of Conduct](http://hood.ie/code-of-conduct/). Please do not just mention it but ask them to read it and ask whether they have questions or concerns. If so, please address them. | ||
2. Find out what their status quo is: | ||
- what skills do they have? | ||
- are they developers? | ||
- frontend / backend / mobile? | ||
- are they non-coders? | ||
- what are they specialised in? | ||
- what are their interests in Hoodie? | ||
- What do they want to work on? | ||
- What are their interests regarding personal skills? | ||
- Is there anything they want to improve at and / or with which we can help them learn? | ||
3. Depending on their skills and knowledge, introduce them to Hoodie-related terms and processes (see [The Hoodie Glossary](../hoodieverse/glossary.html) and [FAQ](http://faq.hood.ie/) for more information). | ||
|
||
|
||
### 3. Introduce them to the surroundings | ||
|
||
Hoodie has various communication channels and workflows that can be quite confusing for people who are new to the community. During this time, your job is to make sure that they know how to effectively communicate with the rest of the community and make sure they are always in the loop. | ||
|
||
And, of course: make sure they know they can always contact you with any questions they have. :) | ||
|
||
#### The IRC channel | ||
- how to access | ||
- if not clear: help find a good client (e.g. Textual for Mac or another client you can recommend) | ||
- what to post | ||
- how to ask | ||
- office hours, see [http://hood.ie/irc](IRC page) for details | ||
|
||
#### GitHub | ||
- repository strucutre | ||
- how to get access | ||
- how to write good commit messages | ||
- how to file issues | ||
- how / why to submit pull requests | ||
|
||
#### Technical topics | ||
- how to read the [documentation](../) | ||
- for developers | ||
- code review process | ||
- release process | ||
- testing process | ||
- conventions | ||
- for non-coding contributors | ||
- content review process | ||
|
||
#### Our Tools | ||
Hoodie has a few tools and workflows that we created or agreed on using. Your job is to give the new contributor a quick overview of those tools and show how they can use or access them. | ||
|
||
- show our [Milestones](http://gr2m.github.io/milestones/) | ||
- show Hoodie [Showcases](http://hood.ie/intro/#showcases) | ||
- show our [Ubersicht](http://espy.github.io/ubersicht/#hoodiehq) | ||
|
||
#### Accounts | ||
|
||
In order to get started for real, the new contributor of course needs access to the Hoodie software and repositories. Please make sure you only create accounts for the things they need access to in order to get their work done. | ||
|
||
- GitHub | ||
|
||
### 4. Define a Workflow | ||
|
||
Finally! Our new contributor is all set and ready to get started. You should now work out a frequent feedback loop that fits both your and the contributor's schedule. | ||
|
||
- mentoring (who does it? + introduction) | ||
- pairings (with whom, how often and when?) | ||
|
||
### 5. Introduce them to the team | ||
|
||
Please introduce them to the other team members by sending a quick welcome email and maybe writing a blog post (e.g. a short interview for the ["A Hoodie for you"](http://blog.hood.ie/category/a-hoodie-for-you/) series, for the interview just send them our [Questionnaire Form](https://docs.google.com/forms/d/144uyYfrX1onnXiWV5wbA3qC_eOoUImolNaMXPdgDWMc/viewform)). Of course not only the team wants to know more about the contributors, but the contributors also want to get to know the team! Maybe you can help arranging short one-on-ones with other team members. | ||
|
||
You should also add them to the the [team section](http://hood.ie/community/#community) of our website and post a tweet about their addition to the team. | ||
|
||
**Hooray, the new contributor is now a part of the big Hoodie Family!** | ||
|
||
### 6. Stay in touch! | ||
|
||
The most diffucult job of onboarding is making sure the contributors are always motivated and never left alone, especially when they are having difficulties or problems. You can stay in touch by offering continuous mentoring and pairing (for example once a week or every two weeks, depending on the amount of work they can and want to contribute), and frequent quick chats or emails. | ||
|
||
You can also ping them when they're online in IRC or another channel and ask how they're doing. We know many of you are doing this anyway because our community members are amazing, but it's good to keep it in mind. It helps strengthen our relationships and show our appreciation. | ||
|
||
### 7. If you need help … | ||
|
||
In case this is too much work for you or there are any issues, please bring up these topics immediately. Please check below how and where to talk about them: | ||
|
||
- If these are issues which are better not discussed with the group in the first place or if you not sure whether it's appropriate to bring them up in the community, please contact another community member first. This is especially applicable for all personal problems which may occur or topics related with the Code of Conduct. **For the latter, please ask the person who brought up the topic for their consensus to involve another person into addressing the issue first.** | ||
- [Lena](https://twitter.com/lrnrd) and [Jan](http://twitter.com/janl) are also there to help you anytime. | ||
- If appropriate (see above for clarification), bring the topic(s) up in the community, e.g. by sending an email to everyone or bringing them up in the group chat. | ||
|
||
### 8. Improve | ||
|
||
After a few weeks you should ask the new Hoodie for feedback on our onboarding process and share their feedback and the insight you received with everyone else. Please also update this document accordingly. | ||
|
||
|
||
Thanks for your effort! It's great to have you in our community! | ||
|
||
<3 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,82 @@ | ||
--- | ||
layout: layout-community | ||
locales: en | ||
--- | ||
|
||
# Hosting a Hoodie Workshop | ||
|
||
*This is a living document and work in progress. If you want to add your feedback or experiences, please [contact us](http://hood.ie/contact).* | ||
|
||
##Prerequisites | ||
|
||
- How long is the workshop supposed to take? (At least 3-4 hours should be given, depending on the experience levels of the attendees) | ||
- How many participants? | ||
- Who can do the Coaching? (Ideal: have 1 coach per 3-4 participants) | ||
- Which OS? | ||
- Will they bring their Laptops or are computers available? (If the latter, with admin rights for participants?) | ||
- Which experience levels? | ||
- HTML / CSS | ||
- JavaScript | ||
- Terminal | ||
- If possible, arrange “Installation Party” before the actual workshop (Participants can meet and also they know, all is setup. So they will feel more comfortable the next day.) | ||
- installation guide is [here](../start) | ||
- Set up a Code of Conduct (e.g. similar to [Hoodie's Code of Conduct](http://hood.ie/code-of-conduct) or [how to design a Code of Conduct](https://adainitiative.org/2014/02/howto-design-a-code-of-conduct-for-your-community/)) | ||
|
||
## To prepare | ||
- Check if there are enough sockets | ||
- Bring extension cords | ||
- Stable WiFi for everyone. Check if special login for participants is required | ||
- Arrange food and enough drinks & snacks. If you can't do that, make sure to ask the participants to bring some snacks and look up some places you all can eat together. | ||
- Prepare (if necessary) short Hoodie intro talk (see [sample talks](http://hood.ie/contribute#talks) or the [Hoodie Events page](http://hood.ie/events)) | ||
- Prepare all important commands on slides or handout. | ||
- If you have more than one person per laptop, please print out the tutorial you are teaching. | ||
- Print the [Hoodie Cheat Sheet](http://hood.ie/dist/presentations/hoodie-cheat-sheet-print.pdf) for each participant | ||
- Prepare all important links as shortlinks | ||
- Prepare typical problems + solutions (also: check FAQ on “Known Errors”) for your coaches | ||
- Prepare a bunch of app ideas (beyond to do list apps) that people can then work on when they know enough about Hoodie, but don’t have a concrete app idea themselves | ||
- Prepare Feedback Form (e.g. like [this one](https://docs.google.com/a/thehoodiefirm.com/forms/d/1toCQfdK4tF2WIXzico5MoMpI_UXpLQ5zvcxFOUhip5M/viewform)) | ||
- Check [Hoodie’s FAQ](http://faq.hood.ie) for known bugs and errors – especially | ||
- [‘npm ERR! Please try running this command again as root/Administrator’](http://faq.hood.ie/#/question/38210259) | ||
- [common Windows installation problems](http://faq.hood.ie/#/question/48204371) | ||
- [Error ’could not start Hoodie`](http://faq.hood.ie/#/question/38210193) | ||
|
||
## Prerequisites for attendees (to announce) | ||
- Bring own Laptop | ||
- Ask attendees to have the latest (or at least not too old) version of their Operating System and Browser – otherwise they run may into trouble. You can find Hoodies prequisites [here](../hoodieverse/system-requirements-browser-compatibilities-prerequisites-before-getting-started-with-hoodie.html) | ||
- If they don’t have one yet, ask them to install an Editor (ideally send a list of suggestions + links) | ||
- Accept Code of Conduct | ||
|
||
## Running Order | ||
|
||
- Welcome everyone | ||
- Talk about Code of Conduct (name welcome / unwelcome behaviour explicitly) and that it will be enforced | ||
- Ask who knows what Hoodie is and does, if not all, give a short introduction to Hoodie | ||
- Ask everyone about their levels of experience + skills, motivation and let them tell you a bit about themselves | ||
- Installation (note: can take much longer than expected) | ||
- check if everyone has Hoodie up and running | ||
- [installation guide](../start) | ||
- note special issues which sometimes occur on Windows | ||
- if Hoodie is already installed, have them ensure they have the latest version by running | ||
<pre><code>hoodie new myApp</code></pre> | ||
- If Hoodie is not the latest version, the Hoodie-CLI will tell you that and prompt the next steps | ||
- Start with first Tutorial: run | ||
<pre><code>hoodie new tutorial / | ||
-t gr2m/hoodie-store-and-account-tutorial</code></pre> | ||
- Admin-Interface – http://127.0.0.1:6002 | ||
- … | ||
- … | ||
- [Plugin Tutorial](../plugins/tutorial.html) (for super advanced participants) | ||
- Boilerplate: <pre><code>hoodie new awesomeApp / | ||
-t zoepage/hoodie-boilerplate</code></pre> | ||
- … | ||
- … | ||
- Build your own App | ||
- Present your App to the Group | ||
- Feedback Round | ||
- ask for Feedback | ||
- hand out link to Feedback Form | ||
- Do not forget to give some feedback. Be nice and ecouraging. | ||
- Say thank you to all the people involved and be proud of yourself. | ||
- If you'd like to, socialize with the group in the next restaurant / coffeeshop / pub. | ||
- Go home, get some sleep | ||
- Check Feedback & add to Workshop materials |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
--- | ||
layout: layout-community | ||
locales: ru | ||
--- | ||
|
||
# Хотите помочь? | ||
Добро пожаловать в <a href="http://hood.ie/community/">наше сообщество</a>! |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There’s no
/
in formal Russian, useили
(or) insteadThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not all about "formal russian"