Update codeowners and remove unused files

[braingram]

This PR removes the unused:

• JenkinsfileRT
• JenkinsfileRT_dev
• CODEOWNERS.txt

and updates the used .github/CODEOWNERS file matching changes in spacetelescope/jwst#9055

The change in ownership should allow this repo to enable Require review from Code Owners in the branch protection rules. PRs that change files outside of the select few defined in the .github/CODEOWNERS file will require approval by a romancal-maintainer before merging. Note that this will not prevent a so approved PR from being merged by a romancal-developer.

The romancal-developers team current contains me and the romancal-maintainers and should have it's membership filled out.

Tasks

• request a review from someone specific, to avoid making the maintainers review every PR
• add a build milestone, i.e. 24Q4_B15 (use the latest build if not sure)
• Does this PR change user-facing code / API? (if not, label with no-changelog-entry-needed)
  • write news fragment(s) in changes/: echo "changed something" > changes/<PR#>.<changetype>.rst (see below for change types)
  • update or add relevant tests
  • update relevant docstrings and / or docs/ page
  • start a regression test and include a link to the running job (click here for instructions)
    • Do truth files need to be updated ("okified")?
      • after the reviewer has approved these changes, run okify_regtests to update the truth files
• if a JIRA ticket exists, make sure it is resolved properly

news fragment change types...

• changes/<PR#>.general.rst: infrastructure or miscellaneous change
• changes/<PR#>.docs.rst
• changes/<PR#>.stpipe.rst
• changes/<PR#>.associations.rst
• changes/<PR#>.scripts.rst
• changes/<PR#>.mosaic_pipeline.rst
• changes/<PR#>.patch_match.rst

steps

• changes/<PR#>.dq_init.rst
• changes/<PR#>.saturation.rst
• changes/<PR#>.refpix.rst
• changes/<PR#>.linearity.rst
• changes/<PR#>.dark_current.rst
• changes/<PR#>.jump_detection.rst
• changes/<PR#>.ramp_fitting.rst
• changes/<PR#>.assign_wcs.rst
• changes/<PR#>.flatfield.rst
• changes/<PR#>.photom.rst
• changes/<PR#>.flux.rst
• changes/<PR#>.source_detection.rst
• changes/<PR#>.tweakreg.rst
• changes/<PR#>.skymatch.rst
• changes/<PR#>.outlier_detection.rst
• changes/<PR#>.resample.rst
• changes/<PR#>.source_catalog.rst

[braingram]

@schlafly @ddavis-stsci This PR includes the corresponding romancal changes to align the workflow with jwst following spacetelescope/jwst#9055

Once this PR is merged the branch protections can be updated. However I do not have the permission to do so. Do either of you?

Finally, is there a list of folks that you'd like me to invite to the romancal-developers team? Once the invites are sent or if you'd like to send them I'll remove myself as a maintainer of that team.

[ddavis-stsci]

LGTM

[ddavis-stsci]

I should have permissions to make these changes. Do you know off hand what the setting is? If not I can look it up or check the JWST setup.

@schlafly @ddavis-stsci This PR includes the corresponding romancal changes to align the workflow with jwst following spacetelescope/jwst#9055

Once this PR is merged the branch protections can be updated. However I do not have the permission to do so. Do either of you?

Finally, is there a list of folks that you'd like me to invite to the romancal-developers team? Once the invites are sent or if you'd like to send them I'll remove myself as a maintainer of that team.

[braingram]

I should have permissions to make these changes. Do you know off hand what the setting is? If not I can look it up or check the JWST setup.

@schlafly @ddavis-stsci This PR includes the corresponding romancal changes to align the workflow with jwst following spacetelescope/jwst#9055
Once this PR is merged the branch protections can be updated. However I do not have the permission to do so. Do either of you?
Finally, is there a list of folks that you'd like me to invite to the romancal-developers team? Once the invites are sent or if you'd like to send them I'll remove myself as a maintainer of that team.

Thanks!

For modifying the branch protections those are:

• at the Settings tab of https://github.com/spacetelescope/romancal
• click the Branches link on the left hand menu

• on the right you'll see a column for main, click Edit

• then enable the setting Require review from Code Owners

For adding members to romancal-developers visit the team page, click the green Add a member button and search/input the user name to add.

[schlafly]

Thanks. I added everyone with a recent romancal commit to romancal-developers team.

[ddavis-stsci]

OK, I've updated the branch protections and so that should be set. There are a few folks I would not have on the romancal-developers team, e.g. Megan S. but I don't see any harm in it. Should we put an announcement on the team-red channel?

…

On 1/10/25 1:18 PM, Eddie Schlafly wrote: Thanks. I added everyone with a recent romancal commit to romancal-developers team. — Reply to this email directly, view it on GitHub <https://urldefense.com/v3/__https://github.com/spacetelescope/romancal/pull/1577*issuecomment-2583465536__;Iw!!CrWY41Z8OgsX0i-WU-0LuAcUu2o!3Bz9sCpBDcNBJLK2SE8Yr1HIQvLIBn10FsQWtSrFTHjPeFP4g1bD_xy277dUy-ghQ1uxAyZONYe9h2FZDuNRnEJM$>, or unsubscribe <https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ALXCXWNOFAS6WMQXXINOK4L2KAFHRAVCNFSM6AAAAABU44WWAWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBTGQ3DKNJTGY__;!!CrWY41Z8OgsX0i-WU-0LuAcUu2o!3Bz9sCpBDcNBJLK2SE8Yr1HIQvLIBn10FsQWtSrFTHjPeFP4g1bD_xy277dUy-ghQ1uxAyZONYe9h2FZDim7--Bt$>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[braingram]

Thanks. I added everyone with a recent romancal commit to romancal-developers team.

Thanks! I removed myself as a maintainer of that list.