Skip to content

Document current state of Open@RIT in 2025#213

Open
jz1141-dotcom wants to merge 1 commit intoFOSSRIT:mainfrom
jz1141-dotcom:patch-1
Open

Document current state of Open@RIT in 2025#213
jz1141-dotcom wants to merge 1 commit intoFOSSRIT:mainfrom
jz1141-dotcom:patch-1

Conversation

@jz1141-dotcom
Copy link
Copy Markdown

Added a section detailing the current situation of Open@RIT in 2025, highlighting its evolution and contributions to the open work ecosystem for the history.

Added a section detailing the current situation of Open@RIT in 2025, highlighting its evolution and contributions to the open work ecosystem.
@MoralCode
Copy link
Copy Markdown
Contributor

Do you have more context for why youre proposing this change?

@jz1141-dotcom
Copy link
Copy Markdown
Author

jz1141-dotcom commented Apr 25, 2026 via email

@MoralCode
Copy link
Copy Markdown
Contributor

The reason I ask is because i feel like a lot of the information you're adding in this section was true about OPEN@RIT at various points in the past (and covered by previous sections), but isnt true in 2025. If you want only 2025 information on OPEN@RIT, I'm not sure what else there is to say besides that it continues to exist.

@jz1141-dotcom
Copy link
Copy Markdown
Author

jz1141-dotcom commented Apr 25, 2026 via email

@MoralCode
Copy link
Copy Markdown
Contributor

MoralCode commented Apr 25, 2026

No worries!

I think if you took the content from #211, incorporated the feedback from the review in that PR and used that in a new section at the end of the history page (like you already did), that would be a good topic for an update to the history page. We have needed to document what happened to the FOSS minor at RIT for a little while now.

Would you like to give that a try?

@jz1141-dotcom
Copy link
Copy Markdown
Author

jz1141-dotcom commented Apr 25, 2026 via email

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.

2 participants