Add basic templates

EXPLAINER.md

@@ -0,0 +1,135 @@
+# [Title]
+
+## Authors:
+
+- [Author 1]
+- [Author 2]
+- [etc.]
+
+## Participate
+- https://github.com/antifraudcg/proposals/issues
+
+## Table of Contents [if the explainer is longer than one printed page]
+
+[You can generate a Table of Contents for markdown documents using a tool like [doctoc](https://github.com/thlorenz/doctoc).]
+
+<!-- START doctoc generated TOC please keep comment here to allow auto update -->
+<!-- END doctoc generated TOC please keep comment here to allow auto update -->
+
+## Introduction
+
+[The "executive summary" or "abstract".
+Explain in a few sentences what the goals of the project are,
+and a brief overview of how the solution works.
+This should be no more than 1-2 paragraphs.]
+
+## Goals [or Motivating Use Cases, or Scenarios]
+
+[What is the **end-user need** which this project aims to address?]
+
+## Non-goals
+
+[If there are "adjacent" goals which may appear to be in scope but aren't,
+enumerate them here. This section may be fleshed out as your design progresses and you encounter necessary technical and other trade-offs.]
+
+## User research
+
+[If any user research has been conducted to inform the design choices presented
+discuss the process and findings.
+We strongly encourage that API designers consider conducting user research to
+verify that their designs meet user needs and iterate on them,
+though we understand this is not always feasible.]
+
+## [API 1]
+
+[For each related element of the proposed solution - be it an additional JS method, a new object, a new element, a new concept etc., create a section which briefly describes it.]
+
+```js
+// Provide example code - not IDL - demonstrating the design of the feature.
+
+// If this API can be used on its own to address a user need,
+// link it back to one of the scenarios in the goals section.
+
+// If you need to show how to get the feature set up
+// (initialized, or using permissions, etc.), include that too.
+```
+
+[Where necessary, provide links to longer explanations of the relevant pre-existing concepts and API.
+If there is no suitable external documentation, you might like to provide supplementary information as an appendix in this document, and provide an internal link where appropriate.]
+
+[If this is already specced, link to the relevant section of the spec.]
+
+[If spec work is in progress, link to the PR or draft of the spec.]
+
+## [API 2]
+
+[etc.]
+
+## Key scenarios
+
+[If there are a suite of interacting APIs, show how they work together to solve the key scenarios described.]
+
+### Scenario 1
+
+[Description of the end-user scenario]
+
+```js
+// Sample code demonstrating how to use these APIs to address that scenario.
+```
+
+### Scenario 2
+
+[etc.]
+
+## Detailed design discussion
+
+### [Tricky design choice #1]
+
+[Talk through the tradeoffs in coming to the specific design point you want to make.]
+
+```js
+// Illustrated with example code.
+```
+
+[This may be an open question,
+in which case you should link to any active discussion threads.]
+
+### [Tricky design choice 2]
+
+[etc.]
+
+## Considered alternatives
+
+[This should include as many alternatives as you can,
+from high level architectural decisions down to alternative naming choices.]
+
+### [Alternative 1]
+
+[Describe an alternative which was considered,
+and why you decided against it.]
+
+### [Alternative 2]
+
+[etc.]
+
+## Stakeholder Feedback / Opposition
+
+[Implementors and other stakeholders may already have publicly stated positions on this work. If you can, list them here with links to evidence as appropriate.]
+
+- [Implementor A] : Positive
+- [Stakeholder B] : No signals
+- [Implementor C] : Negative
+
+[If appropriate, explain the reasons given by other implementors for their concerns.]
+
+## References & acknowledgements
+
+[Your design will change and be informed by many people; acknowledge them in an ongoing way! It helps build community and, as we only get by through the contributions of many, is only fair.]
+
+[Unless you have a specific reason not to, these should be in alphabetical order.]
+
+Many thanks for valuable feedback and advice from:
+
+- [Person 1]
+- [Person 2]
+- [etc.]

README.md

@@ -0,0 +1,6 @@
+# [Anti-Fraud Community Group](https://antifraudcg.github.io/) Templates
+
+This repository contains templates that can be used for items in the Anti-Fraud
+CG.
+
+* [**Explainer** Template](https://github.com/antifraudcg/template/blob/main/EXPLAINER.md) Based on the TAG's [explainer template](https://github.com/w3ctag/tag.w3.org/blob/main/explainers/index.md#explainer-template).

w3c.json

@@ -0,0 +1,6 @@
+{
+    "group": 134685,
+    "contacts": ["dvorak42"],
+    "repo-type": "others",
+    "policy": "open"
+}