Skip to content

Conversation

@cabutlermit
Copy link
Contributor

Why these changes are being introduced

With the updates to user permissions/privileges/roles in our GitHub Organization, it was time to update our developer documentation to reflect these changes.

How this addresses that need

  • Update the GitHub documentation, including the additional information about owners versus members and repository roles
  • Fix other slightly-outdated information in other files

Side effects of this change

None.

Why these changes are being introduced:
With the updates to user permissions/privileges/roles in our GitHub
Organization, it was time to update our developer documentation to
reflect these changes.

How this addresses that need:
* Update the GitHub documentation, including the additional information
about owners versus members and repository roles
* Fix other slightly-outdated information in other files

Side effects of this change:
None.
@cabutlermit cabutlermit force-pushed the github-documentation-updates branch from 0b40fc0 to efa5a62 Compare June 12, 2025 19:14
Why these changes are being introduced:
The previous push to GitHub failed tests because of very outdated
versions in the workflows.

How this addresses that need:
* Update the setup-python action to v4 (from v1) in the workflows
* Update the python version to 3.12 (from 3.7) in the workflows
* Update the python version to 3.12 in the Pipfile and update
Pipfile.lock

Side effects of this change:
I have no idea yet!
@cabutlermit cabutlermit force-pushed the github-documentation-updates branch from efa5a62 to 20d2b1c Compare June 12, 2025 19:18
@cabutlermit cabutlermit marked this pull request as ready for review June 12, 2025 19:19
@cabutlermit cabutlermit requested a review from JPrevost June 12, 2025 19:19
@JPrevost JPrevost self-assigned this Jun 13, 2025
Copy link
Member

@JPrevost JPrevost left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Many of my suggestions are based on some auto formatting you did and not part of your intended changeset. If you'd prefer not to deal with them in this changeset please let me know so I can take care of them separately.


We use [Code Climate](https://codeclimate.com/)'s GitHub integration to monitor
for code smells. Code Climate is free for open source repositories.
We use [Code Climate](https://codeclimate.com/)'s GitHub integration to monitor for code smells. Code Climate is free for open source repositories.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this is a broad truth in our org anymore and only EngX seems to be using it. It's also gotten really weird in the past few weeks as they are rolling out a replacement product.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll leave this for another commit by you or someone else.

repos may still use `master` and should be migrated. GitHub now provides an
easy way to do this in the web UI. In the repo's settings, you can
change the name of the default branch.
While all new repos will be created with `main` as the default branch, older repos may still use `master` and should be migrated. GitHub now provides an easy way to do this in the web UI. In the repo's settings, you can change the name of the default branch.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

older repos may still use `master` and should be migrated if possible

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll leave this for another commit by you or someone else.


The DSpace@MIT codebase is hosted on Atmire's GitLab organization. In order to add or modify tracking code, you will
need a GitLab account. As of June 2023, the Digital Library Systems Manager is our point of contact with Atmire.
The DSpace@MIT codebase is hosted on Atmire's GitLab organization. In order to add or modify tracking code, you will need a GitLab account. As of June 2023, the Digital Library Systems Manager is our point of contact with Atmire.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd mention the position is part of Enterprise Systems as I'd wager people won't know that title. Also, I believe Carl's title is currently Digital Repository Services Engineer

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm going to leave this for another commit by you or someone else.

These are minor changes in response to the code review for this PR>
@cabutlermit cabutlermit requested a review from JPrevost June 13, 2025 18:15
@cabutlermit cabutlermit merged commit 93475d4 into main Jun 13, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants