search

datacarpentry / python-ecology-lesson

Data Analysis and Visualization in Python for Ecologists
https://datacarpentry.org/python-ecology-lesson
Other
162 stars 307 forks source link

Translating python-ecology-lesson into Spanish #324

Closed orchid00 closed 1 year ago

orchid00 commented 5 years ago

Hello maintainers @wrightaprilm @trallard,

I've been working with a group of people into translating SWC lessons into Spanish. We would like to start translating a DC lesson (ping @ErinBecker). Since we already translated an R lesson a Python lesson seems to be a good start for this new project. I would like to hear your thoughts before making a copy of this repo. Is this a good time? or are there any major changes coming up soon-ish? Any other recommendations that you can think of, for when we start sort of to keep things synchronized.

Happy to hear from you!

wrightaprilm commented 5 years ago

Hi @orchid00 -

@raynamharris had mentioned you might be in touch - so glad to see this project moving forward. We recently revamped the plotting and capstone lessons. They've survived their first contact with learners, so I think we shouldn't have major changes in the pipeline (@maxim-belkin, does this sound right to you?).

It's the end of the semester crunch time here, so I'm likely to be a big slow in my responses, but please do let me know if there's anything to support your efforts.

Are you using the slack channel? I have typically been a little resistant to the idea of integrating github notifications in slack, but integrating the github notifications for this repository into the dc-ecology-py channel might be helpful to provide a one-stop review of what, if anything, is changing in the repo. Would that be helpful?

orchid00 commented 5 years ago

Thanks @wrightaprilm. Yes I use slack, I'm not on that channel -yet- but, I'll join :+1: I also thought to leave this issue open for any comments from the community.

wrightaprilm commented 5 years ago

OK, sounds good. I'll tag this with some labels to let community members know they are welcome to discuss and participate.

@ErinBecker, I know there was a little discussion on the maintainers channel about GitHub integration with the lesson slack channels. It sounds like that might be helpful for keeping external folks (like Paula) up-to-date as they work on this task. Is it a possibility to enable this? Meredith's comments in the maintainers channel have more info - I regrettably don't know how to do this.

Edit: Sorry, didn't mean to close.

Are there specific contributions that would be helpful? I was planning to tweet about this, perhaps we can come up with a couple contributions that would be especially needed. Maybe folks with ideas on how to keep the repos synced?

orchid00 commented 5 years ago

Perfect @wrightaprilm! @trallard for the time being I just wanted to bring your attention to a few open PR's https://github.com/datacarpentry/python-ecology-lesson/pulls maybe it is possible to merge some of them. I've read all of them seem valid improvements, but also have some merge conflicts. If you guys decide to leave them for a later revision or for further discussion, that is also fine. Please do let me know what is the final decision.

To keep things sync, I guess at the moment I can look at merged PR's while I agree an automatic notification of changes, would be cool! I'll explore that option in settings

wrightaprilm commented 5 years ago

There are a few open PRs ... they're mostly instructor check-out exercises no one bothered to respond to reviews on. I'll merge #312 at the end of the day today (in about 8 hours) if no one raises additional issues on it.

Very exciting stuff!

maxim-belkin commented 5 years ago

@orchid00, please record the hash (commit id) of this repository when you begin translating it. All translators should then git checkout that hash. Once you finish translating the lesson for that hash, release it and begin translating up to the latest hash again. There is no need to rush-merge pull requests in this repository.

maxim-belkin commented 5 years ago

@wrightaprilm, I'm not sure that all of the labels that you added are applicable to this issue. I'd say this is an example of cross-repository work and we don't have good labels for that kind of stuff.

raynamharris commented 5 years ago

Please see https://github.com/Carpentries-ES/python-ecology-lesson-es.

raynamharris commented 5 years ago

It looks like this was the last commit e9cd8d562011631f59328e2b22a0ecee7148b9ab

raynamharris commented 5 years ago

Also, quick question @maxim-belkin, what is the purpose of recording the hash? Is it to keep up with PRs that y'all merge after we begin translating? Note that we anything we translate will not need to be incorporated back into the english version. After the translation, we might have some lesson development going on (like fixing keywords) but that's down the road.

maxim-belkin commented 5 years ago

Yes, to keep the translated lesson up-to-date (using git diff recorded-hash HEAD). Alternative solution was to fork this lesson and proceed with the translations, using HTML <!-- and --> to comment out translated parts. This way you could merge changes from "upstream" (this lesson) directly

raynamharris commented 5 years ago

okay. forking caused many, many problems last time that @rgaiacs can explain better than I can

orchid00 commented 5 years ago

Hi @maxim-belkin @raynamharris, just letting you know, the repo is not a fork, it is imported. This has been consulted with Curriculum Development lead! :D

Sorry @maxim-belkin i don't know what this means "All translators should then git checkout that hash" and.. to be honest I don't think we need that. We had translated three lessons without doing that. But there is room for a simpler explanation and then we will decide whether to do it at some point.

orchid00 commented 5 years ago

Hi @wrightaprilm, I discovered how to link slack with github, it is an app. I tried to add it but It seems like 10 apps is the maximum number of apps in a free slack account. Sadly there's already 10 apps. @ErinBecker will there be any app we could get rid of? Also, just putting it on the plate, maybe some funding directed to slack will be worth investing in.

rgaiacs commented 5 years ago

okay. forking caused many, many problems last time

I think the correct word is "has many restrictions". GitHub only allows one fork per repository so in the scenario that Alice and Bob are going to translate lesson X to language Y. They already have a fork of X that is render in https://github.io/. To translate X to Y and have it render in https://github.io/ they will need to import and not fork. But when Alice and Bob want to collaborate, their individual import can't receive pull request from the other. The solution is to have one organisation importing the lesson to be translated so that Alice and Bob can fork that import and send pull requests to it. Because of this, any update from the original language can not be perform in GitHub interface.

i don't know what this means "All translators should then git checkout that hash" and.. to be honest I don't think we need that.

This is for the case you are using the same repository for the original language and the translation.

raynamharris commented 5 years ago

Thanks @rgaiacs. your explanation really helped me understand all the nuances.

btovar commented 1 year ago

Please see: https://github.com/datacarpentry/python-ecology-lesson-es