Standard Change - Rename "Community Operations Meeting" to "ProgCode General Meeting"

[RahulR100]

Description

Community Operations, especially in the corporate world today, assumes the completion of administrative tasks / paperwork. However, for ProgCode, while we do occasionally discuss administrative tasks during the call, we also discuss the status of most projects, current events, and personal updates for community building. I believe that renaming the meeting from Operations => General will help new members (and existing ones alike) get a better sense of what the meeting really is.

Problem

Community Operations meetings have been held since the founding of ProgCode in 2017. At the time, several regularly-occurring meetings were held each week, each with a distinct purpose. The Monday meetings were designated "Community Operations" so that community members and volunteer staffers could address matters involving operations, such as the discussion of community proposals and development of administrative processes. By mid-2018, most processes were in place, the number of meetings was reduced, and the Community Operations meeting time began to be used for nearly any matter that was not dedicated to development of a particular tech project. There is concern that the name "Community Operations" suggests a more restricted meeting topic scope. This can be resolved by a name change to "ProgCode General Meeting".

Benefit

Adopting a name which suggests a wider scope may encourage community members to propose topics more related to their experiences and goals in the ProgCode community.

Plan

• Post notice of this initiative in the #team-announcements for a community discussion of all elements of this proposal at the Community Operations Meeting scheduled for Monday, January 26, 2026, at 5pm PT | 6pm MT | 7pm CT | 8pm ET | 1am Tuesday BST/GMT.
• Request community consent to implement the proposal, following discussions at the community operations meeting.
• Notify the community of the vote taken and sharing the video URL in the #team-announcements channel following the vote for consent to implement, in accordance with ProgCode procedures, and allow additional votes & feedback during the standard 72-hour waiting period before ratifying the vote.
• If the vote to implement passes, change all designations of "Community Operations Meeting" to "ProgCode General Meeting", such as in the Agenda, Zoom link, and #team-announcements posts.

Decision Making

Consent to implement a standard change per the Change Process

Reference link(s)

• [Change Process](https://github.com/ProgressiveCoders/functions/wiki/Change-Process