New Crowdin updates

locale/es/CODE_OF_CONDUCT.md

@@ -0,0 +1,12 @@
+---
+title: Contributor Code of Conduct
+---
+
+As contributors and maintainers of this project,
+we pledge to follow the [The Carpentries Code of Conduct][coc].
+
+Instances of abusive, harassing, or otherwise unacceptable behavior
+may be reported by following our [reporting guidelines][coc-reporting].
+
+[coc-reporting]: https://docs.carpentries.org/topic_folders/policies/incident-reporting.html
+[coc]: https://docs.carpentries.org/topic_folders/policies/code-of-conduct.html

locale/es/CONTRIBUTING.md

@@ -0,0 +1,151 @@
+# Contributing
+
+[Software Carpentry][swc-site] and [Data Carpentry][dc-site] are open source projects,
+and we welcome contributions of all kinds:
+new lessons,
+fixes to existing material,
+bug reports,
+and reviews of proposed changes are all welcome.
+
+## Contributor Agreement
+
+By contributing,
+you agree that we may redistribute your work under [our license](LICENSE.md).
+In exchange,
+we will address your issues and/or assess your change proposal as promptly as we can,
+and help you become a member of our community.
+Everyone involved in [Software Carpentry][swc-site] and [Data Carpentry][dc-site]
+agrees to abide by our [code of conduct](CODE_OF_CONDUCT.md).
+
+## How to Contribute
+
+The easiest way to get started is to file an issue
+to tell us about a spelling mistake,
+some awkward wording,
+or a factual error.
+This is a good way to introduce yourself
+and to meet some of our community members.
+
+1. If you do not have a [GitHub][github] account,
+   you can [send us comments by email][contact].
+   However,
+   we will be able to respond more quickly if you use one of the other methods described below.
+
+2. If you have a [GitHub][github] account,
+   or are willing to [create one][github-join],
+   but do not know how to use Git,
+   you can report problems or suggest improvements by [creating an issue][issues].
+   This allows us to assign the item to someone
+   and to respond to it in a threaded discussion.
+
+3. If you are comfortable with Git,
+   and would like to add or change material,
+   you can submit a pull request (PR).
+   Instructions for doing this are [included below](#using-github).
+
+## Where to Contribute
+
+1. If you wish to change this lesson,
+   please work in https://github.com/carpentries-incubator/bioc-rnaseq,
+   which can be viewed at https://carpentries-incubator.github.io/bioc-rnaseq/.
+
+2. If you wish to change the example lesson,
+   please work in https://github.com/carpentries/lesson-example,
+   which documents the format of our lessons
+   and can be viewed at https://carpentries.github.io/lesson-example.
+
+3. If you wish to change the template used for workshop websites,
+   please work in https://github.com/carpentries/workshop-template.
+   The home page of that repository explains how to set up workshop websites,
+   while the extra pages in https://carpentries.github.io/workshop-template
+   provide more background on our design choices.
+
+4. If you wish to change CSS style files, tools,
+   or HTML boilerplate for lessons or workshops stored in `_includes` or `_layouts`,
+   please work in https://github.com/carpentries/styles.
+
+## What to Contribute
+
+There are many ways to contribute,
+from writing new exercises and improving existing ones
+to updating or filling in the documentation
+and submitting [bug reports][issues]
+about things that don't work, aren't clear, or are missing.
+If you are looking for ideas,
+please see [the list of issues for this repository][issues],
+or the issues for [Data Carpentry][dc-issues]
+and [Software Carpentry][swc-issues] projects.
+
+Comments on issues and reviews of pull requests are just as welcome:
+we are smarter together than we are on our own.
+Reviews from novices and newcomers are particularly valuable:
+it's easy for people who have been using these lessons for a while
+to forget how impenetrable some of this material can be,
+so fresh eyes are always welcome.
+
+## What _Not_ to Contribute
+
+Our lessons already contain more material than we can cover in a typical workshop,
+so we are usually _not_ looking for more concepts or tools to add to them.
+As a rule,
+if you want to introduce a new idea,
+you must (a) estimate how long it will take to teach
+and (b) explain what you would take out to make room for it.
+The first encourages contributors to be honest about requirements;
+the second, to think hard about priorities.
+
+We are also not looking for exercises or other material that only run on one platform.
+Our workshops typically contain a mixture of Windows, macOS, and Linux users;
+in order to be usable,
+our lessons must run equally well on all three.
+
+## Using GitHub
+
+If you choose to contribute via GitHub,
+you may want to look at
+[How to Contribute to an Open Source Project on GitHub][how-contribute].
+In brief:
+
+1. The published copy of the lesson is in the `gh-pages` branch of the repository
+   (so that GitHub will regenerate it automatically).
+   Please create all branches from that,
+   and merge the [master repository][repo]'s `gh-pages` branch into your `gh-pages` branch
+   before starting work.
+   Please do _not_ work directly in your `gh-pages` branch,
+   since that will make it difficult for you to work on other contributions.
+
+2. We use [GitHub flow][github-flow] to manage changes:
+   1. Create a new branch in your desktop copy of this repository for each significant change.
+   2. Commit the change in that branch.
+   3. Push that branch to your fork of this repository on GitHub.
+   4. Submit a pull request from that branch to the [master repository][repo].
+   5. If you receive feedback,
+      make changes on your desktop and push to your branch on GitHub:
+      the pull request will update automatically.
+
+Each lesson has two maintainers who review issues and pull requests
+or encourage others to do so.
+The maintainers are community volunteers,
+and have final say over what gets merged into the lesson.
+
+## Other Resources
+
+General discussion of [Software Carpentry][swc-site] and [Data Carpentry][dc-site]
+happens on the [discussion mailing list][discuss-list],
+which everyone is welcome to join.
+You can also [reach us by email][contact].
+
+[contact]: mailto:[email protected]
+[dc-issues]: https://github.com/issues?q=user%3Adatacarpentry
+[dc-lessons]: https://datacarpentry.org/lessons/
+[dc-site]: https://datacarpentry.org/
+[discuss-list]: https://lists.software-carpentry.org/listinfo/discuss
+[github]: https://github.com
+[github-flow]: https://guides.github.com/introduction/flow/
+[github-join]: https://github.com/join
+[how-contribute]: https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github
+[issues]: https://github.com/carpentries-incubator/bioc-rnaseq/issues/
+[repo]: https://github.com/carpentries-incubator/bioc-rnaseq/
+[swc-issues]: https://github.com/issues?q=user%3Aswcarpentry
+[swc-lessons]: https://software-carpentry.org/lessons/
+[swc-site]: https://software-carpentry.org/

locale/es/LICENSE.md

@@ -0,0 +1,82 @@
+---
+title: Licenses
+---
+
+## Instructional Material
+
+All Software Carpentry, Data Carpentry, and Library Carpentry instructional material is
+made available under the [Creative Commons Attribution
+license][cc-by-human]. The following is a human-readable summary of
+(and not a substitute for) the [full legal text of the CC BY 4.0
+license][cc-by-legal].
+
+You are free:
+
+- to **Share**---copy and redistribute the material in any medium or format
+- to **Adapt**---remix, transform, and build upon the material
+
+for any purpose, even commercially.
+
+The licensor cannot revoke these freedoms as long as you follow the
+license terms.
+
+Under the following terms:
+
+- **Attribution**---You must give appropriate credit (mentioning that
+  your work is derived from work that is Copyright © Software
+  Carpentry and, where practical, linking to
+  https\://software-carpentry.org/), provide a [link to the
+  license][cc-by-human], and indicate if changes were made. You may do
+  so in any reasonable manner, but not in any way that suggests the
+  licensor endorses you or your use.
+
+**No additional restrictions**---You may not apply legal terms or
+technological measures that legally restrict others from doing
+anything the license permits.  With the understanding that:
+
+Notices:
+
+- You do not have to comply with the license for elements of the
+  material in the public domain or where your use is permitted by an
+  applicable exception or limitation.
+- No warranties are given. The license may not give you all of the
+  permissions necessary for your intended use. For example, other
+  rights such as publicity, privacy, or moral rights may limit how you
+  use the material.
+
+## Software
+
+Except where otherwise noted, the example programs and other software
+provided by Software Carpentry and Data Carpentry are made available under the
+[OSI][osi]-approved
+[MIT license][mit-license].
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+## Trademark
+
+"Software Carpentry" and "Data Carpentry" and their respective logos
+are registered trademarks of [Community Initiatives][ci].
+
+[cc-by-human]: https://creativecommons.org/licenses/by/4.0/
+[cc-by-legal]: https://creativecommons.org/licenses/by/4.0/legalcode
+[mit-license]: https://opensource.org/licenses/mit-license.html
+[ci]: https://communityin.org/
+[osi]: https://opensource.org

locale/es/README.md

@@ -0,0 +1,47 @@
+# RNA-seq analysis with Bioconductor
+
+[![Create a Slack Account with us](https://img.shields.io/badge/Create_Slack_Account-The_Carpentries-071159.svg)](https://swc-slack-invite.herokuapp.com/)
+
+## Contributing
+
+We welcome all contributions to improve the lesson! Maintainers will do their best to help you if you have any
+questions, concerns, or experience any difficulties along the way.
+
+We'd like to ask you to familiarize yourself with our [Contribution Guide](CONTRIBUTING.md) and have a look at
+the [more detailed guidelines][lesson-example] on proper formatting, ways to render the lesson locally, and even
+how to write new episodes.
+
+Please see the current list of [issues][issues] for ideas for contributing to this
+repository. For making your contribution, we use the GitHub flow, which is
+nicely explained in the chapter [Contributing to a Project](http://git-scm.com/book/en/v2/GitHub-Contributing-to-a-Project) in Pro Git
+by Scott Chacon.
+Look for the tag ![good\\_first\\_issue](https://img.shields.io/badge/-good%20first%20issue-gold.svg). This indicates that the maintainers will welcome a pull request fixing this issue.
+
+## Useful links
+
+- [ ] If you're going to be developing lesson material for the first time
+  according to our design principles,
+  consider reading the [Carpentries Curriculum Development Handbook][cdh]
+- [ ] Consult the [Lesson Example][lesson-example] website to find out more about
+  working with the lesson template
+
+## Maintainer(s)
+
+Current maintainers of this lesson are
+
+- Charlotte Soneson
+- Jenny Drnevich
+- Laurent Gatto
+- Robert Castelo
+
+## Authors
+
+A list of contributors to the lesson can be found in [AUTHORS](AUTHORS)
+
+## Citation
+
+To cite this lesson, please consult with [CITATION](CITATION)
+
+[lesson-example]: https://carpentries.github.io/lesson-example
+[cdh]: https://cdh.carpentries.org
+[issues]: https://github.com/carpentries-incubator/bioc-rnaseq/issues/

locale/es/config.yaml

@@ -0,0 +1,63 @@
+#------------------------------------------------------------
+#Values for this lesson.
+#------------------------------------------------------------
+#Which carpentry is this (swc, dc, lc, or cp)?
+#swc: Software Carpentry
+#dc: Data Carpentry
+#lc: Library Carpentry
+#cp: Carpentries (to use for instructor training for instance)
+#incubator: The Carpentries Incubator
+carpentry: 'incubator'
+varnish: mblue9/varnish
+#Overall title for pages.
+title: 'RNA-seq analysis with Bioconductor'
+#Date the lesson was created (YYYY-MM-DD, this is empty by default)
+created: '2020-09-15'
+#Comma-separated list of keywords for the lesson
+keywords: 'software, data, lesson, The Carpentries'
+#Life cycle stage of the lesson
+#possible values: pre-alpha, alpha, beta, stable
+life_cycle: 'beta'
+#License of the lesson
+license: 'CC-BY 4.0'
+#Link to the source repository for this lesson
+source: 'https://github.com/carpentries-incubator/bioc-rnaseq'
+#Default branch of your lesson
+branch: 'main'
+#Who to contact if there are any issues
+contact: '[email protected]'
+#Navigation ------------------------------------------------
+#Use the following menu items to specify the order of
+#individual pages in each dropdown section. Leave blank to
+#include all pages in the folder.
+#Example -------------
+#episodes:
+#- introduction.md
+#- first-steps.md
+#learners:
+#- setup.md
+#instructors:
+#- instructor-notes.md
+#profiles:
+#- one-learner.md
+#- another-learner.md
+#Order of episodes in your lesson
+episodes:
+  - 01-intro-to-rnaseq.Rmd
+  - 02-setup.Rmd
+  - 03-import-annotate.Rmd
+  - 04-exploratory-qc.Rmd
+  - 05-differential-expression.Rmd
+  - 06-extra-design.Rmd
+  - 07-gene-set-analysis.Rmd
+  - 08-next-steps.Rmd
+#Information for Learners
+learners:
+#Information for Instructors
+instructors:
+#Learner Profiles
+profiles:
+#Customisation ---------------------------------------------
+#This space below is where custom yaml items (e.g. pinning
+#sandpaper and varnish versions) should live
+url: https://carpentries-incubator.github.io/bioc-rnaseq