Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Turkish language localization #2777

Merged
merged 7 commits into from
Nov 23, 2019
Merged
Show file tree
Hide file tree
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions locale/tr/404.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
---
layout: page.hbs
permalink: false
title: 404
---

## 404: Sayfa bulunamadı

### ENOENT: Böyle bir dosya ya da dizin yok
57 changes: 57 additions & 0 deletions locale/tr/about/community.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,57 @@
---
title: Community Committee
layout: about.hbs
---

# Community Committee

The Community Committee (CommComm) is a top-level committee in the Node.js Foundation. The CommComm has authority over outward-facing community outreach efforts, including:

* Community [Evangelism](https://github.com/nodejs/evangelism)
* Education Initiatives
* Cultural Direction of Node.js Foundation
* Community Organization Outreach
* Translation and Internationalization
* Project Moderation/Mediation
* Public Outreach and [Publications](https://medium.com/the-node-js-collection)

There are four types of involvement with the Community Committee:

* A **Contributor** is any individual creating or commenting on an issue or pull request.
* A **Collaborator** is a contributor who has been given write access to the repository
* An **Observer** is any individual who has requested or been requested to attend a CommComm meeting. It is also the first step to becoming a Member.
* A **Member** is a collaborator with voting rights who has met the requirements of participation and voted in by the CommComm voting process.

For the current list of Community Committee members, see the project's [README.md](https://github.com/nodejs/community-committee).

## Contributors and Collaborators

It is the mission of CommComm to further build out the Node.js Community. If you're reading this, you're already a part of that community – and as a part of the Node.js Community, we'd love to have your help!

The [nodejs/community-committee](https://github.com/nodejs/community-committee) GitHub repository is a great place to start. Check out the [issues labeled "Good first issue"](https://github.com/nodejs/community-committee/labels/good%20first%20issue) to see where we're looking for help. If you have your own ideas on how we can engage and build the community, feel free to open your own issues, create pull requests with improvements to our existing work, or help us by sharing your thoughts and ideas in the ongoing discussions we're having in GitHub.

You can further participate in our ongoing efforts around community building - like localization, evangelism, the Node.js Collection, and others - by digging into their respective repositories and getting involved!

Before diving in, please be sure to read the [Collaborator Guide](https://github.com/nodejs/community-committee/blob/master/governance/COLLABORATOR_GUIDE.md).

If you're interested in participating in the Community Committee as a committee member, you should read the section below on **Observers and Membership**, and create an issue asking to be an Observer in our next Community Committee meeting. You can find a great example of such an issue [here](https://github.com/nodejs/community-committee/issues/142).

## Observers and Membership

If you're interested in becoming more deeply involved with the Community Committee and its projects, we encourage you to become an active observer, and work toward achieving member status. To become a member you must:

1. Attend the bi-weekly meetings, investigate issues tagged as good first issue, file issues and pull requests, and provide insight via GitHub as a contributor or collaborator.
2. Request to become an Observer by filing an issue. Once added as an Observer to meetings, we will track attendance and participation for 3 months, in accordance with our governance guidelines. You can find a great example of such an issue [here](https://github.com/nodejs/community-committee/issues/142).
3. When you meet the 3 month minimum attendance, and participation expectations, the CommComm will vote to add you as a member.

Membership is for 6 months. The group will ask on a regular basis if the expiring members would like to stay on. A member just needs to reply to renew. There is no fixed size of the CommComm. However, the expected target is between 9 and 12. You can read more about membership, and other administrative details, in our [Governance Guide](https://github.com/nodejs/community-committee/blob/master/GOVERNANCE.md).

Regular CommComm meetings are held bi-monthly in a Zoom video conference, and broadcast live to the public on YouTube. Any community member or contributor can ask that something be added to the next meeting's agenda by logging a GitHub Issue.

Meeting announcements and agendas are posted before the meeting begins in the organization's [GitHub issues](https://github.com/nodejs/community-committee/issues). You can also find the regularly scheduled meetings on the [Node.js Calendar](https://nodejs.org/calendar). To follow Node.js meeting livestreams on YouTube, subscribe to the Node.js Foundation [YouTube channel](https://www.youtube.com/channel/UCQPYJluYC_sn_Qz_XE-YbTQ). Be sure to click the bell to be notified of new videos!

## Consensus Seeking Process

The CommComm follows a [Consensus Seeking](https://en.wikipedia.org/wiki/Consensus-seeking_decision-making) decision making model.

When an agenda item has appeared to reach a consensus, the moderator will ask "Does anyone object?" as a final call for dissent from the consensus. If a consensus cannot be reached that has no objections then a majority wins vote is called. It is expected that the majority of decisions made by the CommComm are via a consensus seeking process and that voting is only used as a last-resort.
38 changes: 38 additions & 0 deletions locale/tr/about/governance.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
---
title: Project Governance
layout: about.hbs
---

# Project Governance

## Consensus Seeking Process

The Node.js project follows a [Consensus Seeking][] decision making model.

## Collaborators

The [nodejs/node][] core GitHub repository is maintained by the Collaborators
who are added by the Technical Steering Committee ([TSC][]) on an ongoing basis.

Individuals making significant and valuable contributions are made Collaborators
and given commit-access to the project. These individuals are identified by the
TSC and their nomination is discussed with the existing Collaborators.

For the current list of Collaborators, see the project's [README.md][].

A guide for Collaborators is maintained at [COLLABORATOR_GUIDE.md][].

## Top Level Committees

The project is governed jointly by the [Technical Steering Committee (TSC)][]
which is responsible for high-level guidance of the project, and the
[Community Committee (CommComm)][] which is responsible for guiding and
extending the Node.js community.

[COLLABORATOR_GUIDE.md]: https://github.com/nodejs/node/blob/master/COLLABORATOR_GUIDE.md
[Community Committee (CommComm)]: https://github.com/nodejs/community-committee/blob/master/Community-Committee-Charter.md
[Consensus Seeking]: https://en.wikipedia.org/wiki/Consensus-seeking_decision-making
[README.md]: https://github.com/nodejs/node/blob/master/README.md#current-project-team-members
[Technical Steering Committee (TSC)]: https://github.com/nodejs/TSC/blob/master/TSC-Charter.md
[TSC]: https://github.com/nodejs/TSC
[nodejs/node]: https://github.com/nodejs/node
68 changes: 68 additions & 0 deletions locale/tr/about/index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,68 @@
---
layout: about.hbs
title: Hakkında
trademark: Trademark
---

# Node.js® Hakkında

Asenkron, olay tabanlı JavaScript çalışma ortamı olan Node.js, ölçeklenebilir ağ uygulamaları
oluşturmak için tasarlanmıştır. Aşağıdaki "hello world" örneğinde, birçok bağlantı
aynı anda ele alınabilir. Her bağlantıda geri çağırım başlatılır,
ancak yapılacak hiçbir iş yoksa Node.js uyuyacaktır.

```javascript
const http = require('http');

const hostname = '127.0.0.1';
const port = 3000;

const server = http.createServer((req, res) => {
res.statusCode = 200;
res.setHeader('Content-Type', 'text/plain');
res.end('Hello World\n');
});

server.listen(port, hostname, () => {
console.log(`Server running at http://${hostname}:${port}/`);
});
```

Bu, işletim sistemi iş parçacıklarının(thread) kullanıldığı günümüzün yaygın
eşzamanlılık modelinin aksinedir. İş parçacığı tabanlı ağ iletişimi nispeten
yetersiz ve kullanmak için zor. Ayrıca, Node.js kullanıcıları işlemlerin
kilitlenmesinden endişe duymaz, çünkü kilitler yoktur. Node.js'deki neredeyse
hiçbir işlev doğrudan G/Ç gerçekleştirmez, bu yüzden işlem hiç bloklanmaz.
Hiçbir şey engellemediğinden, ölçeklenebilir sistemlerin Node.js'de geliştirilmesi çok makul.

Bu dilin bir kısmı alışılmadık geldiyse, [Blocking vs. Non-Blocking][] hakkında tam bir makale mevcut.

---

Node.js, Ruby'nin [Event Machine][] ve Python'ın [Twisted][] gibi sistemlerine
tasarım olarak benzer ve bunlardan etkilenmiştir. Node.js olay modelini biraz
daha ileri götürür. [event loop][]'u bir kütüphane yerine çalışma ortamı yapısı
olarak sunar. Diğer sistemlerde, genellikle event-loop'u başlatan bir blokeli
çağırım vardır. Tipik olarak, davranış betiğin başlangıcındaki geri çağırımlar
vasıtasıyla tanımlanmıştır ve sonunda bir sunucu `EventMachine::run()` gibi bir
blokeli çağırım vasıtasıyla başlatılır. Node.js'de böyle bir olay-dongüsünü-başlat çağırımı
yoktur. Node.js girdi betiğini yürüttükten sonra basitçe olay döngüsüne girer.
Node.js yerine getirilecek daha fazla geri çağırım kalmadığı zaman olay döngüsünden çıkar.
Bu davranış internet tarayıcısındaki JavaScript gibidir - olay döngüsü kullanıcıdan gizlenmiştir.

HTTP, akış ve düşük gecikme süresi göz önünde bulundurularak tasarlanan Node.js'de birinci sınıf bir vatandaştır.
Bu, Node.js'yi bir web kütüphanesinin veya çatının oluşturulması için çok uygun yapar.

Node.js'nin iş parçacıkları olmadan tasarlanmış olması, ortamınızdaki
birden çok çekirdeğin avantajlarından yararlanamayacağınız anlamına gelmez.
Çocuk işlemler [`child_process.fork()`][] API'miz kullanılarak oluşturulabilirler
ve birbirleriyle iletişim kurması kolay olacak şekilde tasarlanmışlardır.
Aynı arayüz üzerine kurulu [`cluster`][] modülü, çekirdekleriniz üzerindeki
yük dengelemesini sağlamak için işlemler arasında soketleri paylaşmanıza olanak tanır.

[Blocking vs. Non-Blocking]: /en/docs/guides/blocking-vs-non-blocking/
[`child_process.fork()`]: https://nodejs.org/api/child_process.html#child_process_child_process_fork_modulepath_args_options
[`cluster`]: https://nodejs.org/api/cluster.html
[event loop]: /en/docs/guides/event-loop-timers-and-nexttick/
[Event Machine]: https://github.com/eventmachine/eventmachine
[Twisted]: https://twistedmatrix.com/trac/
Loading