docs: add data-analytics/general areas; update README, labels, labeler, CODEOWNERS, workflows, templates

Author: yatharthranjan

.github/CODEOWNERS

@@ -10,6 +10,10 @@ rfcs/platform/**  @yatharthranjan @afolarin @baixiac @mpgxvii @pvannierop
 rfcs/backend/**   @yatharthranjan @afolarin @mpgxvii @pvannierop @this-Aditya @ewelinagr
 rfcs/mobile/**    @mpgxvii @this-Aditya @ec18130 @peyman-mohtashami
 
+# New areas
+rfcs/data-analytics/**  @afolarin @Hsankesara 
+rfcs/general/**         @yatharthranjan @afolarin @mpgxvii @pvannierop
+
 # GitHub metadata and workflows
 .github/** @radar-base/admins
 

.github/ISSUE_TEMPLATE/pre-rfc-discussion.yml

@@ -31,6 +31,19 @@ body:
     attributes:
       label: Stakeholders
       description: Teams/roles who should be involved
+  - type: dropdown
+    id: area
+    attributes:
+      label: Area
+      description: Select the primary area for this discussion
+      options:
+        - platform
+        - backend
+        - mobile
+        - data-analytics
+        - general
+    validations:
+      required: true
   - type: checkboxes
     id: readiness
     attributes:

.github/PULL_REQUEST_TEMPLATE.md

@@ -12,7 +12,7 @@ Checklist
 - [ ] Added to index table in `README.md`
 - [ ] Considered alternatives and documented open questions
 - [ ] Applied appropriate status label (one of: draft, accepted, rejected, superseded, implemented)
-- [ ] Applied area/type labels as relevant (e.g., platform, backend, mobile, privacy; design, process)
+- [ ] Applied area/type labels as relevant (e.g., platform, backend, mobile, data-analytics, general, privacy; design, process)
 
 Reviewers
 ---------

.github/auto-assign.yml

@@ -35,4 +35,16 @@ filter:
       - ec18130
       - peyman-mohtashami
 
+  - label: "area: data-analytics"
+    reviewers:
+      - afolarin
+      - Hsankesara
+
+  - label: "area: general"
+    reviewers:
+      - yatharthranjan
+      - afolarin
+      - mpgxvii
+      - pvannierop
+
 

.github/labeler.yml

@@ -12,4 +12,10 @@ docs:
 "area: mobile":
   - rfcs/mobile/**
 
+"area: data-analytics":
+  - rfcs/data-analytics/**
+
+"area: general":
+  - rfcs/general/**
+
 

.github/labels.yml

@@ -41,6 +41,14 @@
   color: d93f0b
   description: Mobile apps and SDKs
 
+- name: area: data-analytics
+  color: 0e8a16
+  description: Data pipelines, warehousing, BI, metrics, experimentation
+
+- name: area: general
+  color: 1f6feb
+  description: Cross-cutting or domain-agnostic RFCs
+
 - name: area: privacy
   color: 0b8769
   description: Security, privacy, compliance

.github/workflows/required-area-labels.yml

@@ -15,10 +15,10 @@ jobs:
         with:
           mode: minimum
           count: 1
-          labels: "area: platform,area: backend,area: mobile"
+          labels: "area: platform,area: backend,area: mobile,area: data-analytics,area: general"
           add_comment: true
           message: |
             This PR is missing an area label. Please add at least one of:
-            area: platform | area: backend | area: mobile
+            area: platform | area: backend | area: mobile | area: data-analytics | area: general
 
 

README.md

@@ -9,10 +9,11 @@ Quick start
 -----------
 1. Fork this repository.
 2. Create a new branch for your RFC.
-3. Copy `rfcs/0000-template.md` to a new file `rfcs/NNNN-your-title.md` where `NNNN` is the next available RFC number. Place it under an area folder if applicable (e.g., `rfcs/platform/NNNN-your-title.md`).
+3. Copy `rfcs/0000-template.md` to a new file `rfcs/NNNN-your-title.md` where `NNNN` is the next available RFC number. Place it under an area folder if applicable (e.g., `rfcs/platform/NNNN-your-title.md`, `rfcs/backend/NNNN-your-title.md`, `rfcs/mobile/NNNN-your-title.md`, `rfcs/data-analytics/NNNN-your-title.md`, or `rfcs/general/NNNN-your-title.md`).
 4. Fill in all sections.
 5. Open a Pull Request using the provided template.
 6. Apply labels: one `status:` label and at least one `area:` label (see below). Labels are auto-suggested based on file paths.
+7. Link any related issues or discussions directly in the RFC body, such as Pre-RFC discussions (e.g., `RADAR-base/<repo>#<123>`) using the `Discussion` field in the RFC template.
 
 Lifecycle
 ---------
@@ -36,9 +37,9 @@ The RFC process is facilitated by the RADAR-base maintainers. See `CONTRIBUTING.
 
 Areas and ownership
 -------------------
-- Area folders: `rfcs/platform/`, `rfcs/backend/`, `rfcs/mobile/`
+- Area folders: `rfcs/platform/`, `rfcs/backend/`, `rfcs/mobile/`, `rfcs/data-analytics/`, `rfcs/general/`
 - CODEOWNERS: PRs touching these folders auto-request domain reviewers
-- Labels: use one of `area: platform`, `area: backend`, `area: mobile`
+- Labels: use one of `area: platform`, `area: backend`, `area: mobile`, `area: data-analytics`, `area: general`
 
 Status and label requirements
 -----------------------------