Comments (7)
Hi.
On paper I’m all for. However it grows very fast and I’m afraid you’ll have a hard time keeping up with the translations. What do you think?
If you do, please fork it rather than creating a new repo from scratch. I’ll be sure to add a link to your translation in the README. :)
from sjsj.
Thanks! I'll start translation soon. I will ask some russian developers to help me, so I hope it wouldn't take too much time.
from sjsj.
Please ping me on this issue when you feel like we can link to your translation on the main README. In the mean time, I’m closing. :)
from sjsj.
@hugogiraudel
@andrew--r
I believe it would be nice to create GitHub organization (named SJSJ) and then host all the translations under that organization. So, it will be much easier to keep track of any changes\updates.I would love to make a contribution to english, russian, ukrainian and maybe polish forks.
from sjsj.
Hey. Let me think about this for a while, I’ll come back to you. :)
from sjsj.
Alright so I am coming back to this. I am divided I must say.
On one hand, I am glad that some people are willing to invest time and efforts into translations. I think it is great. This is thanks to those people that http://sass-guidelin.es currently exists in 12 languages.
On the other, I feel like this project actually should not really be translated. The whole point is to explain words, terms and expressions from the JavaScript ecosystem. These expression are in English because this is the way things are. Translating theme would defeat the initial purpose. Of course, we could still translate the explanations, but I feel like it is not entirely necessary. I might be wrong though.
On top of that, managing translations is one hell of a job. I spend several hours a week on Sass Guidelines trying to get contributors to update their translation because I care about having all the translations at the same level of content. At the same time, I cannot force them to do so because they are volunteer contributors, and I am super glad that they are willing to contribute. Finding the balance is very hard and I don’t feel like engaging myself into this again on a second project.
Now, if another contributor (or severals) are willing to translate and maintain up to date SJSJ into a 3rd language, I will reconsider my position. At this point, we will discuss moving this project to an organisation, and offering writing privileges to most active contributors for instance.
I hope I don’t appear as insensitive saying all this. I am of course open for discussion.
from sjsj.
Well said! I respect your point of view.
I was thinking about it lately and realized that yes, it could be hard to house all translations under the one organization, and much harder to keep all the translations in sync. For example, there's the fork with Russian translations and it's just a FORK. So to move it to the organization the author must create a separate repository containing all the files from the original fork. Doing so might frighten away some contributors.
Nevertheless, moving this repo to separate organization is the next step in the development of the project. I would say, now is the time to move from the status "personal project" to the status of "community project".
P.S. Having such an organization will allow to easily manage the other translations in the future.
from sjsj.
Related Issues (20)
- Add “Thunk” entry
- make the design pattern one more JavaScript specific HOT 9
- Search icon not rendering properly HOT 3
- Formal definition of currying vs common usage HOT 11
- Add “Monad” entry HOT 1
- Add “Aurelia” entry HOT 1
- Add “Mustache” entry HOT 1
- Add related projects to website
- What is the process/guidance for editing existing definitions? HOT 2
- Add “Pure Function” entry HOT 5
- Add “Hydrate / dehydrate application” entry HOT 1
- Add “thenable” entry HOT 1
- Add "Trailsjs" entry
- Add “Recycling” entry
- Flickering on Mac HOT 7
- Add “Riot” entry
- Cleanup of {}.final files HOT 4
- Add "Cypress" entry
- UX Idea: click on title to go back to index
- Add "WebRTC" entry
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from sjsj.