-
Notifications
You must be signed in to change notification settings - Fork 62
Decision on the need (or lack thereof) for translations/localisation/regionalisation #774
Comments
To start things off... My personal take on this:
|
I suggest we support Option(strategy 1 and 2 simultaneously) non should be left out but I will elaborate more on Regional marketing Reasons; |
Planting seeds in virgin markets before our competition takes hold bears fruit in the long term. There are many benefit to global marketing](https://www.quora.com/What-are-the-benefits-of-international-marketing). There is little benefit to leaving our rhoc treasury idle when it might be invested in the future of rchain. A focus on the short term is not necessary and thus undesirable. Getting rhocs into more hands in itself valuable as it increases the number of people with a stake in rchain promoting it in their circles. Supporting translations is a good way to get rhocs flowing into new markets. At the same time we want to encourage translation that promise a wide readership or why bother. We want to reach the widest audience possible and not restrict ourselves to target groups like developers. A general awareness of rchain is needed first in order to conquer a market. Translation is a part of a marketing process that either attains an adequate readership or not. One person may have all the skill needed but the selection, translation, review, publishing and promotion needs to be a team effort in my view. Cooperative work is necessary and it promotes a collective intelligence. I suggest people doing pieces of the activity need to find their team and guides should help bring teams together. It is not clear to me that translations without a marketing plan should be funded. We need to be about cooperative work, not isolated things done independently. Teaming up into small well connected teams is what is most productive and prevents an organization from becoming chaotic as it scales. Proactively obeying the 10 patterns of decentralized organizations and collective intelligence principles is our challenge for every label in my view. The issues we have had with translations bears evidence to that need. I would be very liberal in placing value on readership independent of demographics. If something is worth publishing and promoted in english, it is worth doing it in every language in my book. We need to be where our competition is and should beat them to where they are not. If we might do the translation someday it is better to spent the rhoc now for the greatest benefit in the long term. |
Why the executive committee? Don't we have a pretty elaborate process for marketing work with circle 1 and 2 and such? Is that not working? |
First I would like to support @jasoncruzzy &@jimscarver. Marketing as a major business tool for growth is very important and also very expensive. To penetrate into peoples mind and capture their attention takes a lot of work and strategy. Marketing for either company's whether for new products or existing product has always been strategy and very expensive too. The essence of regional marketing and promotion can never be over emphasized. Let me wrap with an adage that says what is good for the goose is good for the gander.. If you have it in English why not have it in French ?.. Thanks |
Am in support of "focusing on the core" but there's a need to support localization to a certain extent; when there's an audience. Most translations have little or no audience, there needs to more organization around it like what documents to translate and into what languages. |
Focusing on the core would only limit the outreach/popularity the community needs. Let's take some frameworks likes React JS, Vue JS, etc they only became popular due to meetups which involved localization. Localization is a very vital marketing tool that many big guns in the tech industry have exploited. And further still, some of these documents for on boarding new members sound quite technical and isn't well understood by newbies who want to join the community. The team is work with in penetrate the Africa market have recorded more success than we would have done in Github and we are growing steadily from just one meet up. |
UPDATE: had a call yesterday with @allancto @ICA3DaR5 and @michaelizer regarding this topic. A few (partial) outcomes that I think are worth sharing: Discourage regional entities that encourage siloing of members.Consider the following scenario:
On the call we all agreed that this sort of efforts aren't very valuable to the coop, and should even actively be discouraged. The reason for this is that this splits the community. People should hang out in the main Discord channel, rather than isolate themselves. There is also a horror scenario where I build this Dutch community (paid for by the bounty program), and because I created the account, I have the admin keys to this property. Once I have firmly established myself, I run a scam airdrop or something of the sort... and people can't distinguish "the real RChain" from the community that I've created. Conclusion: all these regional efforts should be actively discouraged. We shouldn't cannibalise on the main (Coop-controlled) properties. Value-added translations@allancto has suggested that translations in and off themselves aren't always very valuable. But, often people can supplement the "core piece" with a regional twist. For instance: better than translating a piece on RChain to Dutch, one could take that piece and write commentary and supplements for it, that explain how this piece is relevant to the specifics of the Dutch context (or the French / Russian / African / etc. context) Regional strategies like meetups, etc. are still very valuableThese are excellent examples of taking the core content of RChain, and giving it a regional / local twist. Similar to the "value added translations" this kind of stuff adds value due to the personal nature of the events. This issue goal needs an updateThe top-level "strategy A vs. strategy B" decision is maybe way too big to tackle here, and needs more time to be sorted out by the community at large. @allancto suggested that some questions like that are better not tackled head-on. I'll need to reconsider how I rephrase this issue, and what more we want to get out of it. [to be continued] |
After reading all of the comments and feedback there is something to be said about both sides of the coin. There are a multitude of regional activities as @pmoorman mentioned above particularly with the meetups that add a great deal of localization value. What doesn't add value to me is the translation into every language as I had openly stated before and mentioned in #483. These questions immediately come to mind:
What comes to mind next is, how much will local adaptation cost? What is the potential return on the costs of adaption (how many more developers and new RAMs will we reach)? and will adaptation delay implementation (for example, a new marketing campaign or messaging)? RChain's multinational community thrives on scale and this scale favors standardization across markets. If we continue to push for localization without implementing a completed marketing strategy in English, how successful can that be? In my opinion this issue in it's entirety, boils down to trading off or waiting on the locally optimal programs in favor or globally optimal ones now. Before I decided to add my flavor to this discussionary pot, I did some reading and perhaps you will also find the reads as interesting as I did. RESEARCH DOCUMENTATION IDENTIFYING MARKETING UNIVERSALS VALUE OF PROPER LOCALIZATION MARKETING TRANSLATION COMPANY ARTICLES |
Well, having read about the different perspectives people have on option 1 & 2, I would like to start by saying everybody made a valid point and its really important this debate is coming up now. Firstly, regional marketing in itself doesn't affect the global goal of Rchain negatively and should be encouraged because I believe Rchain members in various communities around the world should know how best to market Rchain to people around them. Secondly, on the translation issue it has to be noted that not every country uses English to communicate and since the goal of Rchain is to become global, translating to various languages cannot be over emphasized especially for important informations hence the guides in charge of translation should generate a template as it deems fit. So I think the option 1 is better and necessary |
This has been a fruitful discussion. It's so broad that I don't think we can draw conclusions (so here I'm with @allancto). You can see it already in the title: translations/localisation/regionalization. Wow. But here are my two Satoshis: Translations Localization Regionalization "Should we pursue [strategy X] or should we pursue [strategy Y]?" The 'big marketing plan' is entirely focused on getting more developers involved. I think we should accept that as the focus of the marketing funnel. We shouldn't be spending time evangelizing to the general public because that requires explaining blockchain in general. But there is a larger target group around the coders – as the funnel flares – that's up-to-speed on crypto, technical, and capable. The ecosystem needs their skills too. That's the area our regionalization efforts should cover. |
I agree that the community should cooperate with the coops marketing plan. However, that only defines what we encourage members to do ignoring what they may have the energy to do that will not be done if we forbid it. I can understand why targeting developers is important but I also believe that brand awareness in the general public may be even more important in the long term. Blockchain technologies are increasingly being embraced as potential solutions for 3rd would nations and they need to know what rchain can do for them. I am not suggesting we support translations that will have no readership. I am suggesting we support translations suitable for a general audience having a smart objective that includes reasonable exposure and potential readership. We might create a short list of content that we encourage to be translated to any language along with exposure to a requisite audience. Again, choosing between alternatives rather than doing both things in a manifestation of zero sum game thinking that we must overcome in order for synergistic behaviours to emerge from the coop.. I suggest the time required by the label guides and the load put on them is driving this issue. Simple rules for allowing or not allowing activities would make their job easier at the expense of using collective intelligence and making good decisions. Generalization we enforce become discriminatory. I think our challenge is to scale the guide system so that proposals get due consideration without overtaxing our guides and that translators and promoters are guided to the most needed markets without being exclusionary. |
In my opinion here, I think we should make different marketing plans depend on different phases of Rchain. For the first stage like now, we don't even have our own main net launch.We really need good developers which I think most of the skilled can read English. We should focus more on the core.Most of the translation aren't really necessary for my opinion.(Right now if I tell my friends who are developers about Rchain, they always told me Rchain is still under development and there are actually not too many things they can do about it). For further stage(maybe after the main net launch), we can expand our marketing strategy to more regiona depends on the stage of Rchain development and Rchain's facility completeness.For me , the most powerful marketing strategy is to develop a good dapp which most people can use it. For now
For futureLocalizations and translations would be fine |
I completely agree with everything @jimscarver said in his above comments! |
I support Option 1 alongside @jimscarver and the others. This is because, in a business context Localization includes translation, but it also works with everything else in your content that has meaning: Pictures, colors, prices. Because these points are more subliminal, localization connects with consumers on a deeper level, improving their likelihood to buy. For example, imagine you’re comparing sunglasses on two different eCommerce sites. On the first, the graphics look “weird,” prices aren’t in a currency you recognize, and you can’t read the language. On the second, everything you see–images, words, amounts–make sense to you. Which would you buy from? The second one, right? You’re not alone: Common Sense Advisory reports that 75% of consumers agree or strongly agree that when faced with the choice of buying two similar products, they are more likely to purchase the one that has product information in their own language. Businesses with the most international success are those that adapt content for customer culture, language, and etiquette. That’s why they use localization to customize currency, date formatting, units of measurement, and other details that translation alone won’t catch. That being said, i strongly because the coop would compete favourable and possibly come on top in the blockchain industry if localization is tagged along on every stage of development. |
Hey all, I think my aim with this issue — to get a top-level decision on what to do with regards to localisation, regionalisation & translations — was probably unattainable from the start. Because of that, I want to close off this issue now. That said, I think it's led to valuable discussion, that helps the bounty system forward. Here's to hoping we can further converge towards a "social consensus" on these topics in the future. |
As guides for marketing @kitblake @AyAyRon-P and myself found out that it's incredibly hard to allocate budget to proposed tasks or tactics when they don't clearly fit into a larger kind of strategy.
One area in particular, is all the work that's being done for localisation & regionalisation: making RChain available in different languages, for different geographic regions, etc.
Goal
As a guide, I would like to have some strategic guidance as to how we should value these localisation efforts.
2 options
There are roughly 2 different "camps" in this debate:
The first group says... "Being inclusive matters. That means we need to cater to every corner of the world, and leave nobody behind. For that reason it's good to localize everything as far as possible."
The second group says... "We should focus on the core. Localisation should only be done in specific situations, rather than by default"
Without a clear choice by the community on whether to pursue either strategy 1 or 2.... it's impossible to value the work done under such projects.
SMART goal of this issue
I would like both camps to defend their case here as clearly as possible, and then distill a 'multiple choice' sort of question to either the Executive Committee or some other authoritative organ, and have them make a strategic decision on this.
It should have the form "should be pursue [strategy X] or should we pursue [strategy Y]?"
Suggested budget: $xxxx
Timeline: Formulate question before next Exec Committee meeting (can some on fill me in when that is?)
I guess this issue is a bit of a follow-up to #483 by @Jake-Gillberg. Please read that issue also!
The text was updated successfully, but these errors were encountered: