rjones (Mon, 06 Jan 2020 18:35:13 GMT):
User User_1 added by rjones.
rjones (Mon, 06 Jan 2020 18:35:21 GMT):
guoger
guoger (Tue, 07 Jan 2020 06:11:56 GMT):
Thanks Ry!
guoger (Tue, 07 Jan 2020 06:12:36 GMT):
User User_2 added by guoger.
guoger (Tue, 07 Jan 2020 06:12:36 GMT):
User User_3 added by guoger.
guoger (Tue, 07 Jan 2020 06:12:36 GMT):
User User_4 added by guoger.
guoger (Tue, 07 Jan 2020 06:14:07 GMT):
Internationalization of Hyperledger projects
guoger (Tue, 07 Jan 2020 06:14:48 GMT):
@all let's use this channel to coordinate i18n work
richzhao (Tue, 07 Jan 2020 06:17:10 GMT):
thx
guoger (Tue, 07 Jan 2020 06:24:24 GMT):
Let's have another discussion around i18n, would Wed 2PM UTC (9am east coast, 10pm china) work for everybody? cc pandrejko stone-ch richzhao
guoger (Tue, 07 Jan 2020 06:24:24 GMT):
Let's have another discussion around i18n, would Wed 2PM UTC (9am east coast, 10pm china) work for everybody? cc @pandrejko @stone-ch @richzhao
guoger (Tue, 07 Jan 2020 06:24:24 GMT):
Let's have another discussion around i18n, would *Wed 2PM UTC (9am east coast, 10pm china)* work for everybody? cc @pandrejko @stone-ch @richzhao
stone-ch (Tue, 07 Jan 2020 06:25:29 GMT):
The time is ok
pandrejko (Tue, 07 Jan 2020 13:35:55 GMT):
@guoger Dave Enyeart told me he is scheduling a Fabric Contributors call for that time (Wed 9am EST). So I think that time might not work for us.
pandrejko (Tue, 07 Jan 2020 13:36:20 GMT):
@odowdaibm Inviting you to the channel :-)
odowdaibm (Tue, 07 Jan 2020 13:36:20 GMT):
Has joined the channel.
guoger (Tue, 07 Jan 2020 14:47:50 GMT):
oh, that's right... how about right after that?
guoger (Tue, 07 Jan 2020 14:48:05 GMT):
(almost forgot about contributor meeting after holidays)
pandrejko (Wed, 08 Jan 2020 11:50:19 GMT):
That works with me.. I am checking with Anthony.
guoger (Wed, 08 Jan 2020 12:07:43 GMT):
this is probably too much of a last-minute notice and i'm afraid other folks might not be able to attend. How about tomorrow 2PM UTC? @pandrejko
pandrejko (Wed, 08 Jan 2020 12:43:58 GMT):
That works for me - But I need to to check to see if the Fabric Developer COmmunity is using the zoom session at that time. I think they hae their call on Thursdays Unless you have a zoom session we can use.
guoger (Wed, 08 Jan 2020 12:55:12 GMT):
hmm... do we have to use community zoom? otherwise i have webex room that we could use
pandrejko (Wed, 08 Jan 2020 12:55:35 GMT):
OK I have webex as well. I just was not sure if non-IBMers could get in?
pandrejko (Wed, 08 Jan 2020 12:55:35 GMT):
OK I have webex as well. I just was not sure if exxternal folls could get in?
pandrejko (Wed, 08 Jan 2020 12:55:35 GMT):
OK I have webex as well. I just was not sure if exxternal folks could get in?
pandrejko (Wed, 08 Jan 2020 12:55:35 GMT):
OK I have webex as well. I just was not sure if external folks could get in?
guoger (Wed, 08 Jan 2020 12:56:25 GMT):
they can. We use webex for external meetings as well
pandrejko (Wed, 08 Jan 2020 12:56:55 GMT):
OK I'll send an invite then
guoger (Wed, 08 Jan 2020 12:57:06 GMT):
great, thx a lot!
rjones (Wed, 08 Jan 2020 15:00:36 GMT):
pandrejko
rjones (Wed, 08 Jan 2020 15:00:47 GMT):
Has left the channel.
guoger (Thu, 09 Jan 2020 14:01:20 GMT):
joining
guoger (Thu, 09 Jan 2020 14:02:40 GMT):
webex is taking forever to launch for me
guoger (Thu, 09 Jan 2020 15:42:49 GMT):
thank you all for joining the discussion today and i think there were some misunderstandings that need to clarified. I never really tried to decide anything for community. The translation team (people doing actual work) within technical working group china collectively decided to use github. I am not among those (shame on me), but merely forwarding the message. Main reason being: 1) hard to access 2) obscure file conversion 3) no commit sign-off
guoger (Thu, 09 Jan 2020 15:44:42 GMT):
i think we should respect what translators desire and try not to make decision for them, especially tool selection that affects them on daily/weekly basis
guoger (Thu, 09 Jan 2020 15:45:45 GMT):
we'll put up a proposal to document current status and our need, and send to community for review. cheers
pandrejko (Wed, 15 Jan 2020 16:00:58 GMT):
Thanks for posting the process on the ML. Jay would you be able to present the process at the next COntributors meeting?
pandrejko (Wed, 15 Jan 2020 16:00:58 GMT):
Thanks for posting the process on the ML. @guoger would you be able to present the process at the next COntributors meeting?
pandrejko (Wed, 15 Jan 2020 16:00:58 GMT):
Thanks for posting the process on the ML. @guoger would you be able to present the process at the next Contributors meeting?
stone-ch (Fri, 17 Jan 2020 01:58:36 GMT):
When is the next Contributors meeting,do you mean the document group meeting 2020 01 17 ? pandrejko
stone-ch (Fri, 17 Jan 2020 01:58:36 GMT):
ok
stone-ch (Fri, 17 Jan 2020 01:58:36 GMT):
When is the next Contributors meeting,do you mean the document groups meeting 2020.1.17?
stone-ch (Fri, 17 Jan 2020 01:58:49 GMT):
@pandrejko
guoger (Fri, 17 Jan 2020 02:42:46 GMT):
@stone-ch no, i think @pandrejko was talking about next contributor meeting on Jan 22
guoger (Fri, 17 Jan 2020 02:43:55 GMT):
unfortunately that happens to be in the middle of Chinese New Year. Let's do a progress update on Feb 5
stone-ch (Fri, 17 Jan 2020 05:15:21 GMT):
ok
pandrejko (Fri, 17 Jan 2020 13:05:49 GMT):
Sounds good!
sankarshanm (Wed, 22 Jan 2020 03:50:53 GMT):
Has joined the channel.
Silona (Wed, 22 Jan 2020 21:32:48 GMT):
Has joined the channel.
pandrejko (Tue, 04 Feb 2020 20:19:58 GMT):
@stone-ch @gouger I know it is late notice, but would one of you want to present the I18n strategy on the Contributors call on Wednesday? I feel like if we can get Maintainers agreement, then we can move forward with the implementation.
pandrejko (Tue, 04 Feb 2020 20:19:58 GMT):
@stone-ch @guoger I know it is late notice, but would one of you want to present the I18n strategy on the Contributors call on Wednesday? I feel like if we can get Maintainers agreement, then we can move forward with the implementation.
pandrejko (Tue, 04 Feb 2020 20:20:31 GMT):
If not, no worries, we can try for a different call.
stone-ch (Wed, 05 Feb 2020 08:04:06 GMT):
Thank you @pandrejko I will join the meeting tonight.
pandrejko (Wed, 05 Feb 2020 14:22:32 GMT):
@stone-ch Nice job. Thank you for sharing this.
stone-ch (Wed, 05 Feb 2020 14:33:05 GMT):
Thank you @pandrejko , my english speaking is not good, I made a draft before the meeting. But still very nervous when I am reading. :blush:
pandrejko (Wed, 05 Feb 2020 14:57:42 GMT):
It was all good. And more importantly, I think it was well-received!
Silona (Thu, 13 Feb 2020 18:24:34 GMT):
Howdy Contributors and Maintainers! Are you wondering about tapping into Developer marketing for your group or project? Do you have a blog post idea? An awesome announcement? Please attend our Contributor/marketing meeting! https://wiki.hyperledger.org/display/Marketing/2020-02-19+Meeting+notes
pandrejko (Mon, 09 Mar 2020 21:06:50 GMT):
@stone-ch @guoger After the Hyperledger Conference last week in Phoenix we have more people interested in contributing translated content. Di we end up creating a WIKI with instructions for how to add translated content for other languages?
pandrejko (Mon, 09 Mar 2020 21:06:50 GMT):
@stone-ch @guoger After the Hyperledger Conference last week in Phoenix we have more people interested in contributing translated content. Did we end up creating a WIKI with instructions for how to add translated content for other languages?
stone-ch (Wed, 11 Mar 2020 02:41:39 GMT):
[ ](https://chat.hyperledger.org/channel/i18n?msg=bt5cP8rTJfSGGFcp8) We don't have a Wiki right now, we have translate guildline and rules in Chinese like this https://wiki.hyperledger.org/display/TWGC/Getting+Started. If needed I can make a Wiki and help other contributors add the translations of other languages.
stone-ch (Wed, 11 Mar 2020 02:43:16 GMT):
But the first thing is that did they have finished the translations or they just prepare to translate?
stone-ch (Wed, 11 Mar 2020 02:43:16 GMT):
Do they have finished the translations or they just prepare to translate?
stone-ch (Wed, 11 Mar 2020 02:43:16 GMT):
Did they have finished the translations or they just prepare to translate?
pandrejko (Fri, 05 Jun 2020 15:48:26 GMT):
@davidwboswell There is also an internationalization channel here in Rocket chat too.
davidwboswell (Fri, 05 Jun 2020 15:48:26 GMT):
Has joined the channel.
davidwboswell (Fri, 05 Jun 2020 16:17:06 GMT):
@pandrejko -- this is really helpful to know about. we should definitely include a link to this in the how to contribute translations docs that anthony showed. i ca also point people to this when i'm talking to people who want to get involved with translations.
pandrejko (Tue, 09 Jun 2020 16:58:16 GMT):
New Fabric documentation internationalization instructions are available here: https://hyperledger-fabric.readthedocs.io/en/latest/international_languages.html
davidwboswell (Tue, 09 Jun 2020 17:04:27 GMT):
@pandrejko -- thanks for posting. i'll share this out with some community members who have expressed interest in helping to translate
stone-ch (Thu, 11 Jun 2020 07:50:59 GMT):
Greate I will share this with TWGC community members, too.
rjones (Mon, 15 Jun 2020 19:50:39 GMT):
Has joined the channel.
rjones (Mon, 15 Jun 2020 19:50:39 GMT):
Hi - I set up https://www.transifex.com/hyperledger/fabric-i18n/dashboard/ to work with the new repo https://github.com/hyperledger/fabric-docs-i18n/ - how would you all like to move forward?
stone-ch (Wed, 17 Jun 2020 01:34:17 GMT):
We have tried transifex for a few months to translate Fabric documents last year, transifex is good website for translating, but it has some shortcomings make us not use it finally. First, it is too slow for us in China because of the network.Second, when transifex parse the documents, it always missing some marks of markdown syntax, such as " ```
stone-ch (Wed, 17 Jun 2020 01:34:17 GMT):
We have tried transifex for a few months to translate Fabric documents last year, transifex is good website for translating, but it has some shortcomings make us not use it finally. First, it is too slow for us in China because of the network.Second, when transifex parse the documents, it always missing some marks of markdown syntax, such as ` ```
stone-ch (Wed, 17 Jun 2020 01:34:17 GMT):
We have tried transifex for a few months to translate Fabric documents last year, transifex is good website for translating, but it has some shortcomings make us not use it finally. First, it is too slow for us in China because of the network.Second, when transifex parse the documents, it always missing some marks of markdown syntax, such as ` **
odowdaibm (Wed, 17 Jun 2020 06:29:25 GMT):
I agree @stone-ch It seems that most other teams are both using language translations as the Chinese team is -- i.e. not using PO/POT and not using Transifex. I think we need to follow your lead, and I think also gently guide new language teams to do the same as you. It would be ideal if, over time, the CN repo could come in under the i18N repo that @rjones has created.
rjones (Wed, 17 Jun 2020 07:07:20 GMT):
I set up transifex because it looked like it was in use for zh_CN already. Whatever workflow you like
odowdaibm (Wed, 17 Jun 2020 07:10:33 GMT):
Sure, understood @rjones -- very reasonable, and it's still an option for teams that want to use it I guess. I think it's probably OK that we have a light touch on its use -- a bit like building locally, or in RTD. I do think it's more important that for consistency of structure all language teams use the same approach as the CN and BR teams -- that the language translation is a first class asset, and not somehow technically translated from English -- i.e. teams are not using PO/POT approach, and we should try to standardize on that -- as it will make the build the same for all languages.
odowdaibm (Wed, 17 Jun 2020 07:10:33 GMT):
Sure, understood @rjones -- very reasonable, and it's still an option for teams that want to use it I guess. I think it's probably OK that we have a light touch on its use -- a bit like building locally, or in RTD. I do think it's more important that for consistency of structure, all language teams use the same approach as the CN and BR -- that the language translation is a first class asset, and not somehow technically translated from English -- i.e. teams are not using PO/POT approach. We should try to standardize on that -- as it will make the build the same for all languages.
rjones (Wed, 17 Jun 2020 07:19:05 GMT):
how do you want to handle the existing content in labs? I can do some magic and bring it over _in toto_ if you like.
odowdaibm (Wed, 17 Jun 2020 07:25:37 GMT):
I think we need the owners of CN and ML (Malayalam) to agree. I cannot see it being an issue, but it's good form, obviously. Maybe @stone-ch could raise it with the CN working group -- I can discuss with @aneenaalex -- I'm a maintainer for ML, but we'd like Aneena and her team to be happy obviously.
aneenaalex (Wed, 17 Jun 2020 07:25:37 GMT):
Has joined the channel.
rjones (Wed, 17 Jun 2020 07:38:37 GMT):
yes, of course
stone-ch (Wed, 17 Jun 2020 08:53:24 GMT):
Yes, I agree @odowdaibm the the consistency of structure is more important. I think po/pot file is a very good format for translations, for example, if we want to translate the output logs of Fabric, we can use the translations in po files replace the text in print() function, and not need to modify the source code, because the po contains the line number of the source text. Transifex just like a tool to manage the po/pot files and simplified the translate workflow, we can change the po/pot management tool if we find a better one, and what need eventually is po/pot files.
odowdaibm (Wed, 17 Jun 2020 08:58:44 GMT):
Thanks @stone-ch Very interesting and thank you. I noticed though that the CN team didn't use PO/POTs, and neither did @renatost. This is tricky -- we really want to listen and follow what the translation teams suggest and practice rather than dictate, but we will all benefit from a single approach. At the moment that feels like not using PO/POT. Clearly this is a tricky balancing act. @renatost and you might want to discuss here. Right now, CN, BP and ML are our leading translations and if we can get these aligned then it will help all the other folks who are looking at translations right now -- and we have a lot of them (Spanish, French, Japanese...)
renatost (Wed, 17 Jun 2020 08:58:44 GMT):
Has joined the channel.
stone-ch (Wed, 17 Jun 2020 09:19:29 GMT):
Yes, we didn't use PO/POTs in CN team, mainly because I can't find a good tool to manage the files, now our method is use text editor replace the source text with Chinese translations directly, it's more simpler. It's just my suggestion that PO/POTs maybe a better format if we have a good tool. Sure, we should listen more suggestions of other teams.
odowdaibm (Wed, 17 Jun 2020 09:32:07 GMT):
OK, super helpful @stone-ch thank you. I think hen for now, if all the team are happy that we adopt the standard set by the CN teams. I personally like it because it makes CN, PT and ML first class languages, and I think that will help the English documentation. For example, Renato has found some issues with English. Now it does mean that we need to collaborate quite a lot, but I think that's OK. Aneena said that she was fine working with source text like CN, so I think it might be easiest to make that our standard for now.
odowdaibm (Wed, 17 Jun 2020 09:32:07 GMT):
OK, super helpful @stone-ch thank you. I think for now, if all the team are happy, we adopt the standard set by the CN team. I personally like it because it makes CN, PT and ML first class languages, and I think that will help the English documentation. For example, Renato has found some issues with English and fixed them. It does mean that we need to collaborate two ways, but I think that's OK. Aneena said that she was fine working with source text as you do in CN, so I think it might be easiest to make that our standard for now.
stone-ch (Wed, 17 Jun 2020 09:37:56 GMT):
That's great, working with source text is good and actually I like it.
odowdaibm (Wed, 17 Jun 2020 10:06:28 GMT):
Super -- that's a deal then. @rjones we need to think about how we stage the repos coming across with the consent of the maintainers. If, as you suggest, they first get moved in under Fabric, then teams can move the content into i18n under the appropriate directory. Renato has already populated Br_pt. If @stone-ch can raise with the CN maintainers, then I can work with @Aneena and her team to communicate.
odowdaibm (Wed, 17 Jun 2020 10:06:28 GMT):
Super -- that's a deal then. @rjones we need to think about how we stage the repos coming across with the consent of the maintainers. If, as you suggest, they first get moved in under Fabric, then teams can move the content into i18n under the appropriate directory. Renato has already populated Br_pt. If @stone-ch can raise with the CN maintainers, then I can work with @aneenaalex and her team to communicate. @pandrejko for awareness.
renatost (Wed, 17 Jun 2020 14:44:32 GMT):
@odowdaibm and @stone-ch -- Essentially I found two unwanted situations when using PO/POTs: - It requires extra processes in the creation and updating of the content, in the update it will be necessary to perform a more complicated process of differences checking . In the source code this is straightforward. -- POs do not transfer markdown formatting, thus the translation process becomes more difficult.
stone-ch (Wed, 17 Jun 2020 14:59:43 GMT):
Yes, if use PO/POTs we must have a tool to help us manage them. And use source code also has a problem, when the english documents updated we should check the differences and update the translations, now our method is use Idea(a java IDE) "Compare with Branch" to compare the files one by one to find the changes, @renatost do you have any better ways to check the differences?
rjones (Wed, 17 Jun 2020 15:36:51 GMT):
@BrettLogan
BrettLogan (Wed, 17 Jun 2020 15:36:51 GMT):
Has joined the channel.
rjones (Wed, 17 Jun 2020 15:43:56 GMT):
@odowdaibm I'll follow your lead - I created the repo under the guidance of fabric maintainers
BrettLogan (Wed, 17 Jun 2020 16:50:19 GMT):
@odowdaibm I'm having a bit of a hard time following this conversation, as most of the terminology is new to me. Is there an objection to folding the existing Labs repos into a single repo `fabric-docs-i18n` and if so, what are the concerns
odowdaibm (Wed, 17 Jun 2020 16:53:07 GMT):
there isn't -- we've agreed on the structure of the docs. I think it will then be up to the CN team to populate. I've been working with @renatost and @aneenaalex who are both happy that we do this. So we're covered for Br-Pt and Malayalam in terms of populating. Does that help @BrettLogan ?
BrettLogan (Wed, 17 Jun 2020 16:53:43 GMT):
Ok, I just wanted to make sure before I invest my time into getting the CI for doc builds configured.
odowdaibm (Wed, 17 Jun 2020 16:54:00 GMT):
I think we should let the teams populate i18n themselves -- the key thing is to have the doc builds being generated as you say.
odowdaibm (Wed, 17 Jun 2020 16:54:12 GMT):
And right now, the teams don't need Transifex set up either
BrettLogan (Wed, 17 Jun 2020 16:54:27 GMT):
Thank you for the clarification. If there is anything we as the maintainers can do to help, any of the projects should feel free to reach out to myself
odowdaibm (Wed, 17 Jun 2020 16:54:54 GMT):
will do Brett -- On this week's doc WG calls we'll clarify, but Renato and Aneena are fully aware
odowdaibm (Wed, 17 Jun 2020 16:55:02 GMT):
I will update the docs to make contribution clearer
odowdaibm (Wed, 17 Jun 2020 16:55:12 GMT):
thx again for your much appreciated help
BrettLogan (Wed, 17 Jun 2020 16:55:12 GMT):
I'll try to join this week, just need to make sure I highlight it on my calendar
odowdaibm (Wed, 17 Jun 2020 16:55:20 GMT):
sure, and thx
rjones (Wed, 17 Jun 2020 16:58:14 GMT):
@odowdaibm take a look at this: https://github.com/ryjones/fabric-docs-i18n
rjones (Wed, 17 Jun 2020 16:58:51 GMT):
it preserves the history of both the repos under the labs
rjones (Wed, 17 Jun 2020 16:59:20 GMT):
I see it isn't perfect and I need to fix a few things
odowdaibm (Wed, 17 Jun 2020 16:59:56 GMT):
Looking -- I think that having a close mirror to fabric repo would be best
odowdaibm (Wed, 17 Jun 2020 17:00:12 GMT):
I think this implies docs/source with langs under that? in locale?
rjones (Wed, 17 Jun 2020 17:01:39 GMT):
I'm OK moving everything down a few directories if you like
rjones (Wed, 17 Jun 2020 17:02:31 GMT):
My goal was to preserve history of the existing repos
odowdaibm (Wed, 17 Jun 2020 17:02:36 GMT):
I think that might help -- as it will mean all the instructions carry over
odowdaibm (Wed, 17 Jun 2020 17:02:58 GMT):
(yes, I understand, and appreciate)
rjones (Wed, 17 Jun 2020 17:03:10 GMT):
I see I missed the readme, which is still the thing
odowdaibm (Wed, 17 Jun 2020 17:04:53 GMT):
I think having docs/source/locale/
odowdaibm (Wed, 17 Jun 2020 17:04:59 GMT):
would that be OK?
odowdaibm (Wed, 17 Jun 2020 17:05:10 GMT):
I think ML does it this way
rjones (Wed, 17 Jun 2020 17:05:48 GMT):
I'm fine with it. Let me put something up
odowdaibm (Wed, 17 Jun 2020 17:06:03 GMT):
Even if we have a shortened version of this:
odowdaibm (Wed, 17 Jun 2020 17:06:05 GMT):
https://github.com/hyperledger-labs/fabric-docs-ml/tree/master/docs/source/locale/ml/LC_MESSAGES/commands
odowdaibm (Wed, 17 Jun 2020 17:06:38 GMT):
https://github.com/hyperledger-labs/fabric-docs-ml/tree/master/docs/source/locale/ml/
odowdaibm (Wed, 17 Jun 2020 17:07:01 GMT):
or https://github.com/hyperledger-labs/fabric-docs-ml/tree/master/docs/source/ml/
rjones (Wed, 17 Jun 2020 17:07:09 GMT):
does anyone have strong feelings about ml_IN, for instance? I know en_US and en_UK are different
odowdaibm (Wed, 17 Jun 2020 17:07:13 GMT):
both would work well for now
odowdaibm (Wed, 17 Jun 2020 17:07:34 GMT):
I don't know the 4 code for ML
odowdaibm (Wed, 17 Jun 2020 17:07:38 GMT):
ISO 693 is ML
rjones (Wed, 17 Jun 2020 17:07:42 GMT):
it's ml_IN
odowdaibm (Wed, 17 Jun 2020 17:07:48 GMT):
well perfect!
odowdaibm (Wed, 17 Jun 2020 17:07:52 GMT):
ty!
rjones (Wed, 17 Jun 2020 17:08:12 GMT):
I noticed you were posting Pt_Br and I wanted to make sure we're on the same page
odowdaibm (Wed, 17 Jun 2020 17:08:22 GMT):
you're 100% correct
odowdaibm (Wed, 17 Jun 2020 17:08:27 GMT):
ty
rjones (Wed, 17 Jun 2020 17:08:32 GMT):
OK
rjones (Wed, 17 Jun 2020 17:09:26 GMT):
so https://github.com/hyperledger/fabric/tree/master/docs/source/locale/[ml_IN|zh_CN...], right?
rjones (Wed, 17 Jun 2020 17:09:26 GMT):
so https://github.com/hyperledger/fabric... /tree/master/docs/source/locale/[ml_IN|zh_CN...], right?
odowdaibm (Wed, 17 Jun 2020 17:10:10 GMT):
yepper
odowdaibm (Wed, 17 Jun 2020 17:10:20 GMT):
ty
rjones (Wed, 17 Jun 2020 17:13:37 GMT):
@odowdaibm take a look? https://github.com/ryjones/fabric-docs-i18n
rjones (Wed, 17 Jun 2020 17:14:57 GMT):
I think I need to adjust where ml_IN landed
rjones (Wed, 17 Jun 2020 17:21:32 GMT):
I moved the content of ml_IN up one: https://github.com/ryjones/fabric-docs-i18n/tree/master/docs/source/locale/ml_IN/
odowdaibm (Wed, 17 Jun 2020 17:21:53 GMT):
that looks right
odowdaibm (Wed, 17 Jun 2020 17:22:36 GMT):
Pt_Br can go in as a peer of that
odowdaibm (Wed, 17 Jun 2020 17:22:52 GMT):
And it should be fine for the China team to do the same
odowdaibm (Wed, 17 Jun 2020 17:23:15 GMT):
If we then build the site from that for the language options, it's just great
odowdaibm (Wed, 17 Jun 2020 17:23:31 GMT):
this will be a marvellous step forward --ty so much
odowdaibm (Wed, 17 Jun 2020 17:24:07 GMT):
Obv keep china docs coming from their repo build until they're happy to move everything across
rjones (Wed, 17 Jun 2020 17:24:14 GMT):
yes, if you go up one level, you'll see I brought everything over that way
rjones (Wed, 17 Jun 2020 17:24:35 GMT):
https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/131 is pending for the move
odowdaibm (Wed, 17 Jun 2020 17:24:57 GMT):
yes, that's cool - the CN team can bring their directories up
rjones (Wed, 17 Jun 2020 17:25:40 GMT):
it's easy for me to do before the move, if they could tell me what they want, let's do it?
odowdaibm (Wed, 17 Jun 2020 17:32:07 GMT):
I think everything in this directory should be moved to the root except the source directory which should be removed
odowdaibm (Wed, 17 Jun 2020 17:32:11 GMT):
Clipboard - June 17, 2020 6:32 PM
odowdaibm (Wed, 17 Jun 2020 17:32:46 GMT):
or rather they should be in the docs folder
odowdaibm (Wed, 17 Jun 2020 17:32:52 GMT):
with the README.md in the root
odowdaibm (Wed, 17 Jun 2020 17:33:35 GMT):
yes, that's right, as the docs folder is currently empty
odowdaibm (Wed, 17 Jun 2020 17:33:44 GMT):
makes sense I hope
rjones (Wed, 17 Jun 2020 17:34:24 GMT):
could we screen share in 20?
odowdaibm (Wed, 17 Jun 2020 17:34:30 GMT):
sure
odowdaibm (Wed, 17 Jun 2020 17:34:39 GMT):
ding when you're ready, and thanks
rjones (Wed, 17 Jun 2020 17:34:54 GMT):
OK. I updated the pt_BR PR to use the new format
rjones (Wed, 17 Jun 2020 17:37:51 GMT):
https://github.com/hyperledger/fabric-docs-i18n/pull/2
rjones (Wed, 17 Jun 2020 17:43:59 GMT):
@renatost if you are OK with it I will merge
renatost (Wed, 17 Jun 2020 17:45:54 GMT):
I'm comfortable with that. TY.
renatost (Wed, 17 Jun 2020 18:11:12 GMT):
@rjones In the result of merge the docs directory is left inside the pt_BR structure. Can I remove it in my next PR or do you prefer to do it?
rjones (Wed, 17 Jun 2020 18:29:42 GMT):
please restructure it how you like and file a PR
rjones (Wed, 17 Jun 2020 18:30:12 GMT):
probably move the contents of `/.gitignore` into your pt_BR area (and fix the path)
renatost (Wed, 17 Jun 2020 18:33:53 GMT):
no problem... I will tailor my files as required to follow the new structure.
renatost (Wed, 17 Jun 2020 19:01:10 GMT):
@odowdaibm - About the README files. I think that in the pt_BR directory Is better to left the README.md talking about brasilian translation project and we can move the README that we have inside the docs (talking about the build process) to locale dir and after that we can update to reflect the new process of build international language docs. What you think about?
odowdaibm (Wed, 17 Jun 2020 19:02:02 GMT):
yes, exactly right
odowdaibm (Wed, 17 Jun 2020 19:02:11 GMT):
the top level README should be generic
odowdaibm (Wed, 17 Jun 2020 19:02:47 GMT):
and into each locale/
odowdaibm (Wed, 17 Jun 2020 19:03:00 GMT):
Ry and I agree with you, so thanks for pointing it out
odowdaibm (Wed, 17 Jun 2020 19:03:41 GMT):
thanks @renatost
renatost (Wed, 17 Jun 2020 19:04:49 GMT):
I don't have any tool to support that yet. From now that I'm incorporating my repo I need to start to think about that, my first idea was track the JIRA issues and than reflect in my repo but is only a idea. I will reflect about your process and if discover something new I will tell you.
odowdaibm (Wed, 17 Jun 2020 19:06:00 GMT):
Have a think about this process. @pandrejko and I discussed last week, and given all doc changes are tagged, it's an easy matter to find all PRS
odowdaibm (Wed, 17 Jun 2020 19:06:34 GMT):
So I think tracking PRs tagged with doc might be easier @renatost
renatost (Wed, 17 Jun 2020 19:10:12 GMT):
I agree... we can try this.
pandrejko (Wed, 17 Jun 2020 19:24:46 GMT):
Right. Currency is really important and will be a challenge as the translators go through this process. The Fabric docs that they clone today will be different next week - as Renato knows. A minimalist approach would be to query for all the doc PRs and examine the updates, but I expect that process may be cumbersome over time if there are _nn's_ of docs PRs to cull through. I'm trying to think how we can make this easier - by diffing the English versions of the files to see the changes that have been introduced or something like that. Just thinking off the top of my head.
pandrejko (Wed, 17 Jun 2020 19:25:21 GMT):
Maybe just focus on 1 committed release at a time.
odowdaibm (Wed, 17 Jun 2020 19:40:56 GMT):
that;s what we decided for ML for example Pam -- get 2.1 translated, and then it's just delta. Tbh,I like your suggestion of diffs -- it's quite easy to do, and it all languages have the same structure it would be quite easy to see the ascope of the changes
odowdaibm (Wed, 17 Jun 2020 19:40:56 GMT):
that;s what we decided for ML for example Pam -- get 2.1 translated, and then it's just delta. Tbh,I like your suggestion of diffs -- it's quite easy to do, and as all languages have the same structure it would be quite easy to see the ascope of the changes
rjones (Wed, 17 Jun 2020 21:04:26 GMT):
@pandrejko @odowdaibm @aneenaalex hi. Somehow, I deleted the labs repo. I had a checked out copy, tho, and I've restored the master branch. Sorry.
rjones (Wed, 17 Jun 2020 21:04:38 GMT):
https://github.com/hyperledger-labs/fabric-docs-ml
odowdaibm (Thu, 18 Jun 2020 06:35:09 GMT):
Look fine now, thx Ry
BrettLogan (Thu, 18 Jun 2020 16:08:18 GMT):
I setup CI for the i18n repo. So it will now build the doc when PR's are opened
rjones (Thu, 18 Jun 2020 16:38:12 GMT):
@odowdaibm what happened is any open PRs, or any open issues, were deleted. :(
rjones (Thu, 18 Jun 2020 17:14:50 GMT):
@stone-ch howdy
rjones (Thu, 18 Jun 2020 17:15:35 GMT):
@stone-ch Do you want me to do the thing I showed previously, to bring over the lab repo?
rjones (Thu, 18 Jun 2020 17:15:51 GMT):
If you want that, I can move the content to the new repo and archive the lab repo.
renatost (Thu, 18 Jun 2020 17:33:01 GMT):
My new PR had the CI failed. I believe that is because I made a change in the directory structure required to be aligned with the new definition. Could you check please?
BrettLogan (Thu, 18 Jun 2020 17:39:44 GMT):
@renatost It's not a required check, I disabled the required check until you finish reorganizing the directory and then I'll fix CI
BrettLogan (Thu, 18 Jun 2020 17:39:44 GMT):
@renatost It's not a required check, I disabled the required check after I realized you were still reorganizing, until you finish reorganizing the directory and then I'll fix CI
BrettLogan (Thu, 18 Jun 2020 17:39:52 GMT):
So if you are good, I will merge that PR
renatost (Thu, 18 Jun 2020 17:40:16 GMT):
Yes, please.
BrettLogan (Thu, 18 Jun 2020 17:40:33 GMT):
Done
renatost (Thu, 18 Jun 2020 17:41:04 GMT):
Super!
BrettLogan (Thu, 18 Jun 2020 17:41:26 GMT):
And I see the issue with CI, so I will fix that quick
renatost (Thu, 18 Jun 2020 17:41:45 GMT):
TY..
BrettLogan (Thu, 18 Jun 2020 17:48:51 GMT):
All updated, CI will work properly now, thanks Renato
rjones (Thu, 18 Jun 2020 19:25:44 GMT):
@aneenaalex https://github.com/hyperledger/fabric-docs-i18n/tree/master/docs/source/locale/ml_IN all yours!
rjones (Thu, 18 Jun 2020 19:25:57 GMT):
@stone-ch https://github.com/hyperledger/fabric-docs-i18n/tree/master/docs/source/locale/zh_CN all yours!
stone-ch (Fri, 19 Jun 2020 02:52:57 GMT):
got it
stone-ch (Fri, 19 Jun 2020 03:48:54 GMT):
@rjones please open the issues of https://github.com/hyperledger/fabric-docs-i18n, in https://github.com/hyperledger-labs/fabric-docs-cn we use issues managing who will translate which article. The translator can open an issue and leave a message indicated they want to translate the article, then the admin will assign the issue to him/her, avoiding another translator translate the same article.
rjones (Fri, 19 Jun 2020 04:18:56 GMT):
done - oversight on my part
yuki-kon (Fri, 19 Jun 2020 06:48:25 GMT):
Has joined the channel.
odowdaibm (Fri, 19 Jun 2020 06:55:36 GMT):
Hello @yuki-kon Welcome to the discussion and thanks for your collaboration on a Japanese translation!
yuki-kon (Fri, 19 Jun 2020 06:56:45 GMT):
@odowdaibm Thank you for great advice for documatation today! I'm very excited.
odowdaibm (Fri, 19 Jun 2020 06:59:26 GMT):
Hello @BrettLogan @rjones -- Aneena and her team @aneenaalex have been making excellent progress on a ML translation. Once we have a working build pipeline, it would be good to plug in the ML repo. The team have started to work using the same mechanism as CN and PTBR teams -- i.e. flat files rather than PO/POT. This is very helpful, and much appreciated, so that all our languages work the same way.
odowdaibm (Fri, 19 Jun 2020 07:01:47 GMT):
I also like the new directory structure -- but @renatost, I feel that we might be better off without the top level source directory. i.e. *fabric-docs-i18n/docs/source/locale/pt_BR/source/* would become *fabric-docs-i18n/docs/locale/pt_BR/source/*
odowdaibm (Fri, 19 Jun 2020 07:02:58 GMT):
I think it would be a good idea to change this now @rjones @BrettLogan so that we can make it as simple as possible. I know it makes a small change required to CI pipeline, but it's worth it, I think.
BrettLogan (Fri, 19 Jun 2020 07:05:34 GMT):
Not a problem. I am going to disable CI checks for right now and once we are totally settled we can reenable them
odowdaibm (Fri, 19 Jun 2020 07:05:52 GMT):
ty Brett
BrettLogan (Fri, 19 Jun 2020 07:07:58 GMT):
Disabled
rjones (Fri, 19 Jun 2020 07:43:35 GMT):
@odowdaibm do you want this change across all branches, or just master?
rjones (Fri, 19 Jun 2020 07:43:49 GMT):
I think all branches
odowdaibm (Fri, 19 Jun 2020 08:39:57 GMT):
yepper, all branches
rjones (Fri, 19 Jun 2020 09:24:12 GMT):
https://github.com/hyperledger/fabric-docs-i18n/tree/master/docs/locale (done across all branches)
tatsu-sato (Fri, 19 Jun 2020 16:37:26 GMT):
Has joined the channel.
pandrejko (Wed, 24 Jun 2020 14:07:43 GMT):
I shared these links on the Contributors call this morning and thought I would post them here for reference for those interested in getting started with the translations:
Contributing Guide: https://hyperledger-fabric.readthedocs.io/en/latest/CONTRIBUTING.html#contributing-documentation
Internationalization: https://hyperledger-fabric.readthedocs.io/en/latest/international_languages.html
Workgroups: https://wiki.hyperledger.org/display/fabric/International+groups
Github repo: https://github.com/hyperledger/fabric-docs-i18n
rjones (Wed, 24 Jun 2020 14:29:01 GMT):
@pandrejko I thought your guidance to first translate the Contributing guide was great, and obvious in hindsight, but I never would have thought of it
pandrejko (Wed, 24 Jun 2020 15:22:51 GMT):
@BrettLogan Hi Brett. Renato tried to change the advanced configuration settings as you suggested (change the location of the requirements file) but the readthedocs does not seem to be recognizing his changes. Does he have the correct permissions to be able to do that?
pandrejko (Wed, 24 Jun 2020 15:24:30 GMT):
https://github.com/rst77/fabric-docs-i18n
BrettLogan (Wed, 24 Jun 2020 15:30:11 GMT):
@pandrejko @renatost Let me fork Renato's repo and setup my readthedocs to use his and see what I can figure out
renatost (Wed, 24 Jun 2020 15:55:45 GMT):
Thanks...
BrettLogan (Thu, 25 Jun 2020 15:59:01 GMT):
Renato, I am still working on this, I got everything set up yesterday and I am seeting the same issue you are, despite changing the location of the file, its not actually using that file. I may have to reach out to readthedocs support on this
renatost (Thu, 25 Jun 2020 16:25:31 GMT):
No problem. I will still working on the translation until we have this situation fixed.
odowdaibm (Thu, 02 Jul 2020 17:58:59 GMT):
Sounds like we are close on i18n build maybe now Brett has it working on en_US?
BrettLogan (Thu, 02 Jul 2020 18:01:56 GMT):
Yea, I just need to open a support ticket with the ReadTheDoc team and figure out why it isn't honoring the config location when we explicitly override it in the UI
odowdaibm (Thu, 02 Jul 2020 18:02:22 GMT):
great -- I will start to document what we have in the docs -- ty again Brett
renatost (Thu, 02 Jul 2020 18:04:32 GMT):
Hello everyone! I opened one pull request 3 days ago. Someone received some kind of notification about it? It is working fine?
renatost (Thu, 02 Jul 2020 18:05:30 GMT):
Just for know, I'm nobbie in this workflow.
odowdaibm (Thu, 02 Jul 2020 18:05:42 GMT):
I'm happy to approve - let me do that now
renatost (Thu, 02 Jul 2020 18:06:00 GMT):
don't worry... I curious only... :)
odowdaibm (Thu, 02 Jul 2020 18:06:17 GMT):
no worries, it's important we move this through
pandrejko (Thu, 02 Jul 2020 18:06:50 GMT):
I received the notification, but I assume I am not authorized to merge it
BrettLogan (Thu, 02 Jul 2020 18:08:59 GMT):
You are Pam
BrettLogan (Thu, 02 Jul 2020 18:09:17 GMT):
The Fabric-Doc-Mantainers were added as doc maintainers for this repo as well
BrettLogan (Thu, 02 Jul 2020 18:10:08 GMT):
There are two layers of maintainers. The Fabric-Doc-Maintainers can approve for any language. And then each language has their own subset of maintainers who can also approve for their language only
odowdaibm (Thu, 02 Jul 2020 18:10:10 GMT):
I'll add Pam and Joe to list
odowdaibm (Thu, 02 Jul 2020 18:10:14 GMT):
yes they were
odowdaibm (Thu, 02 Jul 2020 18:10:22 GMT):
I've just approved, and merged
odowdaibm (Thu, 02 Jul 2020 18:10:42 GMT):
it should be in now @renatost
pandrejko (Thu, 02 Jul 2020 18:11:07 GMT):
OK. Good to know. Thanks Brett.
renatost (Thu, 02 Jul 2020 18:11:37 GMT):
Yes, thanks @odowdaibm !
odowdaibm (Thu, 02 Jul 2020 18:11:40 GMT):
apols for being a bit slow @renatost Always feel free to ping me, Pam, Joe or me to move this through for you to
pandrejko (Thu, 02 Jul 2020 18:11:43 GMT):
Is it the same process where we add the doc-merge tag?
odowdaibm (Thu, 02 Jul 2020 18:12:50 GMT):
I've added doc tag Pam, is there another?
pandrejko (Thu, 02 Jul 2020 18:13:39 GMT):
Normally, we add the doc-merge tag and then a bot comes through and does the actual merge.
odowdaibm (Thu, 02 Jul 2020 18:14:00 GMT):
nice, seems like that;s not here yet
odowdaibm (Thu, 02 Jul 2020 18:14:19 GMT):
That option wasn't available to me, so I suspect it needs to be applied
odowdaibm (Thu, 02 Jul 2020 18:14:40 GMT):
for now, we can cope, as volumes relatively low, but it would be good to get aligned
odowdaibm (Thu, 02 Jul 2020 18:14:48 GMT):
(or me to fix my ignorance, if I'm wrong!)
BrettLogan (Thu, 02 Jul 2020 18:14:54 GMT):
I will add the mergify bot so you can use the `doc-merge` label
odowdaibm (Thu, 02 Jul 2020 18:15:08 GMT):
superstar - ty Brett
renatost (Thu, 02 Jul 2020 18:18:05 GMT):
I'm not aware about this tagging process. Is this information would need to be in the contributing documentation?
odowdaibm (Thu, 02 Jul 2020 18:18:26 GMT):
you read my mind -- I'm doing updates now and will add!
BrettLogan (Thu, 02 Jul 2020 18:20:22 GMT):
@odowdaibm or @pandrejko , can you approve this: https://github.com/hyperledger/fabric-docs-i18n/pull/22
BrettLogan (Thu, 02 Jul 2020 18:20:54 GMT):
Nevermind, one of the fabric maintainers got it
renatost (Thu, 02 Jul 2020 18:21:15 GMT):
:sunglasses: translation work are giving me new skills... lol...
BrettLogan (Thu, 02 Jul 2020 18:21:53 GMT):
Thats all, the doc-merge label will work now
pandrejko (Thu, 02 Jul 2020 18:22:21 GMT):
Does the doc-merge label that we click Approve first?
pandrejko (Thu, 02 Jul 2020 18:22:21 GMT):
Does the doc-merge label require that we click Approve first?
pandrejko (Thu, 02 Jul 2020 18:22:27 GMT):
(I can't remember)
BrettLogan (Thu, 02 Jul 2020 18:22:44 GMT):
When you add it, once the change is approved (and CI passes if its enabled) once a minute Mergify will come through and automerge any changes with that meet that crtieria
BrettLogan (Thu, 02 Jul 2020 18:22:56 GMT):
Correct, you need to approve (and CI to pass when we enable it)
renatost (Thu, 02 Jul 2020 18:25:03 GMT):
@BrettLogan Can I set this tag when I create the PR?
BrettLogan (Thu, 02 Jul 2020 18:25:20 GMT):
You can, and then once someone approves it, it will auto merge
renatost (Thu, 02 Jul 2020 18:25:54 GMT):
good... thanks
pandrejko (Thu, 02 Jul 2020 19:34:45 GMT):
I think it would be a best practice not to set the doc-merge tag until it is ready to merge - in case a reviewer has comments. Setting it in advance effectively means it only has to be approved by 1 reviewer. Maybe that is ok in this case, but it seems a little risky
pandrejko (Thu, 02 Jul 2020 19:34:45 GMT):
I think it would be a best practice not to set the doc-merge tag until it is ready to merge - in case another reviewer has comments. Setting it in advance effectively means it only has to be approved by 1 reviewer. Maybe that is ok in this case, but it seems a little risky
renatost (Thu, 02 Jul 2020 19:48:15 GMT):
Make sense.
satomicchy (Sat, 04 Jul 2020 14:34:19 GMT):
Has joined the channel.
stone-ch (Wed, 08 Jul 2020 01:47:14 GMT):
hi，@odowdaibm @rjones ，please add @guoger (github-ID:guoger) and @davidkhala (github-ID:davidkhala) into github team fabric-zh_cn-doc-maintainers, they will review and approve my PRs in fabric-docs-i18n repo.
stone-ch (Wed, 08 Jul 2020 01:47:14 GMT):
hi，@odowdaibm @rjones ，please add @guoger (github-ID:guoger) and @davidkhala (github-ID:davidkhala) into github team fabric-zh_cn-doc-maintainers, they will review and approve my PRs in fabric-docs-i18n repo.
stone-ch (Wed, 08 Jul 2020 01:47:14 GMT):
hi， @odowdaibm @rjones ，please add @guoger (github-ID:guoger) and @davidkhala (github-ID:davidkhala) into github team fabric-zh_cn-doc-maintainers, they will review and approve my PRs in fabric-docs-i18n repo.
davidkhala (Wed, 08 Jul 2020 01:47:14 GMT):
Has joined the channel.
BrettLogan (Wed, 08 Jul 2020 01:51:03 GMT):
Jay can already approve, he is a fabric maintainer
BrettLogan (Wed, 08 Jul 2020 01:51:28 GMT):
He can approve across the entire repo
BrettLogan (Wed, 08 Jul 2020 01:51:47 GMT):
We will get David added as well
stone-ch (Wed, 08 Jul 2020 01:54:55 GMT):
Got it, thanks
guoger (Wed, 08 Jul 2020 07:16:50 GMT):
thx Brett!
odowdaibm (Wed, 08 Jul 2020 13:27:46 GMT):
can see added now - thx Brett
nekia (Thu, 09 Jul 2020 05:56:55 GMT):
Has joined the channel.
davidkhala (Thu, 09 Jul 2020 11:01:23 GMT):
@stone-ch 程阳，JP文档这个提交说找不到文件https://dev.azure.com/Hyperledger/Fabric-Docs-i18n/_build/results?buildId=17304&view=logs&j=52a9fd78-3a7e-575d-2495-eb4777527924&t=d3968e5e-308f-5108-7ad9-b3b878c2d055&l=14
我猜测这些文件是不是以前trasifix自动生成的那些？或者是transifix配置文件？
davidkhala (Thu, 09 Jul 2020 11:02:02 GMT):
他们能删么？
siburu (Thu, 09 Jul 2020 11:03:49 GMT):
Has joined the channel.
davidkhala (Thu, 09 Jul 2020 11:05:32 GMT):
我学习了下，发现tox是巴西语言那边用的一个工具，在构建的时候用的
这样我们应该隔离出来免得影响别的语言
aneenaalex (Thu, 09 Jul 2020 11:21:28 GMT):
@odowdaibm Thought of making a PR once everything is finished.I can do a test PR Now.
stone-ch (Fri, 10 Jul 2020 01:02:17 GMT):
我不太确定，我先试一下
odowdaibm (Fri, 10 Jul 2020 09:41:13 GMT):
Please do Aneena -- given the Study Circle tomorrow, let's catch up on Monday to get this done
knibals (Fri, 17 Jul 2020 16:28:31 GMT):
Has joined the channel.
knibals (Fri, 17 Jul 2020 16:28:31 GMT):
@odowdaibm :wave:
knibals (Fri, 17 Jul 2020 16:28:55 GMT):
Hi @renatost
rjones (Fri, 17 Jul 2020 16:50:58 GMT):
howdy @knibals
pandrejko (Fri, 17 Jul 2020 17:36:38 GMT):
@knibals Just want to make sure you've seen Anthony's getting started documentation here: https://hyperledger-fabric.readthedocs.io/en/latest/CONTRIBUTING.html#contributing-documentation Just click the links under there and he walks you through the whole process.
knibals (Mon, 20 Jul 2020 10:16:37 GMT):
@pandrejko Thank you for the link. I've created the Wiki page for the French translation ;)
pandrejko (Mon, 20 Jul 2020 11:29:19 GMT):
That's fantastic Oumar!
rjones (Mon, 20 Jul 2020 18:53:57 GMT):
This is amazing - @pandrejko , @odowdaibm - you two are doing an amazing job here
pandrejko (Mon, 20 Jul 2020 18:56:13 GMT):
All kudos go to @odowdaibm . I'm just the messenger!
aneenaalex (Tue, 21 Jul 2020 04:11:31 GMT):
Fantastic @pandrejko @odowdaibm :slight_smile:
EpaKadiongo (Wed, 22 Jul 2020 13:48:45 GMT):
Has joined the channel.
EpaKadiongo (Wed, 22 Jul 2020 13:48:46 GMT):
congratgs!
EpaKadiongo (Wed, 22 Jul 2020 13:49:01 GMT):
can you send the link?
pandrejko (Wed, 22 Jul 2020 13:50:54 GMT):
@EpaKadiongo Is this the link you are looking for? https://wiki.hyperledger.org/display/fabric/French+documentation+Working+Group
EpaKadiongo (Wed, 22 Jul 2020 13:58:22 GMT):
je voudrais aussi participer a la traduction :slight_smile:
pandrejko (Wed, 22 Jul 2020 16:42:08 GMT):
c'est tres bien!
rjones (Fri, 24 Jul 2020 17:45:58 GMT):
@odowdaibm @pandrejko what will the new Spanish code page be? https://wiki.hyperledger.org/display/fabric/Spanish+Working+Group there are a lot of es_ pages
odowdaibm (Thu, 30 Jul 2020 16:03:03 GMT):
One option is to start with es_ES as Maria is from Spain. I hope that won't offend our Latin American friends. We could always just have es, and not specify country -- the language codes do allow this.
odowdaibm (Thu, 30 Jul 2020 16:03:38 GMT):
I think we should start with es_ES, and to all my Spanish-speaking friends reading this, I hope that's OK -- please say if it's not
rjones (Thu, 30 Jul 2020 16:06:57 GMT):
We can start with es_(nothing) - I was trying to align directories with code pages so the RTD magic would work, but I don't have much opinion on it
rjones (Thu, 30 Jul 2020 16:07:14 GMT):
I saw ru_RU already started
odowdaibm (Thu, 30 Jul 2020 16:07:18 GMT):
I'd prefer to start with es_ES
odowdaibm (Thu, 30 Jul 2020 16:07:20 GMT):
exactly
odowdaibm (Thu, 30 Jul 2020 16:08:01 GMT):
we can always change it later, but keeping it aligned with other 4-codes right now will keep other processes simplier
rjones (Thu, 30 Jul 2020 16:08:40 GMT):
OK. They can create the subdirectory when they like.
rjones (Thu, 30 Jul 2020 16:08:48 GMT):
they, you, whomever :)
odowdaibm (Thu, 30 Jul 2020 16:08:54 GMT):
thx
odowdaibm (Thu, 30 Jul 2020 16:09:08 GMT):
btw, how is CI/CD for public doc builds looking?
odowdaibm (Thu, 30 Jul 2020 16:09:26 GMT):
(not being pushy, just intrested)
odowdaibm (Thu, 30 Jul 2020 16:09:44 GMT):
I think we're getting close with ja_JP and ml_IN and pt_BR
rjones (Thu, 30 Jul 2020 16:12:09 GMT):
dunno, I'm not involved with that - @BrettLogan ?
odowdaibm (Fri, 31 Jul 2020 11:27:36 GMT):
Hello Brett @BrettLogan It would be good to get your thoughts on when we mght be able to try out a public RTD test build for one of our new i18n language directotries. Say Renato's @renatost pr_BR translation?
renatost (Wed, 05 Aug 2020 17:15:18 GMT):
Hi @BrettLogan could we try to make i18n build works? I looking forward to have our work public.
claudiocebpaz (Fri, 07 Aug 2020 14:09:32 GMT):
Has joined the channel.
claudiocebpaz (Fri, 07 Aug 2020 14:09:33 GMT):
Hello, This is Claudio from the LatinAmerican Chapter. We are working on the Spanish Translation.
renatost (Fri, 07 Aug 2020 14:54:53 GMT):
Welcome @claudiocebpaz , I'm glad to see you here and as you know we are ready to help you in everything you need!
davidwboswell (Fri, 07 Aug 2020 15:02:48 GMT):
thanks to @renatost for providing a translation for the Hyperledger home page. we now have a pt_BR home page at: https://pt-br.hyperledger.org/
davidwboswell (Fri, 07 Aug 2020 15:03:23 GMT):
if anyone is interested in providing translations for other languages, please feel free to fill out the form at: https://docs.google.com/forms/d/1KqD_qYH42HqYm_mZQok3bdfS-Dv7g48TYIVBXZqlCLs/edit
pandrejko (Fri, 07 Aug 2020 16:37:54 GMT):
@renatost I approved the spaish translation PR but it looks like there are merge conflict that need to be resolved before it can be merged.
rjones (Fri, 07 Aug 2020 16:59:18 GMT):
@pandrejko which PR?
pandrejko (Fri, 07 Aug 2020 17:00:13 GMT):
https://github.com/hyperledger/fabric-docs-i18n/pull/65
rjones (Fri, 07 Aug 2020 17:06:55 GMT):
working on it
rjones (Fri, 07 Aug 2020 17:14:18 GMT):
https://github.com/hyperledger/fabric-docs-i18n/pull/73
rjones (Fri, 07 Aug 2020 17:14:29 GMT):
I can't edit 65
claudiocebpaz (Fri, 07 Aug 2020 17:17:20 GMT):
@pandrejko how should we address those conflicts?
When I did my fork from the master branch of the repo those issues where there.
Do you want me to fork again?
rjones (Fri, 07 Aug 2020 17:18:36 GMT):
@claudiocebpaz take a look at PR73
claudiocebpaz (Fri, 07 Aug 2020 17:18:38 GMT):
I mean... there were 18 commits in that fork.
claudiocebpaz (Fri, 07 Aug 2020 17:18:44 GMT):
ok
rjones (Fri, 07 Aug 2020 17:19:04 GMT):
@claudiocebpaz This is the PR
claudiocebpaz (Fri, 07 Aug 2020 17:21:40 GMT):
Ok. Sure.
Do you need me to perform any action in that PR? @rjones
rjones (Fri, 07 Aug 2020 17:22:20 GMT):
no. In the future, when you make a PR, please enable "maintainers can edit"
claudiocebpaz (Fri, 07 Aug 2020 17:22:56 GMT):
Ok. Sure. I didn't check for that.
Will do. Thanks.
rjones (Fri, 07 Aug 2020 17:23:13 GMT):
thank you!
rjones (Fri, 07 Aug 2020 17:24:22 GMT):
https://youtu.be/cyl2VwGsWFA https://youtu.be/2Ab_J1ELC3c
claudiocebpaz (Fri, 07 Aug 2020 17:31:19 GMT):
Thanks, @rjones for the videos. I Will join next meeting.
pandrejko (Fri, 07 Aug 2020 17:31:55 GMT):
@rjones Can I approve and merge his pr #73 then now?
rjones (Fri, 07 Aug 2020 17:32:03 GMT):
yes
claudiocebpaz (Fri, 07 Aug 2020 17:33:33 GMT):
Just a quick question. What was the conflict? On the PR 63?
claudiocebpaz (Fri, 07 Aug 2020 17:33:33 GMT):
@pandrejko one question: what is the group policy about docker files?
I have dockerized the documentation build process.
Should I push that in a branch?
rjones (Fri, 07 Aug 2020 17:33:58 GMT):
there were too many to fix
claudiocebpaz (Fri, 07 Aug 2020 17:34:33 GMT):
sure... there were 18 commits. Too much in my opinion.
rjones (Fri, 07 Aug 2020 17:34:36 GMT):
there were several conflicts on CODEOWNERS, and a couple additions and deletions in other branches
rjones (Fri, 07 Aug 2020 17:35:06 GMT):
yes, I usually do a `git rebase -i HEAD~(whatever)` and squash to one commit before I do a PR
claudiocebpaz (Fri, 07 Aug 2020 17:35:28 GMT):
Ok. Thanks. I'll do that before next PR
rjones (Fri, 07 Aug 2020 17:36:34 GMT):
you can also just commit your changes in one subdirectory
rjones (Fri, 07 Aug 2020 17:37:01 GMT):
basically, `git fetch origin (branch name)` `git rebase -i FETCH_HEAD`
rjones (Fri, 07 Aug 2020 17:37:05 GMT):
something like that
claudiocebpaz (Fri, 07 Aug 2020 17:37:37 GMT):
Ok. If you think that should be best. I usually commit from the root of the project on.
claudiocebpaz (Fri, 07 Aug 2020 17:37:49 GMT):
But I can do that.
claudiocebpaz (Fri, 07 Aug 2020 17:37:58 GMT):
:thumbsup:
rjones (Fri, 07 Aug 2020 17:38:05 GMT):
well, whatever your changes are should be applied to the head of the branch you want to commit to
rjones (Fri, 07 Aug 2020 17:38:27 GMT):
if you have changes to /CODEOWNERS that's OK, but I see there has been a lot of needless editing of that file
claudiocebpaz (Fri, 07 Aug 2020 17:39:51 GMT):
That is weird. I only added one line to that file.
rjones (Fri, 07 Aug 2020 17:40:03 GMT):
yes, but others have edited it as well.
rjones (Fri, 07 Aug 2020 17:40:11 GMT):
(me) :)
claudiocebpaz (Fri, 07 Aug 2020 17:40:21 GMT):
hahaha... ok.
claudiocebpaz (Fri, 07 Aug 2020 17:41:00 GMT):
First commit to this repo. Will get better for sure. Thanks!
camohe90 (Fri, 07 Aug 2020 21:09:53 GMT):
Has joined the channel.
claudiocebpaz (Tue, 11 Aug 2020 15:24:57 GMT):
one question: what is the group policy about docker files?
I have dockerized the documentation build process.
Should I push that in a branch?
@pandrejko
pandrejko (Tue, 11 Aug 2020 15:34:22 GMT):
Seems like that could be useful to other translators and doc writers. Would you be able to join our documentation workgroup call on Friday at 11am EST to show it?
But to answer your question, I would want Ry and Brett to be OK with this before we merge it.
claudiocebpaz (Tue, 11 Aug 2020 15:34:54 GMT):
Sure. Totally.
claudiocebpaz (Tue, 11 Aug 2020 15:35:13 GMT):
I'll join on Friday.
pandrejko (Tue, 11 Aug 2020 15:36:00 GMT):
https://zoom.us/j/6223336701
That's great. I'll add you to the agenda
Agenda: https://wiki.hyperledger.org/display/fabric/Documentation+Working+Group
pandrejko (Tue, 11 Aug 2020 15:37:47 GMT):
Feel free to make a PR so others can review it
claudiocebpaz (Tue, 11 Aug 2020 15:39:18 GMT):
Ok. I will.
rjones (Tue, 11 Aug 2020 16:32:09 GMT):
Does it work with GitHub actions?
rjones (Tue, 11 Aug 2020 16:32:33 GMT):
@BrettLogan
claudiocebpaz (Tue, 11 Aug 2020 17:51:47 GMT):
I havent used with github actions. Only for local build.
Let me try and let you know.
claudiocebpaz (Tue, 11 Aug 2020 17:51:47 GMT):
I havent used it with github actions. Only for local build.
Let me try and let you know.
claudiocebpaz (Tue, 11 Aug 2020 17:51:47 GMT):
I haven't used it with GitHub's actions. Only for the local build.
Let me try and let you know.
rjones (Tue, 11 Aug 2020 18:20:12 GMT):
OK. It might be better to use AZP - Brett?
BrettLogan (Tue, 11 Aug 2020 20:36:53 GMT):
I'd be interested to see this, we are redoing the doc build process in fabric, which includes images for building the doc. They are hosted already at `hyperledger-fabric.jfrog.io/fabric-tox`
rjones (Tue, 11 Aug 2020 20:38:07 GMT):
nice
pandrejko (Fri, 14 Aug 2020 12:01:22 GMT):
@BrettLogan @rjones Do either of you know what needs to happen for the CI/CD pipeline for the pt-BR docs?
rjones (Fri, 14 Aug 2020 16:33:54 GMT):
I need to defer to Brett on this - I'm not sure what Fabric wants to do overall
rjones (Fri, 14 Aug 2020 17:11:10 GMT):
I got this working for zh_CN: https://hyperledger-fabric.readthedocs.io/zh_CN/release-2.2/
rjones (Fri, 14 Aug 2020 17:33:15 GMT):
OK. I have spent several hours on this last night and today, and I understand the problem better, so I am working to fix it.
rjones (Fri, 14 Aug 2020 18:25:01 GMT):
@pandrejko hey look at this: https://hyperledger-fabric.readthedocs.io/en/release-2.2/
rjones (Fri, 14 Aug 2020 18:25:50 GMT):
at the bottom, select language `pt`
pandrejko (Fri, 14 Aug 2020 18:42:04 GMT):
Thank you @rjones You are a magician! What is the process to get the es content integrated?
pandrejko (Fri, 14 Aug 2020 18:42:18 GMT):
@renatost It looks like you content is visible now
pandrejko (Fri, 14 Aug 2020 18:42:18 GMT):
@renatost It looks like your content is visible now
rjones (Fri, 14 Aug 2020 18:42:39 GMT):
@pandrejko I'm working on it right now :)
rjones (Fri, 14 Aug 2020 18:42:54 GMT):
I have all of the 2.2 languages in the queue, but RTD is having problems
pandrejko (Fri, 14 Aug 2020 18:42:59 GMT):
@claudiocebpaz ^^ . Thank you Ry.
rjones (Fri, 14 Aug 2020 18:43:28 GMT):
sure thing. There are some rough edges - but it's mostly working
rjones (Fri, 14 Aug 2020 18:44:25 GMT):
in-progress.png
rjones (Fri, 14 Aug 2020 18:47:10 GMT):
I understand the larger issue, though. It's a Zerg rush to build every language, when only one has a change.
rjones (Fri, 14 Aug 2020 18:47:52 GMT):
the solution is to migrate from RTD, but that will be longer term
rjones (Fri, 14 Aug 2020 18:48:34 GMT):
something like fabric.hyperledger.org/docs should point to something we control, that isn't RTD.
rjones (Fri, 14 Aug 2020 19:32:40 GMT):
https://hyperledger-fabric.readthedocs.io/pt/latest/key_concepts.html
rjones (Fri, 14 Aug 2020 19:32:51 GMT):
https://hyperledger-fabric.readthedocs.io/ru/release-2.2/whatis.html
rjones (Fri, 14 Aug 2020 19:33:02 GMT):
https://hyperledger-fabric.readthedocs.io/ja/release-2.2/glossary.html
rjones (Fri, 14 Aug 2020 19:33:13 GMT):
https://hyperledger-fabric.readthedocs.io/ml/latest/
stone-ch (Mon, 17 Aug 2020 03:19:13 GMT):
Great job @rjones , the release-2.2 docs looks good now, can you add the release-1.4 tanslations, we cann't find the release-1.4 Chinese translations now.
rjones (Mon, 17 Aug 2020 07:56:09 GMT):
https://hyperledger-fabric.readthedocs.io/zh_CN/release-1.4/
stone-ch (Mon, 17 Aug 2020 08:50:35 GMT):
:ok_hand:
pandrejko (Mon, 17 Aug 2020 12:32:58 GMT):
@rjones I see the link for the es content now in the Fabric documentation, but it looks like there is no content behind it. Is there something else @claudiocebpaz needs to do so that the es content is visible?
rjones (Mon, 17 Aug 2020 12:44:21 GMT):
Yes. There aren’t a lot of pages translated
claudiocebpaz (Mon, 17 Aug 2020 15:36:32 GMT):
We havent push any translation yet. We have created the translation branch.
And we we'll be transtating the first pages this week.
claudiocebpaz (Mon, 17 Aug 2020 15:43:16 GMT):
One thing is weird. I took the Portuguese branch and copied that.
So It should show as Portuguese at the least.
rjones (Mon, 17 Aug 2020 16:13:52 GMT):
I'm not going to spend any time debugging anything until you have content to display, if that's ok with you? I spent a lot of time on this already and I'm not supposed to spend really, any time
stone-ch (Tue, 18 Aug 2020 00:47:50 GMT):
@claudiocebpaz you can put the english content in the translation branch first, then replace them with translations.
claudiocebpaz (Tue, 18 Aug 2020 01:04:08 GMT):
Thanks. That is what we have now.
But I'll double check tomorrow for sure.
claudiocebpaz (Wed, 19 Aug 2020 00:19:14 GMT):
https://github.com/hyperledger/fabric-docs-i18n/pull/83
@pandrejko I created a pull request for the dockerized process we talked about in the last meeting.
I'll do the same for the global (US) docs.
pandrejko (Wed, 19 Aug 2020 00:20:33 GMT):
That's great. I know @BrettLogan will want to see this.
claudiocebpaz (Fri, 21 Aug 2020 19:51:13 GMT):
Hello, I have a pull request that has been approved
https://github.com/hyperledger/fabric-docs-i18n/pull/95
I have permission to merge. Should I do that? Or wait for another review?
Thanks!
rjones (Fri, 21 Aug 2020 20:35:21 GMT):
@claudiocebpaz I added the doc-merge label and it was merged - you should feel free to merge your own approved PRs
claudiocebpaz (Fri, 21 Aug 2020 20:35:22 GMT):
Thanks, @rjones
claudiocebpaz (Fri, 21 Aug 2020 20:35:40 GMT):
Ill add that label next time
rjones (Fri, 21 Aug 2020 20:35:47 GMT):
I like letting the mergify bot do it
claudiocebpaz (Fri, 21 Aug 2020 20:35:57 GMT):
totally agree
claudiocebpaz (Fri, 21 Aug 2020 20:36:07 GMT):
Didn't know about this label.
claudiocebpaz (Fri, 21 Aug 2020 20:36:22 GMT):
:thumbsup:
rjones (Fri, 21 Aug 2020 20:36:25 GMT):
I knew it existed, but I didn't know if it was enabled for this repo
davidkhala (Sun, 23 Aug 2020 14:10:04 GMT):
(come from a wrong channel) @rjones Hi Ry, for repos `fabric-docs-i18n` could it be configured to allow reviewer to squash commits before merge?
rjones (Sun, 23 Aug 2020 14:16:15 GMT):
Change the .github/settings.yaml
pandrejko (Wed, 26 Aug 2020 12:57:53 GMT):
@odowdaibm Anthony - If you speak to the translators on Friday it is probably worth mentioning about the doc-merge label that can be used by the doc translator maintainers to merge their own PRs. We should probably add that as well to our contributing guide.
pandrejko (Thu, 27 Aug 2020 19:02:59 GMT):
fabric-samples
stone-ch (Mon, 31 Aug 2020 02:47:17 GMT):
@rjones It has merged some Chinese translations, but RTD is not updated. It seems that the webhook is not triggered.
rjones (Mon, 31 Aug 2020 03:01:04 GMT):
which branch? there might only be one published
stone-ch (Mon, 31 Aug 2020 03:05:28 GMT):
release-2.2
rjones (Mon, 31 Aug 2020 03:26:31 GMT):
I just rebuilt it - https://readthedocs.org/projects/fabric-documentation-chinese-translation/builds/11774543/ - try now?
stone-ch (Mon, 31 Aug 2020 04:08:58 GMT):
RTD is updated now.
rjones (Mon, 31 Aug 2020 16:18:20 GMT):
I don't know why it failed to build, but the RTD status page showed it was failing
stone-ch (Mon, 31 Aug 2020 16:29:58 GMT):
release-2.2 Chinese translation build passed last time. Do you mean RTD cannot auto build?
rjones (Mon, 31 Aug 2020 17:23:33 GMT):
rtd.png
rjones (Mon, 31 Aug 2020 17:25:28 GMT):
all I did was manually click the "build" button for 2.2 and it worked. I don't know what, if anything, changed
stone-ch (Mon, 31 Aug 2020 17:28:55 GMT):
yes i can also see the builds page, it fails sometimes because there are more than one build running at the same time, sometimes maybe there somethings wrong in the project
rjones (Mon, 31 Aug 2020 17:29:40 GMT):
I don't know. I know @BrettLogan is working to get us away from the RTD platform and it can't happen fast enough for me
rjones (Mon, 31 Aug 2020 17:31:34 GMT):
what is your rtd username?
rjones (Mon, 31 Aug 2020 17:31:38 GMT):
stone-ch ?
stone-ch (Mon, 31 Aug 2020 17:31:51 GMT):
yes
rjones (Mon, 31 Aug 2020 17:32:18 GMT):
OK, you're now a maintainer :)
stone-ch (Mon, 31 Aug 2020 17:34:19 GMT):
the problem i met is auto compile when i update the translations in github, i don't think it is necessary to change a display platform.
stone-ch (Mon, 31 Aug 2020 17:34:30 GMT):
ok
rjones (Mon, 31 Aug 2020 17:34:54 GMT):
the issue is RTD is moving away from python 2.7, and the work to re-implement everything for Fabric is a lot.
rjones (Mon, 31 Aug 2020 17:35:15 GMT):
as I understand it
stone-ch (Mon, 31 Aug 2020 17:39:36 GMT):
https://github.com/hyperledger/fabric-docs-i18n/pull/88 do you mean the content talked about in this issue?
rjones (Mon, 31 Aug 2020 17:40:44 GMT):
I guess that's part of it? I'm not totally up-to-speed
stone-ch (Mon, 31 Aug 2020 17:43:45 GMT):
ok, I am not notice that before, I will learn more about that.
claudiocebpaz (Mon, 31 Aug 2020 18:38:36 GMT):
I wrote that PR. Let me know If I can help you.
Regards.
BrettLogan (Fri, 04 Sep 2020 17:56:48 GMT):
This PR will fix all the failing doc builds: https://github.com/hyperledger/fabric-docs-i18n/pull/136
BrettLogan (Fri, 04 Sep 2020 17:57:23 GMT):
You'll also notice I enabled Doc Builds for Read The Docs on PR's, so your PR's will be built by RTD as well so you'll find out if they can be built before the code is actually merged
claudiocebpaz (Mon, 07 Sep 2020 19:33:00 GMT):
Hello, @everybody. Is there a bot to copy a file to the i18n repo anytime a new file is added to the doc folder in the main repository?
This is an example: https://github.com/hyperledger/fabric/blob/master/docs/source/secured_asset_transfer/secured_private_asset_transfer_tutorial.md
That file exists in the doc file in the primary repo, but not in the i18n repo.
It was probably added after we copied the folder into i18n.
rjones (Mon, 07 Sep 2020 19:49:01 GMT):
there is no bot.
claudiocebpaz (Mon, 07 Sep 2020 19:49:24 GMT):
Ok. Thanks. We'll do a manual review every now and then. Thanks!
BrettLogan (Mon, 07 Sep 2020 20:01:31 GMT):
We could set up a nightly job to diff the trees of fabric and all of the translations and report and missing docs so teams could look at it
claudiocebpaz (Mon, 07 Sep 2020 20:14:25 GMT):
That would be very helpful. Thanks, @BrettLogan
ravinayag (Sun, 13 Sep 2020 15:35:07 GMT):
Has joined the channel.
ravinayag (Sun, 13 Sep 2020 18:12:57 GMT):
Hi, I raised PR #181 for new lang translation, Pls do review, Tq
claudiocebpaz (Mon, 14 Sep 2020 20:29:54 GMT):
Hello, @rjones and @BrettLogan.
Last friday I was on the documentation workgroup, and I presented a problem. We'll need to have another "group" in the i-18n repo.
This is the scenario to solve:
We are managing the collaborators' efforts in the Github repo using issues, milestones, and project.
But we cannot assign an issue to any user that isn't part of any GitHub group in the repo.
Also, as maintainers, we'll like to have control over revision that these collaborators do. So we have a second verification before the pr is merged.
Right now, we only have one group for maintainers.
So, a big "i18n-collaborator" group for all translation seems the easiest way to go.
We as maintainers could manage to add and delete members, so it's easier on other maintainers.
Makes Sense?
claudiocebpaz (Mon, 14 Sep 2020 20:29:54 GMT):
Hello, @rjones and @BrettLogan .
Last friday I was on the documentation workgroup, and I presented a problem. We'll need to have another "group" in the i-18n repo.
This is the scenario to solve:
We are managing the collaborators' efforts in the Github repo using issues, milestones, and project.
But we cannot assign an issue to any user that isn't part of any GitHub group in the repo.
Also, as maintainers, we'll like to have control over revision that these collaborators do. So we have a second verification before the pr is merged.
Right now, we only have one group for maintainers.
So, a big "i18n-collaborator" group for all translation seems the easiest way to go.
We as maintainers could manage to add and delete members, so it's easier on other maintainers.
Makes Sense?
BrettLogan (Mon, 14 Sep 2020 20:33:28 GMT):
I think your issue is that they aren't part of the "Hyperledger" org. All maintainers have actually been assigned the maintainers role, which allows them to assign issues to people. But in order for people to be assigned issues, they first need to a part of the Hyperledger org on GitHub
claudiocebpaz (Mon, 14 Sep 2020 20:34:01 GMT):
yes, exactly.
BrettLogan (Mon, 14 Sep 2020 20:34:25 GMT):
So they should go to `github.com/hyperledger` and click the `Request to Join` button
BrettLogan (Mon, 14 Sep 2020 20:34:41 GMT):
You wouldn't be able to add them to a team anyway until they've gone through this process
BrettLogan (Mon, 14 Sep 2020 20:35:13 GMT):
And then Ry will get notified and accept them. We've discussed in the past coming up with some automation to handle adding new contributors, but we've never implemented it
claudiocebpaz (Mon, 14 Sep 2020 20:36:06 GMT):
Ok. I could ask them to do so, no problem.
What about having another group? I mean so they can request a pr, but not approve a pr?
BrettLogan (Mon, 14 Sep 2020 20:37:16 GMT):
I'm not sure I understand what you mean by "can request a pr," sorry?
BrettLogan (Mon, 14 Sep 2020 20:37:54 GMT):
You mean assign themselves to an issue?
claudiocebpaz (Mon, 14 Sep 2020 20:39:16 GMT):
I mean approve a request on the repo send by another contributor.
claudiocebpaz (Mon, 14 Sep 2020 20:39:22 GMT):
But I think there is another way
claudiocebpaz (Mon, 14 Sep 2020 20:39:38 GMT):
https://github.com/orgs/hyperledger/teams/fabric-contributors
claudiocebpaz (Mon, 14 Sep 2020 20:39:46 GMT):
we can add them to this group
claudiocebpaz (Mon, 14 Sep 2020 20:40:04 GMT):
so the maintainers can assign to them an issue.
claudiocebpaz (Mon, 14 Sep 2020 20:41:17 GMT):
Ok. we have ten extra contributors that want to help in the translation effort.
I'll ask them to join the Hyperledger team in Github.
BrettLogan (Mon, 14 Sep 2020 20:42:57 GMT):
Yea, that was the one I meant to point you too, apologies
claudiocebpaz (Mon, 14 Sep 2020 20:43:35 GMT):
Thanks, @BrettLogan
I was trying to avoid you or Ry to have to manage this scenario.
rjones (Mon, 14 Sep 2020 22:46:37 GMT):
@claudiocebpaz please send me email with the github IDs thanks
rjones (Mon, 14 Sep 2020 22:47:02 GMT):
@claudiocebpaz we have a group for each language
claudiocebpaz (Mon, 14 Sep 2020 22:47:09 GMT):
Ok. Will do. Thanks.
rjones (Mon, 14 Sep 2020 22:47:24 GMT):
which language is this for?
claudiocebpaz (Mon, 14 Sep 2020 22:47:29 GMT):
Spanish
claudiocebpaz (Mon, 14 Sep 2020 22:48:07 GMT):
The main idea is to separate moderators from collaborators. So before a PR is merge, moderators needs to approve the PR.
claudiocebpaz (Mon, 14 Sep 2020 22:48:07 GMT):
The main idea is to separate moderators from collaborators. So before a PR is merged, a moderator needs to approve the PR.
claudiocebpaz (Mon, 14 Sep 2020 22:48:27 GMT):
To have another manual review before the PR is merged.
rjones (Mon, 14 Sep 2020 22:48:58 GMT):
have them add themselves here: https://wiki.hyperledger.org/display/fabric/Spanish+Working+Group
claudiocebpaz (Mon, 14 Sep 2020 22:49:08 GMT):
Ok.
rjones (Mon, 14 Sep 2020 22:49:43 GMT):
Each PR requires a code review, so it should not be a problem
rjones (Mon, 14 Sep 2020 22:50:07 GMT):
since there is already a group for `-es` - I'd rather not have 500 groups and fine-grained ACLs
rjones (Mon, 14 Sep 2020 22:50:56 GMT):
This is the group: https://github.com/orgs/hyperledger/teams/fabric-es-doc-maintainers/members
claudiocebpaz (Mon, 14 Sep 2020 23:00:19 GMT):
Agree.
I understand that each PR requires a code review. I would like to have another level of approval hierarchy.
The same way I can't approve a PR on the root directory, I would like an es-maintainer to review what a contributor is doing on the "es" directory.
claudiocebpaz (Mon, 14 Sep 2020 23:00:35 GMT):
I think we can make it work this way. Thanks!
claudiocebpaz (Mon, 14 Sep 2020 23:00:35 GMT):
I think we can make it work this way too. Thanks!
davidwboswell (Tue, 15 Sep 2020 14:48:54 GMT):
thanks to @claudiocebpaz for sending me a tweet in spanish about the spanish fabric docs. https://twitter.com/Hyperledger/status/1305880948253192192
davidwboswell (Tue, 15 Sep 2020 14:50:00 GMT):
as other languages go live with their docs, please feel free to send me tweets in that language and i can post that as well on our twitter account. helping people find the translated documentation is something i'm happy to help with.
rjones (Thu, 17 Sep 2020 15:27:57 GMT):
Hi, if you have anything you'd like to see added to the /dev/weekly newsletter, please comment in the next two hours: https://wiki.hyperledger.org/pages/viewpage.action?pageId=39618911
ravinayag (Fri, 16 Oct 2020 06:15:14 GMT):
Hi
rjones (Fri, 16 Oct 2020 06:33:38 GMT):
Howdy!
ravinayag (Fri, 16 Oct 2020 06:36:08 GMT):
just want to check, is anyone from eastern hemisphere joined the call today.. and was there any changes in zoom link ?
rjones (Fri, 16 Oct 2020 16:26:39 GMT):
@ravinayag here is the current meeting invite: https://lists.hyperledger.org/g/fabric/viewevent?repeatid=22053&eventid=879232&calstart=2020-10-16
lnuon (Tue, 08 Dec 2020 23:51:49 GMT):
Has joined the channel.
lnuon (Tue, 08 Dec 2020 23:51:49 GMT):
Hello everyone! The DCI Working Group will be having our last meeting of the year this Friday and we'd really love to see you all there. We'll be discussing/finalizing 2021 plans so it's a great time to get plugged in. https://wiki.hyperledger.org/display/DCI/Diversity%2C+Civility%2C+and+Inclusion+WG+Home
davidwboswell (Fri, 11 Dec 2020 19:04:56 GMT):
Thanks to everyone's hard work over this past year to translate the Fabric documentation in eight different languages. We’d like to showcase the work you've done as well as invite new people to join your translation groups and encourage translations of additional languages. To do that, we could use your help creating a video about the translation community.
Could you please identify someone in your group who would be interested in appearing in a video we are putting together? This person would speak in your native language about the translation work you've done. Could you please also identify someone in your group who would be willing to coordinate with our video production team in English about this project?
When you've picked the people from your translation group for those roles, please send that information to Pam Andrejko (pama@ibm.com). Once we have these names from you we'll follow up with more details.
davidwboswell (Thu, 17 Dec 2020 16:11:49 GMT):
Hyperledger published an annual report today and it has a section called 'Hyperledger in Multiple Languages' that provides a nice summary of everything that the group in #i18n and that the translation groups have done this to provide information to people about Hyperledger in a range of different languages. I thought people here would be interested in checking that out at: https://www.hyperledger.org/learn/publications/hyperledger-annual-report-2020
stone-ch (Tue, 29 Dec 2020 09:55:33 GMT):
Hello david, in 2020 TWGC has hosted 28 online webinars on zoom, and 1 meetup in Chengdu, we have uploaded all the webinars videos to Tencent video https://v.qq.com/s/videoplus/1300396971#uin=6a662f75e9a927ede370ba49c9e883e0. But it seems that the meetups are not counted.
stone-ch (Tue, 29 Dec 2020 09:55:33 GMT):
Hello @davidwboswell , in 2020 TWGC has hosted 28 online webinars on zoom, and 1 meetup in Chengdu, we have uploaded all the webinars videos to Tencent video https://v.qq.com/s/videoplus/1300396971#uin=6a662f75e9a927ede370ba49c9e883e0. But it seems that the meetups are not counted.
stone-ch (Tue, 29 Dec 2020 09:59:23 GMT):
Clipboard - 2020年12月29日下午5点59分
stone-ch (Tue, 29 Dec 2020 10:00:05 GMT):
Clipboard - 2020年12月29日晚上6点00分
stone-ch (Tue, 29 Dec 2020 10:01:23 GMT):
Clipboard - 2020年12月29日晚上6点01分
stone-ch (Tue, 29 Dec 2020 10:02:10 GMT):
Clipboard - 2020年12月29日晚上6点02分
davidkhala (Tue, 29 Dec 2020 10:02:48 GMT):
@stone-ch It seems this reply to a wrong thread. Is it?
stone-ch (Tue, 29 Dec 2020 10:06:35 GMT):
Hello @davidwboswell , in 2020 TWGC has hosted 28 online webinars on zoom, and 1 meetup in Chengdu, we have uploaded all the webinars videos to Tencent video https://v.qq.com/s/videoplus/1300396971#uin=6a662f75e9a927ede370ba49c9e883e0. But it seems that the meetups are not counted in the "Hyperledger Annual Report 2020".
stone-ch (Tue, 29 Dec 2020 10:09:59 GMT):
I resend the message in the channel
rjones (Tue, 29 Dec 2020 17:15:29 GMT):
@DavidBoswell
DavidBoswell (Tue, 29 Dec 2020 17:15:30 GMT):
Has joined the channel.
davidwboswell (Mon, 04 Jan 2021 16:02:14 GMT):
@stone-ch thank you for sharing about the meetups and webinars that TWGC hosted last year. it would be great for us to help share out what is happening there and include them more in our reports, website and social media. i don't have a lot of visibility into what is going on and i think that is also true with jess who put that report together. would it be possible for the TWGC to share regular updates so we'll have this information. or we can look at including details where we are tracking other webinar and meetup activities (i'll add some links below). i'll be happy to work with you to figure out the best way to coordinate around the TWGC's activities.
davidwboswell (Mon, 04 Jan 2021 16:02:41 GMT):
i'm tracking all virtual meetups at this wiki page, although it doesn't include any of the activities in China: https://wiki.hyperledger.org/display/events/Virtual+Hyperledger+Meetups
davidwboswell (Mon, 04 Jan 2021 16:02:59 GMT):
we also have a webinars page on the hyperledger site and could add videos there too: https://www.hyperledger.org/learn/webinars
davidwboswell (Mon, 04 Jan 2021 16:04:34 GMT):
@stone-ch i apologize for the delay in responding to your message. i was off over the holidays but am back now and am happy to talk with you more about this.
stone-ch (Tue, 05 Jan 2021 02:08:28 GMT):
Thanks @davidwboswell , we will add the meetups and webinars in the website this year.
davidwboswell (Tue, 05 Jan 2021 15:23:40 GMT):
@stone-ch -- that's great. and i'll be happy to help you promote those meetups as well if you'd like. if you send me information before the events, we can post about them on hyperledger's twitter and linkedin accounts.
rjones (Tue, 05 Jan 2021 16:01:40 GMT):
could you show me the PR that was merged, and where you expected it to be published?
davidkhala (Wed, 06 Jan 2021 04:28:37 GMT):
What is it?
stone-ch (Wed, 06 Jan 2021 06:46:11 GMT):
[ ](https://chat.hyperledger.org/channel/i18n?msg=K978cptvLXs6Mp2rx) Yes, I'd like to, we will make more connection with the international community in 2021.
rjones (Wed, 06 Jan 2021 16:46:12 GMT):
someone deleted a message asking why the Chinese language wasn't updating
knibals (Fri, 05 Feb 2021 15:19:50 GMT):
Hello, This is Claudio from the LatinAmerican Chapter. We are working on the Spanish Translation.
knibals (Tue, 16 Feb 2021 18:02:58 GMT):
Hello guys! This is my first PR of the French translation(https://github.com/hyperledger/fabric-docs-i18n/pull/362).
All automated tests are green.
So my question is: how long does it take to the PR to be reviewed and eventually merged? (I am pretty excited as you can imagine ;) cc @rjones @davidwboswell
davidwboswell (Tue, 16 Feb 2021 18:03:50 GMT):
congratulations @knibals -- very cool to see a PR for the French translation :)
rjones (Tue, 16 Feb 2021 19:21:19 GMT):
@knibals how much work has been done on the translation itself?
rjones (Tue, 16 Feb 2021 19:33:44 GMT):
@knibals merged!
lordvins226 (Tue, 16 Feb 2021 19:38:33 GMT):
Has joined the channel.
rjones (Tue, 16 Feb 2021 19:39:36 GMT):
@BrettLogan how do I create RTD builds for fr_FR? is that documented somewhere?
BrettLogan (Tue, 16 Feb 2021 19:41:11 GMT):
One second
BrettLogan (Tue, 16 Feb 2021 19:42:47 GMT):
Can you look at the members of the Hyperledger org in RTD and tell me what my username is
BrettLogan (Tue, 16 Feb 2021 19:43:14 GMT):
I think things got messed up when my GitHub account got migrated to an GitHub Staff account
BrettLogan (Tue, 16 Feb 2021 19:46:27 GMT):
Nevermind, didn't realize there is a difference between readthedocs.com and readthedocs.org
BrettLogan (Tue, 16 Feb 2021 19:47:59 GMT):
So, all you need to do is create a `fabric-docs-fr-fr` project on readthedocs.org under the hyperledger org and then add it as a translation here: https://readthedocs.org/dashboard/hyperledger-fabric/translations/
BrettLogan (Tue, 16 Feb 2021 19:47:59 GMT):
So, all you need to do is create a `fabric-docs-fr-fr` project on readthedocs.org under the hyperledger-fabric org on rtd.org and then add it as a translation here: https://readthedocs.org/dashboard/hyperledger-fabric/translations/
rjones (Tue, 16 Feb 2021 19:51:16 GMT):
done, thanks
BrettLogan (Tue, 16 Feb 2021 19:52:01 GMT):
That was way easier than the CICD issue from last week in Indy, I'll take this a hundred times over
BrettLogan (Tue, 16 Feb 2021 19:52:13 GMT):
:laughing:
BrettLogan (Tue, 16 Feb 2021 19:52:24 GMT):
:joy:
rjones (Tue, 16 Feb 2021 19:55:49 GMT):
heh
davidwboswell (Tue, 02 Mar 2021 19:07:17 GMT):
thanks to everyone here for your contributions with translating documentation. we just posted a video and a blog post about the community translation work to show people what is happening and how to get involved. feel free to share these links with anyone who may be interested.
davidwboswell (Tue, 02 Mar 2021 19:07:18 GMT):
https://www.youtube.com/watch?v=Zlwjhtdp_7M
davidwboswell (Tue, 02 Mar 2021 19:07:24 GMT):
https://www.hyperledger.org/blog/2021/03/02/translating-hyperledger-fabric-documentation-into-multiple-languages
ricba (Tue, 02 Mar 2021 22:39:30 GMT):
Has joined the channel.
ricba (Tue, 02 Mar 2021 22:39:31 GMT):
Hello, I just started the italian traslation for Hyperledger Fabric! I am here to request the creation of the new group of maintainers :)
rjones (Wed, 03 Mar 2021 00:26:28 GMT):
sure. what's your github username?
davidwboswell (Wed, 03 Mar 2021 15:29:52 GMT):
@ricba -- that's great to hear that you've started an italian translation. let us know how else we can help get you started.
MohamadSolouki (Fri, 05 Mar 2021 17:29:20 GMT):
Has joined the channel.
MohamadSolouki (Fri, 05 Mar 2021 17:29:20 GMT):
Hello there, I started the translation of Fabric documentation into Persian language. I ask you to create a new group of maintainers :v: my github username is mohamadsolouki
davidwboswell (Fri, 05 Mar 2021 17:45:43 GMT):
@MohamadSolouki -- that's great news about starting a Persian translation effort and thanks for joining this chat channel. please let us know how we can help. and if you'd like to connect with other community members who might want to help, let me know and we can talk about how to do that.
rjones (Fri, 05 Mar 2021 17:53:27 GMT):
@MohamadSolouki invite sent
MohamadSolouki (Fri, 05 Mar 2021 18:33:25 GMT):
everything is fine, many thanks :wink:
rjones (Fri, 05 Mar 2021 18:39:11 GMT):
Sure thing.
rjones (Fri, 05 Mar 2021 19:53:52 GMT):
I just went through and merged a bunch of PRs, and I'm going to trust native speakers to do the right thing and as long as you have DCO correct, I'm merging stuff
rjones (Mon, 08 Mar 2021 18:45:50 GMT):
@ricba are you around?
rjones (Mon, 08 Mar 2021 18:46:42 GMT):
@MohamadSolouki if you're around, could we chat in... an hour and 14 minutes? @ricba also?
aakzubaidi (Mon, 08 Mar 2021 19:00:54 GMT):
Has joined the channel.
aakzubaidi (Mon, 08 Mar 2021 19:00:55 GMT):
Hi, I am starting an effort to establish an Arabic translation. The documentation of the translation process instructs to request the creation of the new group of maintainer:
this is group name: @hyperledger/fabric-ar-doc-maintainers
and this is my GithubID: aakzubaidi
rjones (Mon, 08 Mar 2021 19:06:17 GMT):
@aakzubaidi sure thing - would you have a moment to chat?
rjones (Mon, 08 Mar 2021 19:06:24 GMT):
On Zoom?
aakzubaidi (Mon, 08 Mar 2021 19:06:46 GMT):
yes sure
rjones (Mon, 08 Mar 2021 19:07:04 GMT):
https://zoom.us/my/ry.jones?pwd=RTJ1Q0R2aXVoNi8xajZ6SlM4SzVqQT09
davidwboswell (Mon, 08 Mar 2021 19:10:05 GMT):
@aakzubaidi -- thanks for getting an arabic translation effort started. excited to see that happening. let us know how we can help.
aakzubaidi (Mon, 08 Mar 2021 19:26:17 GMT):
my Pleasure!
Regards,
Ali Alzubaidi
ricba (Mon, 08 Mar 2021 20:13:55 GMT):
Hi @rjones , I'm here now
aakzubaidi (Tue, 09 Mar 2021 20:34:17 GMT):
Hi, I have got some people who express their willingness to participate with me in translation to Arabic. Now, I am just wondering whether there is any open source locale or translation management systems that you recommend out of your experience such that these system enable collaboration, versioning, progress, common terms/glossary and and shows what everyone has contributed and provides with the ability to manage translations, track changes, review and so on.
rjones (Tue, 09 Mar 2021 21:00:06 GMT):
@aakzubaidi some projects use [Transifex](https://www.transifex.com), but I have no personal experience with it
davidwboswell (Tue, 09 Mar 2021 22:28:07 GMT):
@aakzubaidi -- if you have recommendations for tools we should be looking into, feel free to make suggestions. seeing what other open source projects use could give us some good ideas to consider. i'm most familiar with mozilla's translation effort and they use a tool called pontoon. https://pontoon.mozilla.org/
aakzubaidi (Tue, 09 Mar 2021 23:33:17 GMT):
thanks everyone for the suggestions. I will check them out and see how to incorporate them
rjones (Wed, 10 Mar 2021 19:23:40 GMT):
@ricba @aakzubaidi @MohamadSolouki [check this out](https://github.com/hyperledger/fabric-docs-i18n/discussions/384)
ricba (Wed, 10 Mar 2021 21:44:37 GMT):
[ ](https://chat.hyperledger.org/channel/i18n?msg=sEwFKsDTpsy8x6gdR) Sounds good to me!
aakzubaidi (Wed, 17 Mar 2021 19:33:02 GMT):
Thanks for letting us know.
rjones (Thu, 18 Mar 2021 16:23:14 GMT):
@aakzubaidi @MohamadSolouki check this out? https://youtu.be/QJTj9QQCdG8 that is my proposal
rjones (Thu, 18 Mar 2021 17:12:20 GMT):
@alfonsogovela howdy!
alfonsogovela (Thu, 18 Mar 2021 17:12:20 GMT):
Has joined the channel.
rjones (Thu, 18 Mar 2021 18:05:54 GMT):
Hi - the Arabic translation is running into some turbulence around tooling, specifically, how to help contributors without a lot of GitHub experience. Does anyone have any tooling or process they would be willing to share?
aakzubaidi (Thu, 18 Mar 2021 20:25:32 GMT):
Thanks @rjones for raising this. Any thoughts or shared experience will really helps advancing out effort. To put in context, here is a little story. we have managed to build a small team of translators (it is now 4 of us with different level of commitment based on how everyone is available). The group already started translating basic Fabric documents such as WhatIS, Contribution Welcome, and so on . However, we are currently figuring out how to collaborate according to the best practice, and what the right tools to adopt for that. Most of the team lack essential knowledge of Github, ReadtheDocs, Visual Code studio, MD and RST format, and the like. Currently, I suggested them to translate as they can using Google Docs, while we prepare a set of workshops to introduce them to all they need to know on that regard. So, we have an upcoming session for the group to learn how to set Vscode, and how install required tools for ReadTheDocs. Also, We will introduce them to MD and RST markup syntax. So, this is a slow process, but hopefully we eventually see the light through.
aakzubaidi (Thu, 18 Mar 2021 20:29:43 GMT):
Also any suggestion on Right-To-Left RTL issues?
davidwboswell (Thu, 18 Mar 2021 21:35:46 GMT):
@aakzubaidi -- if you don't get a response to your question here, i can connect with the leads from the other active translation efforts and you can try discussing things that way. some of those people may not regularly check this channel.
Otavio.Oliveira (Fri, 19 Mar 2021 06:33:31 GMT):
Has joined the channel.
Otavio.Oliveira (Fri, 19 Mar 2021 06:33:32 GMT):
:pray:
davidwboswell (Fri, 19 Mar 2021 15:19:04 GMT):
hi @Otavio.Oliveira -- nice to see you in the chat
Otavio.Oliveira (Sat, 20 Mar 2021 01:43:42 GMT):
:smiley:
rjones (Tue, 23 Mar 2021 13:53:47 GMT):
@here I would like to ask how we could get a mutual support forum going? I know @ricba needs some assistance on getting the GitHub workflow going, and the Chinese and Japanese teams have fairly well developed workflows
rjones (Tue, 23 Mar 2021 13:54:22 GMT):
I want to help the new translations get rolling, but I really can't do a lot of handholding when it comes to using Git and the like
davidwboswell (Tue, 23 Mar 2021 15:08:12 GMT):
one thought -- would an i18n or translation mailing list be helpful? that might be a more effective way for people to communicate? for instance, i just see 4 people in this group online right now so if someone asks a question many people involved in translations wouldn't be on right now to answer and may miss the question.
stone-ch (Wed, 24 Mar 2021 02:17:01 GMT):
[ ](https://chat.hyperledger.org/channel/i18n?msg=sEwFKsDTpsy8x6gdR) Thanks Ry, I will try this way in Chinese group, and give you a response a few days later.
stone-ch (Wed, 24 Mar 2021 02:26:13 GMT):
[ ](https://chat.hyperledger.org/channel/i18n?msg=F88d3zm63wijJ4LHa) Pontoon seem be similar with transfix, it makes the translating easier. We have tried transfix about two months, but the website is too slow in China, and the translations downloaded always in bad formats, so we decided to use github back again.
rjones (Wed, 24 Mar 2021 13:43:51 GMT):
Ok. I really want to support new translations like Italian but I don’t have the time
davidkhala (Wed, 24 Mar 2021 13:56:32 GMT):
@rjones Hi, Ry, we see odd behavior in Github PR https://github.com/hyperledger/fabric-docs-i18n/pull/387 and wonder if the `enabled auto-merge` is the bug cause of it. The behavior is: this commit authors are `wuqiaoming` and `ZJJ` intially, but after merged, it become you and `ZJJ`.
rjones (Wed, 24 Mar 2021 13:57:07 GMT):
That is strange
rjones (Wed, 24 Mar 2021 13:57:22 GMT):
I will not use auto merge
davidwboswell (Thu, 01 Apr 2021 16:00:23 GMT):
@channel -- for anyone who would prefer to use a mailing list to talk with others involved in translations efforts, so we've set up an internationalization mailing list we can use to discuss ideas with the group. That is at:
https://lists.hyperledger.org/g/internationalization
davidwboswell (Thu, 01 Apr 2021 16:00:23 GMT):
@here -- for anyone who would prefer to use a mailing list to talk with others involved in translations efforts, so we've set up an internationalization mailing list we can use to discuss ideas with the group. That is at:
https://lists.hyperledger.org/g/internationalization
davidwboswell (Thu, 01 Apr 2021 16:01:01 GMT):
feel free to sign up to the list, share the list with anyone you're working with on translations, and feel free to post ideas, comments and suggestions to the list.
rjones (Fri, 16 Apr 2021 16:35:32 GMT):
@MohamadSolouki could we discuss your recent PR?
rjones (Sun, 25 Apr 2021 15:33:57 GMT):
@MohamadSolouki which client are you using for git? which editors? Are you on macOS, Linux, Windows?
MohamadSolouki (Mon, 26 Apr 2021 10:44:48 GMT):
I use VScode on Windows. And, I don't have enough experience in GitHub. I don't know exactly what the squash means or what should I do when the client is mis-configured
MohamadSolouki (Mon, 26 Apr 2021 11:01:38 GMT):
[ ](https://chat.hyperledger.org/channel/i18n?msg=N3uneq22ZfBDs68J4) I use VScode on Windows. And, I don't have enough experience in GitHub. I don't know exactly what the squash means or what should I do when the client is mis-configured
MohamadSolouki (Mon, 26 Apr 2021 11:02:18 GMT):
I use VScode on Windows. And, I don't have enough experience in GitHub. I don't know exactly what the squash means or what should I do when the client is mis-configured
rjones (Mon, 26 Apr 2021 16:09:54 GMT):
OK I will take a look.
rjones (Mon, 26 Apr 2021 21:53:27 GMT):
I am working on a guide for using GitHub for Windows and Visual Code. I've only just started but I see how to get where I'm going. [Take a look](https://wiki.hyperledger.org/display/CA/Use+GitHub+for+Windows+and+VSCode)? @MohamadSolouki @ricba
MohamadSolouki (Tue, 27 Apr 2021 01:52:40 GMT):
Thank you so much, it is helpful.
rjones (Tue, 27 Apr 2021 14:17:08 GMT):
@MohamadSolouki thanks - if there is anything I can expand on, feel free to give pointers
brohamgoham (Fri, 21 May 2021 01:07:41 GMT):
Has joined the channel.
brohamgoham (Fri, 21 May 2021 01:07:42 GMT):
hello
brohamgoham (Fri, 21 May 2021 01:07:59 GMT):
i need help i keep having issues deploying a production ready HLF
davidkhala (Tue, 08 Jun 2021 02:37:06 GMT):
This is a wrong channel to ask so.
satomicchy (Sun, 13 Jun 2021 17:20:40 GMT):
Does anyone know why the wiki's Documentation Working Group folder has been moved to the archive? Japanese group use partly but nobody use that?
rjones (Mon, 14 Jun 2021 00:05:56 GMT):
@satomicchy it doesn't look like it is actually archived - marked read only. I can move it somewhere else if you like
rjones (Mon, 14 Jun 2021 00:11:54 GMT):
@satomicchy I moved it here: https://wiki.hyperledger.org/display/I18N/International+groups I hope that is OK?
satomicchy (Mon, 14 Jun 2021 07:09:05 GMT):
@rjones Yes. That's fine with us. Thanks!
davidwboswell (Mon, 14 Jun 2021 15:10:33 GMT):
@satomicchy -- thanks for pointing that out. i didn't realize that had been put into the archive. not sure what happened, but i'll look into it.
satomicchy (Tue, 15 Jun 2021 08:29:04 GMT):
It seems to be opened only for logged in members. Could you change to the public?
rjones (Tue, 15 Jun 2021 14:38:59 GMT):
Apologies - I fixed that
satomicchy (Tue, 15 Jun 2021 19:39:22 GMT):
Perfect! Thank you!
rjones (Tue, 15 Jun 2021 19:39:56 GMT):
glad it worked!
tonybka (Wed, 14 Jul 2021 14:03:58 GMT):
Has joined the channel.
tonybka (Wed, 14 Jul 2021 14:04:30 GMT):
Hi
tonybka (Wed, 14 Jul 2021 14:05:35 GMT):
anyone here is maintainer of Fabric i18n repo?
tonybka (Wed, 14 Jul 2021 14:06:15 GMT):
I need help
rjones (Wed, 14 Jul 2021 15:27:29 GMT):
hi, how can I help?
davidwboswell (Wed, 14 Jul 2021 15:34:51 GMT):
@tonybka -- thanks for your interest in getting involved in translations. let us know how we can help. and if you'd like to get connected with other community members in vietnam, let me know and i'm happy to help. we have meetup groups in hanoi and ho chi minh city and i can help you meet with others there who may want to help you with the translating.
tonybka (Wed, 14 Jul 2021 16:39:45 GMT):
Hi, my new PR was merged. Thank you!
rjones (Wed, 14 Jul 2021 16:40:37 GMT):
Sure thing! Do you have the `DCO` stuff all worked out now?
tonybka (Wed, 14 Jul 2021 16:41:27 GMT):
However, for the previous one which has closed, it contains 2 commits that I have submitted with the wrong git configs.
tonybka (Wed, 14 Jul 2021 16:41:46 GMT):
Could you help me to remove this PR from project: https://github.com/hyperledger/fabric-docs-i18n/pull/506
tonybka (Wed, 14 Jul 2021 16:42:42 GMT):
Yes. it does, all work fine
tonybka (Wed, 14 Jul 2021 16:44:31 GMT):
I don't want this PR get indexed by Google Bot
tonybka (Wed, 14 Jul 2021 16:44:45 GMT):
It's showing a private project name
tonybka (Wed, 14 Jul 2021 16:45:02 GMT):
Thank you!
rjones (Wed, 14 Jul 2021 16:47:55 GMT):
I can't delete PRs
tonybka (Wed, 14 Jul 2021 16:48:58 GMT):
I see
tonybka (Thu, 15 Jul 2021 00:24:09 GMT):
Hi @davidwboswell, please share with me their contact if possible
tonybka (Thu, 15 Jul 2021 00:25:00 GMT):
Email or github profile is fine
tonybka (Thu, 15 Jul 2021 00:25:13 GMT):
Thanks
davidwboswell (Thu, 15 Jul 2021 14:39:38 GMT):
@tonybka -- there are 600 people in the two meetup groups in vietnam. there are a couple options for contacting them. if you wanted to write a note in vietnamese about the translation effort, i can send that out to all of those people. or we could organize a virtual meetup where we invite everyone in the groups to join and you could present about the translation effort -- people working on translating other languages have done that and it worked well. for reference, the two groups are at: https://www.meetup.com/Hyperledger-Hanoi/ and https://www.meetup.com/Hyperledger-Ho-Chi-Minh-City/
davidwboswell (Thu, 15 Jul 2021 14:39:53 GMT):
let me know what you prefer -- and we could do both too if you'd like
tonybka (Sun, 18 Jul 2021 13:29:54 GMT):
What a coincidence. Actually, I was in the cover picture of Hyperledger Hanoi Meetup group. I and Co-organizer (David Tran) know each other. Let me contact him in person to discuss about this
davidwboswell (Mon, 19 Jul 2021 14:49:13 GMT):
@tonybka -- that's great. cool to know you're in that photo :). let me know what you and david decide and i'll be happy to help. those groups haven't been that active lately so it would be great to do a virtual event to showcase what is going on in the community in vietnam.
justiny (Fri, 10 Sep 2021 01:28:57 GMT):
Has joined the channel.
justiny (Fri, 10 Sep 2021 06:09:31 GMT):
Hi, there is no page in https://wiki.hyperledger.org/display/fabric/International+groups. Has been it moved to other place?
davidwboswell (Mon, 13 Sep 2021 15:33:48 GMT):
@justiny -- yes, it was moved to: https://wiki.hyperledger.org/display/I18N/International+groups
davidwboswell (Mon, 13 Sep 2021 15:34:03 GMT):
if there's a language you're interested in translation for, let us know
justiny (Wed, 15 Sep 2021 07:18:46 GMT):
Thank you! I am interested in translation for Korean. But It seems that the links used in fabric docs have been broken. so I reported an issue(https://github.com/hyperledger/fabric/issues/2920) and made a pull request (https://github.com/hyperledger/fabric/pull/2921) for that.
justiny (Wed, 15 Sep 2021 07:22:08 GMT):
I will make a fix for fabric-docs-i18n once the pull request is merged.
justiny (Wed, 15 Sep 2021 08:23:04 GMT):
I made a pull request (https://github.com/hyperledger/fabric-docs-i18n/pull/551) of the same fix on fabric-docs-i18n. It contains the change of ar, es, fa_IR, fr_FR, it_IT, ja_JP, pt_BR, ru_RU, ta_IN, vi_VN and zh_CN.
justiny (Wed, 15 Sep 2021 09:24:24 GMT):
Please review the pull request.
davidwboswell (Wed, 15 Sep 2021 16:49:49 GMT):
@justiny -- i'm glad to hear you're interested in a translation for korean. that would be really helpful to have more content in korean. you may already know this, but we have an active community in korea and they'd welcome more content. if you'd be interested in connecting with community members there to invite more people to help with translating, let me know and i'm happy to help.
davidwboswell (Wed, 15 Sep 2021 16:50:46 GMT):
and for your question about a pull request, i've asked chris gabriel in the fabric-documentation channel for his help with this. he as done a lot of work on the docs and can help you with the process. if you don't hear back from him soon, let me know and i'll see who else can help out.
justiny (Thu, 16 Sep 2021 00:05:22 GMT):
Thank you for the information! Could you let me know about the community in Korea or Korean members who I can contact to?
justiny (Thu, 16 Sep 2021 00:21:05 GMT):
and I will. Thanks!
justiny (Thu, 16 Sep 2021 01:55:23 GMT):
The pull request (https://github.com/hyperledger/fabric-docs-i18n/pull/551) has just been merged. Thanks!
davidwboswell (Thu, 16 Sep 2021 17:22:29 GMT):
@justiny -- there is a hyperledger korea meetup group that runs regular events and you're welcome to go those to introduce yourself and connect with others in the community. that is at: https://www.meetup.com/Hyperledger-Korea/
davidwboswell (Thu, 16 Sep 2021 17:23:21 GMT):
and we can also help you reach out to other community members about what you're doing with the translation. if you send me your email address, i'll start a thread with the person at the Linux Foundation who support out community in Korea and she can help you connect with people too.
justiny (Fri, 17 Sep 2021 02:23:32 GMT):
Thank you! I will take a look the meetup community and my email address is justin.yang@themedium.io
davidwboswell (Mon, 20 Sep 2021 19:41:01 GMT):
great. i'll start a thread over email.
davidwboswell (Mon, 20 Sep 2021 19:47:43 GMT):
@justiny -- i just connected you with sue, who knows a lot more about the community in korea than i do. let me know if you don't hear back from her soon, but she should be able to help you connect with other community members in korea.
justiny (Wed, 22 Sep 2021 02:25:38 GMT):
Thank you! I am really looking forward to meet the community members!
davidwboswell (Wed, 22 Sep 2021 16:29:11 GMT):
@justiny -- that's great about getting connected with the community in korea. they're active and i would imagine people would be interested in collaborating on your translation effort. if sue doesn't get back to you soon, let me know and i'll follow up.
justiny (Fri, 24 Sep 2021 08:53:56 GMT):
fabric-docs-korean
justiny (Fri, 24 Sep 2021 08:55:01 GMT):
#fabric-docs-korean
sueyoung-chang (Wed, 29 Sep 2021 08:56:03 GMT):
Has joined the channel.
sueyoung-chang (Wed, 29 Sep 2021 08:56:03 GMT):
@justiny Hi Justin, glad to meet you! Looking forward to talk to you on Friday
justiny (Wed, 29 Sep 2021 08:56:47 GMT):
@sueyoung-chang Hi, nice to meet you! me either!
justiny (Tue, 05 Oct 2021 07:27:26 GMT):
Hi, I've been translating fabric doc into Korean (ko_KR). Could you create @hyperledger/fabric-ko_KR-doc-maintainers, please?
justiny (Tue, 05 Oct 2021 07:30:36 GMT):
The base PR is https://github.com/hyperledger/fabric-docs-i18n/pull/555
justiny (Tue, 05 Oct 2021 07:55:53 GMT):
my github username is justin-themedium
rjones (Tue, 05 Oct 2021 15:24:09 GMT):
@justiny thank you - merged! I'll set up the RTD builds later today
justiny (Tue, 05 Oct 2021 15:27:15 GMT):
@rjones Thank you! I've just checked it
rjones (Tue, 05 Oct 2021 15:29:14 GMT):
I set up https://fabric-docs-i18n-ko-kr.readthedocs.io/ko/latest/ but it hasn't built yet
rjones (Tue, 05 Oct 2021 15:30:40 GMT):
https://hyperledger-fabric.readthedocs.io/ko/release-2.2/ here you go
justiny (Tue, 05 Oct 2021 15:31:01 GMT):
Thanks. Let me submit a new pull request for the first page.
rjones (Tue, 05 Oct 2021 15:31:17 GMT):
If you go here: https://hyperledger-fabric.readthedocs.io/en/release-2.2/ you can now choose `ko` as a translation
justiny (Tue, 05 Oct 2021 15:31:42 GMT):
Great!
rjones (Tue, 05 Oct 2021 15:31:56 GMT):
I will be back in two hours, so I can approve PRs once you start adding them
justiny (Tue, 05 Oct 2021 15:38:57 GMT):
I've just submitted https://github.com/hyperledger/fabric-docs-i18n/pull/556
justiny (Tue, 05 Oct 2021 15:43:25 GMT):
I can check the ko documentation in https://hyperledger-fabric--556.org.readthedocs.build/ko/556/
rjones (Tue, 05 Oct 2021 17:56:34 GMT):
Merged
justiny (Wed, 06 Oct 2021 04:56:11 GMT):
Thank you!
rjones (Wed, 23 Mar 2022 17:35:35 GMT):
rjones (Wed, 23 Mar 2022 17:35:35 GMT):
rjones (Wed, 23 Mar 2022 17:35:35 GMT):
