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

Include link to Seneca's ITS Acceptable Use Policy in UI somehow #107

Closed
humphd opened this issue Feb 3, 2023 · 4 comments · Fixed by #492
Closed

Include link to Seneca's ITS Acceptable Use Policy in UI somehow #107

humphd opened this issue Feb 3, 2023 · 4 comments · Fixed by #492
Assignees
Labels
area: web Web development related things [front end/back end] category: front end Front end part of our web service discussion Please tell us what you think!
Milestone

Comments

@humphd
Copy link
Contributor

humphd commented Feb 3, 2023

Seneca has asked that we somehow include a way to remind the user about Seneca's ITS Acceptable Use Policy. Probably having a link, and letting users know about how this affects them. For example, you can't:

  • use IT Resources for personal commercial or financial gain
  • access, create, publish or communicate information that is obscene, pornographic, abusive, defamatory, derogatory, threatening, violent or harassing, including material that may interfere with other individuals’ rights under the Human Rights Code or the Occupational Health and Safety Act
  • create, distribute and/or link to offending materials that conflict with rights and interests protected by Canadian Charter of Rights and Freedoms, the Human Rights Code or the Criminal Code
  • use IT Resources for any purpose that violate the Criminal Code
  • use IT Resources for any purpose (e.g. upload material) that is not in accordance with the Copyright Act, Seneca’s Copyright Policy and Fair Dealing Policy for Copyright-Protected Work

It's not up to us to include all this, but we should link to it. Maybe that means we put it in the page footer? This needs some thought.

@sirinoks sirinoks added category: front end Front end part of our web service area: web Web development related things [front end/back end] discussion Please tell us what you think! labels Feb 13, 2023
@Ririio
Copy link
Contributor

Ririio commented Mar 8, 2023

The user will be on the landing page when they login. We can add a container underneath the cards, and have a sentence or two in regards to the policy. Then we insert a link for "more" informations? Just a thought...

We need more informations on the footer if we're thinking of adding the policy there. Not keen on creating it for the sake of one singular functionality.

@Ririio Ririio self-assigned this Mar 13, 2023
@Ririio Ririio modified the milestones: Milestone 0.6, Milestone 0.7 Mar 13, 2023
@Ririio Ririio modified the milestones: Milestone 0.7, Milestone 0.8 Mar 26, 2023
@humphd
Copy link
Contributor Author

humphd commented Mar 31, 2023

Here's a proposal. Put a sentence with a link at the bottom of this page (where I have the box):

Screenshot 2023-03-31 at 12 14 05 PM

It can say something like:

My.Custom.Domain is meant for educational use only by Seneca students and faculty, and is governed by Seneca's IT Acceptable Use Policy.

You can make Seneca's IT Acceptable Use Policy a link to https://www.senecacollege.ca/about/policies/information-technology-acceptable-use-policy.html

@Ririio
Copy link
Contributor

Ririio commented Mar 31, 2023

I was thinking of adding a footer with links to slack, github, policy etc. but I'm not sure if it's worth it

@humphd
Copy link
Contributor Author

humphd commented Mar 31, 2023

No, people using this won't care about all that stuff (we do, because we're building it). This text I want is different.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: web Web development related things [front end/back end] category: front end Front end part of our web service discussion Please tell us what you think!
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants