Clarify repo where new Gems contributed to o3de should be added (o3de vs o3de-extras)

Open
#57 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Domain
documentation

Research direction

Review the o3de and o3de-extras repositories, the RobotecAI o3de-ros2-gem link, and the existing discussion about where contributed gems belong. The work is done when the SIGs have agreed on and documented soft guidelines distinguishing core gems from extras.

Written by the indexing model from the issue text.

Description

Now that o3de-extras is available for adding news gems, projects and templates outside of the main o3de repo, to the o3de-extras repo.

A conversation has come up about about contributing a gem from an external repo (https://github.com/RobotecAI/o3de-ros2-gem) to o3de and determining whether to add a gem to the core repo https://github.com/o3de or the extras repo https://github.com/o3de/o3de-extras.

Brought up in the discussions is determining the threshold for what makes a gem "core" vs "extra".
Would having some soft guidelines that sigs can agree upon be useful?

Dominant language
No language data
Stars
6
Forks
5
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from o3de/tsc

All issues in o3de/tsc

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.