Proposed update to Warden Addendum

[Greg Arnold (COO)]

At the meeting I proposed a change in the Warden Addendum, which incorporates 3 major changes:

• Fix any spelling errors I found
• Remove references to Head Warden (we never used it)
• Add Educational Warden

Basically, the educational warden will serve as a facilitator for educational activities such as:

• Co-ordinating with the class host a time to have the class
• Handling the EventBrite functions if the class requires it.
• Handling all social media posts (such as Twitter, the blog, Facebook, &c.) to get word out about the class
• Any other actions needing to be undertaken to host a class

This will hopefully lower the bar for hosting a class, allowing us to have more classes!

This is a link for the difference between the two files: https://github.com/Hive13/bylaws-and-membership-addendum/pull/2/files#diff-e4704e61fd9200ea7709b8ff599aa495.  Please note that there is a decent amount of whitespace changes.

Technically, this is a pull request for proposed-warden-update@88af365 into master.

[Daniel McNamara]

Greg, addendum changes fall under bylaw changes as they are part of the bylaws. Which requires a special meeting as described in the bylaws and Ohio state law.

I like the ideas of these changes except the event Brite. That has to do with not knowing how event Brite handles the money aspect, which I feel an elected officer/board should be handling. With some clarification in that aspect I may have a change of opinion.

--
You received this message because you are subscribed to the Google Groups "Hive13 Hackerspace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cincihackerspace+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ian B]

My understanding was that the reason it was created as an addendum was so that it could be modified by a simple vote of the membership rather than requiring a full special meeting.

That being said I would agree with removing the reference to eventbrite, but for different reasons. I feel we should use more generic language, i.e "Handle the use of event management/ticket sales services as necessary", rather than calling out a particular third-party service which may go away or otherwise become impractical for our purposes without warning.

 - Ian B.

To unsubscribe from this group and stop receiving emails from it, send an email to cincihackerspa...@googlegroups.com.

[Dave B.]

Good catch re: eventbrite, Daniel.

There is no reason to tie to one vendor.  Amen to generic ticket management language.  Good idea on solution, Ian.

I was under the impression that the Warden stuff was implemented as an addendum in order to allow it to be changed easier than the bylaws.  Is there ample precedent out there for us to reference and get an answer to something like this?  It's a "generic" enough question that affects enough organizations that I'm sure it's been hashed out already.

-D

[Elly Hall]

Just wanted to clarify things for everyone, because this stuff is complicated and boring, :P so a lot of people don't know these things...  I colour coded things because some words are similar!  YAY! :D

The definition of an addendum as it pertains to our Bylaws:  "In other documents, most importantly in legal contracts, an addendum is an additional document not included in the main part of the contract."  There is also a difference between an amendment and an addendum, in case anyone has any questions about that, and how that pertains to our bylaws under the Amendment section.  An amendment makes a change to a document and is part of the document.  An addendum makes an addition to a document, and is a separate entity.

So it actually isn't part of the bylaws.  In fact, this is precisely why we chose to do these items as addenda, so they could be changed more easily.  They contain information that needs to be more flexible than the contents of the bylaws, which should be stable and take concerted effort to change.

Lastly, special meetings only require 72 hours of notice to the general membership, as stated by our bylaws.

It is correct that bylaw changes require a special meeting with a 2/3 affirmative vote of quorum to pass.  However, as this doesn't apply to this vote, overall, we should be good to go :)

[Daniel McNamara]

Bylaw says 10 days to 60 day notice for special meeting. This conversation also took place a year or 2 ago, I believe Ian Wilson was involved, I emailed him for his stance as I believe he is the one who said that but memory of 2 years ago is fuzzy so... he has the best knowledge on this  out of anyone here I believe.

[Ian B]

Correction: Item #1 under the Notice of Meetings in the bylaws specify 10 to 60 days notice for Annual meetings. However Item #4 under the Notice of Meetings sections specifies 72 hours notice for Special Meetings.

That being said, more notice is always preferable.

- Ian B.

To unsubscribe from this group and stop receiving emails from it, send an email to cincihackerspa...@googlegroups.com.

[Daniel McNamara]

After rereading the bylaws,  Ian you are correct. My mistake, I misread that section. Thank you.

[Greg Arnold (COO)]

If you look at the actual changes provided in the link instead of my summary, I didn't specify any particular vendor.  I just used it specifically in the summary because it's what we use now and people are familiar with it.

Again, the actual changes may be viewed at https://github.com/Hive13/bylaws-and-membership-addendum/pull/2/files#diff-e4704e61fd9200ea7709b8ff599aa495

On Wednesday, August 17, 2016 at 1:01:19 AM UTC-4, Ian Blais wrote:

My understanding was that the reason it was created as an addendum was so that it could be modified by a simple vote of the membership rather than requiring a full special meeting.

That being said I would agree with removing the reference to eventbrite, but for different reasons. I feel we should use more generic language, i.e "Handle the use of event management/ticket sales services as necessary", rather than calling out a particular third-party service which may go away or otherwise become impractical for our purposes without warning.

 - Ian B.

On 08/16/2016 08:05 PM, Daniel McNamara wrote:

Greg, addendum changes fall under bylaw changes as they are part of the bylaws. Which requires a special meeting as described in the bylaws and Ohio state law.

I like the ideas of these changes except the event Brite. That has to do with not knowing how event Brite handles the money aspect, which I feel an elected officer/board should be handling. With some clarification in that aspect I may have a change of opinion.

On Aug 16, 2016 19:56, "Greg Arnold (COO)" <gar...@hive13.org> wrote:

At the meeting I proposed a change in the Warden Addendum, which incorporates 3 major changes:

• Fix any spelling errors I found
• Remove references to Head Warden (we never used it)
• Add Educational Warden

Basically, the educational warden will serve as a facilitator for educational activities such as:

• Co-ordinating with the class host a time to have the class
• Handling the EventBrite functions if the class requires it.
• Handling all social media posts (such as Twitter, the blog, Facebook, &c.) to get word out about the class
• Any other actions needing to be undertaken to host a class

This will hopefully lower the bar for hosting a class, allowing us to have more classes!

This is a link for the difference between the two files: https://github.com/Hive13/bylaws-and-membership-addendum/pull/2/files#diff-e4704e61fd9200ea7709b8ff599aa495.  Please note that there is a decent amount of whitespace changes.

Technically, this is a pull request for proposed-warden-update@88af365 into master.

--
You received this message because you are subscribed to the Google Groups "Hive13 Hackerspace" group.

To unsubscribe from this group and stop receiving emails from it, send an email to cincihackerspa...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ian B]

Ah, I see. I am fine with the wording in the document itself.

- Ian B.

[Greg Arnold (COO)]

Just a reminder to vote on this - you can vote online.  We need to reach quorum to pass this, and it would really help the Hive in its educational goals.

Once again, my initial post is a summary.  The full change set may be viewed at https://github.com/Hive13/bylaws-and-membership-addendum/pull/2/files#diff-e4704e61fd9200ea7709b8ff599aa495.

[Tim]

Forgive my denseness, but is there a specific place you want us to vote?

[Greg Arnold (COO)]

Yes.  You can vote on this thread, just like any other vote!

On Tuesday, August 16, 2016 at 7:56:33 PM UTC-4, Greg Arnold (COO) wrote:

[Gabe Martini]

I  vote yes on this, if my vote still counts

--

[Tim]

I vote yest.

[Greg Arnold (COO)]

Bump again.

On Tuesday, August 16, 2016 at 7:56:33 PM UTC-4, Greg Arnold (COO) wrote:

[Matthew Malarik]

I vote yes

Matt Malarik

--

You received this message because you are subscribed to the Google Groups "Hive13 Hackerspace" group.

To unsubscribe from this group and stop receiving emails from it, send an email to cincihackerspace+unsubscribe@googlegroups.com.

[Dave B.]

I vote yes because the original was clearly quite flawed, but have some questions:

1. Why is the COO not entitled to 50% membership/$1membership compensation if the COO is also serving as a warden? (Lines 44-45)  Is this intended to prevent a war

2. Why are wardens not able to spend their own budget and seek direct reimursement from treasurer vs. COO buys everything (Lines 31-33, 37-40) ?  Is this a check/balances approach?

3. Comment: Line25/26 is kind of meh as wardens don't have direct access to funds - the COO is still in their way.

thanks,

-Dave

--

[Bill]

Yes!

Bill

[Kevin S]

If I had more hands I'd give your vote 4 thumbs up :-)

On Aug 23, 2016 2:43 PM, "Bill" <wjst...@hotmail.com> wrote:

Yes!

Bill

[Greg Arnold (COO)]

1. It didn't seem right for the COO to nominate himself for cheaper dues.
2. That's more so that the COO knows how much of the budget is left.
3. That's just a spacing change; I didn't edit any text there.

To unsubscribe from this group and stop receiving emails from it, send an email to cincihackerspa...@googlegroups.com.

[Dave B.]

Thanks a lot for taking the time to do this Greg!  Nice job.

-D

To unsubscribe from this group and stop receiving emails from it, send an email to cincihackerspace+unsubscribe@googlegroups.com.

[Ryan Hershey]

Belated "yes" vote from the on-call support dungeons.

- Ry

[Lorin Edwin Parker]

yep.

To unsubscribe from this group and stop receiving emails from it, send an email to cincihackerspace+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Hive13 Hackerspace" group.

To unsubscribe from this group and stop receiving emails from it, send an email to cincihackerspace+unsubscribe@googlegroups.com.

[Greg Arnold (COO)]

Just a reminder, this vote is still open, so if you haven't voted yet, please do so.

On Tuesday, August 16, 2016 at 7:56:33 PM UTC-4, Greg Arnold (COO) wrote:

[Michael Bell-Horwath]

I vote Yes.

Mike

--

[Tiffany Bell-Horwath]

If I didn't vote, I vote yes.

--

Tiffany R. Bell-Horwath

Chemistry Ph.D

Visiting Assistant Professor

University of Cincinnati

[Greg Arnold (COO)]

Bump again.  We're getting close to quorum.

[Brad Walsh]

I vote yes (if I haven't already voted). :)

Thanks,

Brad

--

[John2pt0]

I vote yes re: Educational Warden

[Greg Arnold (COO)]

Bump this again.  We're getting close!

[Andrew]

I vote yes.

[Jim Dallam]

I vote "yes" (remotely, back in October...)

JimD

--

You received this message because you are subscribed to the Google Groups "Hive13 Hackerspace" group.

To unsubscribe from this group and stop receiving emails from it, send an email to cincihackerspa...@googlegroups.com.

[Kevin S]

I vote yes

To unsubscribe from this group and stop receiving emails from it, send an email to cincihackerspace+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to the Google Groups "Hive13 Hackerspace" group.

To unsubscribe from this group and stop receiving emails from it, send an email to cincihackerspace+unsubscribe@googlegroups.com.

[Tim]

I already voted on this email thread, but I am reiterating my yes vote.

[Lorin Edwin Parker]

I have already voted yes, but state that I endorse this and stand by my Yes. This will give us the leverage we need to increase education activities, offer more training to members, and more outreach to the community. 

For those of you who have felt frustrated by the lack of training and orientation for new members, the lack of courses or lessons to certify members on equipment like the large CNC, etc. This is the change to our documents which allows us to start holding a higher standard, and put someone in charge, solely for this responsibility. 

The reason we do not offer more classes & certifications in an organized manner is that administrating and organizing classes is tedious and difficult. It requires a designated individual with some power, leverage, and a little compensation (1/2 dues in exchange for a lot of work).

Initiating, organizing, scheduling, and funding classes or courses is difficult -- trust me, I am a career educator. I'd love to teach at Hive13 more, but I am one volunteer here. 

Here's my own case as an example: 

I want to teach, but I need someone to help me advertise the class, put it on eventbrite and get enrollments, make sure that parts have been ordered or equipment is on hand, and just help me set things up. As a teacher, I want to concentrate on my lesson and teaching to the best of my abilities. I simply can't do this without some simple help. I have taught a number of classes, trained people one-on-one, taught skills informally, etc at Hive. I have simply been unable to do my best at this or commit to more because I end up struggling with event-brite, scheduling, making sure announcements go out, calls are answered, etc. This leaves me with less time to prepare my lesson plan, and, often, a need to "wing it". I have opted out of teaching any classes that require materials purchase because I do not want to pay for materials out of pocket and then have no students show up. 

Last year, I spent more than $2000 on materials for my courses at UC OUT OF MY OWN POCKET, without reimbursement. This is the way teaching is, and I do it because I want to teach well and I want my students to succeed. You can go ahead and look up my salary at UC on the News Record database. Go ahead, I'm fine with it, it's public record. I don't do this at UC because I love UC (screw the administration), I do it because it's up to me and the other faculty members to provide education, not someone in a business office. Here's the difference with Hive13, though, UC enrolls my classes, provides for my licensing, accreditation, pays me a salary (even if it's less than I made in industry or at other Universities). AND, I know that when I show up to teach there will be students and many of them (not all) will be invested. Also, if I don't "make it happen", even out of my pocket, then my students lose out on the education they have committed to. I consider my most important contract to be with my students, not with the Provost (the one who signs my contract and my paychecks). Smart, good people don't get into academia because it's lucrative, easy, fun, or prestigious. Seriously, look up my salary, it's on the web. 

The education warden (this is what Greg proposed, and what this is about) will make Hive13 work for teachers. If they do the organization, make sure that my supplies are on hand or ordered, that students will show up, and that classes are announced and advertised, then I can teach. I work way to hard at UC to do all this. This is why I have not taught much at Hive. I wouldn't be able to follow through. 

I would like to offer these classes (and I have taught them, or similar before):

Basic electronics series -- with parts & materials provided.

Audio / acoustics series -- DIY analog synth, microphone, guitar pedals, vacuum tubes, acoustic panels / sound isolation, etc are options. (this is my area of specialization, by the way)

3D printing & Ultimaker -- yeah ulti is coming back after major upgrades to help with design problems that contributed to making it less friendly to Hivers. New feeder, new bowden assembly, new bowden couplings, new power FETs, over-temp and feed failure protection, and more.

<Steps off soap box>

That is why people should vote. Please feel free to abstain or vote no, but VOTE. Above, I wrote why I vote YES. If someone wants to write a counterpoint, please do. This is a collaborative community, and every yes, no, abstain is a contribution to community. 

This has been sitting in limbo for more than a month. Let's move on already!

Lorin

On Wed, Sep 21, 2016 at 8:16 AM, Tim <busyg...@gmail.com> wrote:

I already voted on this email thread, but I am reiterating my yes vote.

--

[James Hartley]

Yes and double-yes (if required) from me.

Sent from my iPhone

On Sep 21, 2016, at 08:16, Tim <busyg...@gmail.com> wrote:

I already voted on this email thread, but I am reiterating my yes vote.

--

You received this message because you are subscribed to the Google Groups "Hive13 Hackerspace" group.

To unsubscribe from this group and stop receiving emails from it, send an email to cincihackerspa...@googlegroups.com.