Improve Persian translation

locale/.vs/VSWorkspaceState.json

@@ -0,0 +1,6 @@
+{
+  "ExpandedNodes": [
+    ""
+  ],
+  "PreviewInSolutionExplorer": false
+}

locale/fa/blog/advisory-board/advisory-board-update.md

@@ -0,0 +1,108 @@
+---
+title: Advisory Board Update
+date: 2014-12-03T18:00:00.000Z
+author: Timothy J Fontaine
+slug: advisory-board-update
+layout: blog-post.hbs
+---
+
+A lot has been happening in Node.js, so I wanted to bring everyone up to date on
+where we are with regards to the advisory board, its working groups, and the
+release of v0.12.
+
+The interim [advisory
+board](https://www.joyent.com/blog/node-js-advisory-board) has met three times
+since its creation. You can find the minutes from the advisory board meetings
+here: [https://nodejs.org/en/about/advisory-board/](https://nodejs.org/en/about/advisory-board/). As
+we have more meetings and minutes, we will announce the dates and times for
+those meeting and their minutes here on the blog. The next meeting is this
+Thursday December 4th, at 1:30PM PST. We're looking to collect as much feedback
+and input from as many representatives of the community as we can, so it's
+important that we keep everyone up to date as much as possible.
+
+The interim advisory board has been working through a series of topics (in
+general meetings as well as working groups) to further hone the scope of the
+board, as well as define the structure that the advisory board will use to
+conduct its meetings. Everyone on the board wants to make sure we're being as
+transparent as possible, so let me describe how things operate so far. The
+board is using a traditional two conference call structure, a public portion
+that is recorded and open for anyone to join, and a private portion that is
+only for board members.
+
+The public portion is meant to provide an update of what happened in the
+previous meeting, as well as the status of action items from the previous
+meeting. At the end of each public session is a open comment section, where
+listeners are able to ask questions and the advisory board can respond.
+
+Following the public portion the board dials into the private conference,
+further discussion happens during this time around specific agenda items,
+working groups providing updates, and facilitating conversations about those
+topics. These conversations are open and frank, and their content is recorded
+in the minutes. Those minutes are then published a few days after the meeting
+in the GitHub repository
+[https://github.com/joyent/nodejs-advisory-board](https://github.com/joyent/nodejs-advisory-board),
+as well as on the website
+[https://nodejs.org/en/about/advisory-board/](https://nodejs.org/en/about/advisory-board/).
+
+There are a few working groups so far, for instance one is focused on making
+sure the membership of the board is representative of the community Node.js
+serves. While the board was initially bootstrapped with its existing
+membership, we want to quickly move to a model that fully represents our
+community. We want the board to represent the broadest spectrum of our
+community, that also enables the board to move swiftly and make progress.
+
+Another working group is having a conversation about governance. This includes
+topics like what is the team that makes decisions for Node.js, how do you
+become a member of that team, how does that team set the roadmap for the
+project, and how does that team makes decisions.
+
+One thing that we all agree on, is that we're not going to be using the
+Benevolent Dictator model. In fact, recently the project hasn't been operating
+that way. We can be more clear about that in our
+[documentation](https://nodejs.org/en/about/organization). We all agree we want
+a healthy and vibrant team, a team focused on making progress for Node.js, not
+for progress's sake, but for the betterment of the software project and the
+community we serve. We also agree that this means that there should be
+consensus among the team. The conversation has been fruitful, and is on going,
+we're continuing to work through the finer points of how much consensus we
+need.
+
+I want to take a moment to describe what consensus means in this context. The
+consensus model is about accountability. Accountability for the changes being
+integrated into the project, accountability for documentation, and
+accountability for releases. While members of the team are responsible for
+subsystems or features of Node.js, everyone reviews each others changes. They
+make sure to understand the impact on their relevant responsibilities.
+
+The goal of the team, especially that of the project lead, is to drive
+consensus and ensure accountability. This means asking critical questions and
+being able to answer them specifically and succinctly, for example:
+
+ * What are we trying to solve with this change?
+ * Does this change effectively solve for this problem?
+ * Does this API have a consumer?
+ * Does this API reach the broadest amount of use cases?
+ * Is this API supportable?
+ * Does this change have adverse effects on other subsystems or use cases (and is that acceptable)?
+ * Does this change have tests that verify its operation, now and in the future?
+ * Does this change pass our style guidelines?
+ * Does this change pass our integration tests for the matrix of our supported configurations?
+   - For instance: ia32 and x64 for Windows, Linux, OSX, SmartOS
+
+These are just some of the questions, and while the questions are not unusual
+or unique to Node.js, they are still important.
+
+Finally, we are very close to releasing v0.12, there's only one major patch
+we're waiting to land. Once that's done we'll be releasing v0.11.15 as a
+release candidate. Assuming no severe issues are filed against v0.11.15 we will
+be going live with v0.12 about two weeks after the v0.11.15 release.
+
+If you have questions for the advisory board you can email
+[[email protected]](mailto:[email protected]) or file an issue on
+its repository
+[https://github.com/joyent/nodejs-advisory-board](https://github.com/joyent/nodejs-advisory-board).
+Thanks for all of your continued contributions to Node.js, in the form of
+[filing issues](https://github.com/joyent/node/issues), [submitting pull
+requests](https://github.com/joyent/node/pulls), and publishing your modules.
+Node.js is lucky to have such an enthusiastic and engaged community, and we're
+excited to be working with you on the future of Node.js.

locale/fa/blog/advisory-board/index.md

@@ -0,0 +1,6 @@
+---
+title: Advisory Board
+layout: category-index.hbs
+listing: true
+robots: noindex, follow
+---

locale/fa/blog/advisory-board/listening-to-the-community.md

@@ -0,0 +1,22 @@
+---
+title: Listening to the Community
+date: 2014-12-05T21:30:00.000Z
+author: Advisory Board
+slug: listening-to-the-community
+layout: blog-post.hbs
+---
+
+We assembled the Node.js Advisory Board (AB) to listen to the community and
+make the necessary changes to have a unified direction for Node.js, a
+passionate group of developers, a vibrant ecosystem of product and service
+providers, and a satisfied user base.  Over the last month we have made great
+progress on an open governance model, API standards, IP management, and
+transparency to ensure the project is community-driven.  These efforts
+explicitly target helping resolve conflicts and with the goal of moving the
+community forward together.  It is important that we understand voices of
+dissent and frustration and work together to build the greater ecosystem.  We
+are committed to this goal.
+
+Node.js remains the trusted platform that users rely on for creative projects
+and to drive business goals.  The v0.12 release will ship shortly and the
+project team is already engaged in discussions about the next release.

locale/fa/blog/announcements/apigee-rising-stack-yahoo.md

@@ -0,0 +1,38 @@
+---
+title: Apigee, RisingStack and Yahoo Join the Node.js Foundation
+date: 2015-12-08T12:00:00.000Z
+status: publish
+category: Annoucements
+slug: apigee-rising-stack-yahoo
+layout: blog-post.hbs
+---
+
+> New Silver Members to Advance Node.js Growth and Enterprise Adoption
+
+**NODE.JS INTERACTIVE 2015, PORTLAND, OR.** — [The Node.js Foundation](https://foundation.nodejs.org/), a community-led and industry-backed consortium to advance the development of the Node.js platform, today announced Apigee, RisingStack and Yahoo are joining the Foundation as Silver Members to build and support the Node.js platform. With over 2 million downloads per month, Node.js is the runtime of choice for developers building everything from enterprise applications to Industrial IoT.
+
+The Node.js Foundation members work together alongside the community to help grow this diverse technology for large financial services, web-scale, cloud computing companies, and more. The newly added [Long-Term Support](https://nodejs.org/en/blog/release/v4.2.0/) release version 4.0 is just one of the many initiatives from the Foundation, which addresses the needs of enterprises that are using Node.js in more complex production environments, and signals the growing maturity of the technology.
+
+“We continue to welcome new Node.js Foundation members that are committed to providing the financial and technical resources needed to ensure the technology continues to evolve, while nurturing the community and ecosystem at the same time,” said Danese Cooper, Chairperson of the Node.js Foundation Board. “We are excited to have Apigee, RisingStack, and Yahoo on board to help grow the diversity of the platform and the community.”
+
+The new members are joining just in time for the inaugural Node.js Interactive event taking place today and tomorrow in Portland, OR. The conference focuses on frontend, backend and IoT technologies, and the next big initiatives for the Node.js Foundation. It includes more than 50 tutorials, sessions and keynotes. To stream the event, go to [http://events.linuxfoundation.org/events/node-interactive/program/live-video-stream](http://events.linuxfoundation.org/events/node-interactive/program/live-video-stream).
+
+More information about the newest Node.js Foundation members:
+
+[Apigee](https://apigee.com/about/) provides an intelligent API platform for digital businesses. Headquartered in San Jose, California, Apigee’s software supports some of the largest global enterprises. Developers can use the Node.js software platform to build highly customized application programming interfaces (APIs) and apps in the [Apigee API management platform](http://apigee.com/about/products/api-management). The integration of the Node.js technology allows developers to use code to create specialized APIs in Apigee, while utilizing the huge community of JavaScript developers.
+
+“We want to provide to the developer community the best platform for building today’s modern apps and APIs,,” said Ed Anuff, executive vice president of strategy at Apigee. “We are committed to the advancement of Node.js and look forward to continuing to utilize the strengths and further possibilities of the technology. The Node.js Foundation provides an excellent place for us to help push this technology to become even better for our developers that use it everyday.”
+
+[RisingStack](https://risingstack.com/) was founded in 2014 by Gergely Nemeth and Peter Marton as a full stack JavaScript consulting company. It provides help with digital transitioning to Node.js and offers a microservice monitoring tool called [Trace](http://trace.risingstack.com/). RisingStack also contributes to several open source projects, and engages the developer community via a popular JavaScript/DevOps [engineering blog](https://blog.risingstack.com/), with a tremendous amount of long reads.
+
+“Node.js is extremely important in JavaScript development, and we have experienced a rapid rise of interest in the technology from enterprises.” said Gergely Nemeth, CEO and Co-Founder of RisingStack. “Our business was established to support this growing technology, and we are very excited to join the Node.js Foundation to help broaden this already active community and continue its growth through open governance.”
+
+Yahoo is a guide focused on informing, connecting and entertaining its users. By creating highly personalized experiences for its users, Yahoo keeps people connected to what matters most to them, across devices and around the world. In turn, Yahoo creates value for advertisers by connecting them with the audiences that build their businesses.
+
+“Joining the Node.js Foundation underscores our deep appreciation for the Node.js community, and our commitment to drive its health and growth,” said Preeti Somal, vice president of engineering, Yahoo. “As a technology pioneer with a deep legacy of JavaScript expertise and a strong commitment to open source, we saw the promise of Node.js from the start and have since scaled to become one of the industry’s largest deployments. We embrace Node.js’s evolution and encourage our developers to be contributing citizens of the Open Source community.”
+
+Additional Resources
+* Learn more about the [Node.js Foundation](https://foundation.nodejs.org/) and get involved with [the project](https://nodejs.org/en/get-involved/).
+
+About Node.js Foundation
+Node.js Foundation is a collaborative open source project dedicated to building and supporting the Node.js platform and other related modules. Node.js is used by tens of thousands of organizations in more than 200 countries and amasses more than 2 million downloads per month. It is the runtime of choice for high-performance, low latency applications, powering everything from enterprise applications, robots, API engines, cloud stacks and mobile websites. The Foundation is made up of a diverse group of companies including Platinum members Famous, IBM, Intel, Joyent, Microsoft, PayPal and Red Hat. Gold members include GoDaddy, NodeSource and Modulus/Progress Software, and Silver members include Apigee, Codefresh, DigitalOcean, Fidelity, Groupon, nearForm, npm, RisingStack, Sauce Labs, SAP, StrongLoop (an IBM company), YLD!, and Yahoo. Get involved here: [https://nodejs.org](https://nodejs.org/en/).