Skip to content
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

Create policy for students who cannot make Tuesday 4pm or Wednesday casual coding sessions #94

Open
kburk1997 opened this issue Dec 17, 2018 · 5 comments

Comments

@kburk1997
Copy link
Member

Description of Issue:

Next semester, we are tentatively doing away with the late small group and making students who cannot attend the Tuesday 4pm sessions go to Wednesday casual coding sessions. However, we have not accounted for students who cannot make either session.

Proposed Solution:

Here are a few ideas:

  • Meet with mentor one-on-one to fulfill requirement
  • If there is enough interest, restart the late small group
@vakrao
Copy link

vakrao commented Dec 18, 2018

I think we should have second session for late group specified in SIS. The work session requirement I think might have to be a Sunday thing then? Due to how lab courses having 4-6 as a popular timeslot Wednesday just might not work. Thoughts?

@kburk1997
Copy link
Member Author

I've had a 3-6 circuits lab on Wednesday one semester, we definitely should rethink making casual coding sessions mandatory for those who can't make Tuesday 4pm, especially since ECSE students may take ECSE seminar and a lab course during the same semester (I remember taking IE with ECSE seminar)

@aeksco
Copy link
Member

aeksco commented Dec 22, 2018

@Bad-Science and I discussed this - we both agreed that ditching the late session in favor of requiring attendance on Wednesday evenings would be sufficient.

@kburk1997 I'm personally of the opinion that if the student cannot attend either they simply won't be able to pursue RCOS for credit that semester. We're not obligated to accommodate everybody, and I think putting too many safety nets in place will ultimately complicate things. For example, hosting 1-to-1 sessions with mentors every week won't scale for either the student in question or their respective mentors.

@vakrao I don't think it's necessary to have a second session listed in SIS - we already have enough problems with SIS as it is with 2 CRNs - if we have a late group CRN, we'll need one for the 2000 and 4000 level courses respectively. Too much complexity IMHO.

I think our current system is sufficient for handling this - with the late group as small as it was last semester I think the Wednesday evening requirement should be sufficient. If students can't make either, they just can't pursue RCOS that semester - just like any other course that conflicts with their required schedule. I think there's always room to make an exception for specific motivated students who need an accommodation, but I don't think it's worth our time crafting policies to handle every possible edge case for the late group issue.

I think we can close this issue if everyone is in agreement @kburk1997 @vakrao @Bad-Science @AdrianCollado

@wdturner
Copy link
Contributor

wdturner commented Dec 26, 2018 via email

@kburk1997
Copy link
Member Author

@aeksco they could also pursue 1 or 2 credits and only attend the Friday sessions, but there's also the problem of them not having an assigned smallgroup

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

No branches or pull requests

4 participants