Skip to content
This repository has been archived by the owner on Feb 1, 2018. It is now read-only.

Create initial version of impact proposal #32

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

sprusr
Copy link
Contributor

@sprusr sprusr commented Apr 19, 2017

Deviated from the template a bit by kind of merging the proposal and impact sections into one. Still got a bit of work to do, but the core of the plan is there.

The word "memes" is acting as a "TODO". The current culture is not (quite) only memes.

@PandelisZ
Copy link
Contributor

PandelisZ commented Apr 19, 2017

Allot of your stuff are in line with what we want to do. Specifically the docs stuff. We should just go ahead and merge both societies into HaACSS

also: https://github.com/HaCSBCU/conduct

edit: OMG, we should make an upstream website project. That we both contribute to and each use to run our sites. ++ to open source collaboration between socs.

edit edit: Lets call it TechSocPages!Then others can fork it, choose a theme for it or create their own, and run their own tech socs!

Copy link

@joenash joenash left a comment

Choose a reason for hiding this comment

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

LGTM!


Certainly with the documentation, this is going to have a lasting effect. The manifesto acts as the definition of what the society is all about, and should help drive decisions that this committee and future committees make. It's also important that this is an evolving document which can be edited and commented on.

I don't think that the docs necessarily have a measurable impact, so it's difficult to work out how successful they are. Perhaps a good idea would be for the committee to review the docs twice a year - once with the new incoming committee, and then once again around mid-term. Members should also be actively encouraged to review them.
Copy link

Choose a reason for hiding this comment

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

Engagement with the docs would be interesting, perhaps hooking them up to google analytics.


I don't think that the docs necessarily have a measurable impact, so it's difficult to work out how successful they are. Perhaps a good idea would be for the committee to review the docs twice a year - once with the new incoming committee, and then once again around mid-term. Members should also be actively encouraged to review them.

With the programme of events, the immediate impact will be seen by the number of members attending the events. In the longer-term, the impact will be the skills and knowledge which members pick up from these sessions and go on to develop further. This is again hard to measure, but if at least one person is encouraged to go on and use what they learn in something, then I'll count it as a success! If the format and planning of the events goes well for the first term, then we'll iterate on the concept and adapt it for people's needs in second term.
Copy link

Choose a reason for hiding this comment

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

We spoke a little bit about one way you can measure this: proportion of students participating in events that go on to become mentors/speakers at future events. You could also do something nifty with the GitHub API and see which of them goes on to make an active repo from the event ;)

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

Successfully merging this pull request may close these issues.

3 participants