New Crowdin updates

content/ar/case-studies/benchmarks.md

@@ -0,0 +1,79 @@
+# Benchmarks
+
+Benchmarks are tests to measure the performance of pandas. There are two different
+kinds of benchmarks relevant to pandas:
+
+- Internal pandas benchmarks to measure speed and memory usage over time
+- Community benchmarks comparing the speed or memory usage of different tools at
+  doing the same job
+
+## pandas benchmarks
+
+pandas benchmarks are implemented in the [asv_bench](https://github.com/pandas-dev/pandas/tree/main/asv_bench)
+directory of our repository. The benchmarks are implemented for the
+[airspeed velocity](https://asv.readthedocs.io/en/v0.6.1/) (asv for short) framework.
+
+The benchmarks can be run locally by any pandas developer. This can be done
+with the `asv run` command, and it can be useful to detect if local changes have
+an impact in performance, by running the benchmarks before and after the changes.
+More information on running the performance test suite is found
+[here](https://pandas.pydata.org/docs/dev/development/contributing_codebase.html#running-the-performance-test-suite).
+
+Note that benchmarks are not deterministic, and running in different hardware or
+running in the same hardware with different levels of stress have a big impact in
+the result. Even running the benchmarks with identical hardware and almost identical
+conditions produces significant differences when running the same exact code.
+
+## pandas benchmarks servers
+
+We currently have two physical servers running the benchmarks of pandas for every
+(or almost every) commit to the `main` branch. The servers run independently from
+each other. The original server has been running for a long time, and it is physically
+located with one of the pandas maintainers. The newer server is in a datacenter
+kindly sponsored by [OVHCloud](https://www.ovhcloud.com/). More information about
+pandas sponsors, and how your company can support the development of pandas is
+available at the [pandas sponsors]({{ base_url }}about/sponsors.html) page.
+
+Results of the benchmarks are available at:
+
+- Original server: [asv](https://asv-runner.github.io/asv-collection/pandas/)
+- OVH server: [asv](https://pandas.pydata.org/benchmarks/asv/) (benchmarks results can
+  also be visualized in this [Conbench PoC](http://57.128.112.95:5000/)
+
+### Original server configuration
+
+The machine can be configured with the Ansible playbook in
+[tomaugspurger/asv-runner](https://github.com/tomaugspurger/asv-runner).
+The results are published to another GitHub repository,
+[tomaugspurger/asv-collection](https://github.com/tomaugspurger/asv-collection).
+
+The benchmarks are scheduled by [Airflow](https://airflow.apache.org/).
+It has a dashboard for viewing and debugging the results.
+You’ll need to setup an SSH tunnel to view them:
+
+```
+ssh -L 8080:localhost:8080 [email protected]
+```
+
+### OVH server configuration
+
+The server used to run the benchmarks has been configured to reduce system
+noise and maximize the stability of the benchmarks times.
+
+The details on how the server is configured can be found in the
+[pandas-benchmarks repository](https://github.com/pandas-dev/pandas-benchmarks).
+There is a quick summary here:
+
+- CPU isolation: Avoid user space tasks to execute in the same CPU as benchmarks, possibly interrupting them during the execution (include all virtual CPUs using a physical core)
+- NoHZ: Stop the kernel tick that enables context switching in the isolated CPU
+- IRQ affinity: Ban benchmarks CPU to avoid many (but not all) kernel interruption in the isolated CPU
+- TurboBoost: Disable CPU scaling based on high CPU demand
+- P-States: Use "performance" governor to disable P-States and CPU frequency changes based on them
+- C-States: Set C-State to 0 and disable changes to avoid slower CPU after system inactivity
+
+## Community benchmarks
+
+The main benchmarks comparing dataframe tools that include pandas are:
+
+- [DuckDB (former H2O.ai) benchmarks](https://duckdblabs.github.io/db-benchmark/)
+- [TPCH benchmarks](https://pola.rs/posts/benchmarks/)

content/ar/case-studies/citing.md

@@ -0,0 +1,134 @@
+# Citing and logo
+
+## Citing pandas
+
+If you use _pandas_ for a scientific publication, we would appreciate citations to the published software and the
+following paper:
+
+- [pandas on Zenodo](https://zenodo.org/search?page=1\&size=20\&q=conceptrecid%3A%223509134%22\&sort=-version\&all_versions=True),
+  Please find us on Zenodo and replace with the citation for the version you are using. You can replace the full author
+  list from there with "The pandas development team" like in the example below.
+
+  ```
+    @software{reback2020pandas,
+        author       = {The pandas development team},
+        title        = {pandas-dev/pandas: Pandas},
+        month        = feb,
+        year         = 2020,
+        publisher    = {Zenodo},
+        version      = {latest},
+        doi          = {10.5281/zenodo.3509134},
+        url          = {https://doi.org/10.5281/zenodo.3509134}
+    }
+  ```
+
+- [Data structures for statistical computing in python](https://pub.curvenote.com/01908378-3686-7168-a380-d82bbf21c799/public/mckinney-57fc0d4e8a08cd7f26a4b8bf468a71f4.pdf),
+  McKinney, Proceedings of the 9th Python in Science Conference, Volume 445, 2010.
+
+  ```
+    @InProceedings{ mckinney-proc-scipy-2010,
+      author    = { {W}es {M}c{K}inney },
+      title     = { {D}ata {S}tructures for {S}tatistical {C}omputing in {P}ython },
+      booktitle = { {P}roceedings of the 9th {P}ython in {S}cience {C}onference },
+      pages     = { 56 - 61 },
+      year      = { 2010 },
+      editor    = { {S}t\'efan van der {W}alt and {J}arrod {M}illman },
+      doi       = { 10.25080/Majora-92bf1922-00a }
+    }
+  ```
+
+## Brand and logo
+
+When using the project name _pandas_, please use it in lower case, even at the beginning of a sentence.
+
+The official logos of _pandas_ are:
+
+### Primary logo
+
+<table class="table logo">
+    <tbody><tr>
+        <td>
+            <img alt="" src="{{ base_url }}static/img/pandas.svg"/>
+        </td>
+        <td style="background-color: #150458">
+            <img alt="" src="{{ base_url }}static/img/pandas_white.svg"/>
+        </td>
+    </tr>
+</tbody></table>
+
+### Secondary logo
+
+<table class="table logo">
+    <tbody><tr>
+        <td>
+            <img alt="" src="{{ base_url }}static/img/pandas_secondary.svg"/>
+        </td>
+        <td style="background-color: #150458">
+            <img alt="" src="{{ base_url }}static/img/pandas_secondary_white.svg"/>
+        </td>
+    </tr>
+</tbody></table>
+
+### Logo mark
+
+<table class="table logo">
+    <tbody><tr>
+        <td>
+            <img alt="" src="{{ base_url }}static/img/pandas_mark.svg"/>
+        </td>
+        <td style="background-color: #150458">
+            <img alt="" src="{{ base_url }}static/img/pandas_mark_white.svg"/>
+        </td>
+    </tr>
+</tbody></table>
+
+### Logo usage
+
+The pandas logo is available in full color and white accent.
+The full color logo should only appear against white backgrounds.
+The white accent logo should go against contrasting color background.
+
+When using the logo, please follow the next directives:
+
+- Primary logo should never be seen under 1 inch in size for printing and 72px for web
+- The secondary logo should never be seen under 0.75 inch in size for printing and 55px for web
+- Leave enough margin around the logo (leave the height of the logo in the top, bottom and both sides)
+- Do not distort the logo by changing its proportions
+- Do not place text or other elements on top of the logo
+
+### Colors
+
+<table class="table">
+    <tbody><tr>
+        <td style="text-align: center;">
+            <svg xmlns="http://www.w3.org/2000/svg" width="100" height="100">
+                <circle cx="50" cy="50" r="50" fill="#150458"/>
+            </svg>
+
+            <br/>
+            <b style="color: #150458;">Blue</b><br/>
+            RGB: R21 G4 B88<br/>
+            HEX: #150458
+        </td>
+        <td style="text-align: center;">
+            <svg xmlns="http://www.w3.org/2000/svg" width="100" height="100">
+                <circle cx="50" cy="50" r="50" fill="#ffca00"/>
+            </svg>
+
+            <br/>
+            <b style="color: #150458;">Yellow</b><br/>
+            RGB: R255 G202 B0<br/>
+            HEX: #FFCA00
+        </td>
+        <td style="text-align: center;">
+            <svg xmlns="http://www.w3.org/2000/svg" width="100" height="100">
+                <circle cx="50" cy="50" r="50" fill="#e70488"/>
+            </svg>
+
+            <br/>
+            <b style="color: #150458;">Pink</b><br/>
+            RGB: R231 G4 B136<br/>
+            HEX: #E70488
+        </td>
+    </tr>
+</tbody></table>

content/ar/case-studies/coc.md

@@ -0,0 +1,65 @@
+# Code of conduct
+
+As contributors and maintainers of this project, and in the interest of
+fostering an open and welcoming community, we pledge to respect all people who
+contribute through reporting issues, posting feature requests, updating
+documentation, submitting pull requests or patches, and other activities.
+
+We are committed to making participation in this project a harassment-free
+experience for everyone, regardless of level of experience, gender, gender
+identity and expression, sexual orientation, disability, personal appearance,
+body size, race, ethnicity, age, religion, or nationality.
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery
+- Personal attacks
+- Trolling or insulting/derogatory comments
+- Public or private harassment
+- Publishing other's private information, such as physical or electronic
+  addresses, without explicit permission
+- Other unethical or unprofessional conduct
+
+Furthermore, we encourage inclusive behavior - for example,
+please don't say “hey guys!” but “hey everyone!”.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+By adopting this Code of Conduct, project maintainers commit themselves to
+fairly and consistently applying these principles to every aspect of managing
+this project. Project maintainers who do not follow or enforce the Code of
+Conduct may be permanently removed from the project team.
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community.
+
+A working group of community members is committed to promptly addressing any
+reported issues. The working group is made up of pandas contributors and users.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the working group by e-mail ([email protected]).
+Messages sent to this e-mail address will not be publicly visible but only to
+the working group members. The working group currently includes
+
+<ul>
+    {% for person in maintainers.coc %}
+    <li>{{ person }}</li>
+    {% endfor %}
+</ul>
+
+All complaints will be reviewed and investigated and will result in a response
+that is deemed necessary and appropriate to the circumstances. Maintainers are
+obligated to maintain confidentiality with regard to the reporter of an
+incident.
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 1.3.0, available at
+[https://www.contributor-covenant.org/version/1/3/0/][version],
+and the [Swift Code of Conduct][swift].
+
+[homepage]: https://www.contributor-covenant.org
+[version]: https://www.contributor-covenant.org/version/1/3/0/
+[swift]: https://swift.org/community/#code-of-conduct