Skip to content

Scale directorship meeting requirement by semester #124

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 18, 2017

Conversation

csssuf
Copy link
Member

@csssuf csssuf commented Oct 30, 2017

Check one:

  • Semantic Change: something about the meaning of the text is different
  • Non-semantic Change: Spelling, grammar, or formatting changes.

Summary of change(s):
Scale the permanent directorship meeting requirement based on how many semesters a member is active for. This moves the requirement in line (more or less) with the requirement for introductory members (one per week).

Things to note:

  • I made the requirement fifteen per semester rather than one per week for a few reasons. The primary reason is that scaling it per week seems too fine-grained to me, and requires considerable extra bookkeeping. Scaling by week also makes the requirements per semester 14, which isn't quite as round a number as I'd like. It also made the wording slightly more cumbersome.
  • I'm not convinced the wording of my change is ideal, so I'd welcome feedback on how to improve that. In particular, I want to make sure it doesn't read as requiring meeting attendance to actually be distributed to 15 per semester - just a total of 30 for the whole year, if you're active both semesters.

Copy link
Member

@sgreene570 sgreene570 left a comment

Choose a reason for hiding this comment

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

"Permanent Directors" does not include Ad-Hoc Directors. My recent amendment uses the wording "House directorship".
Also, maybe some wording should be added to clarify that 30 meetings will be required for members who are active for both the fall and spring semesters.

@csssuf
Copy link
Member Author

csssuf commented Oct 30, 2017

Hmm, the changes from your PR seem to have mysteriously disappeared. I suspect #117 was merged after #122 and accidentally ate those changes. This will need to be resolved separately. My amendment isn't intending to change that, in any case. I do think the wording is clear on requiring 30 meetings for those who are present for fall and spring - what makes you think it isn't?

@csssuf
Copy link
Member Author

csssuf commented Oct 30, 2017

Wow, Github's web UI for resolving conflicts is hot trash. Gonna force-push a real fix.

@csssuf csssuf force-pushed the committee-meetings branch from d7f3ccc to 9d36fcf Compare October 30, 2017 17:09
@zthart
Copy link
Contributor

zthart commented Nov 6, 2017

I don't know if this was ever discussed anywhere, but was there any reason you opted for another specific number rather than generic language so that this problem didn't need to be fixed when RIT changes their mind about semesters again?

Something to the tune of

... attend at least the number of directorship meetings (including permanent and Ad-Hoc directorship meetings) equal to the number of weeks in each Academic Semester in which they are an active member.

Just a thought

It would make the requirement 28 (as things stand now), rather than 30, which is a less-nice number, but it would definitely keep the section accurate so long as RIT doesn't decide to go back to quarters or some funky trimester shit.

@csssuf
Copy link
Member Author

csssuf commented Nov 6, 2017

Yeah, I thought about that, but it seemed like it made the language a little awkward. I'd be happy to change it if we can figure out a good way to phrase things.

@zthart
Copy link
Contributor

zthart commented Nov 6, 2017

also maybe in which -> during which

so that it reads ... each Academic Semester during which they are an Active Member.

@zthart
Copy link
Contributor

zthart commented Nov 6, 2017

What about ... attend at least the number of directorship meetings ... equal to the length of each Academic Semester (in weeks) during which they are an active member.

We could also provide an example at the end such that we still give an absolute number, but one that could be updated as a non-semantic change should the length of each semester change.

Beyond that, we could just take a page from the part of the constitution that already works this way and word it as

Attend at least one House directorship meeting for each week of the process each Academic Semester in which they are an Active Member.

@csssuf
Copy link
Member Author

csssuf commented Nov 6, 2017

Yeah, that sounds pretty reasonable.

@csssuf csssuf force-pushed the committee-meetings branch from 9d36fcf to 264e6d7 Compare November 6, 2017 18:20
@bmbowdish
Copy link
Contributor

"Equal to the number of weeks of active membership" seems a little wordy. I think a number per semester would suffice.

@bmbowdish
Copy link
Contributor

Additionally, the wording would need to be EXTREMELY clear in that it would not mean "one meeting per week" but "one meeting per week by the end of the period"

@csssuf
Copy link
Member Author

csssuf commented Nov 6, 2017

Actually, I totally forgot the other reason I set it to a fixed number - implementing it in conditional is way easier as a fixed number. I guess I'd like to hear some more opinions on this one.

@zthart
Copy link
Contributor

zthart commented Nov 6, 2017

The other benefit to being generic, is that it handles people leaving via a Leave of Absence, etc.

It may be harder to get right in conditional, but it’s far from impossible.

@zthart
Copy link
Contributor

zthart commented Nov 6, 2017

Also, it is clear it doesn’t require attendance of one per week, nowhere in the text does it use the phrase “one meeting per week”. It says the number is equal to the number of weeks.

See the comment on or current 10 weeks process

@sgreene570
Copy link
Member

Amendment passed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants