[GH-ISSUE #3447] [Governance] Consider transitioning the project to a dedicated GitHub Organization #1289

New issue

Open

opened 2026-10-16 21:03:48 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-16 21:03:48 +00:00

Owner

Originally created by @matbrgz on GitHub (Oct 14, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/3447

Before submitting

I searched the open and closed issues and pull requests for a related discussion.
I understand the contribution scope must be reviewed before integration; open questions are welcome here.
This discussion does not include credentials, private samples, or sensitive target data.

Decision needed

Would maintainers consider transitioning the project from the personal user account (morluto/rea) to a dedicated GitHub Organization (for example, rea-tools, aligning with the official https://rea.tools domain, or rea-project) to support team-based governance, scalable review workflows, and long-term sustainability?

Context and evidence

With over 213,000 GitHub stars, 52,000+ forks, and hundreds of active community contributors, REA has grown into one of the most prominent open-source AI reverse-engineering ecosystems. Currently, the repository is hosted under the personal account of @morluto.

While this structure worked well in early stages, hosting an ecosystem of this scale under a personal account introduces structural limitations:

Role-Based Access Control and Teams: Personal user accounts cannot create GitHub Teams. In an Organization, maintainers can define teams (e.g., @rea-tools/ghidra-maintainers, @rea-tools/triage, @rea-tools/security), enabling granular permissions and team-based review assignments without granting full repository write/admin access to individuals.
Review Routing & CODEOWNERS: As noted in #3445, native CODEOWNERS works best with organizational teams so review duties can rotate among specialists rather than pinging a single individual handle.
Project Continuity & Governance: Organizations provide multi-owner administration, mitigating single-point-of-failure risks and simplifying sponsorship/financial stewardship (e.g. GitHub Sponsors / Open Collective for organizations).
Multi-Repository Architecture: An organization cleanly groups related repositories under one umbrella (e.g., core rea, docs/website, separate provider bridges, or external skill packs).

Expected interaction with targets

No target interaction (documentation or usability only)

Migration safety

GitHub handles repository transfers seamlessly:

Existing clone URLs (git clone https://github.com/morluto/rea.git) and web URLs automatically redirect to the new organization namespace.
Existing GitHub Pages, releases, issues, and pull requests are fully preserved.

Options and tradeoffs

Option A (Dedicated Organization, e.g. rea-tools): Establish an organization matching the canonical website domain (rea.tools), transfer morluto/rea into it, and invite core maintainers as Organization Owners / Team Leads.
Option B (Retain Personal Namespace): Keep morluto/rea under the personal account and rely on individual collaborator permissions.

Verification readiness

Idea only; I need help defining checks

Success criteria and open questions

What are the core maintainers' views on formalizing an organization structure for the project at this stage of growth?

Originally created by @matbrgz on GitHub (Oct 14, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/3447 [![Type: Community / Governance](https://img.shields.io/badge/type-community_%2F_governance-lightgrey.svg?style=flat-square)](https://github.com/morluto/rea) [![Status: Proposed](https://img.shields.io/badge/status-proposed-blue.svg?style=flat-square)](https://github.com/morluto/rea) [![Ecosystem: REA](https://img.shields.io/badge/ecosystem-morluto%2Frea-8A2BE2.svg?style=flat-square)](https://github.com/morluto/rea) ### Before submitting - [x] I searched the open and closed issues and pull requests for a related discussion. - [x] I understand the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope) must be reviewed before integration; open questions are welcome here. - [x] This discussion does not include credentials, private samples, or sensitive target data. ### Decision needed Would maintainers consider transitioning the project from the personal user account (`morluto/rea`) to a dedicated GitHub Organization (for example, `rea-tools`, aligning with the official https://rea.tools domain, or `rea-project`) to support team-based governance, scalable review workflows, and long-term sustainability? ### Context and evidence With over 213,000 GitHub stars, 52,000+ forks, and hundreds of active community contributors, REA has grown into one of the most prominent open-source AI reverse-engineering ecosystems. Currently, the repository is hosted under the personal account of @morluto. While this structure worked well in early stages, hosting an ecosystem of this scale under a personal account introduces structural limitations: 1. **Role-Based Access Control and Teams**: Personal user accounts cannot create GitHub Teams. In an Organization, maintainers can define teams (e.g., `@rea-tools/ghidra-maintainers`, `@rea-tools/triage`, `@rea-tools/security`), enabling granular permissions and team-based review assignments without granting full repository write/admin access to individuals. 2. **Review Routing & CODEOWNERS**: As noted in #3445, native `CODEOWNERS` works best with organizational teams so review duties can rotate among specialists rather than pinging a single individual handle. 3. **Project Continuity & Governance**: Organizations provide multi-owner administration, mitigating single-point-of-failure risks and simplifying sponsorship/financial stewardship (e.g. GitHub Sponsors / Open Collective for organizations). 4. **Multi-Repository Architecture**: An organization cleanly groups related repositories under one umbrella (e.g., core `rea`, docs/website, separate provider bridges, or external skill packs). ### Expected interaction with targets - No target interaction (documentation or usability only) ### Migration safety GitHub handles repository transfers seamlessly: - Existing clone URLs (`git clone https://github.com/morluto/rea.git`) and web URLs automatically redirect to the new organization namespace. - Existing GitHub Pages, releases, issues, and pull requests are fully preserved. ### Options and tradeoffs - **Option A (Dedicated Organization, e.g. `rea-tools`)**: Establish an organization matching the canonical website domain (`rea.tools`), transfer `morluto/rea` into it, and invite core maintainers as Organization Owners / Team Leads. - **Option B (Retain Personal Namespace)**: Keep `morluto/rea` under the personal account and rely on individual collaborator permissions. ### Verification readiness - Idea only; I need help defining checks ### Success criteria and open questions - What are the core maintainers' views on formalizing an organization structure for the project at this stage of growth?

bsakaguchi referenced this issue

2026-10-17 21:10:03 +00:00

[PR #1289] [MERGED] fix(ghidra): stop dereferencing the removed error payload in address verification #2770

bsakaguchi referenced this issue

2026-10-17 21:10:04 +00:00

[PR #1294] [MERGED] test(process): check malformed capture choices concurrently #2774