wics-uw / website Goto Github PK

Will need to look into this.

We want to give people an idea of what sort of information that we're looking for when they want to propose an event.

Based on the event proposal form that can be found in the drive.

Here: https://docs.google.com/forms/d/1nF1Ssna-j1L9gQQPcTgb8kr81FjKVbprc07cglXYEIk/edit

"WARNING: Unable to find /content/S2016/S16-updated-event-wics-csc.md, skipping url replacement"

Our internal wiki has info on WeeChat and other stuff. I'd be great to put it all on our website for folks to have lots of options. It's already on gitlab in markdown so it would be pretty easy to move over!

In my experience, members on co-op can be effective. Akshaya did quite well as Big Csters director.

I would say office manager, sys-admin, chair and secretary should be on a study term.

@wics-uw/contributors

See #59 for what that might look like, in terms of updating links, archiving a copy of the previous committee page, etc.

People have contacted us about volunteer opportunities per our About page, but it would be great if we could elaborate on our open positions in more detail. Whether it's implemented as a link to a google form application or a page with some permanent descriptions, it would be cool either way to see something along these lines.

A question I get a lot is: why do you have some women-only events? Maybe we could make a FAQ and include an answer to that that in it?

update the volunteer page to link to https://lists.uwaterloo.ca/mailman/listinfo/wics-volunteers (and the wics sys one) instead of the google form

that way we don't have to sign them up ourselves

if we can style it like Elana did https://lists.uwaterloo.ca/mailman/listinfo/wics-announce, that'd be cool

Similar to #155, a number of events never made it onto the website for the W16 term. It would be nice if we had a record on the website for posterity's sake, since Facebook events are very ephemeral.

Related to #119

I mentioned both "Accountability" and "Consensus-based decision making" in the meta-issue, because I don't think they're properly represented.

Until Heroku adds support for auto-deploying review apps for org members' forks, I have to go in and manually hit deploy to launch our review apps for PRs. This is annoying and also my turnaround time is not great. I'd like to give another syscom member/committee access. Any volunteers?

See #59 for what that might look like, in terms of updating links, archiving a copy of the previous committee page, etc.

#215 (comment)

it's already mentioned briefly in the readme, but adding this longer explanation about never pulling would be helpful (at @arshiamufti's suggestion)

The information on our partnership with BlackBerry on the sponsorships is pretty outdated.

In the body of the post here: http://wics.uwaterloo.ca/2015/01/new-website/

It would list the magazines we subscribe to, any books (electronic or physical) that are available to read. Not sure if this should be a brand new tab on the website or we should link to it in our about page?

• Office policy should be linked there
• Code-of-Conduct link should have spaces, not dashes

Also possibly related: can we get the versioning on the office policy to match that of the Code of Conduct?

There are too many things we want in the navbar

Volunteering should really be there (#254) but what do we take away?

Dropdown menus aren't super easy but is an option: getpelican/pelican#1037

Or we could try moving navbar items to links on other pages (e.g. media and calendar as links at the top of the events page) - is this possible?

Now Tags is on its own line again. Why wasn't this tested? This should be fixed ASAP.

When we have too many qualified applicants who are new, I think these decisions can still be made through the normal interview/evaluation process.

When we have too many qualified returning members, the decision for who gets to be on committee should be escalated, because clearly we can't be objective about ourselves. What I put in for this situation was that everyone should go through the regular interview/application process and be evaluated by the serving Director of WiCS.

Thoughts? @wics-uw/contributors

Since our office is moving, we need to update the location on http://wics.uwaterloo.ca/contact-us/

Tasks:

1. Update the Contact-Us page
2. Write a website post informing people about the move

Required information:

• Office is moving to MC3013C

Similar to #196. Do we have this video available anywhere so I can upload it to the csclub's mirror?

related pull requests/issues from other terms: #166 #96 #66 #59 #27

• Create and event/blog post detailing our office hours for this term

Our "about" page seems to imply that our office is open to all trans individuals, because the page was written before we declared our office women-only. This should probably be updated---that is, either we determine whether we want our office to continue to be women-only or if we want to include more groups.

I'd like to change "non-binary folk" to "non-binary individuals" on our FAQ. It's a bit more formal.

Problem:

• Volunteer sign up form is hard to find
• Currently click paths:
  • About > Form
  • FAQ > About > Form
  • FAQ > Volunteer Opportunities Page > Form

The click paths don't seem that bad, but for some reason it's really hard to find.

Possible solutions:

• Adding a volunteer tab to the nav bar

Related Issues:

• #249

I would like other people with commit access to be able to hit the "deploy to Heroku" button for the review apps. Please let me know here if you are interested, and we can sync up offline to send you an email invite. Pinging @wics-uw/committers.

In #112, it became clear that there were too many issues raised with the constitution to address in a single pull request. Hence, I merged that PR into a separate branch such that we can address issues one-by-one.

Here is a list of known issues/requests that we've seen thus far for the constitution. For each one, feel free to make a single issue to track it if it requires extensive discussion.

• Fix keypair in metadata from hidden: true to status: hidden
• Wording: should we say "Director of Women in CS" or "Chair of the WiCS Committee"?
• Should an individual be able to serve as Chair for two or more consecutive terms?
• Which committee members can be on co-op?
• What do we do when no returning member wishes to be Chair? (PR #146)
• What do we do when there are too many interested and qualified returning and new committee members? (PR #146)
• Do we need "dissolution" and "acceptable use of committee resources" sections? (PR #147)
• Add a formal procedure for choosing communication and organizational technologies (PR #137)
• Add more detail in the interview procedure (PR #146)
• Add a responsibility for all committee members to identify when others are falling behind on their responsibilities and a suggested script/procedure to ensure they get help (PR #143)
• Additional value: Accountability
• Additional value: Consensus-building
• Add a section on volunteers and require the next term's first volunteer meeting to be planned before interviews begin (PR #144)
• Add responsibility for chair: resolving internal committee disputes (PR #143)
• Update value: Technical Excellence (PR #148)
• What happens when a committee member resigns? Should there be a procedure for removing a committee member? (PR #152)
• How do we enforce this document?
• Expand scope of purpose and vision: change 'in' to 'interested in' (PR #151)
• Add Fatema's responsibility for Chair (PR #153)

Feel free to suggest more in comments, I will update this issue as progress is made.

We usually take a couple of pictures at our events and since @SrishtiG recently uploaded pictures of the recent Toronto meetup and WiCS orientation, it would be cool to have selected photos on our website instead of just Facebook/Twitter because

• not everyone uses Facebook/Twitter
• it's a more central location for them
• a picture is worth a thousand words \o/

Not quite sure if there are any technical constraints here @ehashman @fboxwala @evykassirer?

See #101 for a PR to model this after.

The processed file is already on mirror.csclub: http://mirror.csclub.uwaterloo.ca/wics/coop-panel-w16.mp4

Problem:

• README doesn't address:
  • When during the pull request process commits should be squashed
  • Doesn't explain what is actually means to squash a commit
• Possible mistakes:
  • "git push --force" should be "git push origin BranchName --force"

This may help people with submitting pull requests and keeping the website up to date if they are not super familiar with git: https://aint.io/

Might be a cool thing to research and look into.

Could be a good first task for the README for a new Heroku org member (ala #180).

There are a bunch of tags for posts on the site. Some are redundant and some are only used on one post and probably won't be used again - let's remove these.

There have been discussions about changing all links that link to a page on wics.uwaterloo.ca to be relative instead of absolute.

Discuss below!

Here's some research:

http://www.navegabem.com/linking-strategy.html
https://moz.com/blog/relative-vs-absolute-urls-whiteboard-friday
http://stackoverflow.com/questions/2005079/absolute-vs-relative-urls

As a way for people to send us anonymous feedback all the time - the form can email us when it's been submitted

We probably want this in the FAQ?

You may not have noticed, but we have both an "academic" and "academia" tag! Furthermore, a number of our events aren't fully tagged. It would be cool to go through the tag list and amalgamate some of these duplicate tags, as well as drudging through all of the articles and ensuring they have a full list of tags.

You can find the tag page here.

Under current committee, the term is listed as Spring 2015, but this should read Fall 2015.

Under Spring 2015, there's a bunch of unnecessary text/link/title at the top. Everything before "Chair" can be removed.

Problem:

• Currently we are linking to a Google Form for people to use to sign up for volunteering
• This means that we have to copy over the email addresses to the mailing list which causes mistakes

Solution:

• Link to https://lists.uwaterloo.ca/mailman/listinfo/wics-volunteers instead

So I even already have the page and the link all updated in a branch that's been sitting around for months; the issue has been getting the actual video published. There were some problems with the audio. Hopefully the existence of this issue will remind me to get it done :)

This was mentioned in a meeting in F15 but never done

We take pictures at events, but won't take your picture if you're not wearing a lanyard.

We'll always tell everyone at the beginning of the event that photos taken will end up on social media unless you specifically ask otherwise (or are wearing a lanyard)

I'm assuming this would go under http://wics.uwaterloo.ca/policies/

WARNING: There are 2 variants of "wics-csc-s16" with lang en
WARNING:    /tmp/build_fc0927ffb54766d5c964bdd3120814e8/wics-uw-website-47f9fdf/content/S2016/S16-updated-event-wics-csc.md
WARNING:    /tmp/build_fc0927ffb54766d5c964bdd3120814e8/wics-uw-website-47f9fdf/content/S2016/S16-event-wics-csc.md

Sorry Bhargavi, I missed this in code review. Can you fix it please?

We have an office policy but it should probably be publicly available, linked on our website.

For the pelican metadata, this page should have "status: hidden" to ensure it doesn't appear in the top bar navigation.

I think for posterity's sake we should archive these on our website. It would be cool if someone went through the Facebook event backlog and created website posts for any missing events for the Fall 2015 term. This would also be a good way for a first-time contributor to get involved in the website.

For whatever reason, our CSS theming is a bit inconsistent. I commented on how this looks to be a problem in #115. This problem affects pages such as the Office Policy, and soon, the MUA Summary.

I believe the required fix is to add some margin to ul elements, to match that of p elements.

I think the rule change here is beginner-friendly, so please feel free to comment on here if you are interested in working on this and would like to pair or have me mentor.

Making an issue for this because I think it requires some discussion. I'm of the opinion that there should be a term limit but higher than two. Three would be acceptable to me.

A two-consecutive term limit seems unnecessary because a chair who has already served a term is chair has experience and is potentially the best candidate to be chair again. Furthermore, it can be hard to find anyone to do the job (see Fall15) so having more restrictions seems like a bad idea.

@wics-uw/contributors opinions and suggestions.

• http://wics.uwaterloo.ca/2015/07/intersectionality-workshop/ - should have 'feminism' and 'workshop', not 'academic'
• http://wics.uwaterloo.ca/2015/07/alterconf-toronto-2015/ - should have 'conference' and not 'social'
• http://wics.uwaterloo.ca/2015/06/you-are-not-your-grades/ - should have 'academic' and possibly not social
• http://wics.uwaterloo.ca/2015/05/google-talk/ - should have 'industry'
• http://wics.uwaterloo.ca/2015/03/git-website-workshop/ - should have tag 'open source'