├── .gitignore ├── communities ├── uchicago │ └── community-assessment.md~ ├── edinburgh-compsoc │ └── computy-impact-proposal.md ├── university-of-waterloo │ └── community-assessment.md ├── dortmund-student-hackers │ ├── community-assessment.md │ └── impact-proposal.md ├── nobody │ ├── community-assessment.md │ └── community-impact-proposal.md ├── indian-institute-of-information-technology-allahabad │ ├── community-impact-proposal.md │ └── community-assessment.md ├── Montclair State University │ └── community-assessment.md ├── usc-project-athena │ └── community-assessment.md ├── occidental-college │ └── community-assessment.md ├── isi-web-devs │ └── community-assessment.md ├── Entrenology-club-at-ALU │ ├── community-assessment.md │ ├── community impact proposal.md │ └── community-impact-proposal.md ├── conu-hackers │ ├── community-assessment.md │ └── community-impact-proposal.md ├── sussex-hackers │ ├── community-impact-proposal.md │ └── community-assessment.md ├── acm-manipal │ └── community-assessment.md ├── university-of-buea │ ├── community-impact-proposal.md │ └── community-assessment.md ├── depaul-css │ └── community-assessment.md ├── students-new-to-hacker-culture │ ├── community-assessment.md │ └── community-impact-proposal.md ├── uclutechsoc │ └── community-assessment.md ├── citytechsoc │ ├── community-impact-proposal.md │ └── community-assesment.md ├── FPU-Tech-Community │ ├── impact-proposal.md │ └── community-assesment.md ├── kcl-tech-society │ ├── community-impact-proposal.md │ ├── kcl-tech-society │ └── community-assessment.md ├── manitoba-hackers │ ├── manitoba-impact-proposal.md │ └── community-assessment.md ├── UNAM-Engineering │ ├── community-impact-proposal.md │ └── community-assessment.md ├── KMAhackers │ └── community-assessment.md ├── epfl-hackers │ ├── community-assessment.md │ └── community-impact-proposal.md ├── qut-codenetwork │ └── community-assessment.md ├── hacksoc-notts │ └── community-impact-proposal.md ├── hacs │ └── community-assesment.md └── plymouth-university │ └── community-impact-proposal.md ├── todos ├── week-8.md ├── week-7.md ├── week-6.md ├── week-4.md ├── week-5.md ├── week-3.md ├── week-1.md └── week-2.md ├── docs ├── write-a-readme.md ├── write-an-abstract.md ├── logistics.md ├── community-assessment.md └── community-impact-proposal.md └── README.md /.gitignore: -------------------------------------------------------------------------------- 1 | .DS_Store 2 | -------------------------------------------------------------------------------- /communities/uchicago/community-assessment.md~: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /communities/edinburgh-compsoc/computy-impact-proposal.md: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /todos/week-8.md: -------------------------------------------------------------------------------- 1 | # To Do 2 | 3 | 1. **VERY IMPORTANT** [Complete the end of training survey](https://goo.gl/forms/5QchKjbKsv7DurQ53). Due by 22nd May. 4 | 1. Attend a PROGRAM ENDING call. Refer to [logistics doc](https://github.com/campus-experts/spring-2017/blob/master/docs/logistics.md) for calendar. 5 | 1. Join Guest calls on Wednesday and Thursday. 6 | -------------------------------------------------------------------------------- /todos/week-7.md: -------------------------------------------------------------------------------- 1 | # To Do 2 | 3 | 1. **VERY IMPORTANT** [Complete the end of training survey](https://goo.gl/forms/5QchKjbKsv7DurQ53) 4 | 1. Attend Wednesday's training talk, Lara Hogan on "Demystifying Public Speaking", Wednesday 10th May, times [here](https://www.timeanddate.com/worldclock/converter.html?iso=20170510T160000&p1=136&p2=224&p3=75&p4=179&p5=2408&p6=241&p7=47&p8=37&p9=267). 5 | 1. Attend Thursday's training talk, Lee Dohm on Community Management. Thursday 11th May, times [here](https://www.timeanddate.com/worldclock/converter.html?iso=20170511T160000&p1=136&p2=224&p3=179&p4=75&p5=tz_mut&p6=267&p7=37&p8=47&p9=2408&p10=241). 6 | 7 | -------------------------------------------------------------------------------- /todos/week-6.md: -------------------------------------------------------------------------------- 1 | # To Do 2 | 3 | 1. Attend today's [Tech Talk](https://github.com/campus-experts/spring-2017/issues/48), Browsers behind your back with Phil Nash. 4 | 1. Watch last week's guest talk with [TechNottingham](https://www.dropbox.com/s/b1s37d9tbpmtrok/technottingham.mp4?dl=0). 5 | 1. Attend Wednesday's training talk, Lara Hogan on "Demystifying Public Speaking", Wednesday 3rd May, times [here](https://www.timeanddate.com/worldclock/converter.html?iso=20170503T160000&p1=136&p2=224&p3=75&p4=179&p5=2408&p6=241&p7=47&p8=37&p9=267). 6 | 1. Complete this week's exercise, [write an abstract](https://github.com/campus-experts/spring-2017/blob/master/docs/write-an-abstract.md)! 7 | 1. Complete the mid-training survey: https://goo.gl/forms/wDBO77MzuKyiaAa72. 8 | 9 | -------------------------------------------------------------------------------- /todos/week-4.md: -------------------------------------------------------------------------------- 1 | # To Do 2 | 3 | 1. Complete the pull request for your Community Impact Proposal, and review the [pull request comments](https://github.com/campus-experts/spring-2017/pulls?q=is%3Apr+is%3Aopen+label%3Aimpact-proposal). 4 | 1. Watch the Technical Writing guest talk (recording to follow). 5 | 1. Complete the Technical Writing week exercise - [Write a README](https://github.com/campus-experts/spring-2017/blob/master/docs/write-a-readme.md)! 6 | 1. Participate in the [discussion](https://github.com/campus-experts/discuss/issues) this week - [engaging your community in passion projects](https://github.com/campus-experts/discuss/issues/1). 7 | 1. Attend [Thursday's guest talk](https://github.com/campus-experts/spring-2017/issues/28), Music Computing with Hugh Rawlinson from Spotify. 8 | -------------------------------------------------------------------------------- /todos/week-5.md: -------------------------------------------------------------------------------- 1 | # To Do 2 | 3 | 1. Complete the mid-training survey: https://goo.gl/forms/wDBO77MzuKyiaAa72 4 | 1. Watch the [Technical Writing guest talk](https://www.dropbox.com/s/8mk2lfcrvmj02cb/week4.mp4?dl=0) if you haven't already. 5 | 1. Complete the Technical Writing week exercise - [Write a README](https://github.com/campus-experts/spring-2017/blob/master/docs/write-a-readme.md)! 6 | 1. Participate in the [discussion](https://github.com/campus-experts/discuss/issues) this week - [passing the torch](https://github.com/campus-experts/discuss/issues/2). 7 | 1. Attend Wednesday's training talk, we'll be joined by Emma and Andrew Seward talking about how they built their community, [TechNottingham](http://www.technottingham.com/). 8 | 1. Attend [Thursday's guest talk](https://github.com/campus-experts/spring-2017/issues/39), an overview of mapping and location based applications with James Milner. 9 | 1. There is no new exercise this week, to give you time to catch up on your proposals, assessments and READMEs. 10 | 11 | -------------------------------------------------------------------------------- /todos/week-3.md: -------------------------------------------------------------------------------- 1 | # To Do 2 | 3 | 1. Open a PR against this repo to share the [Community Impact Proposal](../docs/community-impact-proposal.md) on your fork with other Campus Experts. Please add the `impact-proposal` label to your PR. 4 | 1. Review PRs with the `community-assessment` and `impact-proposal` label with the goal of providing feedback to other Campus Experts, and to refine your own documents. 5 | 1. Using the feedback you gained from other experts, adjust your documents as needed and merge when ready. 6 | 1. Think about what knowledge and resources you need to enact your proposal, and make a speaker request in the [guest speakers](https://github.com/campus-experts/spring-2017/issues/1) issue. 7 | 1. Vote on how we should conduct group discussions [here](https://githubeducation.slack.com/archives/C2TQDRQSG/p1491916310177519) 8 | 1. Attend one of the office hours for this week -- the [program logistics document](../docs/logistics.md) explains what to do if you are unable to attend. 9 | 1. Attend the Git/GitHub training on 11th April (9pm UK, 1pm SF), and the GraphQL workshop on 12th April (5pm UK, 9am SF)! 10 | -------------------------------------------------------------------------------- /todos/week-1.md: -------------------------------------------------------------------------------- 1 | # To Do 2 | 3 | 1. Review the [program logistics document](../docs/logistics.md). 4 | 1. Fork this repo. 5 | 1. Use the [Community Assessment template](../docs/community-assessment.md) to define your community's needs. Work on this in your fork, you'll start a PR during next week's activities to share with other Campus Experts. Save your community assessment document in a folder titled `communities`, and then create an additional subfolder with the name of your community. For example, if I was creating a community assessment for Women of Color in Savannah, I'd create: `communities/woc-savannah/community-assessment.md`. If I was creating a community for London Hackers, the path would be: `communities/london-hackers/community-assessment.md`. 6 | 1. [Provide suggestions](https://github.com/campus-experts/spring-2017/issues/1) for guest speakers. 7 | 1. [Add your bio and profile picture](https://github.com/campus-experts/spring-2017/issues/2) so other Experts can get to know you. 8 | 1. Attend one of the office hours for this week -- the [program logistics document](../docs/logistics.md) explains what to do if you are unable to attend. 9 | -------------------------------------------------------------------------------- /todos/week-2.md: -------------------------------------------------------------------------------- 1 | # To Do 2 | 3 | 1. Open a PR against this repo to share the [Community Assessment](../docs/community-assessment.md) on your fork with other Campus Experts. Please add the `community-assessment` label to your PR. 4 | 1. Review PRs with the `community-assessment` label with the goal of providing feedback to other Campus Experts, and to refine your own Community Assessment. 5 | 1. Using the feedback you gained from other experts, adjust your Community Assessment as needed and merge when ready. 6 | 1. Begin to define what you'll do to address your community's needs by filling out your [Community Impact Proposal](../docs/community-impact-proposal.md). Work on this in your fork, you'll start a PR during next week's activities to share with other Experts. Save your community impact proposal in the path `communities/YOUR-COMMUNITY/computy-impact-proposal.md`. 7 | 1. Now that you've more clearly defined what you'll do for your community, visit the [guest speaker suggestions issue](https://github.com/campus-experts/spring-2017/issues/1) once again, and review your suggestions or provide additional ones. 8 | 1. Attend one of the office hours for this week -- the [program logistics document](../docs/logistics.md) explains what to do if you are unable to attend. 9 | -------------------------------------------------------------------------------- /docs/write-a-readme.md: -------------------------------------------------------------------------------- 1 | # Write a README 2 | _This exercise will be updated with more resources after the Technical Writing talk_ 3 | 4 | The README is the first thing people see when visiting your project. In this exercise, you'll apply what you learnt during the [Technical Writing](https://www.dropbox.com/s/8mk2lfcrvmj02cb/week4.mp4?dl=0) talk to a project README. 5 | 6 | ## Task 7 | You should complete **one** of the following: 8 | 9 | - Open an [issue](https://github.com/campus-experts/spring-2017/issues) and describe how you would improve upon an existing project's README. It can be any project! 10 | - Create a new README. This can be for one of your own projects, a fictional project, or a project you know of that doesn't yet have a README. When you've create the README, open an [issue](https://github.com/campus-experts/spring-2017/issues) and link to it. 11 | 12 | Once you've reviewed or completed a README, you'll receive feedback on your issue. **Remember** to take the time to read and comment on eachothers issues! 13 | 14 | ## What is a README and how do I create one? 15 | 16 | - https://help.github.com/articles/about-readmes/ 17 | 18 | ## Bonus activity 19 | If you've improved upon another README, or create a README for a project without one, you could open a pull request to contribute that README to the project! Just make sure to read their contributing guidelines (usually found in CONTRIBUTING.md) and follow any pull request templates. 20 | 21 | -------------------------------------------------------------------------------- /communities/university-of-waterloo/community-assessment.md: -------------------------------------------------------------------------------- 1 | # University of Waterloo 2 | 3 | ## Definition 4 | * Students interested in tech at the University of Waterloo 5 | 6 | ## Size 7 | * the university has 35,000 students and I think that approximately 20% of that, 7000 students, are likely in a technology-related program 8 | * I'd like this number to grow to possibly 8000, because I know of a lot of people who have wanted to switch into a tech-related major or do not even know if they would be a good fit for tech 9 | 10 | ## Resources 11 | * since Waterloo is a STEM-focused school and yet, there is not much student-led resources, nor specific resources for those in tech (eg. technical mock interviews, technical panels) 12 | * a lot of companies come to Waterloo to recruit and they often hold workshops 13 | 14 | ## Accessibility 15 | * accessibility for the resources are quite open but the downfall is that people often will not seek them out and there just isn't that much to begin with 16 | 17 | ## Interests 18 | * Waterloo is msotly an engineering school with a heavy interest in compuster science and software engineering 19 | 20 | ## Goals 21 | * because Waterloo has a co-op system, many students are studying to get a good co-op job 22 | 23 | ## Location 24 | * on Waterloo campus would be the best and most convenient 25 | * there are many buildings that can accomodate up to thousands of students 26 | 27 | ## Communication 28 | * there is a Facebook group for Computer Science within University of Waterloo 29 | * if a Github organization was started, it may help for resource sharing 30 | 31 | ## Culture 32 | * not sure how the culture is exactly with new ideas 33 | -------------------------------------------------------------------------------- /docs/write-an-abstract.md: -------------------------------------------------------------------------------- 1 | # Write a talk abstract! 2 | 3 | This week, we'll be hearing from Lara Hogan on "Demystifying Public Speaking". In this activity, we'll apply what we've learned, and write a talk abstract. 4 | 5 | When conferences or meetups look for talks, typically they put out what's called a "call for papers", or "call for proposals". This is where you pitch your talk idea to the conference organisers. Part of the CFP is usually the abstract; this is a short, snappy section that gets the audience excited about your talk. The abstract is what would appear in the brochure or on the website, describing your talk to attendees who may view it. An abstract should be a paragraph or two. 6 | 7 | ## The Task 8 | 9 | - Come up with a talk topic. This can be something based on your current expertise, or [something you want to learn and speak about in the future](http://weareallaweso.me/for_speakers/starting-with-nothing.html). 10 | - Write an abstract. You can find tips [here](http://weareallaweso.me/for_speakers/how-to-write-a-compelling-proposal.html) and [here](http://speaking.io/plan/writing-a-cfp/). 11 | - Create your abstract in your fork, in your communities subfolder (the [same place](https://github.com/campus-experts/spring-2017/blob/master/todos/week-1.md) you made the community assessment and impact proposal). 12 | - Open a pull request to submit your abstract. 13 | - Review and comment on other abstracts! 14 | 15 | ## Stretch goals 16 | 17 | You've written an abstract, why not submit it? 18 | - Check out [Papercall](http://papercall.io), [Technically Speaking](https://tinyletter.com/techspeak) or [Eventil](eventil.com) to find places to submit your talk. 19 | - You could also look for [local meetups](meetup.com) that may be interested. 20 | - Why not give the talk to other Campus Experts? :sparkles: Chat with Joe! 21 | 22 | -------------------------------------------------------------------------------- /communities/dortmund-student-hackers/community-assessment.md: -------------------------------------------------------------------------------- 1 | ### Definition 2 | 3 | Students interested in tech at the Dortmund campus. 4 | 5 | ### Size 6 | The community right now consists of 10 people. 7 | FH Dortmund ca. 12k students, TU Dortmund ca 30k students. Few thousand CS students + other related disciplines, so the goal till the end of the year would be to atleast double the number of people in the community. 8 | 9 | ### Resources 10 | A hacker space. 11 | We organize a hackathon once a year (DO!Hack) and Local Hack Day. 12 | I'm thinking about talking to local companies, if they would be interested in slots for speakers. 13 | 14 | ### Accessibility 15 | Resources are hard to get (different schools, different systems and no cooperation between students from both schools) 16 | 17 | ### Interests 18 | STEM-heavy schools 19 | 20 | ### Goals 21 | They are students hoping to get a degree. Most of them don't work during semester. 22 | It seems like they are trying to get in touch with companies, that are located around the campus (lots of startups but also already established mid-sized companies). These companies also have trouble reaching out to students. 23 | Some of them are passionate about developing, others seem to be very passionate about one particular technology and one particular use of it. 24 | 25 | Goals: set up monthly meetups with tech talks from students (so the students can get into public speaking) and with speakers from local companies. 26 | Each meetup would consist of 2-3 lighting talks (max. 10minutes each) and a talk by a speaker guest (up to 35 minutes). 27 | 28 | ### Location 29 | Dortmund Campus, lot's of rooms, that can be used by students for free. 30 | No water or snacks nearby, except for the automats in another building. 31 | 32 | ### Communication 33 | Whatsapp. 34 | Other means of communication could be beneficial. 35 | 36 | ### Culture 37 | Not sure how it really is. 38 | -------------------------------------------------------------------------------- /communities/dortmund-student-hackers/impact-proposal.md: -------------------------------------------------------------------------------- 1 | ## Summary of the Community's Needs 2 | 3 | /** 4 | Provide a summary of what you learned from your community assessment, coupled with the feedback from others (like the opinion of other Campus Experts, community leaders, and stakeholders). 5 | 6 | The following pieces might help strengthen this section: 7 | - **Community demographics**: Include data gathered from your community assessment like: the size of the community that you are targeting with your proposal, the educational background of your community, and the resources they currently have at their disposal and how accessible they are to the community. 8 | - **Communication**: For a community to thrive, they need to be able to communicate with each other, identify how your community prefers to communicate. 9 | - **Culture**: Summarize the existing culture within the community you are working with. 10 | **/ 11 | 12 | ## Your Proposal 13 | 14 | Lighting talks, 1-2 hours per month, Once a month on tuesday. 15 | Each person has 5-10 minutes to present a topic (something that they're interested in, they work on or just think is interesting for attendees). 16 | The community will stay in touch using Slack and Facebook groups and info about new meetups will be posted on meetup.com. 17 | 18 | 19 | ## Your Proposal's Impact 20 | 21 | Target audience: students from the field of STEM. 22 | Community needs: introducing students to public speaking, finding people interested in various topics. 23 | Resources: a room (students at my school can book rooms for free :)! ), posters and stickers for promoting the meetups (can get them very cheaply, so I'm gonna foot the bill). 24 | Media: finding speakers on campus (posters, talking to people), using social media to stay in touch with speakers/attendees. 25 | 26 | Content knowledge: 27 | 28 | Timeline: On december 13th we gonna meetup for lighting talks for the very first time. After that the talks will be organized on second tuesday of each month. 29 | 30 | ## Planning for the Future 31 | 32 | Success will be measured mostly by the number of speakers every month. The more we get, the more topics will be presented, the more people will be interested in attending. 33 | Between each meetup there will be 1 month, so that it will be possible to implement changes and think them through. 34 | -------------------------------------------------------------------------------- /communities/nobody/community-assessment.md: -------------------------------------------------------------------------------- 1 | # nobody 2 | 3 | ## Definition 4 | * A open source contributing group currently consists of students. 5 | * We contribute to the open source projects, and train more studetns to get involved. 6 | 7 | ## Size 8 | * Currently 9 | * We have about 13 students and 5 mentors here, and had about 4 or 5 students per generation before. 10 | * Ideally 11 | * It'll be good to have about 20~30 students each round! 12 | 13 | ## Resources 14 | * We teach and learn about git, GitHub flow, nodejs, shellscript and Linux related knowledges. 15 | * We have course every week, and also have non-periodical hackathons. 16 | 17 | ## Accessibility 18 | * The courses are after class. 19 | * Since we are all young students without child, so there is no childcare yet. 20 | * We don't have disabled member yet, and will be happy to make sure the accessibility for them once we are going to have! 21 | 22 | ## Interests 23 | * Our community consists of computer science students, but are not limited to that, hope to have some students from other majors in future. 24 | * All the free and open source related topics could be welcome here. 25 | 26 | ## Goals 27 | * People get involved in our community would 28 | 1. Like to learn about how to involve in open source project contribution, and learn some development tools/skills/experience. 29 | 2. Like to share about how to involve in open source project contribution, and teach some development tools/skills/experience. 30 | * We don't have any "degree" and I think nobody would come here for a degree. 31 | * We hope the students been trained will have the ability the contribute to many of the interesting projects by the correct work flow and methods. 32 | 33 | ## Location 34 | * Taiwan 35 | 36 | ## Communication 37 | * We use Telegram, Facebook and Slack to communicate with each others. 38 | 39 | ## Culture 40 | * Don't say we have nobody to do something or nobody can do something, we are the "nobody". 41 | * Instead of just complaining about the wrong things, we go and hack it, improve it. 42 | * Learn from the whole world, even from a passers-by, and spread what the good things you learned. 43 | * Contributing to the community as well as learning the skills at the same time, most of the practices will become real contributions in the world. 44 | -------------------------------------------------------------------------------- /communities/indian-institute-of-information-technology-allahabad/community-impact-proposal.md: -------------------------------------------------------------------------------- 1 | Now that you've [thought about your community's needs](community-assessment.md), it's time to take some action! Use this template to help you fill out your proposal. We invite you to change the contents of this template around and use the embedded tips and evaluation criteria to help you make a :sparkles: impact on your community. 2 | 3 | ## Summary of the Community's Needs 4 | 5 | Provide a summary of what you learned from your community assessment, coupled with the feedback from others (like the opinion of other Campus Experts, community leaders, and stakeholders). 6 | 7 | The following pieces might help strengthen this section: 8 | - **Community demographics**: Students at Indian Institute of Information Technology, Allahabad 9 | - **Communication**: Facebook Group, Gmail and IRC 10 | - **Culture**: The community is currently heavily focused on competitive programming. 11 | 12 | 13 | ## Your Proposal 14 | 15 | I would be starting a new course called [CS055](https://github.com/CS055/CS055) to bring interest among students in open source and development. 16 | I would be taking the help of 2 other GSOC students for this course. The plan is to conduct 1 class a week for the 17 | Students enrolled in the course. The classes would be conducted throughout the semester. 18 | 19 | ## Your Proposal's Impact 20 | 21 | - Target audience 22 | - Students being interested in free and open source projects but don't have enough domain knowledge and skills. 23 | - Community needs 24 | - A lot of students are interested in open source. But they are not sure how to get started to open source. 25 | - Resources 26 | - Classroom in University 27 | - It would be nice if GitHub can arrange some guest lectures(remote) for this course. 28 | - Media 29 | - We will have all the slides uploaded in the GitHub course repo 30 | - Content knowledge 31 | - I think we can handle the topics which we are going to deliver :). 32 | - Timeline 33 | - We are planning to start the course in the last week of Jan. It would be conducted every week throughout the semester 34 | 35 | ## Planning for the Future 36 | 37 | - When will you review the impact of your proposal? 38 | - Once the courses finished 39 | - How will you measure success? 40 | - How many students stayed till the end of the course. Number of GSOC selections in the next year can be also a good measure. 41 | - How frequently will you iterate on your community plans? 42 | - Every week -------------------------------------------------------------------------------- /communities/Montclair State University/community-assessment.md: -------------------------------------------------------------------------------- 1 | ### Definition 2 | 3 | Doubtful CS students who need reassuring and support. 4 | 5 | ### Size 6 | Montclair State University currently has 16,336 undergraduates with around a couple thousand being CS majors. MSU is known more for its liberal arts as its dance program is in the top 5 in the nation. cPersonally, I interact and meet many CS and STEM majors in chance encounters because there really is no “to-go” community event in my school. 7 | 8 | ### Resources 9 | Currently there are STEM field related career/major fairs and departmental resources like flyers, office hours, and online boards. 10 | 11 | ### Accessibility 12 | Out of the resources we actually have, they are quite accessible. Montclair State University prides itself on being handicap and disability friendly. Ranging from handicap buses that transport you around campus to almost all doors being automated. 13 | 14 | ### Interests 15 | My community is mainly made of liberal arts oriented students and out of the CS students within it, they are mainly open to all topics. 16 | 17 | ### Goals 18 | I want to create a hackathon for our school to highlight our schools technical aspect and a financially stable and fun hack nights to promote students to develop cool projects with other talented coders! 19 | 20 | ### Location 21 | We currently meet on Montclair State University campus, either in conference rooms or open lounges - depends on outside schedules. Parking at MSU is literal hell so most of the students attending these gatherings live on campus. Cost is free but planning is usually months in advance due to school’s lack of response. Normally, only a couple of students attend the meetings so there’s tons of space if it were ever needed. We don’t supply snack or drinks regularly so vending machines near by are the only source of snacks/beverages. 22 | 23 | ### Communication 24 | The only form of communication our tech community has is during face to face club meetings. The official Computer Science club we have is currently not active due to new school regulations. We could definitely benefit from other ways of communication. I’m interested in getting my community an official Facebook group or maybe a Slack channel to get everyone talking to each other. 25 | 26 | ### Culture 27 | The only real issue my community has trouble with is getting over the initial disagreement over regulations and policies from the school itself. It’s difficult and troublesome to continue facing these roadblocks when you’re trying to create opportunities and events in your community. -------------------------------------------------------------------------------- /communities/usc-project-athena/community-assessment.md: -------------------------------------------------------------------------------- 1 | # University of Southern California - Project Athena 2 | 3 | ### Definition 4 | - Females at USC or in the Southern California area who are interested in coding and tech 5 | 6 | ### Size 7 | - In April, we're hosting AthenaHacks, a hackathon to give this community an open and collaborative environment to build and learn new things. We had over 1000 applicants apply, and 400 RSVP'd. 8 | - I would like this community to be as big as possible to give everyone a wide-spread community of friends and connections. 9 | - Project Athena is in its first year, so ideally would like it to grow continuously. 10 | 11 | ### Resources 12 | - There are a few CS-related clubs on campus, such as Association for Computing Machinery (ACM), Women in Computing (WiC), Girls in Tech (GiT). 13 | - Clubs like ACM host a small hackathon every semester, and offer weekly workshops such as interview prep or web development. 14 | 15 | ### Accessibility 16 | - The current technical resources are focused on CS majors on a whole (like ACM). GiT and WiC are focused on creating a community, but don't offer technical workshops for females in CS. 17 | - Meetings are usually held at night since most students have class during the day. 18 | 19 | ### Interests 20 | - The community is heavily dominated by CS students, but there have been students who are interested in coding, or having a CS minor. 21 | - I hope that the community will also talk about impostor syndrome and the environment of the tech world for females. 22 | 23 | ### Goals 24 | - People get involved on campus to set themselves up for success in the future (ie. grad school, work) 25 | - The students are all hoping to complete their degree, and most want to work in industry. 26 | - Regardless of major, they are passionate about developing and learning new things. 27 | - Activities such as hackathons, group projects, and workshops can be implemented to set the community up for success. 28 | 29 | ### Location 30 | - Classrooms for meetings can be booked on USC's campus. 31 | - Community will meet in person and meetings can be recorded and posted online for those who cannot make it 32 | 33 | ### Communication 34 | - The community stays in touch through the Facebook group and the slack. 35 | - Email will be used for communication between the community and the organizing team. 36 | 37 | ### Culture 38 | - This community will be welcoming to all ideas and beliefs. There will be a 0% harrassment policy since this is supposed to be an open forum for women in tech to be themselves. 39 | - If there is a disagreement, things will be talked out peacefully between the parties until it is resolved. 40 | - The organizing team has written out a policy of how the club/community should be run. 41 | - Personally, I will oversee any community activities to make sure everyone is feeling safe and happy. 42 | -------------------------------------------------------------------------------- /communities/occidental-college/community-assessment.md: -------------------------------------------------------------------------------- 1 | # Occidental College 2 | 3 | ### Definition 4 | - Students interested in tech at Oxy 5 | - Open to anyone, heavily focusing on POCs and WOCs 6 | 7 | ### Size 8 | - There is roughly ~2000 students at Occidental. Oxy only has a computer science minor, with roughly ~120 students enrolled in a class every semester. However, roughly 20% of students are STEM majors. 9 | - I'd like to help grow the CS curriculum/minor, ideally to the same amount of Oxy STEM majors (~400) in the next couple years. 10 | 11 | ### Resources 12 | - Aside from the minor, there aren't many ways to learn about tech at Oxy. There are STEM-related clubs (POC in STEM, WiSTEM, and Oxy Open Source) that aren't actively hosting tech related meetings. 13 | - There is a CS opportuntity mailing list, filtered by the CS department chair. 14 | - Occidental has a Critical Maker Studio, where they offer beginner-level techy workshops and tinkering kits (Arduinos, Raspberry Pis). However they often do not get high numbers in attendance because lack of advertising. 15 | 16 | ### Accessibility 17 | - Current resources seem to only target those who are already tech savvy, restricting involvement from those with interest but limited tech skills. 18 | 19 | ### Interests 20 | - I am interested in opening up the community to all backgrounds, as long as one has an interest, they have a community! 21 | - That being said, the community will not only talk about tech, but the environment of tech and the gender/ethic/socio-economic gap. Topics will include imposter syndrome and how to combat these stereotypes. 22 | - Also interested in various interdisciplinary topics with CS, not limited to STEM topics. 23 | - 24 | 25 | ### Goals 26 | - At Occidental, most active clubs on campus advocate for some social good. I plan that this community will advocate for diversity in CS and STEM. 27 | - Though Oxy only has a minor, the department is expanding and hoping to have a major in the nearby future. With this community on campus, it will bring awareness needed to kickstart the major creation process. 28 | - Everyone in the club should have an interest in tech. 29 | - I hope to plan group projects and workshops for all levels. 30 | 31 | ### Location 32 | - Meeting rooms and classrooms can be rented out for a certain time everyday. 33 | - Community will meet online and in person 34 | 35 | ### Communication 36 | - Ideal ways for communication between the community would be: email, Facebook page/group, and a personal website. 37 | - Could your organization benefit from one or more of those, or another way of communicating? 38 | 39 | ### Culture 40 | - This community will be welcoming to all types of ideas. All new ideas will be communicated respectfully, regardless on what medium it is passed on. New members are a plus - always welcome! 41 | - The community will heavily be focused on inclusion in CS; any kind of harassment will not be tolerated. Harassment == removal from the community. 42 | -------------------------------------------------------------------------------- /communities/isi-web-devs/community-assessment.md: -------------------------------------------------------------------------------- 1 | ## Assessing Your Community's Needs 2 | 3 | ### Definition 4 | 5 | - ISI Web Devs 6 | 7 | Information Systems Engineers students interested on going beyond what is taught on the classrooms and learn web development related technologies. 8 | 9 | ### Size 10 | 11 | < TODO: figure out how many CS students are there > 12 | 13 | They goal is to have a medium size group between 50 & 100 students interested in helping each not only become great Information Systems Engineers but to also go beyond want is taught in the classrooms. 14 | 15 | ### Resources 16 | 17 | There are some talks given by the students and people from local companies. But they are not frequent and the group that attends is small. 18 | 19 | ### Accessibility 20 | 21 | Through the **Students Group** when can make the arrangements to get resources from the University. This is a bureaucratic process though. 22 | 23 | Meetings should be arranged during hours that are accessible for the majority of the students. 24 | 25 | * _The Students Group or Students Center is a group of students that represent the interests of all the students community. Kind of like a Students Party_. 26 | 27 | ### Interests 28 | 29 | They idea would be to target students that are already in the CS field. 30 | 31 | ### Goals 32 | 33 | They goal of the community is to grow as a whole and to be able cover the topics and areas that the current CS degree can not cover, specifically the areas related to web development. 34 | 35 | The goal would be to target students that are eager to learn not only what they can learn on the classrooms but go beyond that. 36 | 37 | Meetups, talks and workshops held monthly. Also build an online community focused on sharing and helping each others to grow as web developers. 38 | 39 | ### Location 40 | 41 | The best location for the meetings would be on campus since students go there daily. 42 | 43 | There is public transportation and free parking. 44 | 45 | It is possible to get free access to classrooms that can accommodate the participants well enough. These classrooms have projectors and desks so either workshops, meetups and talks can be held. 46 | 47 | ### Communication 48 | 49 | Students communicate mostly through social networks and messaging systems. 50 | 51 | Creating a Github organization, a Trello board and an Slack team would help cover communication. 52 | 53 | - **Github organization**: sharing resources, slides, workshops code, etc. 54 | - **Trello board**: voting workshops/talks topics, speakers, etc. 55 | - **Slack team**: have a space were students can share resources and help each others. Having a more open way to communicate between community members. 56 | 57 | ### Culture 58 | 59 | Students like new ideas, but they tend to be rude when they communicate online. A strong **Code of Conduct** is important to improve in this aspect. Disagreements should be handled politely and look for a solution that takes into account everybody's interests. Some kind of penalty should be included in the Code of Conduct. 60 | -------------------------------------------------------------------------------- /communities/indian-institute-of-information-technology-allahabad/community-assessment.md: -------------------------------------------------------------------------------- 1 | # Indian Institute of Information Technology Allahabad 2 | 3 | ### Definition 4 | Students at [Indian Institute of Information Technology Allahabad](http://iiita.ac.in/) 5 | 6 | ### Size 7 | 8 | There are ~1000 undergrads and ~500 postgraduates pursuing Information Technology (~70%) and related streams (~30% - Electronics and Communication Engineering, Bio-Medical and Stem Cell Engineering) in the university. We plan to target the students who are attending the first and second year. 9 | 10 | ### Resources 11 | 12 | Students occasionally conducts workshops on Web development, Competitive Programming, Open Source, App development etc. We host two hackathons every year at the university. IIIT-A hacks which is the inter university hackathon and [Hack In The North](http://www.hackinthenorth.com/) which is an inter University hackathon. 13 | 14 | ### Accessibility 15 | The workshops are accessible to everyone. We try to conduct workshops when there are no classes in the University. 16 | The classes are held in University classrooms. The workshops are beginner friendly and cover the concepts from beginning. Most of the workshops are taken by the members of the technical society of the college. 17 | 18 | ### Interests 19 | The community is made up of mostly students pursuing Information Technology. Other than competitive programming most of the students would be interested in web development, open source contributions and app development. 20 | 21 | ### Goals 22 | Very few students are interested in development at the University. Majority of the students spend their time doing competitive programming(hackerrank, spoj, codeforces etc). The main goal is to change this culture and encourage students to get involved in Open Source and Development. Most of the first year students attend the workshops. The participation from second and third years are very small. Even though there is a significant number of students participating in workshops very few stick with development after the first year. Most of them move to competitive programming and leave development and open source completely. The goal is to increase the number of students who continue with open source and development after the first year. 23 | 24 | ### Location 25 | The community gather in university classrooms and labs for attending workshops and hackathons. They are free to use but require permission from faculty incharge. All most all the students stay in campus hostels. Water is available 24x7. Snacks are available from the nearby cafeteria. 26 | 27 | ### Communication 28 | We use university mailing groups and facebook groups for communication. It would be good to have a chat room and a Github organization. We can possibly setup a Zulip instance or use a slack group for communication. 29 | 30 | ### Culture 31 | The community is welcoming to new students and ideas. Most of the workshops are focused on first years which we assume have zero knowledge on development. We try to teach everything from scratch. Disagreements are usually handled using polls. It would good to have well documented policies. -------------------------------------------------------------------------------- /communities/Entrenology-club-at-ALU/community-assessment.md: -------------------------------------------------------------------------------- 1 | Definition: The Entrenology club at ALU is a community of students who are interested and passionate about technology and 2 | entrepreneurship. Our goal is to build a community of developers who can ude their skills in implementing entrepreneurial ideas. 3 | 4 | Size: 5 | - Currently, the community is made up of about 50 students with close to 25 active members. 6 | - I would like to community to increase in number as much as possible as new students enroll. 7 | - The number of students increased after introducing some staff members to be our facilitators. 8 | 9 | Resources: 10 | - Currently, we have a computer lab with resources such as raspberry pi, arduinos, and other necessary tools. We equally have some 11 | students 12 | who are developers and highly qualifies staff members who help facilitate the community's activities. 13 | - We usually have meetups twice a month. We also organise office hours with he community leads and our assisting staff members. 14 | 15 | Accessibility: 16 | - The resources are readily available for any registered club or activities on campus and also use free online tools. 17 | - Our meetings are held on saturdays since no classes are organised on saturdays. 18 | - As of now, we haven't made any provision for people with disabilities. 19 | 20 | Interests: 21 | - Our community isn't only about computer science students but students who are interested in technology and have entreprenuerial ideas 22 | which technology will solve. 23 | - We are open to topics revolving around technology, programming, developing softwares, designing. 24 | 25 | Goals: 26 | - Our goal is to build a community of young developers who are passionate about technological innovations and are ready to drive 27 | entrepreneurial ideas by using the technical skills they acquire. 28 | - Students are interested in learning about computer programming, building up their skills, working together in team and sharing 29 | innovative 30 | ideas regardless of their major. 31 | - The students are hoping to learn skills that will permit them tobe developers and innovators. 32 | - Activities for our community could be hackathons, bootcamps and code sprints to boost participation and effective learning from each 33 | other. 34 | 35 | Location: 36 | - We usually meet on campus which is accessible to those on campus but difficult to those off campus. 37 | - Transportation might be needed at times while the space if free since we are registered. 38 | - The space can host close to 30 students, with comfortable seats and available projector. 39 | - Water or snacks are not available nearby but provision can be made for that. 40 | - 41 | Communication: 42 | - Our community has a mailing list and equally a facebook group. 43 | - Meetup invites are usually sent out through email while the facebook group is use to keep members updated about our activities. 44 | 45 | Culture: 46 | - We welcome new ideas but the idea has to be reviewed by the leaders of the group before validating it. 47 | - No document clearly stating our policies and procedures exists. 48 | - In case of a disagreement, the leaders of community must come to a compromise. 49 | - Personnaly, I handle disagreements b organising a separate meeting for the leaders only, to talk about the problem and decide on 50 | the best way forward. 51 | -------------------------------------------------------------------------------- /docs/logistics.md: -------------------------------------------------------------------------------- 1 | # Campus Expert Program Logistics 2 | 3 | - [Spring 2017 Repo](#spring-2017-repo) 4 | - [Your Fork](#your-fork) 5 | - [Office Hours](#office-hours) 6 | - [Slack Channel](#slack-channel) 7 | - [Facebook Group](#facebook-group) 8 | 9 | ### Spring 2017 Repo 10 | 11 | The [Spring 2017 Repo](https://github.com/campus-experts/spring-2017) is your cohort's repository (you're looking at it now!). You'll use this repo to access all program resources like the schedule of activities, but you can also open issues with questions or bugs you find. As you develop artifacts throughout the program, you'll also open Pull Requests against this repo to collaborate with other Campus Experts. 12 | 13 | ### Your Fork 14 | 15 | During week 1, you'll be directed to fork the Spring 2017 repo into your personal account. Your forked repo will house your program artifacts. You'll solicit feedback from other Campus Experts via a Pull Request against the Spring 2017 Repo. 16 | 17 | ### Office Hours 18 | 19 | Office hours will be hosted [on Zoom](https://github.zoom.us/j/4245140792) each week. We've scheduled a variety of office hours each week, providing options for each major time zone. You don't need to attend all of the office hours each week, but you should attend at least one. In the event that you are unable to attend one of the office hours, a recording will be made available. Some weeks (like Week 1) will contain structured content. Other weeks will contain unstructured time for Q&A with the facilitators and other Campus Experts. Although some of the office hours are titled by region, you can attend whichever event is convenient for you. 20 | 21 | Zoom is a video conferencing tool. We choose Zoom as it makes great recordings, and has some features to facilitate group discussions. You can find out more about it [here](http://zoom.us). If you have difficulty using the Zoom app, you can also phone into the office hours from any number, instructions are in the calendar invite. 22 | 23 | You can see the calendar below, where you can add or copy events to your own calendar: 24 | https://calendar.google.com/calendar/embed?src=github.com_ei82gchda2egevr7aukq6uj1f0%40group.calendar.google.com&ctz=Europe/London 25 | 26 | iCal feed of the office hours: https://calendar.google.com/calendar/ical/github.com_ei82gchda2egevr7aukq6uj1f0%40group.calendar.google.com/private-233bba914713b889d94dd47b339ede2e/basic.ics 27 | 28 | Additional office hours may be held to accommodate guest speakers. Recording of these office hours will also be made available. 29 | 30 | ### Slack Channel 31 | 32 | You've already received an invitation to the [GitHub Education Slack channel](http://githubeducation.slack.com). When joining the Slack, please set your username to your GitHub username. Use this space to have synchronous-ish discussions with other Campus Experts and facilitators. This is **your** space. 33 | 34 | Discussions about the training will take place in #ce-spring-2017, and announcements related to all Campus Experts will be made in #campus-experts-public. 35 | 36 | ### Facebook Group 37 | 38 | There is an optional Facebook group where we cross post announcements and news. It's meant to be an easier place to get notifications for those of you who use Facebook every day, but discussions and content will still primarily be on Slack and the repo. You can request membership [here](https://www.facebook.com/groups/1276763579081259/). 39 | -------------------------------------------------------------------------------- /communities/conu-hackers/community-assessment.md: -------------------------------------------------------------------------------- 1 | # Concordia University 2 | 3 | ### Definition 4 | - Any student at Concordia University interested in technology. These students want to discuss and share topics related to technology and who would like to improve their skills. 5 | 6 | ### Size 7 | - The current size shall be the members of the HackConcordia Facebook page, 1233 members. However, only a handful of members are active on the page. 8 | - An objective would be to double this number by the end of the school year. 9 | - The group started from 0 members in late 2014. 10 | 11 | ### Resources 12 | - The resources available to people in the community are average. The community is provided with articles from the tech community at large (outside of HackConcordia) about new and relevant topics in tech. 13 | - Utilizing the GitHub organization page to provide online tutorials, articles, and much more is an objective. 14 | - Without a permanent space, the community is unable to hold office hours and therefore communicates mainly through online messaging (e-mails, Facebook chat, Facebook group, etc.) 15 | - ConUHacks, the annual Concordia hackathon, is hosted in January for students to come together and collaborate on projects. 16 | 17 | ### Accessibility 18 | - Providing accessibilities to those who may not check Facebook frequently would be an objective i.e. uncovering new means of communication to reach as many members of the community in one place (whether it be through Slack or some form of online communication service). 19 | - Providing accessibility for people with disabilities is an objective (ensure website, tutorials, etc. when being created are mindful of those with disabilities) 20 | 21 | ### Interests 22 | - The community consists mainly of computer science and engineering students. There exists non-computer science and engineering students, however this number is very small. The community _may_ be interested in other topics, however with limited time and ressources it is difficult to consider. 23 | 24 | ### Goals 25 | - Members get involved in the community, because they are interested in collaborating to learn and compete in hackathons. 26 | - These members are interested in improving their skills and securing internships + fulltime jobs. 27 | - A main goal would be to utilize the GitHub organization page to provide a hub for collaborating on open-source projects with other students. Their objective would be to grow their skills, give back to the community, create useful systems, and build their CV. 28 | - In addition to the main goal, ensuring the community is open and welcoming to all participants must be maintained at all times. 29 | 30 | ### Location 31 | - The community is currently based solely online through a Facebook group (there does exist a website). 32 | - Establishing a hacker space on campus is nearly impossible as the University is located in the city with space being expensive and limited. 33 | 34 | ### Communication 35 | - The community communicates almost 100% through the Facebook group. There is a newsletter that gets used at most once a month. 36 | - There exists a Twitter account that is currently not active. 37 | - Finding other means of communications would be great to be able to expand and grow the community. 38 | 39 | ### Culture 40 | - The community is welcoming to new people, however it is only encouraged to share tech related items. 41 | - A policy or procedure would need to be established and documented to be able to handle arising disagreements. 42 | -------------------------------------------------------------------------------- /communities/sussex-hackers/community-impact-proposal.md: -------------------------------------------------------------------------------- 1 | ## Summary of the Community's Needs 2 | 3 | Provide a summary of what you learned from your community assessment, coupled with the feedback from others (like the opinion of other Campus Experts, community leaders, and stakeholders). 4 | 5 | The following pieces might help strengthen this section: 6 | - **Community demographics**: Include data gathered from your community assessment like: the size of the community that you are targeting with your proposal, the educational background of your community, and the resources they currently have at their disposal and how accessible they are to the community. 7 | - **Communication**: For a community to thrive, they need to be able to communicate with each other, identify how your community prefers to communicate. 8 | - **Culture**: Summarize the existing culture within the community you are working with. 9 | 10 | 11 | ## Your Proposal 12 | 13 | In this section, articulate the project you want to accomplish during the Campus Experts program; provide a brief summary of what you are planning to accomplish with your project. 14 | 15 | The following pieces might help strengthen this section: 16 | - **Timing**: You're starting this proposal in Week 2 of the program, and you'll need to execute on your project by Week 6, so you have just about 4 weeks to plan and execute your project. Set the scope appropriately. 17 | - **Community demographics**: If you are planning on increasing the size of the community, identify ways you are planning on accomplishing that. Explain how your efforts might help you create a more diverse community. 18 | - **Goals**: You identified the goals of your community assessment. Include a summary of those goals and how your proposal addresses those goals. 19 | - **Communication**: For a community to thrive, they need to be able to communicate with each other, identify how your community will be able to stay in-contact. This includes in-person meetings, webinars, and chat/forum platforms. 20 | 21 | 22 | ## Your Proposal's Impact 23 | 24 | In this section, analyze your community's needs against what your proposal aims to accomplish. 25 | Itemize each of the needs you hope to address with your proposal and indicate whether each of these needs are within the scope of your proposal. 26 | 27 | When identifying the impact of your proposal, you should focus on the following areas: 28 | - Target audience 29 | - Who are you expecting to impact based on your proposal? 30 | - Community needs 31 | - What specific issue are you addressing with your proposal? 32 | - Resources 33 | - What resources do you need to accomplish your proposal? 34 | - How will you obtain those resources? 35 | - Media 36 | - How are you preparing to deliver your community impact project? 37 | - What are you going to do to prepare to deliver the content? 38 | - Content knowledge 39 | - How knowledgeable are you on about the topic your community impact project focuses on? 40 | - What resources do you have at your disposal to enhance that knowledge? 41 | - Timeline 42 | - Develop a rough timeline for your community impact project. 43 | - If you are presenting content, identify the timing of your presentation. 44 | 45 | ## Planning for the Future 46 | 47 | In this section, think about how your efforts can expand beyond this 8-week program. Some questions you can answer that might help strengthen this section are: 48 | 49 | - When will you review the impact of your proposal? 50 | - How will you measure success? 51 | - How frequently will you iterate on your community plans? 52 | -------------------------------------------------------------------------------- /docs/community-assessment.md: -------------------------------------------------------------------------------- 1 | ## Assessing Your Community's Needs 2 | 3 | Fully understanding the needs of your community is a complex concept that will likely take lots of time, conversation, and observation. Depending on your situation, you may already have a great idea for what your community needs. You may not, and that's OK. We will go over these questions and topics broadly during week 1, and discuss responses in more detail in week 2. Here are some things to keep in mind when assessing your community and hoping to grow it. 4 | 5 | Please write down your 6 | - Answers to these questions for current community 7 | - Answers to these questions for **an ideal version** of your current community 8 | - Ideas on how to improve in each category 9 | 10 | After you've completed these questions, define your community in several short paragraphs for discussion in week 2. 11 | 12 | ### Definition 13 | - How would you define your community? Try to be open minded, but here are some examples of ways you could define your community: 14 | - Women that use Linux 15 | - Girls learning how to code 16 | - Students interested in tech in the Central Florida region 17 | - Computer Science teachers in the Orange County school district 18 | - Online computer programming professors 19 | - Hackers in and around London 20 | 21 | ### Size 22 | - How many people are currently in your community? 23 | - How many would you _like_ to be in your community? 24 | - Historically, has the group always been about the same size? If not, what brought on that change? 25 | 26 | ### Resources 27 | - What is currently available to people in your community to learn about tech? 28 | - Are there meetups, seminars, online tools, office hours, hackathons? 29 | 30 | ### Accessibility 31 | - How accessible are the current resources in your community? 32 | - Are meetings held during hours where people may be working? 33 | - Is there childcare available? 34 | 35 | ### Interests 36 | - Is your community made up only of computer science students? Are you OK with that? 37 | - Is your community open to other topics, or are their interests very specific? 38 | 39 | ### Goals 40 | - Why do people get involved in your community? 41 | - Are they students hoping to get a degree? 42 | - Are they trying to ramp-up to get a job? 43 | - Are they passionate about developing, regardless of their major? 44 | - What activities and goals can you set for your community based on their existing goals? 45 | 46 | ### Location 47 | - Where does your community currently gather? 48 | - Is it an online-only group so far, or is there a place where people can meet? 49 | - Is there parking, and if so, is it free? 50 | - Is there public transportation available to and from meet-ups? 51 | - Is the location accessible to those both on and off campus? 52 | - How much does it cost to use the space? 53 | - How flexible is the space for different types of presentations and meetings? 54 | - How many people can it fit? 55 | - Is there comfortable seating for all shapes and sizes? 56 | - Is there water or snacks available nearby? 57 | 58 | ### Communication 59 | - How does your community get in touch with one another? 60 | - Is there an email group, a GitHub organization, a Twitter account, a Facebook group, a chat room or channel? 61 | - Could your organization benefit from one or more of those, or another way of communicating? 62 | 63 | ### Culture 64 | - How welcoming is your community to new people and new ideas? 65 | - What happens if there is a disagreement? 66 | - Are there any policies or procedures in place, and are they documented? 67 | - How will you personally handle it? 68 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | Click on a week for details about the activities for that week. Future weeks will become available as the program progresses. 2 | 3 | # This Week 4 | 5 | Week | Starts | Ends | General Topics | :movie_camera: 6 | --- | --- | --- | --- | --- 7 | [Week 8](https://github.com/campus-experts/spring-2017/blob/master/todos/week-8.md) | Mon, 2017-05-15 | Sun, 2017-05-21 | Guest talk: Sara Chipps, Jewelbots. Guest talk: Peter Dave Hello 8 | [Week 7](https://github.com/campus-experts/spring-2017/blob/master/todos/week-7.md) | Mon, 2017-05-08 | Sun, 2017-05-14 | Guest talks: [Lara Hogan, Public Speaking](https://www.timeanddate.com/worldclock/converter.html?iso=20170510T160000&p1=136&p2=224&p3=75&p4=179&p5=2408&p6=241&p7=47&p8=37&p9=267). [Lee Dohm, Community Management](https://www.timeanddate.com/worldclock/converter.html?iso=20170511T160000&p1=136&p2=224&p3=179&p4=75&p5=tz_mut&p6=267&p7=37&p8=47&p9=2408&p10=241) | [Lara Hogan](https://www.dropbox.com/s/l4l3jqs9ohq30hf/larafixed.mp4?dl=0), [Lee Dohm](https://www.dropbox.com/s/1wnmxn5hyeaoo2j/leedohm.mp4?dl=0) 9 | [Week 6](https://github.com/campus-experts/spring-2017/blob/master/todos/week-6.md) | Mon, 2017-05-01 | Sun, 2017-05-04 | [Tech Talk: Phil Nash](https://github.com/campus-experts/spring-2017/issues/48) | [Phil Nash, Service workers](https://www.dropbox.com/s/a54bjekn69n848a/philnashserviceworkers.mp4?dl=0) 10 | [Week 5](https://github.com/campus-experts/spring-2017/blob/master/todos/week-5.md) | Mon, 2017-04-24 | Sun, 2017-04-30 | Guest talk: Andrew & Emma Seward, Community case study. [Tech Talk: James Milner](https://github.com/campus-experts/spring-2017/issues/39) | [Technottingham](https://www.dropbox.com/s/b1s37d9tbpmtrok/technottingham.mp4?dl=0). [Location based applications](https://www.dropbox.com/s/gkxfg9sgb8vmxjz/jamesmilnertalk.mp4?dl=0) 11 | [Week 4](todos/week-4.md) | Mon, 2017-04-17 | Sun, 2017-04-23 | [Guest talk: Matt Desmond & Jenn Leaver, Technical Writing](https://github.com/campus-experts/spring-2017/issues/25). [Tech Talk: Hugh Rawlinson, Music Computing](https://github.com/campus-experts/spring-2017/issues/28) | [Technical writing](https://www.dropbox.com/s/8mk2lfcrvmj02cb/week4.mp4?dl=0). [Music Computing](https://www.dropbox.com/s/yivpltknazr185h/hughmusic.mp4?dl=0). Office Hours [1](https://www.dropbox.com/s/w13ume3iy8dgb42/week4-19th.mp4?dl=0) [2](https://www.dropbox.com/s/6qhea1t6o9e8gef/week4-19th2.mp4?dl=0)| 12 | [Week 3](todos/week-3.md) | Mon, 2017-04-10 | Sun, 2017-04-16 | [Git/GitHub training](https://github.com/campus-experts/spring-2017/issues/22), [GraphQL tech talk, Impact proposal reviews](https://github.com/campus-experts/spring-2017/issues/12) | [Git/GitHub Workshop](https://www.dropbox.com/s/086yd5pq0m3e82f/gittalkcut.mp4?dl=0), [GraphQL Workshop](https://www.dropbox.com/s/nb6n9f9kr8nre1a/graphql.mp4?dl=0). [Office Hours](https://www.dropbox.com/s/luey2g2cq0ou6dg/week3-officehours.mp4?dl=0) 13 | [Week 2](todos/week-2.md) | Mon, 2017-04-03 | Sun, 2017-04-07 | Share assessment results & introduce impact proposal | [Video](https://www.dropbox.com/s/onvv9hdqwgptpww/week2.mp4?dl=0) 14 | [Week 1](todos/week-1.md) | Mon, 2017-03-27 | Sun, 2017-04-02 | Introductions, logistics, community assessment | [Video](https://www.dropbox.com/s/3anmr8othdfa2vy/29thMarch2017Spring.mp4?dl=0) 15 | 16 | ### Coming Up 17 | 18 | Week | Starts | Ends | General Topics 19 | --- | --- | --- | --- 20 | -------------------------------------------------------------------------------- /communities/sussex-hackers/community-assessment.md: -------------------------------------------------------------------------------- 1 | ## Assessing Your Community's Needs 2 | 3 | Fully understanding the needs of your community is a complex concept that will likely take lots of time, conversation, and observation. Depending on your situation, you may already have a great idea for what your community needs. You may not, and that's OK. We will go over these questions and topics broadly during week 1, and discuss responses in more detail in week 2. Here are some things to keep in mind when assessing your community and hoping to grow it. 4 | 5 | Please write down your 6 | - Answers to these questions for current community 7 | - Answers to these questions for **an ideal version** of your current community 8 | - Ideas on how to improve in each category 9 | 10 | After you've completed these questions, define your community in several short paragraphs for discussion in week 2. 11 | 12 | ### Definition 13 | - The current community I am a part of is hackers at Sussex University. 14 | - Ideally this will grow to a community in and around Brighton (to connect the two universities in that area). 15 | 16 | ### Size 17 | - The community is about 20 or so people, with low activity and low engagement. 18 | - I would ideally like to see a larger number of students to get involved with more frequent events to foster engagement. 19 | The group is still less than a year old, probably 6 months and has been lacking in community leaders. 20 | - I would like to create a community run online space where the community is in charge of its own growth. By which I would like to see anyone, society or individuals, able to create and run events how they see fit and make this accessable to anyone interested. 21 | 22 | ### Resources 23 | Hackathon society, external makerspace, occasional meetups, maybe a hackathon. 24 | I would like to see hardware resources and hardware and software workshops and consistant meetups to share ideas. 25 | 26 | ### Accessibility 27 | Society is accessable to students of Sussex. Makerspace meets on thursdays after 8 for dropins or more availability for members. 28 | Meetups aren't run by students. Hackathon is organised by the society, but currently infrequent in nature. 29 | 30 | ### Interests 31 | The community is only CS students, but I would like to see this grow and become accessable to students of all degrees, with an interest in technology. For now, I will be focusing on the CS students. 32 | 33 | ### Goals 34 | Students hoping to get a degree and some trying to ramp-up to get a job 35 | - What activities and goals can you set for your community based on their existing goals? 36 | 37 | ### Location 38 | Currently the location is online only. 39 | 40 | - Where does your community currently gather? 41 | - Is it an online-only group so far, or is there a place where people can meet? 42 | - Is there parking, and if so, is it free? 43 | - Is there public transportation available to and from meet-ups? 44 | - Is the location accessible to those both on and off campus? 45 | - How much does it cost to use the space? 46 | - How many people can it fit? 47 | - Is there comfortable seating for all shapes and sizes? 48 | - Is there water or snacks available nearby? 49 | 50 | ### Communication 51 | Facebook and Whatsapp chat. 52 | 53 | ### Culture 54 | Currently the community is inward facing. It has been described as Cliqué-y and uninviting. 55 | - How welcoming is your community to new people and new ideas? 56 | The group at present in unflexable and this needs work. Available space however is extremely flexable, on campus. 57 | - What happens if there is a disagreement? 58 | - How flexible is the space for different types of presentations and meetings? 59 | 60 | - Policies or procedures? 61 | A code of conduct exists for HackSoc, and I would like to incorperate this into the community as a standard 62 | 63 | - How will you personally handle it? 64 | Unsure. 65 | -------------------------------------------------------------------------------- /communities/acm-manipal/community-assessment.md: -------------------------------------------------------------------------------- 1 | ## Assessing Your Community's Needs 2 | 3 | Fully understanding the needs of your community is a complex concept that will likely take lots of time, conversation, and observation. Depending on your situation, you may already have a great idea for what your community needs. You may not, and that's OK. We will go over these questions and topics broadly during week 1, and discuss responses in more detail in week 2. Here are some things to keep in mind when assessing your community and hoping to grow it. 4 | 5 | Please write down your 6 | - Answers to these questions for current community 7 | - Answers to these questions for **an ideal version** of your current community 8 | - Ideas on how to improve in each category 9 | 10 | After you'be completed these questions, define your community in several short paragraphs for discussion in week 2. 11 | 12 | ### Definition 13 | ACM Manipal -- our university's ACM chapter 14 | 15 | ### Size 16 | We have about ~35 core committee members who're directly responsible for running the club. 17 | 18 | ### Resources 19 | We currently organise events, technical workshops throughout the semester. During breaks, we try to fit in a few online sessions on a technical topic. We also started a mentorship program for people new to CS by pairing them up with someone more experienced. Microsoft conducts a 24-hour annual hackathon called Code.Fun.Do. 20 | 21 | ### Accessibility 22 | My community is located in a place which can be best described as a college town. Hence, most people involved in any activity are students of my college itself. We normally organise events after classes when everyone ins 23 | 24 | ### Interests 25 | The community is made up primarily of people from CS and IT branches. However, there are a few students from Mechanical and Electrical as well. We do not exclude anyone based on their branch. 26 | There is a lot of focus on competitive programming in my college and very little on software development, research, etc. The whole goal of starting this ACM chapter is to broaden the perspective of how most people perceive CS and its extent. 27 | 28 | ### Goals 29 | People primarily get involved with this community to grow and advance their technical skills. Most of them do it to bag a good job, yes, a few people are really passionate about developing as well. 30 | Right now, I really want to focus on involvement with open source as a way of acquiring real world software development skills as none of this is a part of the average college curriculum. 31 | 32 | 33 | ### Location 34 | It's primarily in-person group. Our college provides us classrooms for meetings, events, etc for free. They're equipped with chairs, desks, a blackboard and projector. There are open spaces within a reach as well. Since most of our gatherings happen on campus and are attended by students, we do not need transportation. Water is available nearby but snacks aren't provided. 35 | 36 | ### Communication 37 | Our primary means of communication for the committee members is a WhatsApp group. We tried using Slack, but it was very difficult to get people there to discuss anything, hence we had to discontinue its use. We also have a Facebook group which we use for polls, long form discussions, etc. We communicate with other students from our college by means of mail and a Facebook page. 38 | 39 | ### Culture 40 | Our community is very welcoming to new people! We encourage everyone who wants to learn about CS to join us. Our goal is to a have an inclusive, safe environment for everyone who wants to be a part of our community. We also have a Code of Conduct in place to ensure the same. In case of a disagreement, we try to iron it by listening to all the parties involved and making the decision which is in the best interests of our community and all the people involved. We encourage everyone to chip in irrespective of what year or branch they belong to. 41 | 42 | -------------------------------------------------------------------------------- /communities/university-of-buea/community-impact-proposal.md: -------------------------------------------------------------------------------- 1 | ## Summary of the Community's Needs 2 | - The community consist mainly of Computer Science and Computer Engineering students. The only reliable resource we have is a location within our University campus which we can use for events. We also try to provide Internet connection during some events, but this tends to be costly. 3 | 4 | - In terms of communication we have a Google groups mailing list, Whatsapp group and also GitHub organization where we talk about community projects. Our community is still very new and so we are focused on creating awareness and we are very open to any help we can get. 5 | 6 | ## Proposal 7 | - Organize workshops to increase awareness about software development 8 | - This would involve a series of meetups and workshops to promote software development practices like open-source contribution. Following my previous meetup in November 2016, there would also be a GitHub workshop in January 2016.I would also organize further Google Summer of Code meetups between Febuary-March 2017 before GSoC applications begin. I would work on organizing hackerthons subsequently. The aim of this events is to increase the level awareness. 9 | 10 | - Training program for high school students 11 | - As part of my campus experts impact proposal, I am currently working on a training program which would involve a two months training for secondary schools students during the months of August and September. The aim of this program is to provide the students with knowledge of computer science topics like datastucture and coding and it would also promote participation in programs like the Google Code-In for secondary school students. The program would end with a hackerthon/contest where prices would be awarded to the best students, to motivate the participants to work harder. 12 | 13 | - The goals of my proposal include increasing awareness and motivation with respect to software development within my community. 14 | 15 | - So far we use [Mailing-List](https://groups.google.com/forum/#!forum/ubcsc-programming-club), WhatsApp, SMS, GitHub([wiki](https://github.com/ubcsc/ubcscwiki/wiki) etc) or any other possible means of communication available, to pass across information and stay in contact. 16 | 17 | ## Proposal's Impact 18 | - Target audience 19 | - Who are you expecting to impact based on your proposal? Computer science and engineering students of the University of Buea and High School students. 20 | - Community needs 21 | - The main issue I am addressing is, to increase the level of awareness and motivtion in my community. 22 | 23 | - Resources 24 | - We need reliable internet connection and sponsorship to run most of the events. I intend to request sponsorship support from Companies Like Google and Github 25 | 26 | - Media 27 | - My community impact project would be delivered mainly by hosting events and also though online media. I would do some research in order to prepare content to be delivered and I would also seek help from more experienced persons. 28 | 29 | - Content knowledge 30 | - I believe I have good knowledge and experience on the topics related to the content I would be presenting. There are also some very good resources online which I believe would be helpful, some of which I discovered through the GitHub campus expert training program. 31 | 32 | - Timeline 33 | - January: GitHub workshop. 34 | - Early March: GSoC Meetup. 35 | - August - September: High School Training program. 36 | - Content presentation would be about 40 minuter per presentation. 37 | 38 | ## Planning for the Future 39 | - When will you review the impact of your proposal? 40 | - Continually after every event 41 | 42 | - How will you measure success? 43 | - Number of active participants in the community. 44 | - Number of persons who develop or start contributing to useful open source 45 | 46 | - How frequently will you iterate on your community plans? 47 | - Very often. 48 | -------------------------------------------------------------------------------- /communities/conu-hackers/community-impact-proposal.md: -------------------------------------------------------------------------------- 1 | ## Summary of the Community's Needs 2 | 3 | Through the community assessment, the community size is determined to be the size of the [HackConcordia](https://www.facebook.com/groups/hackconcordia/) Facebook group, which is currently 1,283 members (compared to 1,233 members at the beginning of the campus experts program). The group is open to any student at Concordia University who interested in technology. These students want to discuss and share topics related to technology, they want to improve their skills, get experience with hands-on projects, and to land internships, part-time, and full-time positions. The group primarily targets students who are interested in going beyond what is taught in the classroom. 4 | 5 | The community interacts through the Facebook group. With the use of http://sociograph.io/, at this current time we are able to see that in the past month there have been 32 posts, from 19 different authors, with a combined total of 24 comments and 149 likes. 6 | 7 | ## The Proposal 8 | 9 | The beginning of an open source initiative at Concordia University. 10 | 11 | **Plan of attack**: The launch of this initiative will begin with a "Hack Week" in January from the 16th to the 19th. This will take place a week before HackConcordia's annual hackathon, [ConUHacks II](https://conuhacks.io/), happening January 21-22, 2017. 12 | 13 | Hack Week will be a week of tutorials hosted on campus and uploaded online to provide students with resources to leverage skills for the hackathon. Students will gain confidence and be equipped for their (potentially first) hackathon project. By lowering the barrier of entry for students through these workshops, we anticipate to have more projects submitted during the hackathon and foster a community of students with the desire to learn, to share, and to help one another. In addition, this initiative will also increase participation in the upcoming external hackathons across North America. Overall, we hope to conquer and eliminate the obstacles students face when wanting to contribute to open source projects. 14 | 15 | The first step will be to create a Free GitHub Organization page and to post some initial content. This content should include at a minimum the following: 16 | - An about section 17 | - How to get involved 18 | - Learning resources (external) 19 | - Workshops/tutorials created by Concordia students (minimum the ones for Hack Week) 20 | - Code of Conduct 21 | 22 | For now, communication between members will remain on the Facebook page. A Slack group will be considered once the group reaches a certain number of members and a consistent level of participation is present. 23 | 24 | ## Proposal's Impact 25 | 26 | *Target audience* 27 | - Students attending ConUHacks hackathon and any students interested in getting gaining knowledge on the tools and resources they can use to build their first hackathon project. And those who want to broaden their scope of technology. 28 | 29 | *Community needs* 30 | - The want to contribute to open source, but the fear/obstacles that are associated with open source. 31 | - The idea of having "workshops for the students by the students!". 32 | 33 | *Resources* 34 | - Current resources is to develop the 4-5 workshops/tutorials for the Hack Week. 35 | - The first open source project will be generated after the workshops and hackathon happen. 36 | 37 | *Timeline* 38 | - December 19th - January 9th: Prepare content for Organization page. 39 | - January 16th - January 19th: Hack Week. 40 | - January 21st - January 22nd: hackathon. 41 | - January 23rd > : First project is created. 42 | 43 | ## Planning for the Future 44 | 45 | - The proposal will be reviewed and will be reassessed every month for the first 3 months. At which point, a new interval for reviewing will be set. 46 | - Success will be measured based on the contributions to the GitHub organization page as well as the number of participants to external hackathons. 47 | -------------------------------------------------------------------------------- /docs/community-impact-proposal.md: -------------------------------------------------------------------------------- 1 | Now that you've [thought about your community's needs](community-assessment.md), it's time to take some action! Use this template to help you fill out your proposal. We invite you to change the contents of this template around and use the embedded tips and evaluation criteria to help you make a :sparkles: impact on your community. 2 | 3 | ## Summary of the Community's Needs 4 | 5 | Provide a summary of what you learned from your community assessment, coupled with the feedback from others (like the opinion of other Campus Experts, community leaders, and stakeholders). 6 | 7 | The following pieces might help strengthen this section: 8 | - **Community demographics**: Include data gathered from your community assessment like: the size of the community that you are targeting with your proposal, the educational background of your community, and the resources they currently have at their disposal and how accessible they are to the community. 9 | - **Communication**: For a community to thrive, they need to be able to communicate with each other, identify how your community prefers to communicate. 10 | - **Culture**: Summarize the existing culture within the community you are working with. 11 | 12 | 13 | ## Your Proposal 14 | 15 | In this section, articulate the project you want to accomplish during the Campus Experts program; provide a brief summary of what you are planning to accomplish with your project. 16 | 17 | The following pieces might help strengthen this section: 18 | - **Timing**: For most of you, it'll be nearing summer as you finish the training. This means exams, end of semester, and students disappearing to go on internships. This means it might be best to consider an event that happens after you return in the new semester: think about the impact that the new students will have on the event, and what the effect of students graduating will be. 19 | - **Community demographics**: If you are planning on increasing the size of the community, identify ways you are planning on accomplishing that. Explain how your efforts might help you create a more diverse community. 20 | - **Goals**: You identified the goals of your community assessment. Include a summary of those goals and how your proposal addresses those goals. 21 | - **Communication**: For a community to thrive, they need to be able to communicate with each other, identify how your community will be able to stay in-contact. This includes in-person meetings, webinars, and chat/forum platforms. 22 | 23 | 24 | ## Your Proposal's Impact 25 | 26 | In this section, analyze your community's needs against what your proposal aims to accomplish. 27 | Itemize each of the needs you hope to address with your proposal and indicate whether each of these needs are within the scope of your proposal. 28 | 29 | When identifying the impact of your proposal, you should focus on the following areas: 30 | - Target audience 31 | - Who are you expecting to impact based on your proposal? 32 | - Community needs 33 | - What specific issue are you addressing with your proposal? 34 | - Resources 35 | - What resources do you need to accomplish your proposal? 36 | - How will you obtain those resources? 37 | - Media 38 | - How are you preparing to deliver your community impact project? 39 | - What are you going to do to prepare to deliver the content? 40 | - Content knowledge 41 | - How knowledgeable are you on about the topic your community impact project focuses on? 42 | - What resources do you have at your disposal to enhance that knowledge? 43 | - Timeline 44 | - Develop a rough timeline for your community impact project. 45 | - If you are presenting content, identify the timing of your presentation. 46 | 47 | ## Planning for the Future 48 | 49 | In this section, think about how your efforts can expand beyond this 8-week program. Some questions you can answer that might help strengthen this section are: 50 | 51 | - When will you review the impact of your proposal? 52 | - How will you measure success? 53 | - How frequently will you iterate on your community plans? 54 | -------------------------------------------------------------------------------- /communities/depaul-css/community-assessment.md: -------------------------------------------------------------------------------- 1 | ## DePaul's Computer Science Society (CSS) 2 | 3 | ### Definition 4 | DePaul's CSS is a group of students that are interested in computer science. The goal of this club is to promote involvement outside of the classroom. 5 | The way that we do this is by promoting hackathons, holding 2-credit hour class, and organizing workshops, talks, and office visits. 6 | 7 | ### Size 8 | On Facebook, there are about 460 CSS members. This consists of current students, staff/faculty, and alumni. 9 | Roughly 25 students attend the weekly meetings. I'm hoping to increase the number of active members by 5 - 10. 10 | Historically, there have not been many active members that would attend the weekly meetings. 11 | 12 | I believe that with the changes that were made for this year have increased attendance rates because us board members 13 | have tried to put together workshops/talks that are beneficial and relevant to the students. 14 | These workshops and talks vary from learning how to make a basic Rails app to interview preparation to learning more about various companies. 15 | 16 | ### Resources 17 | We have weekly meetings, a Facebook group, and Slack team. 18 | Special events are shared in all platforms. CSS specific events are held in meetings. 19 | 20 | ### Accessibility 21 | Meetings are held after most classes are over with (Wednesdays at 5pm). People that have night classes are able to attend up to 30 minutes. 22 | Our online platforms are accessible to anyone that has a Facebook profile or `@mail.depaul.edu` email. 23 | If someone prefers to use their personal email over their school email, we send out special invites to Slack. 24 | The CDM building has elevators and wide doorways for those with disabilities. 25 | 26 | ### Interests 27 | Even though it is the Computer Science Society, members aren't required to major in CS. 28 | In fact, we have a variety of majors ranging from business to animation! 29 | While we focus mainly on CS-specific topics, we make sure to listen to any and all requests. 30 | For example, many people requested tutoring sessions and resume reviews, which we have started earlier this year. 31 | 32 | 33 | ### Goals 34 | People join CSS to learn more outside of their classes, make new friends, get help (e.g., tutoring, preparing for interviews, fixing their laptop, etc.), 35 | find hackathon team members, and more. Members are passionate about CS and want to get more out of simply attending their classes. 36 | If someone isn't getting what they want out of the community, they are more than welcome to make a request to one of the board members. 37 | 38 | ### Location 39 | CSS meets on Wednesdays in the CDM building. We tried to find a day and time where majority of people would be able to come in by taking a poll. 40 | The room that we have at the moment can comfortably fit up to 40 people and is accessible to everyone. Since the room is provided by DePaul, it's completely free to use. 41 | With DePaul's UPass (unlimited free rides on the CTA), students are able to easily travel to CDM or to any place where a special event is being held as long as it's in the city. 42 | At the moment, we do not provide snacks or drinks, but are looking into getting funding in order to provide it in the future quarters. 43 | Members can easily get food or drinks at one of the many places nearby (e.g., Starbucks, Potbelly's, Chipotle, Jimmy John's, etc.). 44 | If members can't attend the meetings, we share important information on the Slack team and Facebook group. 45 | Members can also reach out to anyone for help through the online platforms (e.g., asking for homework help, seeing who's attending a certain hackathon, or sharing cool tech info). 46 | 47 | ### Culture 48 | We're definitely a very welcoming community. Anyone is able to join! 49 | Some business students have joined to partner up with members to create apps. 50 | We also allow members to share any ideas that they may have for a meeting/workshop. 51 | If there is a disagreement, we follow DePaul's rules of reporting more serious conducts to the dean. 52 | If there is a disagreement amongst board members, we simply put things to a vote. 53 | -------------------------------------------------------------------------------- /communities/university-of-buea/community-assessment.md: -------------------------------------------------------------------------------- 1 | ## University of Buea 2 | 3 | ### Definition 4 | 5 | Students at the [University of Buea](http://ubuea.cm/), interested in technology. Both current students and alumni of the University of Buea make up the majority of the [Silicon Mountain](https://en.wikipedia.org/wiki/Silicon_Mountain) community which is known to be Cameroons largest technology hub. Within my community there is a high level of interest in software development and entrepreneurship. 6 | 7 | ### Size 8 | 9 | The University of Buea consists of about 20000 students, but just about 2500 of this students are enrolled into technology related programs and just about 500 of this students are involved in community activities. The number of persons participating in the community has been improving due to the increase in the number of students who have been participating in the Google Summer of Code each year. It would be good to increase the number of active community members to about 2000. 10 | 11 | ### Resources 12 | Some available resource in my community through which people can learn about tech include: 13 | - Internet. 14 | - PL(Programming Lnaguage) meetups. These are free programming language meetups which have been organized by the [Google Developer Group (GDG) Buea](https://www.facebook.com/gdgbuea/) and a local tech startup called [Skademy](https://www.skademy.com/). 15 | - Conferences like the [Silicon Mountain conference](http://www.smconf.org/) have been organized in the past year and also tech events like the Google IO extended. 16 | - Internship opportunities are also provided by local tech startups. 17 | 18 | ### Accessibility 19 | Most of the resources are very accessible, but the only issue may be the cost of some resources like Internet and paying for the location where events are held. Meetings are sometimes held when people are working but most of the information is also passed across through mailing lists and online forums so that everyone could be informed of latest updates.No provisions have been made for people with disabilities. 20 | 21 | ### Interests 22 | My community consists mostly of computer science and computer engineering students but there are also some few people with different academic background. 23 | We are open to other topics but we also have some topics which are our focus for the moment like software development and entrepreneurship. 24 | 25 | ### Goals 26 | There is an increase in the number of people getting involved, since they have been motivated by the success of other members of the community and also by the amount of effort that is been put to teach people skills that are essential in the tech community. 27 | 28 | A majority of the people in the community are students hoping to get a degree in computer science or computer engineering. 29 | 30 | My goal for my community would be to increase the number of open-source contributors and also the number of participants in the Google Summer of Code and I would also like to organize more competitive events like hackerthons in order to increase the number of active community members. 31 | 32 | ### Location 33 | For training events we use some classes at our university, but for other events like hackerthons, some alumni of our university who are members of the community voluntarily give out some space at their startup and for events like conference we pay for some larger halls in town, which is really expensive. Depending on the event we can accommodate from 10 – 2000 persons and we always make sure water and snacks are provided at any event. 34 | 35 | ### Communication 36 | We mostly use GitHub, online forums, mailing list, Twitter, Facebook, SMS and any other possible means of communication available. 37 | 38 | ### Culture 39 | My community is in need for, and open to new people and new ideas.It has always been our desire to invite people from other parts of the world to present talks or workshop during some of our events or conferences. A vote is used to resolve the disagreement but most of the procedures or policies are not officially documented and I would personally handle it through a debate to get more information on why a specific option should be chosen over another. 40 | -------------------------------------------------------------------------------- /communities/nobody/community-impact-proposal.md: -------------------------------------------------------------------------------- 1 | Now that you've [thought about your community's needs](community-assessment.md), it's time to take some action! Use this template to help you fill out your proposal. We invite you to change the contents of this template around and use the embedded tips and evaluation criteria to help you make a :sparkles: impact on your community. 2 | 3 | ## Summary of the Community's Needs 4 | 5 | Provide a summary of what you learned from your community assessment, coupled with the feedback from others (like the opinion of other Campus Experts, community leaders, and stakeholders). 6 | 7 | The following pieces might help strengthen this section: 8 | - **Community demographics**: 5 core members, 15 normal members, 100% consists of CS student, we core members are now trying to train the 15 new comes about git, GitHub flow, markdown and other essentials about contributing to the FOSS projects. 9 | - **Communication**: Slack, Facebook group and messenger, face to fact communication. 10 | - **Culture**: Start to learn, don't be afraid of the past experience, contribute back to the community! 11 | 12 | 13 | ## Your Proposal 14 | 15 | We now have 2 hours course every week, and will have a workshop in December, maybe a hackathon in January, I'm not going to make the increasing the community size a main goal, as most of the students super interested in contributing free and open source projects already started their way to do it, our target are those students are just interested, but didn't find their way to start yet, the students want to be trained. 16 | 17 | Our gaol is to make the students originally didn't know about git, GitHub, open source culture can be able to pick the projects they are using and then contribute to the project they picked. We start from collecting the super easy to solve [issues](https://github.com/cdnjs/cdnjs/issues/9248) for the students, those issues are libraries on CDNJS lack of license info, the listed libraries in the issue are picked by confirmation of the clear license info, and send pull request from using GitHub web UI to add the missing license, students will learn the concept of git and GitHub, web library, how to fork repository, create git branch, write commit message, mention related issue on GitHub, and then send the pull request on GitHub. After that, there are courses about git command line, GitHub workflow, git branching, ... kinds of related skills and knowledge to make them get the essential skill to contribute. 18 | 19 | We now use Facebook group, Facebook messenger, Slack, and GitHub (issue/PR comment) to communicate with each other. 20 | 21 | ## Your Proposal's Impact 22 | 23 | In this section, analyze your community's needs against what your proposal aims to accomplish. 24 | Itemize each of the needs you hope to address with your proposal and indicate whether each of these needs are within the scope of your proposal. 25 | 26 | When identifying the impact of your proposal, you should focus on the following areas: 27 | - Target audience 28 | - Students being interested in free and open source projects but don't have enough domain knowledge and skills. 29 | - Community needs 30 | - Introducing about free and open source projects, how they impact our life and the world, why should we learn and what will we get from it. 31 | - Resources 32 | - Classroom or meeting room, we could bower from school. 33 | - Some helpful swags(not sure if I should call it swag), like GitHub Git cheat sheet poster and stickers, I already received some from GitHub Education. 34 | - Teachers and TAs, we already have 5 active people as core members and few more not very active but can also help and join. 35 | - Foods and drinks for workshop and hackathon, I could buy some. 36 | - Media 37 | - We'll have slides for it 38 | - Content knowledge 39 | - I think I'm fine with the topics as that are the things I'm doing everyday :) 40 | - Timeline 41 | - We now have a two hours course (almost) every and about an one hour TA hour, will keep it to the end of this semester and decide if we'll still have it in the winter vacation. 42 | - We are going to held a workshop in one of the December weekends 43 | 44 | ## Planning for the Future 45 | 46 | In this section, think about how your efforts can expand beyond this 8-week program. Some questions you can answer that might help strengthen this section are: 47 | 48 | - When will you review the impact of your proposal? 49 | - Once the courses finished 50 | - How will you measure success? 51 | - See if we'll get new students to join core members 52 | - How frequently will you iterate on your community plans? 53 | - Every two weeks or one month 54 | -------------------------------------------------------------------------------- /communities/students-new-to-hacker-culture/community-assessment.md: -------------------------------------------------------------------------------- 1 | # GitHub Campus Experts 2 | ### Week 1 3 | 4 | About my community: 5 | 6 | ##### Definition 7 | Durham's technical community is very much focused on theoretical Computer Science, so the idea of a hackathon is completely foreign to most students here. If I were to summarize my community in one line, it would be: 8 | ~ "University students who are just discovering the hacker culture" 9 | 10 | It would be wonderful to see our computer scientists more involved in extra-curricular activities, which would also give them the opportunity to bond with others over a love for technology, regardless of their academic backgrounds. Perhaps by bringing the hacker culture to them, and exposing them to the benefits of getting involved, they would be more inclined to participate. Raising awareness, and giving them the opportunity to experience it for themselves, is definitely the way forward. 11 | 12 | ##### Size 13 | The community still remains rather small, with roughly 20 staying committed to the Computing Society. Fewer than 10 people, amongst the hundreds of us, regularly attend hackathons. It would truly be ideal if at least a quarter of all our computer science students were involved in hackathons. The group was much smaller before, with CompSoc having only 5 members, but we have been able to entice people to commit to the society by running workshops, and giving out free pizza with the money that we get from sponsors. 14 | 15 | ##### Resources 16 | Lectures, and lectures alone. The students are not driven to learn things outside of the course because they don't realize just how much they are capable of building. Meetups happen every week with CompSoc, where we occasionally hold workshops and teaching sessions, but the responsibility of organizing it falls in the hands of very few people, making it difficult to hold such events too often (with the exception of the meetups). We would definitely appreciate support from our department to run events. Hopefully, by sparking enthusiasm, more would be encouraged to take part, allowing work to be delegated and more events to take place. 17 | 18 | ##### Accessibility 19 | Meetings are held after lectures on Monday, so it has not been possible to get access to any form of professional help, such as from lecturers, demonstrators, etc. The venue where the meetups are held is also quite a distance away from the University's main site, which may deter some from attending the meetup. 20 | 21 | ##### Interests 22 | My community is mostly made up of computer science students, but hopefully that will change. I would like to get as many people involved in technology as possible, so that they can cultivate a passion for it; and it's a real plus that a diverse skillset tends to churn out the best ideas, too. 23 | 24 | ##### Goals 25 | They usually get involved to learn how to code (and to enjoy the free pizza, for sure). The business students tend to get involved to learn more about the different ways that they can leverage tech for their startup ideas. It would likely encourage a lot more people to join if we could run regular workshops for our students. 26 | 27 | ##### Location 28 | The community usually gathers in the Students' Union building, which is conveniently located close to town. However, the infrastructure in the building is really lacking; we do not even have enough power sockets to supply our members power with. Having no A/V equipment in the building makes running workshops difficult, too; but, more importantly, without any rooms suitable for large numbers of people, it has truly been a challenge to try to keep students committed, especially when they are forced to squeeze uncomfortably into a room. At most, the room could hold 40 people, and there are vending machines nearby. 29 | 30 | ##### Communication 31 | There is a Slack channel, which is currently still undersubscribed, so our primary communication channel is through internal mailing lists, as well as a Facebook page. Having more communication channels might not be beneficial, but we should instead focus on improving the students' response to these channels. 32 | 33 | ##### Culture 34 | We encourage anyone to come for the events, regardless of their skills. Since we would like more people to get involved, we definitely value their input as much as we value ours. We run on a casual basis, so no documentation is involved, although we do have health and safety rules. If a disagreement were to occur, I would probably mediate the two disagreeing parties and talk things through with them, as we recently did between CompSoc and Entrepreneurs Durham -- which eventually led to cooperation between the two societies. -------------------------------------------------------------------------------- /communities/uclutechsoc/community-assessment.md: -------------------------------------------------------------------------------- 1 | ## Assessing Your Community's Needs 2 | 3 | ### Definition 4 | - Students at University College London interested in technology and more specifically programming 5 | 6 | 7 | ### Size 8 | - ~600 people are signed up as members, [steadily growing.](http://techsoc.io/graphs/) 9 | Around 200 of those actively go to events and participate in the community. 10 | 11 | - There are 30000 students at UCL. Ideally we want them all to be excited about technology :wink: Realistically we actively encourage students to join our community, but there is no number we are trying to hit. We are in a comfortable position regarding community size. Our focus tends to lie more on making the community more tightly knit than growing it. 12 | 13 | - Historically, the community has been slightly smaller. We made it easier this year for newcomers to join by making our membership free and introducing a mentorship programme. 14 | 15 | ### Resources 16 | - In terms of learning material, we usually refer them to the vast amounts of amazing online resources. 17 | - In terms of what we ourselves offer, at the moment we run a few things: 18 | - Socials (casual get-togethers) 19 | - Projects (theme-based, 10 week long opportunities to work on something collaboratively with others) 20 | - Harvard CS50 (Beginner workshop series in C) 21 | - Coding & Cookies (Beginner workshop series currently focused on web development) 22 | - Mentorship Programme (A programme in which more involved members of the community introduce newer members and make them feel welcome) 23 | - Hackathons 24 | - Tech Talks (Talks on interesting topics around technology from interesting speakers.) 25 | - Career opportunities 26 | - One off-events (such as an introduction to hackathons, an introduction to open source, etc.) 27 | - and more to come soon! 28 | 29 | ### Accessibility 30 | - The community is fairly accessible, mostly because all of the members and the committee tend to be very helpful and welcoming. 31 | - Events tend to be in the evening, so most students tend to be free, but some clashes are unavoidable. 32 | - However, there is definitely more that can be done. We cater best to our average member, who tends not to have kids or a disability. As a result we tend not to have any special arrangements in place. We can definitely do more to improve on this. 33 | - This year we have a postgrad representative to help us reach out more and better understand the needs of the postgraduate community. 34 | 35 | ### Interests 36 | - The community is made up of people who care about technology, who like to build and learn new things. 37 | - A big proportion of the community is Computer Science, but we're becoming more diverse every year. Here is a [graph](http://techsoc.io/graphs/) that gives an indication of how our members are distributed across multiple departments. 38 | - The community tends to be very open to all sorts of interests, as long as there is some sort of relation to technology. 39 | 40 | ### Goals 41 | - There are quite a few reasons students get involved in the community: 42 | - They want to meet people that have a common interest 43 | - They want to learn about a particular technology (for example Virtual Reality) 44 | - They want to get started with programming 45 | - They are interested in one of the topics covered by a Tech Talk 46 | - They are interested in some of the career opportunities the society sponsors offer. 47 | 48 | 49 | ### Location 50 | - The community is very much at home around the [UCL Bloomsbury Campus](https://www.google.com/maps/place/University+College+London/@51.5245592,-0.1362288,17z/data=!3m1!4b1!4m5!3m4!1s0x48761b2f69173579:0xd008c67faecc133e!8m2!3d51.5245592!4d-0.1340401) 51 | - We make extensive use of the university's rooms. Those rooms can typically meet our requirements for the number of people that attend our events. 52 | - There are a variety of different rooms and facilities that can accommodate our range of events. 53 | - Because of the central London location, there is: 54 | - limited/no parking 55 | - very good public transportation 56 | - very good access to water and snacks 57 | 58 | ### Communication 59 | - There are quite a few communication platforms. Mostly communication tends to happen via: 60 | - The Facebook page and group 61 | - Our community slack team 62 | - Our weekly newsletter 63 | - In person at events! 64 | 65 | - We're also present and active on Twitter, Instagram, Snapchat, Medium, and YouTube 66 | 67 | 68 | ### Culture 69 | - The community tends to be very welcoming to new people and new ideas. It's important to try out things :smile: 70 | - We have a code of conduct and there are various more specific policies surrounding for example posting on the Facebook group. 71 | -------------------------------------------------------------------------------- /communities/citytechsoc/community-impact-proposal.md: -------------------------------------------------------------------------------- 1 | ### Summary of Community’s needs 2 | 3 | - Community demographics: There are nearly 200 students who have signed up to our weekly mailing list and showed some form of interest in the society’s activities. But only about 20 students actively participate in events that we host and refer them to. The members are majority Computer Science students. 4 | - Communication: We use Slack as our primary means of enabling the community to reach each other, but it’s proving difficult to keep people on there since it’s another app to use. So we’re exploring using Facebook more. We also send out weekly emails of upcoming events and interesting resources. 5 | - Culture: The culture is still new and developing, but we aim to keep it as open and flexible as possible, given a lot of the students haven’t been exposed to the content we provide so there are naturally questions students have that we want them to be able to ask. We try to provide events and content based on the interests of the community members to some extent 6 | 7 | ### Proposal 8 | 9 | The primary project I had planned to do as part of the Campus Experts programme was to organise the Local Hack Day as a way for students within City’s community to get an introductory taste of what a Hackathon is and why they should value them. 10 | 11 | - Timing: The date for Local Hack Day coincided nicely with Week 6 of the programme which was well timed. 12 | - Community demographics: We wanted to market the event to as many different people as possible to see who would be interested in a hack day. We used our usual social media accounts but we also put up posters all over campus, no just within the technical departments. We ended up getting not just CS students, but also structural engineering, sociology and math students who really enjoyed the event. 13 | - Goals: Some of the goals I identified as part of the Community Assessment were having introductions to different technical related items such as Git, as well as introducing hackathons to students who’ve never been. I think this was the right project to achieve those goals, since there a some workshops and the event taught the attendees that hackathons are primarily a place of learning, as opposed to competing. 14 | - Communication: We continued to use Slack as a way of communicating leading up to the event, during and afterwards, so students could share what they had done. 15 | 16 | ### Proposal Impact 17 | 18 | Target Audience: The target audience of the Local Hack Day is current community members who have never been to a hackathon and want to understand what it is without investing too much (such as travel and overnight stays). 19 | Community needs: The specific issue that I was addressing was the misunderstanding of hackathons and their purpose. 20 | Resources: The main resource was a venue, some swag and food. We managed to book a good-sized common room on campus, and MLH and GitHub provided pretty cool swag (thanks!). We also managed to get the Department of Computer Science to cover the cost of the food. The Campus Experts talk on Git also proved to be very useful for my workshop on how to use Git and GitHub. 21 | Media: To prepare for the impact project, I spent time practicing the delivery of my Git workshop, as well as delegating some of the workshops to other great members of the team. 22 | Content Knowledge: Since I was primarily managing the overall day as well as delivering the Git workshop, I spent time going through the best practical ways to teach Git. The resources pointed to by the Campus Experts speakers proved to be useful. 23 | Timeline: The Local Hack Day itself was a single day of course. I had planned for my Git workshop to be 45 minutes long, but it ended up running over an hour since I got some interesting and very welcome questions. But a lot of the other plans I’ve made will require a longer time frame, such as ongoing meetups, workshops and hackathons. 24 | 25 | ### Planning for the future 26 | 27 | There were other initiatives that I had planned on the Experts programme that would be implemented the following term: 28 | 29 | - Continuing and diversifying the content of the weekly emails that we sent to our members. 30 | - Sending out a questionnaire in the new year to get a better understanding of what the community wanted to get out of the events we held, the type of events that we ran, as well as to get a better understanding of how the community’s demographic may have changed over the last few months. 31 | - Hosting the Global Game Jam, since there is a strong interest in game development among CS with Games Technology students. 32 | - More frequent events where the community can congregate and talk/share. 33 | - HackCity 34 | 35 | I plan to iterate on my community plans every 3-4 weeks based on feedback that we get from our community members. 36 | -------------------------------------------------------------------------------- /communities/FPU-Tech-Community/impact-proposal.md: -------------------------------------------------------------------------------- 1 | ##Summary of the Community's Needs 2 | The current size of our community is around 100 students. Due to our University being only 2 years old we have around 1,300 students enrolled, all with technology focused majors. Being in an all STEM school I would like to expand the community to at least 15% of the school’s population, or 195 students. This means that I want to expand the community to about double its current population. 3 | 4 | The community at FPU, has access to internet and computers to program on. They also have limited access to hardware. This hardware includes Arduinos, Raspberry Pi’s, basic electronics, and some drones. Occasionally, we will get guest speakers from industry to come and give free seminars and there are clubs that regularly give workshops. 5 | 6 | My community prefers to communicate through email and social media. Email is most effective for announcements and outreach, and social media is better for regular reminders for meetings or events, and questions. 7 | 8 | Currently the hacker community is underdeveloped; There is a large amount of interest however the community is not engaged or does not know how to become engaged. I would like to believe that our community is very welcoming. However, because we all have become so close, it may be turning off new members. This is like how you may be hesitant to join a new friend group because it seems like it is already established and you are unneeded. I think it is good that we are aware of this though and make an effort to personally walk up to new faces and introduce ourselves/make conversation. 9 | 10 | ##Your Proposal 11 | I want to focus on growing the hacking community here at FPU. We know that there is more interest in hacking and we still have more to grow to meet that interest. At the beginning of the next semester I plan on having a couple meetups to try and reach out to the underclassmen. Hopefully this will also help us reach out to more women in CS who are interested in learning or being more involved. At the meeting I am going to encourage any new people to go to the next meeting and bring a friend. 12 | 13 | One of my main goals is to establish an online platform for our community. I want to create a webpage where everyone can have easy access to our resources and tools. This way more people can become involved/benefit even if they cannot make our club meetings or workshops. 14 | 15 | ##Your Proposal's Impact 16 | My proposal is going to impact new students with an interest in being more involved and who want to learn more. Hopefully that will include more women, because women are hard to reach out to and retain at FPU. If the outreach is successful we will be able to make a large community of people who can reach out to each other for anything they may need. To make sure that the proposal happens I am going to need to find someone to sponsor the meet up. I am going to start internally, and ask the CS professors if they know of any resources for people trying to get students more involved in coding. The next step after that would be to write up a proposal for SGA and see if there is a possibility that the student government can support the event. The next possible resources are clubs within the university. I will ask different related clubs if they would be interested in helping promote the event and, if they have any resources, if they would be interested in paying for food. 17 | 18 | One possible outcome of the meetup as well is finding someone to help me make an online media platform (website). The plan is to make a subdomain under the hackathon’s domain, PolyHacks. The website would most likely be shape.polyhacks.com and it would be a way for us (the community leaders) to let people know when events are happening, post resources or workshops we have made, and propagate our community values. I have been in charge of community outreach and branding for the hackathon, so I believe I have all the tools needed to recruit new people, the hard part is retaining them after the event. I am also going to be talking to the student life coordinator for the university to try and make sure I am reaching out as efficiently as possible. 19 | 20 | I don’t have a very concrete timeline but I would like to have the meet up in early January (at the beginning of the semester) and have an online platform up and running by the beginning of March. 21 | 22 | ##Planning for the Future 23 | The effectiveness of the event will be observable after the next two meetings. That is when we will be able to see the retention and growth rate difference. A successful event could result in a >10% increase in attendance to our meetings. As long as we have interest in hacking I will do everything I can to empower the people in the community. As long as they are interested, I will help them find new opportunities and knowledgeable people. 24 | -------------------------------------------------------------------------------- /communities/FPU-Tech-Community/community-assesment.md: -------------------------------------------------------------------------------- 1 | #Assessing Your Community's Needs 2 | 3 | ##Definition 4 | Florida Polytechnic University’s tech community. FPU is an all STEM university that was established in 2014. I want to focus on our students with technology focused majors and interests. 5 | 6 | ##Size 7 | The current size of our community is around 100 students. Due to our University being only 2 years old we have around 1,300 students enrolled, all with technology focused majors. Being in an all STEM school I would like to expand the community to at least 15% of the school’s population, or 195 students. This means that I want to expand the community to about double its current population. 8 | The funny thing is we have no history. 9 | Since 2014, the size of this community has been increasing as the school’s population increases. This isn’t a natural growth because at the beginning of the school’s history, most of the students were freshman, then last year they were mostly freshman and sophomore, and so on. Therefore next year will be the first year there is a “full house” of students. This means that only after next year can the community begin to have a natural, or organic, growth. And around then I would like to shoot for 15% of the population again. 10 | 11 | ##Resources 12 | Currently our school has few resources for people in our community to learn about tech. Occasionally, we will get guest speakers from industry to come and give free seminars and there are clubs that regularly give workshops. We struggle with obtaining the resources to produce the quantity and quality of workshops that we would like. Within our community there are only a hand full that are willing to give a workshop or feel qualified to teach others. 13 | 14 | ##Accessibility 15 | Our school has a small population and that results in very personal relationships within the majority of our community. Ultimately this results in very easy accessibility to resources even between students and faculty. However, one of our biggest struggles is encouraging students to reach out to others to get the resources they are looking for. 16 | 17 | ##Interests 18 | Something kind of unique about our community is that computer science majors are by far the major with the lowest participation. Even our Hackathon organizing team is entirely made up of Electrical, Mechanical and Computer Engineering Majors. We provide a pretty wide variety of workshops, from software to hardware to graphic design, but we would like more participation from computer science and other majors. 19 | 20 | ##Goals 21 | Our main goal for our community is to bridge the gap between what we learn in class and creating. We’ve managed to maintain a group of passionate developers from all majors, but we would like to get more participation from freshman and computer science students. 22 | Our current goals are to hold at least 3 workshops a semester, a Hack Day in the fall and our Hackathon (PolyHacks) in the spring. In addition to this, we hold club meetings at least twice a month to keep students involved and grow our community. 23 | 24 | ##Location 25 | Our location has its advantaged and disadvantages. Currently our university has one academics building. As an all STEM school we also have no library and all of our literature is online. Therefore there is really only one building for all club activities to take place. This has its disadvantages because we have to wait until after the majority of classes are over to be able to reserve a room and having late meetings turns off commuters that have to drive home. The advantage is that everyone in the university can easily access the building and attend our meetings/events. 26 | Another large advantage is that the venue is 100% free and we can accommodate to fit a large amount of people comfortably in a meeting. Also, parking is not really an issue because there is free parking a reasonable walking distance away from the building. 27 | 28 | ##Communication 29 | Currently our main form of communication has been through an email group. However, this has proven to be quite limiting because we can only contact people who have already attended a meeting which makes it hard to reach out to others. 30 | Some of our struggles have been keeping our social media up to date and communicating with freshman. We have a facebook group with a decent amount of members but we fail to update it regularly on meetings and events. Also, 46% of our school is currently made up of freshman and we do not have a decent way of communicating with them. This is something we hope to find a solution for in the near future. 31 | 32 | ##Culture 33 | I would like to believe that our community is very welcoming. However, because we all have become so close, it may be turning off new members. This is like how you may be hesitant to join a new friend group because it seems like it is already established and you are unneeded. I think it is good that we are aware of this though and make an effort to personally walk up to new faces and introduce ourselves/make conversation. 34 | -------------------------------------------------------------------------------- /communities/Entrenology-club-at-ALU/community impact proposal.md: -------------------------------------------------------------------------------- 1 | ## Summary of the Community's Needs 2 | 3 | Provide a summary of what you learned from your community assessment, coupled with the feedback from others (like the opinion of other Campus Experts, community leaders, and stakeholders). 4 | 5 | The following pieces might help strengthen this section: 6 | - **Community demographics**: The community is made up of close to 50 students (Hoping to increase with more freshmen this year) with about 25 consistent and active members and 5 leads. Most of the members are beginners in HTML/CSS, Java and Android who have started 7 | their majors in Computer science but the community is opened to all students interested in the entrepreneurship side of coding. The leaders are experienced HTML/CSS, Java and Android developers who are equally passionate about entrepreneurship. Equally, experienced staff members are available as facilitators. We equally have a shared folder on google drive containing some resources. 8 | - **Communication**: Invites to events/meetups are usually sent via email to all on our mailing list while reminders are posted our our Facebook page. We equally use posters to spread the word about upcoming events. 9 | - **Culture**: Our community is opened to any new member from any major who shows interest and commitment and also to new ideas which must be validated by the leaders. No document clearly stating our policies and procedures but in case of conflict, the community leaders are required to discuss and agree on a possible solution. We equally engage our members to always hear their opinion in order to act for a common good. 10 | 11 | 12 | ## Your Proposal 13 | 14 | In this section, articulate the project you want to accomplish during the Campus Experts program; provide a brief summary of what you are planning to accomplish with your project. 15 | 16 | The following pieces might help strengthen this section: 17 | - **Timing**: This proposal is to be executed as from January 2017 when school resumes. 18 | - **Community demographics**: We plan on informing other students in neigboring Universities and also to get interested freshmen involved in our activities through posters, announcements during other events on campus and facebook. This will help create a diverse community of students from different universities, majors, sexes but with a common interest. 19 | - **Goals**: The general aim is to build a community of developers, innovators, creatives and changemakers who can used their coding skills to implement entrepreneurial ideas. The first goal will be to introduce the community to GitHub. 20 | - **Communication**: We hope to continue meeting twice monthly with event invites being sent out by email and added on google calendar. Also, meetups/hackathons or codesprings will be posted on the community's facebook page and posters created depending on the event. 21 | 22 | 23 | ## Your Proposal's Impact 24 | 25 | In this section, analyze your community's needs against what your proposal aims to accomplish. 26 | Itemize each of the needs you hope to address with your proposal and indicate whether each of these needs are within the scope of your proposal. 27 | 28 | When identifying the impact of your proposal, you should focus on the following areas: 29 | - Target audience 30 | - Beginners in Computer Science at the African Leadership University. 31 | - Community needs 32 | - Helping students develop coding skills in HTML/CSS, Java, Android and using GitHub. 33 | - Resources 34 | - Many more mentors and experienced facilitators will be invited during our events. 35 | - I will download the necessary tools before the events. 36 | - I will get a projector from school. 37 | - Media 38 | - I plan on delivering this community impact proposal during a workshop on campus. 39 | - The date of the workshop will be announced during an event called "The Assembly" which brings together all staffs and students. 40 | - To deliver the content, I intend on preparing some slides on the basics, getting the necessary tools ready. 41 | - Content knowledge 42 | - I have been using GitHub and I intend to enhance my knowledge using video tutorials and mentors. 43 | - Timeline 44 | - Develop a rough timeline for your community impact project. 45 | - I wil do my research work on GitHub and how important it is for developers. 46 | - Then prepare a powerpoint presentation that will last 30mins. 47 | - After the presentation, we will have 1 hour to help each community member create their GitHub accounts and familiarize themselves. 48 | 49 | ## Planning for the Future 50 | 51 | In this section, think about how your efforts can expand beyond this 8-week program. Some questions you can answer that might help strengthen this section are: 52 | 53 | - When will you review the impact of your proposal? After each event/meetup, I will review the impact of my proposal. 54 | - How will you measure success? The success of my proposal will be measured by the increase in the number and quality of projects students will be working on showing increase in skills. 55 | - How frequently will you iterate on your community plans? After reviewing the success of an event, the results will indicate if to iterate or not. 56 | -------------------------------------------------------------------------------- /communities/kcl-tech-society/community-impact-proposal.md: -------------------------------------------------------------------------------- 1 | Now that you've [thought about your community's needs](community-assessment.md), it's time to take some action! Use this template to help you fill out your proposal. We invite you to change the contents of this template around and use the embedded tips and evaluation criteria to help you make a :sparkles: impact on your community. 2 | 3 | ## Summary of the Community's Needs 4 | 5 | Provide a summary of what you learned from your community assessment, coupled with the feedback from others (like the opinion of other Campus Experts, community leaders, and stakeholders). 6 | 7 | The following pieces might help strengthen this section: 8 | - **Community demographics**: 30 core members, 100 members that come and go; The majority (>90%) are studying a CS degree, the rest are studying some other STEM degree (Maths, Neuroscience, Physics). The core team provides computer science workshops(Android/iOS, Web, C++, algorithms), hackathons (HackKing's, HackLondon, First Year Hack, Local Day Hack), surgery-style sessions (SOS Java). These are open to everyone and are beginner friendly and the materials are provided on the Tech Societies' Github page or specific facebook pages. 9 | - **Communication**: There are two slack channels (one aimed at organising the events/workshops/hackathons, one public), facebook pages for each event/workshop/hackathon, twitter, snapchat, newsletter, dedicated website. Facebook pages are the most used, followed by slack and twitter. Core members sent newsletter weekly. 10 | - **Culture**: Everyone is welcomed, regardless of their belief, ethnicity and background. We don't really have disagreements, but when they do happen, we try to act in a peaceful and constructive way and we also try to avoid toxic people. In terms of the core team, we want everyone to be involved in something (event/workshop etc). Those who do not prove their interest in the society and are not proactive are asked to leave. 11 | 12 | 13 | ## Your Proposal 14 | 15 | In this section, articulate the project you want to accomplish during the Campus Experts program; provide a brief summary of what you are planning to accomplish with your project. 16 | 17 | The following pieces might help strengthen this section: 18 | - **Timing**: The changes I am thinking of will applied during next academic year after being debated with the rest of the committee. 19 | - **Community demographics**:The majority of the community studies computer science. We need more people from other STEM subject getting involved,as technology is present in all these fields in one way or another. I would like the proportion of CS/Non-CS students to be fairly equal. I would like to approach the Non-CS students with some workshops/events aimed at technology used in their specific areas. 20 | - **Goals**: Balance the CS/Non-CS students involved with the community to a ratio of 70-30(from 90-10). 21 | - **Communication**: Organisation wise, slack and google drive to store important documents. Communication between the core team and the rest of the community is best deliver through facebook groups and newsletter. 22 | 23 | 24 | ## Your Proposal's Impact 25 | 26 | In this section, analyze your community's needs against what your proposal aims to accomplish. 27 | Itemize each of the needs you hope to address with your proposal and indicate whether each of these needs are within the scope of your proposal. 28 | 29 | When identifying the impact of your proposal, you should focus on the following areas: 30 | - Target audience 31 | - Non-CS STEM students withing King's College London 32 | - Community needs 33 | - Introducing the target audience to technology events and involving them into events/workshops about their specific area of interest (ie Physics) 34 | - Resources 35 | - Workshops content on different areas, connection with people working with technology from the specific areas, identifying interesting events. 36 | - Lots of researching, asking people already involved in the community for guidance. 37 | - Media 38 | - Interactive workshops(ie live coding), presentations, guiding people to attend events of interest. 39 | - Researching, inviting people of interest to do sessions with the students. 40 | - Content knowledge 41 | - Not very knowledgeable, but I am prepare to learn from others in order to achieve the goals described above. 42 | - Connection to other societies in the university, professors and people in the community with more knowledge than me. 43 | - Timeline 44 | - Research about technology in other STEM areas -> identify people that could help me achieve this -> plan a useful workshop/event with a person of interest 45 | - Advertise interesting events on our page 46 | - Collaborate with other sociaties 47 | 48 | ## Planning for the Future 49 | 50 | In this section, think about how your efforts can expand beyond this 8-week program. Some questions you can answer that might help strengthen this section are: 51 | 52 | - I will review the impact proposal once I have more knowledge of what can be done 53 | - My efforts will be successful when I see more Non-CS students getting involved with our community 54 | - I will iterate after every attempted event and see how I can improve the next one 55 | -------------------------------------------------------------------------------- /communities/Entrenology-club-at-ALU/community-impact-proposal.md: -------------------------------------------------------------------------------- 1 | 2 | ## Summary of the Community's Needs 3 | 4 | Provide a summary of what you learned from your community assessment, coupled with the feedback from others (like the opinion of other Campus Experts, community leaders, and stakeholders). 5 | 6 | The following pieces might help strengthen this section: 7 | - **Community demographics**: The community is made up of close to 50 students (Hoping to increase with more freshmen this year) with about 25 consistent and active members and 5 leads. Most of the members are beginners in HTML/CSS, Java and Android who have started 8 | their majors in Computer science but the community is opened to all students interested in the entrepreneurship side of coding. The leaders are experienced HTML/CSS, Java and Android developers who are equally passionate about entrepreneurship. Equally, experienced staff members are available as facilitators. We equally have a shared folder on google drive containing some resources. 9 | - **Communication**: Invites to events/meetups are usually sent via email to all on our mailing list while reminders are posted our our Facebook page. We equally use posters to spread the word about upcoming events. 10 | - **Culture**: Our community is opened to any new member from any major who shows interest and commitment and also to new ideas which must be validated by the leaders. No document clearly stating our policies and procedures but in case of conflict, the community leaders are required to discuss and agree on a possible solution. We equally engage our members to always hear their opinion in order to act for a common good. 11 | 12 | 13 | ## Your Proposal 14 | 15 | In this section, articulate the project you want to accomplish during the Campus Experts program; provide a brief summary of what you are planning to accomplish with your project. 16 | 17 | The following pieces might help strengthen this section: 18 | - **Timing**: This proposal is to be executed as from January 2017 when school resumes. 19 | - **Community demographics**: We plan on informing other students in neigboring Universities and also to get interested freshmen involved in our activities through posters, announcements during other events on campus and facebook. This will help create a diverse community of students from different universities, majors, sexes but with a common interest. 20 | - **Goals**: The general aim is to build a community of developers, innovators, creatives and changemakers who can used their coding skills to implement entrepreneurial ideas. The first goal will be to introduce the community to GitHub. 21 | - **Communication**: We hope to continue meeting twice monthly with event invites being sent out by email and added on google calendar. Also, meetups/hackathons or codesprings will be posted on the community's facebook page and posters created depending on the event. 22 | 23 | 24 | ## Your Proposal's Impact 25 | 26 | In this section, analyze your community's needs against what your proposal aims to accomplish. 27 | Itemize each of the needs you hope to address with your proposal and indicate whether each of these needs are within the scope of your proposal. 28 | 29 | When identifying the impact of your proposal, you should focus on the following areas: 30 | - Target audience 31 | - Beginners in Computer Science at the African Leadership University. 32 | - Community needs 33 | - Helping students develop coding skills in HTML/CSS, Java, Android and using GitHub. 34 | - Resources 35 | - Many more mentors and experienced facilitators will be invited during our events. 36 | - I will download the necessary tools before the events. 37 | - I will get a projector from school. 38 | - Media 39 | - I plan on delivering this community impact proposal during a workshop on campus. 40 | - The date of the workshop will be announced during an event called "The Assembly" which brings together all staffs and students. 41 | - To deliver the content, I intend on preparing some slides on the basics, getting the necessary tools ready. 42 | - Content knowledge 43 | - I have been using GitHub and I intend to enhance my knowledge using video tutorials and mentors. 44 | - Timeline 45 | - Develop a rough timeline for your community impact project. 46 | - I wil do my research work on GitHub and how important it is for developers. 47 | - Then prepare a powerpoint presentation that will last 30mins. 48 | - After the presentation, we will have 1 hour to help each community member create their GitHub accounts and familiarize themselves. 49 | 50 | ## Planning for the Future 51 | 52 | In this section, think about how your efforts can expand beyond this 8-week program. Some questions you can answer that might help strengthen this section are: 53 | 54 | - When will you review the impact of your proposal? After each event/meetup, I will review the impact of my proposal. 55 | - How will you measure success? The success of my proposal will be measured by the increase in the number and quality of projects students will be working on showing increase in skills. 56 | - How frequently will you iterate on your community plans? After reviewing the success of an event, the results will indicate if to iterate or not. 57 | 58 | -------------------------------------------------------------------------------- /communities/manitoba-hackers/manitoba-impact-proposal.md: -------------------------------------------------------------------------------- 1 | 2 | ## Summary of the Community's Needs 3 | 4 | **Community demographics**: 5 | 6 | * The Manitoba Hacker community is relatively small with approximately 25-30 members who attend our local student hacker club called .devClub. It is a community centered around weekly meetings and occasional hack days where students can meet to create a project of their choosing. Most students who choose to join the community are in their upper years as very few first years are aware of the club’s existence. The potential to increase the community’s size is massive as there has been an influx of new students into both the departments of Computer Science (>700 students) and Computer Engineering. 7 | 8 | * The community also is able to obtain room bookings from the university free of charge as well as event funding from the Science Student Association and UMSU (University of Manitoba Student Union). Furthermore, the Computer Science Students Association also help host events for students during the school year. The club lacks hardware tools, but have a maker space called SkullSpace that is approximately 40 minutes away by bus. 9 | 10 | 11 | **Communication**: 12 | * Our community tends to communicate predominantly through slack and through facebook. There is a dedicated Facebook group called “Manitoba Hackers” that posts regularly about hacker-related events. In the future, our hope is to utilize email as an option as well. 13 | 14 | **Culture** 15 | * The culture within the hacker community has yet to be defined as students are quite dispersed throughout the department. There is not much of a unified community at school since the students who attend the U of M mainly live with their parents and commute from their homes. Many students choose to leave shortly after classes are over. That said, a small group of dedicated students do meet on a weekly basis, but there is almost an underground culture to the club. Communication about the club is kept to word-of-mouth and may exclude new students who want to join. 16 | 17 | 18 | ## Proposal 19 | 20 | * Over the next few months, I hope to set up a dedicated website and blog for the student hacker community as I will be away from campus. I want to grow the online community around the school and help to work with my friends to build the hacker community. Posts will be about hacker events around the city and also helping students organize their local hacker events. At the same time, I will work closely with the local developers club to organize a weekly speaker series and to invite speakers from around Winnipeg to talk and educate students about new technologies. We will also try working with MLH and setting up local host events to complement our own planned events. 21 | 22 | 23 | * For those who can’t physically make it to meetings, a webinar will also be under consideration for student hackers to meet online and to bring in guest speakers as well. 24 | 25 | * There will also be a focus on getting students to try attending hackathons that are in the surround area such as MinneHacks in Minneapolis and Calhacks. 26 | The goals of the community assessment is to get more people hacking and to build new side projects. Students also want to build industry skills to complement their classroom education. With the webinar, online blog and the hacker nights at school, students will be able to accomplish all of these goals. 27 | 28 | 29 | 30 | ## Impact 31 | - Target audience: 32 | - The target audience are the university students in Manitoba who are interested in technology and building projects. 33 | - Community needs 34 | - We are specifically trying to increase the hacker community and encourage students to meet others and build upon their ideas using technology. 35 | - Resources 36 | - The primary need of the community is to obtain funding to support students who come to events such as purchasing new hardware such as arduinos, raspberry pi’s and paying for food at hacker nights. 37 | - We will be applying for funding with the university’s student union as well as getting funding with the science student association and the department of Computer Science. 38 | - Media 39 | - It is my goal to identify other student leaders in the community to help with running the developer club on campus. Since the plan is quite ambitious, there will be a need to fund a group of dedicated students who can take time off school to help support the group. 40 | - Content knowledge 41 | - I have had experience meeting other hackers at other hackathons and learned mostly through discussion on what helps hacker growth. At the same time, I hope to reach out to others at the MLH organizer slack as well as emailing the Florida Hackers for ideas. 42 | 43 | 44 | ## Planning for the Future 45 | - I will review the proposal in mid February to see if the plans are still feasible and speak with other GitHub experts on their opinions on whether our plans can be improved. 46 | - The main measure of success will be done through surveys sent out to the community and asking for feedback from participants on their satisfaction. If most students rate their satisfaction as either average or above average, then the community would be considered a success. Other metrics could be counting the number of people attending webinars and meetings. If there are >30 people attending consistently, then that would also be considered a success. 47 | - Community plans will be iterated every 4 months and meetings will be set up with other student leaders to figure out the proper course of action. 48 | 49 | -------------------------------------------------------------------------------- /communities/UNAM-Engineering/community-impact-proposal.md: -------------------------------------------------------------------------------- 1 | # Comunity Impact UNAM Engineering 2 | 3 | ## Summary of the Community's Needs 4 | 5 | After holding a several conversations with some members of the Computer 6 | Engineering School, I was able to get a deeper understanding on some core 7 | points the community has been looking for or found missing in their period 8 | as students. The topics that were discussed the most were: 9 | 1. **Design and Develop Algorithms**. 10 | 2. **Develop Real-life apps** (Experience). 11 | 3. **Public Speaking** (Soft Skills in General). 12 | 4. **Meeting Industry Leaders and Companies** (Aspirational Figures and Trayectories). 13 | 5. **Leadership** 14 | 6. **What to do after graduation?** (Work/Masters/?) 15 | 7. **Resume and Interview practices** 16 | 17 | 18 | ### Community demographics 19 | - **Size**: 42 Registered Members; 10 members sharing repos. 20 | - **Age**: 18-30 years. 21 | - **Main Backgrounds**: Computer Engineers, Computer Scientists. 22 | - **Secondary Backgrounds**: Psicologists, Lawyers, etc. 23 | - **Resources**: 24 | - **People**: We have students we lots of expierience and freshmen as well. 25 | Also we have some teachers who mainly work on open source. 26 | - **Github Organization**: Our main platform it allows us to achieve our 27 | goals. It allows discussiones, code shaing and information gathering. 28 | 29 | ### Communication 30 | We usually communicate in private FB Messages or via Github Issues. 31 | 32 | ### Culture 33 | We strongly believe that opening school projects gives others the posibility to 34 | learn from others. We're open to have a diverse community based on the will to learn 35 | and share. We know that students on the campus are developing projects and research 36 | papers that should be proudly shown to others outside the university. 37 | 38 | 39 | ## Proposal 40 | What we're looking for in the first month of the project is to have a well 41 | stablished structure on the Github Organization that would allow new commers 42 | to join the group/conversation easily and understand the collaboration method 43 | that we apply. Also would like to hold small meetups so the community starts 44 | to know each other and get to meet people in the industry. 45 | 46 | 47 | ### Timing 48 | | Week | Title | Description | Status | 49 | |:----:|:-------------------------------:|:-----------------------------------------------------------------------------------------------------------------:|:---------------------------:| 50 | | 3 | Research Similar Organizations | Look for similar organization on github that use organizations to manage the group. Analyze what works for them. | :white_square_button: | 51 | | 4 | Implement Structure Changes | After finishing the research on other organizations implement the structure they have in our GH organization. | :white_square_button: | 52 | | 5 | Generate event calendar | Publish an event calendar on the organization that includes on campus events and off campus events as well. | :white_square_button: | 53 | | 6 | Push Changes & Feedback | Push changes to GH Organization and receive feedback from the members. | :white_square_button: | 54 | 55 | ### Community Demographics 56 | For these first steps will be focusing on Computer Engineers since they are 57 | the closest demographic with the availability that others enter as well. 58 | 59 | ### Goals 60 | - **Structure, structure, structure**. 61 | - Event Planning. 62 | - Improve accesibility for new commers. 63 | - Recruit **Awesome** People. 64 | 65 | ### Communication 66 | This shoud be discussed. Though Slack sounds as a tipical answer to communication 67 | problems it can also be the source of people deserting projects. 68 | 69 | 70 | ## Proposal's Impact 71 | 72 | In this section, analyze your community's needs against what your proposal aims to accomplish. 73 | Itemize each of the needs you hope to address with your proposal and indicate whether each of these needs are within the scope of your proposal. 74 | 75 | When identifying the impact of your proposal, you should focus on the following areas: 76 | - **Target audience** 77 | - Computer Engineering Students. 78 | - Computer Science Students. 79 | - **Community needs** 80 | - Building a Structure for the Community. 81 | - Meeting Industry Leaders 82 | - Develop Real Life Applications. 83 | - **Resources** 84 | - We know many people from the dev community that could give 85 | interesting talks. 86 | - We know people from other communities that could have usefull tips to 87 | improve the github organization. 88 | - **Media** 89 | - The delivery of the proposal will be seen in the Github Organization Page. 90 | - We could see if life streaming works and ad the links to the meetups in the 91 | GH repo. 92 | - **Content knowledge** 93 | - We're well connected in the industry robably would need to investigate more about 94 | other organizations that take place in GH and their structures. 95 | 96 | ## Planning for the Future 97 | 98 | - When will you review the impact of your proposal? 99 | 100 | Two weeks after Week 6 101 | 102 | - How will you measure success? 103 | 104 | By the conversations that take place on the Organization, the number of newcommers, amount of new 105 | repos in the gitjub organization and meetup assitance. 106 | 107 | - How frequently will you iterate on your community plans? 108 | 109 | Every 2 months. 110 | -------------------------------------------------------------------------------- /communities/KMAhackers/community-assessment.md: -------------------------------------------------------------------------------- 1 | KMA hackers - not really a name, but will do for now 2 | 3 | Needed Now: stable meetup schedule, existing community is little and rarely has something in common out of study events. 4 | 5 | 6 | -idea - Initiate event quotas (external/internal, fun/educational/challenges), start organizational group of people, 7 | start monthly meetings and have also some fun on schedule, not only lections , but dinners, quests and hardware workshops. 8 | 9 | 10 | Needed ideally: promotion. The faculty is really awesome technically and not very big, 11 | which helps to build long-term relationships among studs and teachers, but even within KMA university people 12 | have no idea about what FI students are studying and doing socially. When high schoolers decide where to go after graduation, 13 | they rarely concider KMA FI, because they don`t know how cool it really is. 14 | 15 | 16 | -idea - Start online community and have a row of events for newbies in spring and fall, widely announced. 17 | Take part officially in the biggest conferences and partner with the most established IT groups from other unis. 18 | 19 | 20 | --Definition 21 | KMA hackers - (after Kyiv-Mohyla academy) - can also transform into Key Men Around or Keeping Magic Available 22 | (no drugs, I mean.. we will have to work on it yet :) ) 23 | 24 | 25 | --Actual size is up to hundred, of whom maybe 25-35 are active and engaged. Others are mainly busy with their own work 26 | or join communities of other unis. 27 | I do not look to draw up quantity, rather quality, but increasing group activity must bring more people (like 80), 28 | and having a 10-20 alumnis with us would benefit serious projects and tech talks. 29 | Historically size was defined by FI faculty of KMA - being a rather small university, faculty of informatics has just three BA 30 | programmes, if 7-8 of each specialization and year of study participates, we have roughly 100 members. 31 | 32 | 33 | --Resources 34 | On one hand learning process is empowered with tech companies, which give internship and tutorial projects for student teams, 35 | and this is agreed, but not wholly organised by university community. And they are only available for KMA FI students, 36 | due to their knowledge basis. Library and database are available. Resources for holding meetings limit to general open spaces 37 | (two in university, could be busy) and study rooms, which are in teachers` responsibility. Friendly professor lets community 38 | to have tech talks or do workshop in computer equipped room. 39 | No hackathons were held, seminars are split with IT companies and other communities in university. 40 | Online system of grading also gives access to some materials, but is limited. 41 | 42 | 43 | --Accessibility 44 | 45 | 46 | Every FI student is eligible to reach those resources, but other studs are not entering, lacking technical level 47 | (there`s a layer of events and support for starters and non-math people missing). 48 | Meeting are mostly held at evenings, they are open but place is limited to uni rooms. 49 | No special requests are considered as audience is very homogenous - just middle and senior CC students. 50 | 51 | 52 | --Interests 53 | Right now it is not only made up only of computer science students, but also meetings are covering 54 | only very narrow technical topics.My research shows that people are not taking initiative but would participate 55 | in themed workshops and quests or hackathons eagerly. 56 | 57 | 58 | --Goals 59 | Being students, these members are heading toward degree and are aimed at most practical involvement. 60 | They get jobs at third year mostly, and would spare some time to activities which only bring some new experience - 61 | like sharing or do some teambuilding, maybe some practical soft skills for employment also, but mostly brainy info. 62 | Literally it is community of nerds, which could change to geeks, if we start some area to actually communicate. 63 | I personally want this group to become more open to students of other major (like my own, Sociology) by bridging them. 64 | 65 | 66 | --Location 67 | Offline meetings are initiated and supported with teachers, consequently held freely in equipped classrooms 68 | (we have an option to use projector or whiteboard, seating is the same at all locations and not designed to serve comfort), 69 | rarely in library - internet there is poor. Online communication is NOT organized (we should start with fb page, 70 | but apparently not everyone is using it, so we think of having slack instead). 71 | University place is located near subway and there are shops and restaurants. 72 | Transport is not a problem up until midnight. We can host 20 - 80 people comfortably, 73 | for anything bigger it is better to ask coworking or tech company to host us (or bigger uni, they can fit 150 people OK). 74 | 75 | 76 | --Communication 77 | Word of mouth, board announcements, teachers are sharing at office hours (that`s what gonna be fixed at first). 78 | We need a living channel, used by most people, able to transmit info both ways - 79 | reminders and propositions to memebers + feedback from them. 80 | 81 | 82 | --Culture 83 | University policy is mostly concerning ukrainian and english language, intellectual property, 84 | no-abuse and no-bribe rules. No special code of conduct is needed. 85 | People are not entering if they are not enrolled FI students, so there are no quarrels now, 86 | but if we change openness to invite everyone keen and interested, not only faculty members, 87 | we have to design rules and even levels of involvement. I always follow no-asshole rule, and if we face any disagreement 88 | it should be decided quite, between opponents, me as organizer or Andrew Hlybovets( PhD and trusted by everyone person) 89 | acting as mediators. 90 | 91 | 92 | 93 | 94 | -------------------------------------------------------------------------------- /communities/manitoba-hackers/community-assessment.md: -------------------------------------------------------------------------------- 1 | ##Manitoba Hackers 2 | 3 | ##Definition 4 | * University students interested in tech and coding at the University of Manitoba (population: 28 000 students) . It is our hope that the community grows beyond just the University of Manitoba, as there are neighbouring universities at University of Winnipeg (population: 10 000 ) and Brandon University (population: 3000) and several high schools in Winnipeg that teach programming. 5 | 6 | ##Size 7 | * Currently there is a Developers club at the University of Manitoba with a Facebook membership of about 80 members. However, there are only about 25-30 members who actively attend meetings. 8 | * The potential for growth is very high since there are **>700 computer science** students enrolled in the department of Computer Science. This does not include students who are in Computer Engineering and other engineering disciplines. Ideally, we would like to have at least a quarter of the students enrolled in computer science to be involved with Manitoba Hackers, i.e. ~180. 9 | 10 | * The limitation for growth depends on the number of interesting workshops/events that can be created. It also depends on how many students would like to spread awareness about the group. 11 | 12 | ##Resources 13 | * There is currently a developers club that meets on a weekly basis to allow members to learn about technology and have monthly hack nights 14 | * Since Winnipeg is a fairly isolated city, there are few hackathons that are within a driving distance. The closest hackathon to Winnipeg is MinneHacks, which is a 7.5 hour drive. Even further is HackISU (9 hour drive) and Hack K-State (12 hour drive). However, the start-up tech community is quickly growing in an area known as the Exchange District, a small hub for new tech start-ups to set up their operations. It is here where many computer science students find internship positions. 15 | * SkullSpace is a hackerspace located 30 minutes from the university that provides 24 hour access to resources such as a hardware lab, 3-D printer and space for soldering. Weekly meetings attract developers from the surrounding community and provide occasional workshops as well. 16 | 17 | 18 | ##Accessibility 19 | * The Developers Club meetings are held in the Engineering building classrooms, but do not currently have a set structure and attrition is very high amongst the membership. There lacks a consistent meeting location and room locations frequently change at the last minute. This makes it difficult at times for members to find meetings. 20 | * Meetings are held once a week on Thursdays with attendance about 20-30 people. 21 | * The school classrooms are quite accessible for those with disabilities. 22 | 23 | 24 | 25 | ##Interests 26 | * The community is made up of only computer science students, but it is our hope that students from outside the department come to learn more about coding. The engineering department remains a large population that have yet to integrate into the community. 27 | * There lacks structure in the current group, a re-evaulation will be conducted and a new community may be required to be created to change the current structure of meetings. 28 | 29 | ## Goals 30 | * Students have expressed their concern that there are few opportunities for them to engage in the developer community outside of class. 31 | * Many students want to join a group to build side projects and improve their coding skills outside of class. The material taught in class rarely reflects what current employers desire. It is our hope that Manitoba Hackers can provide students with an ability to bridge that gap in knowledge. 32 | 33 | * Outide of actually building projects, Manitoba Hackers can also be a place where students can find resources to find and prepare for tech jobs. Certain meetings can be dedicated to technical interview prep and introduce online resources such as LeetCode and Interview Cake. 34 | * The passion for developing remains low and we are hoping to get students to participate in more activities outside of class such as hackathons. We will be hosting our first ever hackathon called HackCentral between February 17th-19th, 2017 and hope to attract 450 students (college and high school) from across the province. 35 | * We will also be inviting members of SkullSpace to provide workshops such as Intro to Git, or Intro to Arduino programming. 36 | 37 | ##Location 38 | * The community gathers in school classrooms once a weekly 39 | * Parking is free after school hours and there is a free bus pass for all students. 40 | * It is difficult for certain students to remain on campus after class as most students live off-campus and most live with their families. 41 | * The cost to book rooms at the university is free of charge and there are large projectors in most rooms. 42 | * Each room fits about 50 people maximum 43 | * Water is close by, but the lack of funding makes providing snacks quite challenging. 44 | 45 | ##Communitcation 46 | * Online informal chats for the community happen at the DevClub slack channel as well as the Manitoba Hackers facebook group. 83 members are in the DevClub slack and 49 members are in the facebook group. 47 | * Having a github could also make storing projects a lot easier and for others to collaborate. 48 | 49 | ## Culture 50 | * There isn't a strong leadership team right now in the community and it is a challenge to find other individuals who will dedicate their time to grow the community. Building a strong team is the next step we plan to take in building the community. 51 | * Disagreements would be mediated by at least 2 people who are impartial to the situation. 52 | * A Code of Conduct will be drafted for the Manitoba Hackers to ensure that all members can participate free of harrassment. 53 | * To handle disagreements, I hope to have private conversations with all parties involved before making any judgements on taking any necessary action. 54 | -------------------------------------------------------------------------------- /communities/epfl-hackers/community-assessment.md: -------------------------------------------------------------------------------- 1 | ### Definition 2 | - How would you define your community? Try to be open minded, but here are some examples of ways you could define your community: 3 | - Students interested in working on cool tech projects outside of academia at EPFL. 4 | 5 | ### Size 6 | - How many people are currently in your community? 7 | - Hard to tell as there is no official club or society, but I would estimate we are around 5 people. 8 | - How many would you _like_ to be in your community? 9 | - Hard to say, but I would estimate that there are around 150 students (based on the number of EPFL students who applied to participate in LauzHack 2016) who would be interested in being part of such a community. That would be pretty great! 10 | - Historically, has the group always been about the same size? If not, what brought on that change? 11 | - Can't really tell as there has been no metric. Many students are working on cool tech projects, but there hasn't really been any gathering to form a group. 12 | 13 | ### Resources 14 | - What is currently available to people in your community to learn about tech? Are there meetups, seminars, online tools, office hours, hackathons? 15 | - Outside of lectures, not alot. 16 | - I organzied the first hackathon at EPFL last year - LauzHack 17 | - There are colloquiums organized by the CS department at EPFL where guest lecturers present their research followed by a Q&A, although these are not very frequent and have fairly low attendance. 18 | - Around "recruiting season" several companies come to EPFL and have some talks and workshops. 19 | 20 | ### Accessibility 21 | - How accessible are the current resources in your community? 22 | - Quite accessible - pretty much anyone can join in. 23 | - Are meetings held during hours where people may be working? 24 | - There are no meetings held at the moment, although its something we're looking to start. If we do, it will be in the evenings when people aren't working/in class. 25 | 26 | ### Interests 27 | - Is your community made up only of computer science students? Are you OK with that? 28 | - It contains students who study Computer Science or Communication Systems, but we're totally open to students from all areas in EPFL. 29 | - Is your community open to other topics, or are their interests very specific? 30 | - It is quite open to suggestion and will accomodate any topic as long as it is tech related, and there is interest in it. 31 | 32 | ### Goals 33 | - Why do people get involved in your community? 34 | - Its an opportunity to work on cool project where they have the freedom to work on anything they are intersted in, rather than something they are forced to in their classwork. Its also a support structure as there are other people to guide you if you are stuck or to give you advice - this way you aren't doing this on your own. 35 | - Are they students hoping to get a degree? 36 | - Yes 37 | - Are they trying to ramp-up to get a job? 38 | - Yes, but not all of them 39 | - Are they passionate about developing, regardless of their major? 40 | - Yes 41 | - What activities and goals can you set for your community based on their existing goals? 42 | - Goals 43 | - Learn something new 44 | - Work on a 'side-project' on your own/with friends 45 | - Activities 46 | - Participate in hackathons 47 | - Have occasional meetups to discuss anything (questions, challenges, doubts about a project, a class, an interview) 48 | - Have regular workshops to (usually) learn/practice and (occasionally) teach something. 49 | 50 | ### Location 51 | - Where does your community currently gather? Is it an online-only group so far, or is there a place where people can meet? 52 | - So far we just talk online - we aren't big enough to have "gatherings". But if/when we meet there are lots of public spaces and easily accessible classrooms at EPFL's campus. 53 | - Is there parking, and if so, is it free? 54 | - Yes 55 | - Is there public transportation available to and from meet-ups? 56 | - Yes 57 | - Is the location accessible to those both on and off campus? 58 | - Yes 59 | - How much does it cost to use the space? 60 | - Free 61 | - How flexible is the space for different types of presentations and meetings? 62 | - Can accomodate everything 63 | - How many people can it fit? 64 | - On a regular basis upto 50 people - in more exceptional cases upto 100. 65 | - Is there comfortable seating for all shapes and sizes? 66 | - Yes 67 | - Is there water or snacks available nearby? 68 | - Yes 69 | 70 | ### Communication 71 | - How does your community get in touch with one another? 72 | - So far just a facebook chat group. But when the group grows, we'll definitely need a better way. 73 | - There is a facebook group for the computer science department at EPFL, but it is quite neglected as it is only used to anounce when exam results are out, or to occasionally advertise some event. 74 | - Is there an email group, a GitHub organization, a Twitter account, a Facebook group, a chat room or channel? 75 | - Nope. 76 | - Could your organization benefit from one or more of those, or another way of communicating? 77 | - Yes, certainly! Slack would be ideal as it can host general chatter (like the facebook group HH:EU), and also more precise channels e.g. "Going to MLH prime", "Node.js enthusiasts", etc. 78 | 79 | ### Culture 80 | - How welcoming is your community to new people and new ideas? 81 | - We are pretty welcoming to new people and new ideas. 82 | - What happens if there is a disagreement? 83 | - As we are a rather small community, we just discuss it amongst ourselves and come to some sort of resolution. Once more formal we will have some form of community admistration which will handle this. 84 | - Are there any policies or procedures in place, and are they documented? 85 | - At the moment no, but as we grow we'd have something similar to the MLH code of conduct. 86 | - How will you personally handle it? 87 | - If I have to handle some sort of disagreement I'd listen to both sides to understand the motives involved, and from there figure out the best way forward. If need be, also get some advice from other community mods/admin -------------------------------------------------------------------------------- /communities/kcl-tech-society/kcl-tech-society: -------------------------------------------------------------------------------- 1 | ## Assessing Your Community's Needs 2 | 3 | Fully understanding the needs of your community is a complex concept that will likely take lots of time, conversation, and observation. Depending on your situation, you may already have a great idea for what your community needs. You may not, and that's OK. We will go over these questions and topics broadly during week 1, and discuss responses in more detail in week 2. Here are some things to keep in mind when assessing your community and hoping to grow it. 4 | 5 | Please write down your 6 | - Answers to these questions for current community 7 | - Answers to these questions for **an ideal version** of your current community 8 | - Ideas on how to improve in each category 9 | 10 | After you've completed these questions, define your community in several short paragraphs for discussion in week 2. 11 | 12 | ### Definition 13 | - How would you define your community? Try to be open minded, but here are some examples of ways you could define your community: 14 | - Students of King's College London part of the tech society/community 15 | 16 | 17 | ### Size 18 | - How many people are currently in your community? 19 | - 30 core, about 100 that come and go. 20 | 21 | - How many would you _like_ to be in your community? 22 | - Giving the fact that there are around 2500 students in STEM degrees(UG+PGT), only 5% are members of the society. I would like to improve our numbers to around 300 members(12%), 23 | and balancing the CS/Non-CS student ratio to 70-30. 24 | 25 | - Historically, has the group always been about the same size? If not, what brought on that change? 26 | - Yes, by introducing and supporting underepresented people to study tech. 27 | 28 | ### Resources 29 | - What is currently available to people in your community to learn about tech? 30 | - Online materials, hackahtons, workshops, sharing information. Unfortunately I do not have any statistics I can share about the numbers of attendees or recurring people. 31 | 32 | - Are there meetups, seminars, online tools, office hours, hackathons? 33 | - Yes. 34 | 35 | ### Accessibility 36 | - How accessible are the current resources in your community? 37 | - Pretty accessible. 38 | 39 | - Are meetings held during hours where people may be working? 40 | - No, the few that exist are outside office hours. 41 | 42 | - Is there childcare available? 43 | - Most likely the university provides this. 44 | - Is there accessibility for people with disabilities? 45 | - Yes. 46 | 47 | ### Interests 48 | - Is your community made up only of computer science students? Are you OK with that? 49 | - The majority are from computer science degree, few from other STEM degrees, but would be amazing if other people from different areas would join us. 50 | 51 | - Is your community open to other topics, or are their interests very specific? 52 | - The main interest is tech, but the topics are as many as are the persons in the community. 53 | 54 | ### Goals 55 | - Why do people get involved in your community? 56 | - Some get involved because of the way the community supports it's memebers, other out of curiosity or love for the topic. 57 | 58 | - Are they students hoping to get a degree? 59 | - Yes. 60 | 61 | - Are they trying to ramp-up to get a job? 62 | - I don't believe so. 63 | 64 | - Are they passionate about developing, regardless of their major? 65 | - Yes. 66 | 67 | - What activities and goals can you set for your community based on their existing goals? 68 | - Organising/attending hackathons, being known as tech people, developing usable products. 69 | 70 | ### Location 71 | - Where does your community currently gather? 72 | - There is never a time when all memebers are present, but the majority gather at HackKings. 73 | 74 | - Is it an online-only group so far, or is there a place where people can meet? 75 | - Yes, diverse slack channels, facebook groups. 76 | 77 | - Is there parking, and if so, is it free? 78 | - There is, but it's usually busy. Although I do not think people need it. 79 | 80 | - Is there public transportation available to and from meet-ups? 81 | - Yes. 82 | 83 | - Is the location accessible to those both on and off campus? 84 | - Yes. 85 | 86 | - How much does it cost to use the space? 87 | - It doesn't, but the space needs to be booked in advance, otherwise there might be possible not to get one. 88 | 89 | - How flexible is the space for different types of presentations and meetings? 90 | - Flexible. 91 | 92 | - How many people can it fit? 93 | - Maximum is around 200 in one room, but there can be multiple rooms available. 94 | 95 | - Is there comfortable seating for all shapes and sizes? 96 | - Yes. 97 | 98 | - Is there water or snacks available nearby? 99 | - Yes. 100 | 101 | ### Communication 102 | - How does your community get in touch with one another? 103 | - Usually in slack( mostly core members and some dedicated members), facebook group, website of Tech Society, email etc. 104 | 105 | - Is there an email group, a GitHub organization, a Twitter account, a Facebook group, a chat room or channel? 106 | - Yes, all of them. 107 | 108 | - Could your organization benefit from one or more of those, or another way of communicating? 109 | - The tech society provides all of them, but the one who cost need to be provided by our own money. 110 | 111 | ### Culture 112 | - How welcoming is your community to new people and new ideas? 113 | - Very, we are open to anyone. 114 | 115 | - What happens if there is a disagreement? 116 | - We try to resolve it peacefully and we try to avoid negative or toxic people. 117 | 118 | - Are there any policies or procedures in place, and are they documented? 119 | - There are some in regards to room bookings, membership and the likes. 120 | 121 | - How will you personally handle it? 122 | -One thing I would do is have surgery hours with more experienced developers to help people start out/ improve in a speicifc area and have meetings/workshops on non-mainstream technologies. 123 | -------------------------------------------------------------------------------- /communities/kcl-tech-society/community-assessment.md: -------------------------------------------------------------------------------- 1 | ## Assessing Your Community's Needs 2 | 3 | Fully understanding the needs of your community is a complex concept that will likely take lots of time, conversation, and observation. Depending on your situation, you may already have a great idea for what your community needs. You may not, and that's OK. We will go over these questions and topics broadly during week 1, and discuss responses in more detail in week 2. Here are some things to keep in mind when assessing your community and hoping to grow it. 4 | 5 | Please write down your 6 | - Answers to these questions for current community 7 | - Answers to these questions for **an ideal version** of your current community 8 | - Ideas on how to improve in each category 9 | 10 | After you've completed these questions, define your community in several short paragraphs for discussion in week 2. 11 | 12 | ### Definition 13 | - How would you define your community? Try to be open minded, but here are some examples of ways you could define your community: 14 | - Students of King's College London part of the tech society/community 15 | 16 | 17 | ### Size 18 | - How many people are currently in your community? 19 | - 30 core, about 100 that come and go. 20 | 21 | - How many would you _like_ to be in your community? 22 | - Giving the fact that there are around 2500 students in STEM degrees(UG+PGT), only 5% are members of the society. I would like to improve our numbers to around 300 members(12%), 23 | and balancing the CS/Non-CS student ratio to 70-30. 24 | 25 | - Historically, has the group always been about the same size? If not, what brought on that change? 26 | - Yes, by introducing and supporting underepresented people to study tech. 27 | 28 | ### Resources 29 | - What is currently available to people in your community to learn about tech? 30 | - Online materials, hackahtons, workshops, sharing information. Unfortunately I do not have any statistics I can share about the numbers of attendees or recurring people. 31 | 32 | - Are there meetups, seminars, online tools, office hours, hackathons? 33 | - Yes. 34 | 35 | ### Accessibility 36 | - How accessible are the current resources in your community? 37 | - Pretty accessible. 38 | 39 | - Are meetings held during hours where people may be working? 40 | - No, the few that exist are outside office hours. 41 | 42 | - Is there childcare available? 43 | - Most likely the university provides this. 44 | - Is there accessibility for people with disabilities? 45 | - Yes. 46 | 47 | ### Interests 48 | - Is your community made up only of computer science students? Are you OK with that? 49 | - The majority are from computer science degree, few from other STEM degrees, but would be amazing if other people from different areas would join us. 50 | 51 | - Is your community open to other topics, or are their interests very specific? 52 | - The main interest is tech, but the topics are as many as are the persons in the community. 53 | 54 | ### Goals 55 | - Why do people get involved in your community? 56 | - Some get involved because of the way the community supports it's memebers, other out of curiosity or love for the topic. 57 | 58 | - Are they students hoping to get a degree? 59 | - Yes. 60 | 61 | - Are they trying to ramp-up to get a job? 62 | - I don't believe so. 63 | 64 | - Are they passionate about developing, regardless of their major? 65 | - Yes. 66 | 67 | - What activities and goals can you set for your community based on their existing goals? 68 | - Organising/attending hackathons, being known as tech people, developing usable products. 69 | 70 | ### Location 71 | - Where does your community currently gather? 72 | - There is never a time when all memebers are present, but the majority gather at HackKings. 73 | 74 | - Is it an online-only group so far, or is there a place where people can meet? 75 | - Yes, diverse slack channels, facebook groups. 76 | 77 | - Is there parking, and if so, is it free? 78 | - There is, but it's usually busy. Although I do not think people need it. 79 | 80 | - Is there public transportation available to and from meet-ups? 81 | - Yes. 82 | 83 | - Is the location accessible to those both on and off campus? 84 | - Yes. 85 | 86 | - How much does it cost to use the space? 87 | - It doesn't, but the space needs to be booked in advance, otherwise there might be possible not to get one. 88 | 89 | - How flexible is the space for different types of presentations and meetings? 90 | - Flexible. 91 | 92 | - How many people can it fit? 93 | - Maximum is around 200 in one room, but there can be multiple rooms available. 94 | 95 | - Is there comfortable seating for all shapes and sizes? 96 | - Yes. 97 | 98 | - Is there water or snacks available nearby? 99 | - Yes. 100 | 101 | ### Communication 102 | - How does your community get in touch with one another? 103 | - Usually in slack( mostly core members and some dedicated members), facebook group, website of Tech Society, email etc. 104 | 105 | - Is there an email group, a GitHub organization, a Twitter account, a Facebook group, a chat room or channel? 106 | - Yes, all of them. 107 | 108 | - Could your organization benefit from one or more of those, or another way of communicating? 109 | - The tech society provides all of them, but the one who cost need to be provided by our own money. 110 | 111 | ### Culture 112 | - How welcoming is your community to new people and new ideas? 113 | - Very, we are open to anyone. 114 | 115 | - What happens if there is a disagreement? 116 | - We try to resolve it peacefully and we try to avoid negative or toxic people. 117 | 118 | - Are there any policies or procedures in place, and are they documented? 119 | - There are some in regards to room bookings, membership and the likes. 120 | 121 | - How will you personally handle it? 122 | -One thing I would do is have surgery hours with more experienced developers to help people start out/ improve in a speicifc area and have meetings/workshops on non-mainstream technologies. 123 | -------------------------------------------------------------------------------- /communities/qut-codenetwork/community-assessment.md: -------------------------------------------------------------------------------- 1 | ## Assessing Your Community's Needs 2 | 3 | Fully understanding the needs of your community is a complex concept that will likely take lots of time, conversation, and observation. Depending on your situation, you may already have a great idea for what your community needs. You may not, and that's OK. We will go over these questions and topics broadly during week 1, and discuss responses in more detail in week 2. Here are some things to keep in mind when assessing your community and hoping to grow it. 4 | 5 | Please write down your 6 | - Answers to these questions for current community 7 | - Answers to these questions for **an ideal version** of your current community 8 | - Ideas on how to improve in each category 9 | 10 | After you've completed these questions, define your community in several short paragraphs for discussion in week 2. 11 | 12 | ### Definition 13 | - How would you define your community? Try to be open minded, but here are some examples of ways you could define your community: 14 | - Generally speaking; students, staff and alumni of Queensland University of Technology and industry professionals in Brisbane, Australia. 15 | - CodeNetwork was founded from QUT and now has a national, and somewhat international, presence. 16 | 17 | ### Size 18 | - How many people are currently in your community? 19 | - Currently we have 2,225 members. 20 | - How many would you _like_ to be in your community? 21 | - What's the population of the MultiVerse? 22 | - Historically, has the group always been about the same size? If not, what brought on that change? 23 | - We have grown from 6 founding members in almost two years. 24 | - Events such as hackathons and more specifiably the media attention they bring have catapulted membership numbers. 25 | 26 | ### Resources 27 | - What is currently available to people in your community to learn about tech? 28 | - We hold a weekly meetups that are open to anyone. 29 | These are generally focused on bringing developers from industry in to speak, demo, 30 | and otherwise just interact with students. Strictly developers, no HR. 31 | - Hackathons are held twice a year, running over a weekend. 32 | We have had huge success running these and have found them to be extremely beneficial to the community. 33 | Most recently one team made the Australian Census Great Again, handling 4x the load with a $1000 budget 34 | which they spent only $30 of. 35 | - We use the [CodeNetwork](facebook.com/groups/WeCodeAlot/) Facebook Page for general communication and community interaction. 36 | 37 | ### Accessibility 38 | - How accessible are the current resources in your community? 39 | - There is no restriction on attending out events or joining the FaceBook page. Except for Recruiters to an extent. 40 | - Are meetings held during hours where people may be working? 41 | - Typically we try to hold all events outside of regular business hours. 42 | - Is there childcare available? 43 | - No. 44 | - Is there accessibility for people with disabilities? 45 | - Yes. 46 | 47 | ### Interests 48 | - Is your community made up only of computer science students? Are you OK with that? 49 | - Primarily yes. There are quite a few electrical and mechanics engineers scattered around too. 50 | - Is your community open to other topics, or are their interests very specific? 51 | - I'd say the primary intrest of our community of web application development 52 | but everyone is very open to pretty much anything. 53 | 54 | ### Goals 55 | - Why do people get involved in your community? 56 | - To learn and share common interests. 57 | - Are they students hoping to get a degree? 58 | - The majority of our community are students. 59 | - Are they trying to ramp-up to get a job? 60 | - Some are, some aren't. 61 | - Are they passionate about developing, regardless of their major? 62 | - All active members are. 63 | - What activities and goals can you set for your community based on their existing goals? 64 | - Run more workshops based on community requested content. 65 | - Develop a more interactive online presence to facilitate projects, job listings etc. 66 | - World domination. 67 | 68 | ### Location 69 | - Where does your community currently gather? 70 | - Generally at the QUT campus. Occasionally events are held off campus. 71 | - Is it an online-only group so far, or is there a place where people can meet? 72 | - Both. Weekly meetups occur. 73 | - Is there parking, and if so, is it free? 74 | - Yes, no. 75 | - Is there public transportation available to and from meet-ups? 76 | - Yes 77 | - Is the location accessible to those both on and off campus? 78 | - Yes. Even on campus events are open to non-students. 79 | - How much does it cost to use the space? 80 | - We have only used event spaces that were free thus far. 81 | - How flexible is the space for different types of presentations and meetings? 82 | - On campus can be difficult for more complex events. 83 | In that event we generally look towards local co-working spaces for event space. 84 | - How many people can it fit? 85 | - Typical weekly meetup space can accommodate ~100. 86 | - Is there comfortable seating for all shapes and sizes? 87 | - Yes. 88 | - Is there water or snacks available nearby? 89 | - Yes. 90 | 91 | ### Communication 92 | - How does your community get in touch with one another? 93 | - [CodeNetwork](facebook.com/groups/WeCodeAlot/) Facebook Page. 94 | - Is there an email group, a GitHub organization, a Twitter account, a Facebook group, a chat room or channel? 95 | - All of the above. Slack is relatively inactive though. Facebook page is very active. 96 | - Could your organization benefit from one or more of those, or another way of communicating? 97 | - I think it could benefit from a more active Slack. We have tried to drive interest in this with little success. 98 | 99 | ### Culture 100 | - How welcoming is your community to new people and new ideas? 101 | - Very. Culture is very important to us. 102 | - What happens if there is a disagreement? 103 | - Thus far we have had very few conflicts within the community and these have been dealt with very quickly. 104 | We have banned members from Facebook and asked a few not to addend events due to this. 105 | - Are there any policies or procedures in place, and are they documented? 106 | - We enforce a single rule; don't be a dick. 107 | - How will you personally handle it? 108 | - Timeout in the corner for all those involved. 109 | -------------------------------------------------------------------------------- /communities/epfl-hackers/community-impact-proposal.md: -------------------------------------------------------------------------------- 1 | ## Summary of the Community's Needs 2 | 3 | - **Community demographics**: Currently a very small community of about 5 people, we aim to grow to 150 people during the next academic year. Our community will include anyone with a passion for tech and an interest in working on passion projects outside of academia, regardless of their educational background. Currently the community doesn't have many resources available, except for LauzHack which was organized with the aim of kick starting the community. 4 | 5 | 6 | - **Communication**: At the moment communications are direct messages between members by email/IM, but as the community grows a Facebook group and Slack channel will be introduced as required. 7 | 8 | - **Culture**: At the moment, we don't have any meetups or regular group activity so it has been hard to develop a community culture. People pretty much work on their own individual projects and interactions are limited to asking for help if and when needed. 9 | 10 | ## Your Proposal 11 | 12 | Launching a new student association at EPFL for the community, and organizing regular meet-ups for the members of the association. 13 | 14 | - **Timing**: For us the key timing will be the start of the next semester. We would ideally like to setup an official university association by the end of the summer, thereby enabling us to pitch the associations at the associations fair at the start of the academic year. This will be key to letting people (especially first years) know that we exist and how to get in touch with us. Soon after this we would start weekly/monthly meetups for the community to bond and get comfortable with other members. The idea behind these meetups is to give community members the chance to learn something cool and new, and also be able to discuss any issues they are dealing with. Such meetups will also be ideal for promoting hackathons and encouraging traveling to hackathons all over Europe. 15 | 16 | - **Community demographics**: We definitely want to increase the size of the community many fold. To do so the first step is to become an official university association. Following this, our main outreach would be through word-of-mouth as people who enjoy being a part of the community will hopefully tell their friends about it. While this is a great form of 'organic growth', the community might lack diversity as theres a high probability that most people who join us will only be from a computer science background. In order to attract people with more diverse backgrounds we will reach out to other departments in the university (not just Computer Science). 17 | 18 | - **Goals**: 19 | - My goals were for community members to learn something new, and to work on 'side-projects' on their own/with friends. 20 | - The proposal helps meet these goals in the following ways: 21 | - Forming the association enables us to formally create the support structure for community members to meet their goals. 22 | - Community members will (hopefully) learn something new at the meetups 23 | - We will promote hackathons through the association, as hackathons are a great place to both get started with a side-project and to learn something new over a weekend. 24 | - By 'socializing' with people with the same passion for tech, community members are more likely to work with each other. 25 | - With a diverse range of experiences within the community (hopefully), anyone who needs help should be able to find someone who can guide them. 26 | 27 | - **Communication**: 28 | - Meetups: Main form of interaction on a regular basis 29 | - Facebook group: Easy way to reach out to many people, available for any posts that community members find useful/interesting/relevant. A bit like a localized version of HH:EU. Can also be used to make announcements. 30 | - Slack: For more focused communication. Will probably not be in active use for announcements, etc but will be useful for creating local communities. For example need help with Python, ping the python channel on slack - all people interested in Python will be there. 31 | 32 | 33 | ## Your Proposal's Impact 34 | 35 | - Target audience 36 | - Who are you expecting to impact based on your proposal? 37 | - I'm expecting to impact the students at EPFL who are interested in tech but don't know how to start to dabble with it. 38 | - Community needs 39 | - What specific issue are you addressing with your proposal? 40 | - With this proposal, I aim to give students the support structure they need to pursue their passion projects. 41 | - Resources 42 | - What resources do you need to accomplish your proposal? 43 | - A lot of patience to deal with the red tape in setting up a new association 44 | - Venue for meetups 45 | - Perhaps some swag to give an incentive to newbies to come for the first time. 46 | - How will you obtain those resources? 47 | - We can get the venue from the university 48 | - For swag we'll try to get some sponsors. 49 | - Media 50 | - During meetups: 51 | - Presentations/demos 52 | - Live coding 53 | - Guest talks by interesting people (if possible) 54 | 55 | - Content knowledge 56 | - How knowledgeable are you on about the topic your community impact project focuses on? 57 | - I can't say that I am the most knowledgeable when it comes to talks. I can cover a few areas, but can't cover everything on my own. 58 | - I am very knowledgeable on how to convince people to go to hackathons though :D 59 | - What resources do you have at your disposal to enhance that knowledge? 60 | - People! Different people have different skill sets. So the person who has alot of experience in a topic will 'lead' the meetup which is about the corresponding topic. 61 | - Timeline 62 | - Mid September (week 1 of semester): Setup student association 63 | - Mid October (~week 4 of semester): have first meet up 64 | - November 10-12 (~week 8 of semester): LauzHack 2.0 65 | 66 | ## Planning for the Future 67 | 68 | - When will you review the impact of your proposal? 69 | - Probably in December at the end of the semester. We'll have enough information to tell if the community has grown. 70 | - How will you measure success? 71 | - Number of regular attendees at meetups 72 | - Number of members attending hackathons 73 | - Volume of interactions online 74 | - Member happiness - ideally by talking to community members try to get an idea if they are benefiting from the community. Although surveys would be easier. 75 | - How frequently will you iterate on your community plans? 76 | - Probably once a semester. Its too hard to tell if something worked or not in the short term. 77 | -------------------------------------------------------------------------------- /communities/hacksoc-notts/community-impact-proposal.md: -------------------------------------------------------------------------------- 1 | Now that you've [thought about your community's needs](community-assessment.md), it's time to take some action! Use this template to help you fill out your proposal. We invite you to change the contents of this template around and use the embedded tips and evaluation criteria to help you make a :sparkles: impact on your community. 2 | 3 | ## Summary of the Community's Needs 4 | 5 | The HackSoc Community is a student community from a range of disciplines, it is on the larger size in terms of how many members it has (200+) but the number of these that engage in the community is considerably less, below 50. 6 | 7 | Currently HackSoc have access to rooms that can be used for events and plenty of resources to run teaching sessions. There are good links with sponsors who continue to support the society and the society has a slack channel that is used for communications. 8 | 9 | Communications are something that are lacking, there is a weekly email but this can be sporadic in its sending and compiling, the members that run the society have some difficulty coming together in one place and of late there hasn't been good communication to members for HackSoc events, there is no strategy it is as and when people are available which can seem inconsistent. This could also make the society team seem inaccessible to members as they often seem too busy too be accessible. 10 | 11 | The preferred method of communication is slack - there is a Facebook group and Twitter but the majority of communications are done through email and discussion in slack. 12 | 13 | The culture within HackSoc is about making and doing. It promotes learning coding skills and those that engage are people who are enthusiastic about learning something new and making a thing, they are often beginners and a mix of new CS students and students from other disciplines. 14 | 15 | ## Your Proposal 16 | 17 | In this section, articulate the project you want to accomplish during the Campus Experts program; provide a brief summary of what you are planning to accomplish with your project. 18 | 19 | The HackSoc community needs to evaluate the communication with it's members now that the society has continued to grow, preferred methods may not be the most suitable or effective for the current audience so it would be good to evaluate engagement using social media analysis tools. 20 | 21 | This would require gathering this data and presenting it to the HackSoc executive committee, which would fall within my role on the committee of Outreach and Inclusivity Secretary. 22 | 23 | It would be appropriate to hold this meeting at the end of the Autumn semester to evaluate the messaging in this period and learn from what did and didn't work, in order to apply this to a strategy for after the holiday period. 24 | 25 | The plan's aim should not be to increase the community (i.e. promote what we do to those who aren't members) but to increase the engagement within the society. There would be a goal to ensure our members see value in being part of the society and feel valued by the community. 26 | 27 | Addressing our overall messaging would address the following goals: 28 | 29 | - Ensure HackSoc are using the most effective way of contact our members 30 | - Provide HackSoc members with knowledge of how best to contact or contribute to the community 31 | - Increase engagement by reaching people through their most used method 32 | - Increase communications & awareness of HackSoc 33 | - Identify the best methods to keep in contact with the members of the community 34 | 35 | The communication of this plan will begin with in-person meetings amongst the committee and communications to our members via social media for their input into our future communications. 36 | 37 | The community will continue to communicate through the existing methods (Slack, Facebook, Twitter & Email) which will be assessed when this proposal is implemented. 38 | 39 | 40 | ## Your Proposal's Impact 41 | 42 | The target audience for this proposal is all HackSoc members, with a focus on the less active members of the society. 43 | 44 | It aims to address and understand the needs of newer members who may not be aware of how HackSoc operate or aren't sure how to engage with the community. 45 | 46 | Resources required to enact this proposal will be open source analytic software (often provided by social media tools and platforms). 47 | 48 | The proposal will be delivered in a presentation to the committee and a recorded round table discussion about how the society will address this in the next semester. 49 | 50 | Following this a set of guidelines for the engagement and messaging could be created within the HackSoc Organisation on GitHub and on any society shared drives for future committee members to be aware of and evaluate. 51 | 52 | As an individual I have previously working in music promotions and communications for events, I have good knowledge of social media platforms and tools, along with history in growing social media accounts (inspire WIT Twitter account - from 79 followers to 1000+). I am aware of good practices in messaging and feel that I would be able to effectively impact this proposal. 53 | 54 | To grow this knowledge I could access community blogs, discuss with other campus experts and test a variety of social media delivery tools available online. I could also take free online courses on communications and encourage my peers on the committee to do the same. 55 | 56 | 57 | Timeline: 58 | 59 | Nov-Dec (approx. 2 weeks) = Analyse current social media communications 60 | Dec (before 16th December) = Present findings to committee and hold round table discussion 61 | Dec-Jan (approx. 4 weeks) = Develop strategy & documents to support this, with community input 62 | Jan = hold meeting with committee to confirm strategy & put into place 63 | 64 | ## Planning for the Future 65 | 66 | The impact of this proposal could be evaluated throughout and at the end of the spring semester, through social media analysis and levels of engagement in future HackSoc activities from the society members. 67 | 68 | Success would be quantified by number of members engaging in activities, however there could also be qualitative data in terms of asking the community for feedback once the strategy is in place. 69 | 70 | This is a plan that could be iterated each semester, as this would give time enough to evaluate if the preferred methods of communication have changed (they may fluctuate month to month so a longer period would give more realistic engagement data) 71 | 72 | It could be written into the role of both Inclusivity and Outreach, as well as General Secretaries to consider this at the end of each semester. 73 | 74 | 75 | -------------------------------------------------------------------------------- /communities/UNAM-Engineering/community-assessment.md: -------------------------------------------------------------------------------- 1 | # UNAM Engineering 2 | [UNAM Engineering](https://github.com/unamfi) is a small Github organization started on 2016 with the objective to provide students a space 3 | where they were able to share the projects they have been developing on their classes and hackathons, tools and tips for other students. We 4 | promote students to go to meetups and various event, help them prepare for job/internship opportunities and provide office hours. 5 | 6 | ### Definition 7 | 8 | - How would you define your community? Try to be open minded, but here are some examples of ways you could define your community: 9 | - Students interested in developing projects in their free time. 10 | - Students already working on research and/or developing apps. 11 | - Students interested to attend hackathons and meetups. 12 | - Students interested in landing internship opportunities. 13 | - Students interested in meeting industry companies and people. 14 | 15 | 16 | ### Size 17 | - How many people are currently in your community? 18 | 19 | Currently there's 45 people on the GitHub organization and around 10 people have submitted repos. 20 | 21 | - How many would you _like_ to be in your community? 22 | 23 | Getting to 150 people in the organization and having a 20% - 25% members contributing. 24 | 25 | - Historically, has the group always been about the same size? If not, what brought on that change? 26 | 27 | The group grew a lot in the beginning and people used to share they're code. After four months the growth 28 | stopped because we didn't promote it outside of our core friends. Usually, the last couple months of the semester 29 | we get a lot of traffic from students looking for final projects done on previous years. 30 | 31 | ### Resources 32 | - What is currently available to people in your community to learn about tech? 33 | 34 | We have some guides and projects done in the organization which help students understand the topics they see 35 | in their classes as well as some small courses. 36 | 37 | - Are there meetups, seminars, online tools, office hours, hackathons? 38 | 39 | Currently, we don't promote meetups nor seminars nor hackathons but is something we look forward to do. We have online tools. 40 | We do office hours but not in an organized structure. Most of the time students come to the lab and ask for help. 41 | 42 | ### Accessibility 43 | - How accessible are the current resources in your community? 44 | 45 | All of the community resources are open sourced. 46 | 47 | - Are meetings held during hours where people may be working? 48 | 49 | We don't hold meetups so far. 50 | 51 | - Is there childcare available? 52 | 53 | We don't have childcare available. 54 | 55 | ### Interests 56 | - Is your community made up only of computer science students? Are you OK with that 57 | 58 | As a community we're open to anyone who wants to join though a bast mayority are computer engineers. 59 | 60 | - Is your community open to other topics, or are their interests very specific 61 | 62 | We're open to projects that are related to CS or CE so we might talk about other topics and how people 63 | solved them with code. 64 | 65 | ### Goals 66 | - Why do people get involved in your community 67 | 68 | Most of the people that join is to share their code with the organization or to ask for code exmaples about 69 | their classes. 70 | 71 | - Are they students hoping to get a degree 72 | 73 | Yes, most of them. We also have graduates as part of the community. 74 | 75 | - Are they trying to ramp-up to get a job 76 | 77 | Most are looking for internships for summer/winter. 78 | 79 | - Are they passionate about developing, regardless of their major 80 | 81 | Yes, we have also psychologist and law students that love to code. 82 | 83 | - What activities and goals can you set for your community based on their existing goals 84 | 85 | - Sharing Code. 86 | - Learning from other students. 87 | - Students meeting each other. 88 | - Building a public "Portfolio" of the projects that students are making in the univesity. 89 | 90 | 91 | ### Location 92 | - Where does your community currently gather? 93 | 94 | We talk via FB Messenger and Github. 95 | 96 | - Is it an online-only group so far, or is there a place where people can meet? 97 | 98 | It is online so far though we could meet at the lab I'm working in. 99 | 100 | - Is there parking, and if so, is it free? 101 | 102 | There's public parking close though it's highly saturated. 103 | 104 | - Is there public transportation available to and from meet-ups? 105 | 106 | Yes, we are connectd to the two main public transportation systems in Mexico. 107 | 108 | - Is the location accessible to those both on and off campus? 109 | 110 | It's accesible for both. 111 | 112 | - How much does it cost to use the space? 113 | 114 | For students the spaces are free you just need to ask for it which sometimes can be a long process. 115 | 116 | - How flexible is the space for different types of presentations and meetings? 117 | 118 | For meetups and presentations in general is preaty flexible. for hackathons is more complicated and, so far, 119 | we haven't been able to organize one on campus. 120 | 121 | - How many people can it fit? 122 | 123 | Depends on the space you ask for. It goes from 40-160 and in special occations you can get a 440 space. 124 | 125 | - Is there comfortable seating for all shapes and sizes? 126 | 127 | Yes 128 | 129 | - Is there water or snacks available nearby? 130 | 131 | Yes 132 | 133 | 134 | ### Communication 135 | - How does your community get in touch with one another? 136 | 137 | We use FB Messenger and in rare ocations GH issues. 138 | 139 | - Is there an email group, a GitHub organization, a Twitter account, a Facebook group, a chat room or channel? 140 | 141 | We have the Github organization as the main contact form. 142 | 143 | - Could your organization benefit from one or more of those, or another way of communicating? 144 | 145 | Yes we could. We could explore better ways to connect al members. 146 | 147 | ### Culture 148 | - How welcoming is your community to new people and new ideas? 149 | 150 | We're open to new people and ideas. 151 | 152 | - What happens if there is a disagreement? 153 | 154 | We usually don't have disagreements. In the worst case escenario we vote for the best solution and include memebers. 155 | 156 | - Are there any policies or procedures in place, and are they documented? 157 | 158 | We don't have many policies and they're on a Github Repo. 159 | 160 | - How will you personally handle it? 161 | 162 | We need to improve how the GH organization is structured to make it more transparent in policies and procedures. 163 | -------------------------------------------------------------------------------- /communities/students-new-to-hacker-culture/community-impact-proposal.md: -------------------------------------------------------------------------------- 1 | ## Summary of the Community's Needs 2 | 3 | 4 | 5 | - **Community demographics**: Beginning wih CompSoc, which is a rather small community of about 20 people, the ultimate aim is to be able to share the love for technology and encourage the growth of the hacker culture across the entire campus, regardless of educational backgrounds. At the moment, the focus is on encouraging members of CompSoc (the first years, in particular, as they make up the majority of the society and will be taking over leadership from the end of this academic year) to get involved in hackathons. Unfortunately, without the university's support, we lack the resources needed to support their endeavors, and because of Durham's location, getting to hackathons in other locations is difficult; the only thing we can do is to assure them that these events are worth it - which is probably most effectively done by hosting more tech events ourselves. 6 | 7 | 8 | - **Communication**: Most communication is bilateral between the Exec and the members, done through internal mail systems, and a Facebook page. However, we are trying to encourage more active communication, by introducing the use of Slack. 9 | 10 | 11 | - **Culture**: As much as we are trying to create an inclusive community, it has been difficult trying to engage our members. At the moment, it is very much a culture where people work on their own individual projects and speak to one another only when they need help, so we are trying to encourage more sociable meetups. 12 | 13 | 14 | 15 | 16 | ## Your Proposal 17 | 18 | Taking advantage of the launch of GGO16 at the start of November, we will use this as our month-long collaborative project to encourage exploratory programming -- the core of the hacker culture. 19 | 20 | 21 | 22 | 23 | 24 | 25 | - **Timing**: We will begin running weekly coding workshops for the student body in Week 5 (due to room booking issues), which will be marketed across the campus to students of all educational backgrounds, to encourage them to try programming. We will begin the idea-generation phase for GGO16 in our CompSoc Meetup at the end of Week 2, and will spend November building the project collaboratively. By Week 6, we will collect the students' ideas and feedback from the program so that these events can be improved upon, and will then hold Local Hack Day on Dec 3 to implement some of this feedback. At the same time, we can use this opportunity to demonstrate the benefits of the hacker culture to the University, in hopes that they will be more supportive of tech events in the future. 26 | 27 | 28 | - **Community demographics**: By bridging the gap between CompSoc and the entrepreneurial society, Entrepreneurs Durham, I hope to involve students from business backgrounds in technology, while exposing the technologists to the application of tech in business. Having over a thousand members, Entrepreneurs Durham offers an avenue for marketing and is willing to pool resources with CompSoc in exchange for technical guidance. 29 | 30 | 31 | - **Goals**: By running regular workshops for the community, we would be equipping them with the skills and confidence that they need to take on exploratory programming on their own. Once they have this confidence, they are more likely to build projects, and would not be put off from taking part in hackathons. 32 | 33 | 34 | - **Communication**: Having weekly meetups is likely to allow the students to ask us any questions that they may have from a week before. With social media outlets, like Facebook, students are also able to post their questions and have discussions with every member of the society. We are in the process of transitioning to Slack, but, unfortunately, because Slack is unfamiliar to most, we have been struggling to encourage our members to adopt the technology. 35 | 36 | 37 | 38 | 39 | ## Your Proposal's Impact 40 | 41 | - Target audience: My main focus to begin with would be on the technical community, and should be achievable within the scope of the proposal. It is possible to work on the larger community simultaneously, too, but it will not hold as much priority. However, any longer lasting impact, e.g. inspiring the students enough to want to carry the hacker culture on as a tradition, will take a longer amount of time, and more sustained effort. 42 | 43 | 44 | - Community needs 45 | : The proposal aims to give students the foundational skills and confidence needed for them to want to pick up exploratory programming, and actively seek out the hacker culture. 46 | 47 | 48 | - Resources: Although the venue for our events and the equipment required will be covered by the university, we would still require funding to pay for pizza, which would incentivize participation in our tech events. This money can only be acquired through sponsorship. 49 | 50 | - Media: We have already begun discussing and forming the curriculum for the weekly workshops, which would follow a specific "track", balancing CS fundamentals with rapid prototyping (for the non-technical students who may not necessarily see the importance in understanding CS fundamentals). By involving the Exec of CompSoc, as a team, we may be better able to answer any of the questions that the students may have about a specific topic. However, we are considering the feasibility of having lecture-style demonstrations that the students can follow, with multiple technical mentors who can help students struggling with the content. 51 | 52 | - Content knowledge 53 | : I am probably underqualified, but am trying my best to help students as much as I can. I am struggling with time management, though; between University commitments, and extracurricular activities, it is incredibly difficult to spend too much time preparing for these events. 54 | 55 | - Timeline 56 | : The end of Week 2 is the start of GGO2016, allowing us to add this to the agenda for our weekly CompSoc meetups for the next 4 weeks. Preparation for the coding workshops will begin in Week 3, and the coding workshops themselves will be held 57 | from Week 5 onwards (due to room booking issues). At the end of Week 5/start of Week 6 is Local Hack Day; after which, we will collect feedback for the past few tech events that we will then reflect upon and integrate into future events. 58 | 59 | ## Planning for the Future 60 | 61 | 62 | 63 | A hackathon is in the pipeline for January of 2017, and will be the first 24-hour MLH hackathon to be held at Durham University. Hopefully, by the end of January 2017, the hacker culture will flourish in Durham and our students will become more involved in tech events. It would truly be a success if they become inspired, and the hacker culture becomes a tradition at the university, especially amongst the technologists. However, due to time and resource constraints, these activities can only be carried out till the end of Epiphany Term. 64 | -------------------------------------------------------------------------------- /communities/citytechsoc/community-assesment.md: -------------------------------------------------------------------------------- 1 | ## Assessing Your Community's Needs 2 | 3 | ### Definition 4 | Currently: 5 | - A collective of primarily technical students at City, University of London who are passionate about technology and want to do things with for the sake of personal development. 6 | 7 | Ideally: 8 | - A larger collective of students at City, from a range of backgrounds who are passionate about technology and want to apply it to different ideas, with an emphasis on personal development. 9 | - Theres a very strong entrepreneurial community among students at the university, which is spearheaded by [CityVentures](http://www.city.ac.uk/cityventures), part of the enterprise division of the university. But after having gone to almost every event of theirs in my first year, I realised there was close to zero technical students taking part in this community. It would be great to see more technical students integrating into it and taking advantage. 10 | 11 | Improvements: 12 | - There has been interest from non technical students in learning to program. It would be nice to accommodate for them and create an environment where students exchange varying skill sets. 13 | - Getting more students that are familiar with hardware - such as Electrical Engineering students, involved in the tech community. 14 | 15 | ### Size 16 | Currently: 17 | - The society was formally started in September 2016, and we have just over 100 students who are signed up onto the society's Slack account. 18 | - However, about 30 - 40 have actively participated in the events that we have hosted thus far. 19 | 20 | Ideally: 21 | - It would be great if at the very least, all of the students who have previously expressed interested actively partook in the events that we hold, but preferably if most technical students at the university joined in the activities. 22 | - It would be even better if students of other backgrounds, such as maths, business, etc attended the events, so as to create a multidisciplinary community where a strong interest in technology and it's applications is the driving factor. 23 | 24 | Historically: 25 | - There wasn't much of a technology community before-hand, at least nothing publicly advertised. It was the main reason we started City Tech - there was a need for a tech community on campus that wasn't being fulfilled. 26 | - From conversations with departmental academics, there was a similar initiative a few years ago that did not outlast the students who started it. 27 | 28 | ### Resources 29 | Currently: 30 | - We've often referred students to online courses such as codecademy, Udacity, Udemy, Coursera and the likes. We've also set up a Slack group, with specific channels for help with specific topics, such as git-help and gamedev channels, and a learning channel for general questions. 31 | - We've run an Intro to Git workshop and have other workshops planned, as well as drop in sessions for Java. 32 | - We're trying to push the students to go to upcoming hackathons at other universities as well as hosting our own: MLH Local Hack Day, Global Game Jam and Hack City. We try to make good use of the events run by the Hackathon Hackers EU community by advertising them internally. 33 | 34 | ### Accessibility 35 | Currently: 36 | - Resources are quite accessible to students who tend to engage well. 37 | - It seems like the students who currently attend our events are those that may have already had some experience with development. 38 | - We tend to hold events after 5pm, since that's when most students will have finished lectures/tutorials by. However, it may be too late in the day for some, so theres always this constant trade-off. 39 | 40 | Ideally: 41 | - It would be great to have a way of reaching out to beginners, and breaking the initial barriers to learning, as most of the community will just be getting into the technology field. We've run events and use Slack to overcome this which has helped, but I think there may also be other ways. 42 | - Figuring out a way of determining when the best time for events would be for everyone, without leaving people out. 43 | - We should also be doing more to cater to people with disabilities. 44 | 45 | ### Interests 46 | Currently: 47 | - Students who have attend events so far (since September) have been wholly Computer Science students, despite there having been interest (such as during Freshers Week) from non CS students. 48 | 49 | Ideally: 50 | - There was a lot of interest from non CS students wanting to learn to program from scratch for personal reasons, as well as academic reasons (some Maths students wanted help with VB.NET for example). It would be great to have some technical events that are tailored to beginners from any discipline, rather than assuming any technical literacy at all. 51 | 52 | Given the age of the community, there is a sense of ambiguity as to what topics students would be open to. Maybe a better job needs to be done to capture individual interests. 53 | 54 | ### Goals 55 | Based on the events we've held, he primary reason students get involved seems to be to develop as a technical individual: to learn things they don't yet know. 56 | - This seems like it's primarily driven by wanting to do well at university as well as find jobs. 57 | 58 | Some of the goals/activities we've thought of setting have been introductions to different technologies and tech related items: Intro to Git, Intro to iOS dev, MLH Local Hack Day for students who may be intimidated by (new to) hackathons. 59 | 60 | The community is young so we're still understanding it's goals and needs. 61 | 62 | ### Location 63 | - We have a Slack group which all students who are interested in the tech society are added to. We use this as a place to ask questions, have discussions, announce upcoming (internal/external) hackathons and events. 64 | - Our events (mainly workshops) have so far been hosted at the university. 65 | - We've also advertised events not run by us, such as the Dinner hosted by Bloomberg and Hacktoberfest LDN, where some members have turned up. 66 | - The university is generally in a very good location for technology related events, being a short work from Old Street (Silicon Roundabout) and Angel. 67 | - We have a newly renovated open space at the university built specifically for CS students, that can fit 60-70 people. As a new society, we've also been recently granted access to book classrooms and lecture theatres for events, providing they're available. 68 | - Theres limited access to parking nearby, but good access to public transportation. 69 | 70 | ### Communication 71 | - We use Slack as our primary means of enabling the community to reach each other. We also have public Twitter and Facebook pages, as well as an internal Facebook group. 72 | - We also send out a weekly email of events coming up that week: events that we're running as well as other interesting tech related events worth going to. 73 | 74 | ### Culture 75 | - The community is new and still developing it's culture. But so far, it has been very welcoming of new people - given almost everyone is new. We're trying to create a culture where students can ask any questions and be open about what they don't understand. 76 | - We take on board new ideas since we believe the events that we plan should be driven by what the community wants and is interested in. 77 | - There are formal policies in place with regards to the society as being a part of the university's Student Union. 78 | - Personally, I think both sides of any disputes should be heard before trying to cater to whatever each party feels needs to be improved. 79 | -------------------------------------------------------------------------------- /communities/hacs/community-assesment.md: -------------------------------------------------------------------------------- 1 | # Assessing Your Community's Needs 2 | 3 | ### Glossary 4 | 5 | BCU: Birmingham City University 6 | CEBE: The computing faculty at BCU 7 | SU: Student's union (Birmingham City University Students Union) 8 | 9 | ## Definition :page_with_curl: 10 | 11 | [HaCS](https://hacs.tech) (Hackathon and Computing Society at BCU) members and other local university participants. HaCS tries to operate as openly as possible and regularly invites students from the surrounding universities to events. 12 | 13 | ## Size :chart_with_upwards_trend: 14 | 15 | - How many people are currently in your community? 16 | - We have ~130 registered society members through the students union, which receive weekly newsletter updates. We also have 300+ members in our [Facebook group](https://facebook.com/groups/hacs). Facebook is a mix of many other university students as well as a subset of our registered members. Of the 130 registered members ~20 are highly active within the community and of the 130 we get 15-30 attending our weekly events. Attendance for weekly events varies and it is not always the same 15-30 subset. 17 | - How many would you _like_ to be in your community? 18 | - I would like our active numbers to go up to 50 or 70 really active members from our university. I believe theres allot of hidden talent and enthusiasm to be found at BCU with a yearly intake of 300 undergrads into computer science and related subjects. 19 | - Historically, has the group always been about the same size? If not, what brought on that change? 20 | - Historically we have had roughly the same percentage of registered vs active members. We have seen growth since year 1 from 60 to 130 and we are now moving into year 3. 21 | 22 | ## Resources :computer: 23 | 24 | - What is currently available to people in your community to learn about tech? 25 | - There are our own workshops that we run, university library resources, hackathons and Birmingham/Midlands meetups. There are also university/department run workshops and events that happen throughout the term. 26 | 27 | - Are there meetups, seminars, online tools, office hours, hackathons? 28 | - Yes. There are three student run hackathons (BrumHack, AstonHack and BullHacks). There are also many me meetups by companies and communities in the area such as Tech Wednesdays (run by an incubator type office space), Brum JS (Javascript community regularly hosted by Talis) and many others. 29 | 30 | ## Accessibility :wheelchair: 31 | 32 | - How accessible are the current resources in your community? 33 | - Pretty accessible so long as you are a BCU student. There are some extra hoops we have to jump through to accommodate for non BCU students. 34 | 35 | - Are meetings held during hours where people may be working? 36 | - Not so far. We've always kept to meetups towards the end of the working day or after. We are planning to run more earlier however. 37 | 38 | - Is there childcare available? 39 | - No, this is a hot topic at SU meetings. 40 | - Is there accessibility for people with disabilities? 41 | - Yes, elevators and other modern facilities to accommodate. 42 | 43 | ## Interests :telescope: 44 | - Is your community made up only of computer science students? Are you OK with that? 45 | - A majority of members are CS or related. We do have many networking students from the same faculty. We are actively trying to accommodate more faculties and disciplines. One of our targets is to get many more Arts and media tech students coming to our events. We run many beginner friendly web development type workshops and have many talented web developers that could help them share their creativity on the web! 46 | 47 | - Is your community open to other topics, or are their interests very specific? 48 | - Main interest is definitely tech. There is also allot of interest in video games so we try to run lans too. 49 | 50 | ## Goals :dart: 51 | 52 | - Why do people get involved in your community? 53 | - To meet fellow course mates in a more relaxed student lead atmosphere. To make new friends and to learn about new and interesting technologies and workflows. 54 | 55 | - Are they students hoping to get a degree? 56 | - I hope so. Yes. 57 | 58 | - Are they passionate about developing, regardless of their major? 59 | - To a degree. One of our core aims is to introduce more people to the fun nature of the degree they've selected. 60 | 61 | - What activities and goals can you set for your community based on their existing goals? 62 | - Employability is a big one. Just generally to get our members out of the university grind and into real fun projects. 63 | 64 | ## Location :earth_africa: 65 | 66 | - Where does your community currently gather? 67 | - Mondays at the pub for our weekly social and Wednesdays during our workshops. We rarely see everyones faces at once however. 68 | 69 | - Is it an online-only group so far, or is there a place where people can meet? 70 | - Nope. We try to facilitate in person meetups as much as possible. On campus and at hackathons 71 | 72 | - Is there parking, and if so, is it free? 73 | - Yes more than you could ever need. Mostly paid. 74 | 75 | - Is there public transportation available to and from meet-ups? 76 | - Yes. Also a plethora of options. Two stations with direct connections to the whole of the UK and even a really super fast one soon in the future one day maybe. 77 | 78 | - Is the location accessible to those both on and off campus? 79 | - Yes, although more accessible to those on campus. We have noticed reduced attendance and willingness to stay long hours after lectures when students aren't immediately local 80 | 81 | - How much does it cost to use the space? 82 | - `int cost = 0;` But booking of space within 2 weeks required. We have a permanent booking for our weekly rooms and regularly book out the local pub for free also. 83 | 84 | - How flexible is the space for different types of presentations and meetings? 85 | - Flexible, all types of events are possible. From conferences to workshops. 86 | 87 | - How many people can it fit? 88 | - Depends widely. Our regular rooms could comfortably accommodate 30. We have access to much larger rooms and lecture halls 89 | 90 | - Is there comfortable seating for all shapes and sizes? 91 | - `return True` 92 | 93 | - Is there water or snacks available nearby? 94 | - Yes, water fountains and vending machines are always open. Canteen is normally empty. 95 | 96 | ## Communication :loudspeaker: 97 | 98 | - How does your community get in touch with one another? 99 | - Facebook pretty much exclusively. We do have a newsletter but thats one way communication. 100 | 101 | - Is there an email group, a GitHub organisation, a Twitter account, a Facebook group, a chat room or channel? 102 | - Yes, all of the above. [Facebook](https://www.facebook.com/groups/hacsbcu/), [Twitter](https://twitter.com/hacsbcu), @HaCSBCU, [Web](https://hacs.tech) 103 | 104 | - Could your organisation benefit from one or more of those, or another way of communicating? 105 | - We will use whatever the majority use and is effective 106 | 107 | ## Culture :performing_arts: 108 | 109 | - How welcoming is your community to new people and new ideas? 110 | - Yes please! In fact, why not join our [Facebook](https://hacs.tech/) group right now! 111 | 112 | - What happens if there is a disagreement? 113 | - We do our best to all conduct ourselves appropriately as adults. We are also working towards creating and implemneting a [code of conduct](https://github.com/HaCSBCU/conduct) for all interactions 114 | 115 | - Are there any policies or procedures in place, and are they documented? 116 | - We have a manifesto and many other official documents. The boring SU documentation stuff is accessible in our committee slack and on the BCU moodle portal. 117 | -------------------------------------------------------------------------------- /communities/plymouth-university/community-impact-proposal.md: -------------------------------------------------------------------------------- 1 | # Plymouth University Community Impact Proposal 2 | 3 | This impact proposal has been created from initial [Community Assessment for Plymouth University](./community-assessment.md). 4 | 5 | ## Summary of the Community's Needs 6 | 7 | ### Demographics 8 | 9 | Plymouth University is filled with many people from all different backgrounds. So far in this community it seems to mostly be people on computer science related courses such as a Comp. Games, Comp. Networking, Comp. Sci, etc. These courses at the university are also rather male dominated, though I have noticed slow movement over the years towards a more gender balanced community. 10 | 11 | All the students are studying for honours degrees or higher, making them educated although you do get a wide range of abilities and experience with regard to programming in particular. Many freshers come in with no programming experience which does seem to make events somewhat difficult to run. 12 | 13 | ### Communication 14 | 15 | Currently the existing tech communities in the uni seem to gravitate towards facebook, however in large groups or pages the interaction seems to lower interaction. Most of the general chit-chat seems to happen on small group chats or on the few discord channels floating around. It seems that for event organisation, facebook is the main platform as well. 16 | 17 | It would be good to get some sort of central hub of chatter going on with tech based folk at the university. Somewhere that people can share new finds and discuss news as well as advertise their own projects. 18 | 19 | ### Culture 20 | 21 | The community is slowly suffering from a decrease in passiation and increase in apathy. According to lecturers, even attendance to lectures has decreased signficiantly over the past few years. It seems for some reason students are unwilling to turn up to both required and optional content. 22 | 23 | The culture at core has mostly lost all buzz and excitement. Finding a highly visible platform to centre discussion around would be a fantastic way to slowly revive the culture. 24 | 25 | ## The Proposal :ring: 26 | 27 | I'm in a bit of an odd situation, the first being a scattered community and the second is I'm graduating this year and so I won't be around to enact a huge amount of change myself. After talking with Joe we decided it might be a good idea to find some folks to pick up the torch and begin handing over to them and potentially mentoring a little bit. 28 | 29 | I was also put in touch with an ex-leader of a previous large society in Plymouth. The number piece of advice they gave was to stay well away from the Students Union and ensure any new societies are not setup under them, and instead remain under a faculty. 30 | 31 | ### Communication and Organisation 32 | 33 | The idea would be to form a new facebook page (rather than a group) and begin trying to generate high quality, high signal discussion to form a small culture which we can then grow. This page would be spearheaded by the new community leaders, allowing them to brand it and mold it into their own foundation. 34 | 35 | ### Goals 🥅 36 | 37 | * Identify new budding community leaders. 38 | * Pull together material to aid them in reforging the community such as: 39 | * A brief history of the community and the current trajectory. 40 | * Tips on navigating various university social structures (which staff are active and willing to get involved, how to avoid the students union, etc). 41 | * Contact details for key players in any remaining tech pockets (Plymouth Game Devs, etc). 42 | * Work with them to plan some next steps for the community within the first semester of the 2017/18 academic year. 43 | 44 | ## Impact :punch: 45 | 46 | The following are the community needs listed in a slightly clearer format, next to each need are details of how the proposal will meet this need or reasons for why it is not within the scope. 47 | 48 | * **Injection of more varied learning materials** - This is to address the issue where freshers come in with very little practical knowledge making it hard for them to get heavily involved with events like hackathons. Sadly this is _outside of the scope_ but should be generated as a biproduct of more discussion. 49 | * **A low noise, high signal communication platform** - This is _within scope_ and going to be one of the core focuses of the project. It should provide a solid media platform for the community to come together in an async format, discussing things that interest them and ignoring the pieces that don't. Through this it should also provide a platform for the community to build new events and reach reach the wider global population with good visibility into what it is doing. 50 | * Within this it'll be important to ensure that the community is branded in a friendly but energetic form. This will help form the undelying culture we wish to promote within the universities tech community. 51 | * **Engaging lower years within the Honours courses** - It's important that we find some enthusiastic students who are further back in their degrees so that they can begin to grow this community over the course of a few years rather than trying to rush for a one year run before they move on as well. This should hopefully bring a more even balance community demographics as these lower years seem to have a better balance of backgrounds. 52 | 53 | ### Rough timeline 54 | 55 | As there is little time left in the year, some of this may span over the summer or into the next year. The following are a number of steps which might be used to achieve this vision and accomplish the project, though they are likely to change as things progress. 56 | 57 | 1. Identify some budding community leaders - This should be done before the summer, so preferably within the **next 2-3 weeks**. I'll do this by approaching lecturers and other key staff to try and identify some students who seem to be natural leaders within their groups. Beyond this I'll also reach out within the current GDSoc (Game Dev Soc) and the few other pockets to see if there are people who might share the same vision. _If this must be delayed until after the summer, all will not be lost as this will open up a new pool of freshers who might be up for the challenge._ 58 | 2. Begin forming new discussion platform - Ideally this would take place during the summer, so that content can culture can build up within the platform. The idea would be to have the community leaders invite those they know that would interested in joining the community, but not pushing for high numbers and instead focusing on good discussion. **This is dependant on the first stage**. 59 | 3. Begin advertising and recruitment - Once the leaders have made the platform their own and figured out how they wish to use it, it would then be the time to begin attacting new members. This would be largely down to the students that year, but a possible approach to this could be organising a hackathon or mini-conference which is open to all within the university. This would kick off things off as a public group and begin to draw in new people who might be interested in joining the community. 60 | 61 | ## The future :crystal_ball: 62 | 63 | Pretty much this entire proposal stems beyond the 8 week programe. So the main thing to focus on here is success measures. While much of this depends on the new leadership which steps forward, here are some initial success measures which could be used. 64 | 65 | 1. A group is established with some core values and aims considered. 66 | 2. Interest by one or more students in taking on the campus expert training to succeede myself. 67 | 3. New knowledge being delivered by students to each other. 68 | 4. Regular high quality discussion taking place via the communication platform. 69 | 70 | Beyond Plymouth as I move forward, I'll be moving to Bristol as a software engineer at Gradient. This will give me a chance to connect in with Bristol Uni and try and hook in a few students to the Campus Expert programme to pass on the tourch for the south west. 71 | --------------------------------------------------------------------------------