devicetree-spec.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Grant Likely
	<grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	Grant Likely
	<grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Subject: [DTSpec PATCH] Create FAQ.md
Date: Wed, 25 May 2016 12:36:36 +0100	[thread overview]
Message-ID: <1464176196-18056-1-git-send-email-grant.likely@linaro.org> (raw)

Copy the FAQ from the website to the main repository so any developer can update it.

Signed-off-by: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
---
 FAQ.md | 45 +++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 45 insertions(+)
 create mode 100644 FAQ.md

diff --git a/FAQ.md b/FAQ.md
new file mode 100644
index 000000000000..0d8a032cdc23
--- /dev/null
+++ b/FAQ.md
@@ -0,0 +1,45 @@
+# FAQ
+
+## Getting the Specification
+
+### Where can I find the latest version of the Devicetree Specification
+
+You can always find the latest released, as well as all older releases,
+in our GitHub repository:
+
+[Devicetree Specification release repository](https://github.com/devicetree-org/devicetree-specification-released)
+
+### How often is a new specification released
+
+We're planning to make a v1.0 release by end of August, 2016,
+which will be up to date with current core DT bindings used by the Linux kernel.
+
+A second major release is planned for December 2016 to cover new features.
+
+## Governance
+
+### Do I need to be a member to comment and send patches for the Spec?
+
+No. Changes to the spec are proposed and discussed on a 
+[public mailing list](http://vger.kernel.org/vger-lists.html#devicetree-spec)
+and the source document is hosted in the
+[Devicetree Specification](https://github.com/devicetree-org/devicetree-specification)
+project on GitHub.
+
+You can find details about the mailing list and submission process in the [Readme](README.md) file.
+
+### What will membership give me?
+
+Membership gives you a seat on Technical Steering Committee (TSC). 
+The TSC is responsible for handling governance issues, 
+managing the technical goals, release schedule, 
+and helping to define vision for future versions of the spec.
+
+### How is Linaro and devicetree.org connected?
+
+Linaro kick started this process and is hosting devicetree.org under its organisation. 
+[devicetree.org](http://devicetree.org) membership fees are associated with devicetree.org
+only and not with Linaro membership.
+The membership proceeds go towards the defraying of Linaro’s costs for hosting devicetree.org.
+
+If you have useful FAQs you would like to see here, please contact us through the mailing list
-- 
2.7.4

                 reply	other threads:[~2016-05-25 11:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1464176196-18056-1-git-send-email-grant.likely@linaro.org \
    --to=grant.likely-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
    --cc=devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).