fa: Init a new locale in Persian (#1866)

Create a new locale in Persian for more people speaking Persian and do contributions to that, based on the failure PR：#1844

Author: Maledong

locale/fa/404.md

@@ -0,0 +1,7 @@
+---
+layout: page.hbs
+permalink: false
+title: 404
+---
+## 404: Page could not be found
+### ENOENT: no such file or directory

locale/fa/about/community.md

@@ -0,0 +1,56 @@
+---
+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/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.

locale/fa/about/governance.md

@@ -0,0 +1,139 @@
+---
+title: Project Governance
+layout: about.hbs
+---
+# Project Governance
+
+## Technical Steering Committee
+
+The project is jointly governed by a Technical Steering Committee (TSC)
+which is responsible for high-level guidance of the project.
+
+The TSC has final authority over this project including:
+
+* Technical direction
+* Project governance and process (including this policy)
+* Contribution policy
+* GitHub repository hosting
+* Conduct guidelines
+* Maintaining the list of additional Collaborators
+
+Initial membership invitations to the TSC were given to individuals who
+had been active contributors, and who have significant
+experience with the management of the project. Membership is
+expected to evolve over time according to the needs of the project.
+
+For the current list of TSC members, see the project
+[README.md](https://github.com/nodejs/node/blob/master/README.md#tsc-technical-steering-committee).
+
+## Collaborators
+
+The [nodejs/node](https://github.com/nodejs/node) GitHub repository is
+maintained by the TSC and additional Collaborators who are added by the
+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 addition as
+Collaborators is discussed during the weekly TSC meeting.
+
+_Note:_ If you make a significant contribution and are not considered
+for commit-access, log an issue or contact a TSC member directly and it
+will be brought up in the next TSC meeting.
+
+Modifications of the contents of the nodejs/node repository are made on
+a collaborative basis. Anybody with a GitHub account may propose a
+modification via pull request and it will be considered by the project
+Collaborators. All pull requests must be reviewed and accepted by a
+Collaborator with sufficient expertise who is able to take full
+responsibility for the change. In the case of pull requests proposed
+by an existing Collaborator, an additional Collaborator is required
+for sign-off. Consensus should be sought if additional Collaborators
+participate and there is disagreement around a particular
+modification. See _Consensus Seeking Process_ below for further detail
+on the consensus model used for governance.
+
+Collaborators may opt to elevate significant or controversial
+modifications, or modifications that have not found consensus to the
+TSC for discussion by assigning the ***tsc-agenda*** tag to a pull
+request or issue. The TSC should serve as the final arbiter where
+required.
+
+For the current list of Collaborators, see the project
+[README.md](https://github.com/nodejs/node/blob/master/README.md#current-project-team-members).
+
+A guide for Collaborators is maintained in
+[COLLABORATOR_GUIDE.md](https://github.com/nodejs/node/blob/master/COLLABORATOR_GUIDE.md).
+
+## TSC Membership
+
+TSC seats are not time-limited.  There is no fixed size of the TSC.
+However, the expected target is between 6 and 12, to ensure adequate
+coverage of important areas of expertise, balanced with the ability to
+make decisions efficiently.
+
+There is no specific set of requirements or qualifications for TSC
+membership beyond these rules.
+
+The TSC may add additional members to the TSC by a standard TSC motion.
+
+A TSC member may be removed from the TSC by voluntary resignation, or by
+a standard TSC motion.
+
+Changes to TSC membership should be posted in the agenda, and may be
+suggested as any other agenda item (see "TSC Meetings" below).
+
+No more than 1/3 of the TSC members may be affiliated with the same
+employer.  If removal or resignation of a TSC member, or a change of
+employment by a TSC member, creates a situation where more than 1/3 of
+the TSC membership shares an employer, then the situation must be
+immediately remedied by the resignation or removal of one or more TSC
+members affiliated with the over-represented employer(s).
+
+## TSC Meetings
+
+The TSC meets weekly on a Google Hangout On Air. The meeting is run by
+a designated moderator approved by the TSC. Each meeting should be
+published to YouTube.
+
+Items are added to the TSC agenda which are considered contentious or
+are modifications of governance, contribution policy, TSC membership,
+or release process.
+
+The intention of the agenda is not to approve or review all patches.
+That should happen continuously on GitHub and be handled by the larger
+group of Collaborators.
+
+Any community member or contributor can ask that something be added to
+the next meeting's agenda by logging a GitHub Issue. Any Collaborator,
+TSC member or the moderator can add the item to the agenda by adding
+the ***tsc-agenda*** tag to the issue.
+
+Prior to each TSC meeting, the moderator will share the Agenda with
+members of the TSC. TSC members can add any items they like to the
+agenda at the beginning of each meeting. The moderator and the TSC
+cannot veto or remove items.
+
+The TSC may invite persons or representatives from certain projects to
+participate in a non-voting capacity. These invitees currently are:
+
+* A representative from [build](https://github.com/node-forward/build)
+  chosen by that project.
+
+The moderator is responsible for summarizing the discussion of each
+agenda item and sending it as a pull request after the meeting.
+
+## Consensus Seeking Process
+
+The TSC follows a
+[Consensus Seeking](http://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 an agenda item cannot reach a consensus, a TSC member can call for
+either a closing vote or a vote to table the issue to the next
+meeting. The call for a vote must be approved by a majority of the TSC
+or else the discussion will continue. Simple majority wins.

locale/fa/about/index.md

@@ -0,0 +1,69 @@
+---
+layout: about.hbs
+title: About
+trademark: Trademark
+---
+# About Node.js®
+
+As an asynchronous event driven JavaScript runtime, Node is designed to build
+scalable network applications. In the following "hello world" example, many
+connections can be handled concurrently. Upon each connection the callback is
+fired, but if there is no work to be done, Node will sleep.
+
+```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}/`);
+});
+```
+
+This is in contrast to today's more common concurrency model where OS threads
+are employed. Thread-based networking is relatively inefficient and very
+difficult to use. Furthermore, users of Node are free from worries of
+dead-locking the process, since there are no locks. Almost no function in Node
+directly performs I/O, so the process never blocks. Because nothing blocks,
+scalable systems are very reasonable to develop in Node.
+
+If some of this language is unfamiliar, there is a full article on
+[Blocking vs Non-Blocking][].
+
+---
+
+Node is similar in design to, and influenced by, systems like Ruby's
+[Event Machine][] or Python's [Twisted][]. Node takes the event model a bit
+further. It presents an [event loop][] as a runtime construct instead of as a library. In other systems there is always a blocking call to start the
+event-loop.
+Typically behavior is defined through callbacks at the beginning of a script
+and at the end starts a server through a blocking call like
+`EventMachine::run()`. In Node there is no such start-the-event-loop call. Node
+simply enters the event loop after executing the input script. Node exits the
+event loop when there are no more callbacks to perform. This behavior is like
+browser JavaScript — the event loop is hidden from the user.
+
+HTTP is a first class citizen in Node, designed with streaming and low latency
+in mind. This makes Node well suited for the foundation of a web library or
+framework.
+
+Just because Node is designed without threads, doesn't mean you cannot take
+advantage of multiple cores in your environment. Child processes can be spawned
+by using our [`child_process.fork()`][] API, and are designed to be easy to
+communicate with. Built upon that same interface is the [`cluster`][] module,
+which allows you to share sockets between processes to enable load balancing
+over your cores.
+
+[Blocking vs Non-Blocking]: https://nodejs.org/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]: https://nodejs.org/en/docs/guides/event-loop-timers-and-nexttick/
+[Event Machine]: https://github.com/eventmachine/eventmachine
+[Twisted]: http://twistedmatrix.com/