Skip to content
This repository has been archived by the owner on Feb 24, 2024. It is now read-only.

Commit

Permalink
markdown source builds
Browse files Browse the repository at this point in the history 
Auto-generated via {sandpaper}
Source  : 7132d77
Branch  : l10n_main
Author  : Joel Nitta <[email protected]>
Time    : 2023-11-21 11:06:29 +0000
Message : New translations index.md (Japanese)
  • Loading branch information
@actions-user
actions-user committed Nov 21, 2023
1 parent 6c2d086 commit 490b971
Show file tree
Hide file tree
Showing 3 changed files with 31 additions and 52 deletions.
12 changes: 8 additions & 4 deletions LICENSE.md
View file
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
title: "Licenses"
title: Licenses
---

## Instructional Material
Expand All @@ -24,7 +24,7 @@ Under the following terms:

- **Attribution**---You must give appropriate credit (mentioning that your work
is derived from work that is Copyright (c) The Carpentries and, where
practical, linking to <https://carpentries.org/>), provide a [link to the
practical, linking to https\://carpentries.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.
Expand All @@ -35,10 +35,10 @@ Under the following terms:

Notices:

* You do not have to comply with the license for elements of the material in
- 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
- 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.

Expand Down Expand Up @@ -73,7 +73,11 @@ 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
67 changes: 21 additions & 46 deletions index.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -3,56 +3,31 @@ permalink: index.html
site: sandpaper::sandpaper_site
---

Wolfman and Dracula have been hired by Universal Missions (a space
services spinoff from Euphoric State University) to investigate if it
is possible to send their next planetary lander to Mars. They want to
be able to work on the plans at the same time, but they have run into
problems doing this in the past. If they take turns, each one will
spend a lot of time waiting for the other to finish, but if they work
on their own copies and email changes back and forth things will be
lost, overwritten, or duplicated.

A colleague suggests using [version control](learners/reference.md#version-control) to
manage their work. Version control is better than mailing files back and forth:

- Nothing that is committed to version control is ever lost, unless
you work really, really hard at it. Since all old versions of
files are saved, it's always possible to go back in time to see
exactly who wrote what on a particular day, or what version of a
program was used to generate a particular set of results.

- As we have this record of who made what changes when, we know who to ask
if we have questions later on, and, if needed, revert to a previous
version, much like the "undo" feature in an editor.

- When several people collaborate in the same project, it's possible to
accidentally overlook or overwrite someone's changes. The version control
system automatically notifies users whenever there's a conflict between one
person's work and another's.

Teams are not the only ones to benefit from version control: lone
researchers can benefit immensely. Keeping a record of what was
changed, when, and why is extremely useful for all researchers if they
ever need to come back to the project later on (e.g., a year later,
when memory has faded).

Version control is the lab notebook of the digital world: it's what
professionals use to keep track of what they've done and to
collaborate with other people. Every large software development
project relies on it, and most programmers use it for their small jobs
as well. And it isn't just for software: books,
papers, small data sets, and anything that changes over time or needs
to be shared can and should be stored in a version control system.
ウルフマンとドラキュラはユニバーサル・ミッションズ（ユーフォリック州立大学からスピンオフした宇宙
サービス）に雇われ、次の惑星着陸船を火星に送ることが可能かどうかを調査しています。 彼らはそれぞれ同時に計画を立てたいのですが、前にもこのような仕事をしようとしたら困ったことがありました。 交代制にすれば、各自がもう片方が終わるのを待つのに多くの時間を費やすことになります。しかし、それぞれ自分のコピーを編集して、メールで添付ファイルを送ったりすると情報の喪失や上書き、複製などといった問題が起こります。

:::::::::::::::::::::::::::::::::::::::::: prereq
同僚が[バーション管理](learners/reference.md#version-control)を使って作業を管理することを勧めました。 バージョン管理はファイルを送り返すよりも優れています：

## Prerequisites
- 本当に消そうとしない限り、バージョン管理に入れらた（「コミットされた」）ものが失われることはありません。 古いバージョンのファイルはすべて保存されているため、特定の日に誰が何を書き込んだのか、特定の結果を生成するためにどのバージョンのプログラムが使用されたのかなど、正確に確認することが可能です。

In this lesson we use Git from the Unix Shell.
Some previous experience with the shell is expected,
*but isn't mandatory*.
- 誰が何をいつ変更したのかという記録があるため、後に問題が生じた場合、連絡するべき人が分かる上に必要に応じて「元に戻す」機能のように、以前のバージョンに戻すことができます。

- 同じプロジェクトで複数の人が協力し合う場合、間違って誰かの変更を見落としたり上書きしたりする可能性があります。 バージョン管理システムは、二つの変更点の間に不一致があった場合、自動的にユーザーに知らせてくれます。

::::::::::::::::::::::::::::::::::::::::::::::::::
バージョン管理を使うことによって得をするのはチームだけではありません: 個人で作業をしている研究者にもメリットがあります。 何が、いつ、何故変わったのかを記録しておくことは、後で昔のプロジェクトを見返すことになった場合などに（例えば、1年後、プロジェクトの詳細を忘れてしまった時などに）、非常に便利です。

バージョン管理は、デジタル世界における実験ノートです。
専門家が、自分が行ったことを記録し、
他の人々と共同作業を行うために使用するものです。 大規模なソフトウェア開発
プロジェクトはすべてGit に依存しており、ほとんどのプログラマーは小さな仕事
でも使用しています。 書籍、論文、小規模なデータセット、時間の経過とともに変化するもの、
共有する必要があるものは、バージョン管理システムに保存することができるし、そう**すべき**です。

:::::::::::::::::::::::::::::::::::::::::: prereq

## 予備知識

このレッスンでは、UnixシェルからGitを使います。
シェルの使用経験があることが望ましいですが、_必須ではありません_。

::::::::::::::::::::::::::::::::::::::::::::::::::
4 changes: 2 additions & 2 deletions md5sum.txt
View file
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
"file" "checksum" "built" "date"
"CODE_OF_CONDUCT.md" "aa54988020ee279c8375831ccd9c229f" "site/built/CODE_OF_CONDUCT.md" "2023-11-21"
"LICENSE.md" "b24ebbb41b14ca25cf6b8216dda83e5f" "site/built/LICENSE.md" "2023-11-21"
"LICENSE.md" "a28efe88838e3073f3f6db11bc125754" "site/built/LICENSE.md" "2023-11-21"
"config.yaml" "b6d9ed3e5970de3643d8c1edf24aae9a" "site/built/config.yaml" "2023-11-21"
"index.md" "a0bf9198af03d79145509a9fd132ab8d" "site/built/index.md" "2023-11-21"
"index.md" "5fba22f4ccdf526028f9782ee580cd59" "site/built/index.md" "2023-11-21"
"episodes/01-basics.md" "9537209793cae03b3192a178f7806bb1" "site/built/01-basics.md" "2023-11-21"
"episodes/02-setup.md" "3429667bbb04a9eedda7be169cbadffd" "site/built/02-setup.md" "2023-11-21"
"episodes/03-create.md" "80ca2f6dfa26d0f44c576df62349d719" "site/built/03-create.md" "2023-11-21"
Expand Down

0 comments on commit 490b971

Please sign in to comment.