Bylaws & Administrivia Hacknight! Mon 1/21 6pm

[Will Bradley]

Hey all:

As our organization grows, we've gotta keep our bylaws and other administrative stuff up to date and reflecting our goals. HeatSync is constantly a work in progress, and there are some parts of our bylaws, wiki, etc that need to get updated to match our current/intended practices.

SO, let's all get together and figure out what those changes should look like! Come to the lab on Monday 1/21 at 6pm (we may break away to nearby venues to chat so as not to hog up lab space) with your laptops and ideas.

This is a WORK meeting moreso than a TALK meeting; let's break out the laptops and draft some good stuff! Any substantial changes that seem like good ideas will probably make it into proposals, minor uncontroversial changes will probably just make it straight to the wiki/etc.

[Jeremy Leung]

Thanks Will for getting this meeting going and for everyone that came in to discuss this stuff.  Our bylaws have been up on Github for some time now here:

https://github.com/heatsynclabs/administration/blob/master/bylaws.md

I've updated them to make sure they match the wiki's content.  All of our notes from the meeting have been posted on the site as "Issues".  To participate in making the bylaws better all you have to do is grab a github account, navigate to the link above, review the bylaws, and then click on the "Issues" button on the top of the web interface.

Here you'll see multiple issues that have been posted already and can be discussed.  Check them out.  If you have any issues with lines that are already being discussed go ahead and contribute to the existing discussions. 

New additions to the bylaws or corrections to other lines in the bylaws can be added to the issues section by clicking on "New Issue", giving the issue a descriptive title(I would suggest something like "Section #: Section Name - Item #: Short Descriptive Blurb", and then in the description start the discussion with further details "This doesn't...I think that...this conflicts with".

This way we can track our changes and allow for thorough discussion for issues with specific lines in the document.