Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should we create teams to manage areas of operation? #244

Open
amcewen opened this issue Jan 13, 2016 · 10 comments

Comments

@amcewen
Copy link
Member

commented Jan 13, 2016

From the Organisers meeting - http://wiki.doesliverpool.com/DoESMeetingMinutes20151029

Seems like a decent organisational pattern at other hackspace/makerspaces (e.g. Nottinghack and Cambridge Makespace both take that approach).

@johnmckerrell to list teams, and ask the mailing list about people to own machines. All to think about people to approach explicitly

We have a laser-cutters email address. However only @DefProc seems to know about it.

Action: @johnmckerrell to move it forwards - (list teams, and ask the list about people to own machines. All to think about people to approach explicitly)

@johnmckerrell

This comment has been minimized.

Copy link
Member

commented Jun 14, 2016

Notes from meeting 20160614 - me to do something with this

@johnmckerrell johnmckerrell changed the title Should we look to teams to help taking care of equipment? Should we create teams to manage areas of operation? Jun 14, 2016

@johnmckerrell

This comment has been minimized.

Copy link
Member

commented Jun 14, 2016

Look at areas of operation rather than just equipment, relates to the problem of not enough organisers.

@johnmckerrell

This comment has been minimized.

Copy link
Member

commented Jun 14, 2016

  • Opening & Closing
  • Maker Night
  • Communications
  • Events abroad (any events outside DoES)
  • Snacks
  • Accounting
  • Web team
  • Events at home
    • A/V
  • Equipment
    • Laser Cutter
    • 3D Printers
    • Soldering
    • Woodwork
    • CNC
    • Vinyl cutters
@amcewen

This comment has been minimized.

Copy link
Member Author

commented Aug 3, 2016

That's a long list. Are there any obvious groupings or particularly pressing ones to start with? I think we should have an existing organiser involved in (or at least helping bootstrap) any group to spot crossovers, bring people up to speed on how to get things done (what systems are in place already, who to bug about things, etc.) and so on.

There is a makernight group already. I've created a new page on the wiki to detail what these groups are - should we list the members of the groups on there too?

@ajlennon

This comment has been minimized.

Copy link
Contributor

commented Sep 12, 2016

Happy to help - just let me know what to do.

@amcewen

This comment has been minimized.

Copy link
Member Author

commented Oct 4, 2016

Would a first step be to pick a couple of teams, rather than running at the whole list? In the organisers meeting we thought this could be:

  • Workshop (to cover all the tools)
  • Events (to cover applying to MakeFests, etc.) and communications (for more active talking about DoES to outsiders)
  • Admin support (opening/closing, snacks, accounting)

Then we can try to choose people (as well as accepting volunteers - thanks @ajlennon!) to ask if they'd like to join a particular team

@cheapjack

This comment has been minimized.

Copy link

commented Oct 4, 2016

Like this

  • Maker Night
    • Workshop
    • Equipment
      • Laser Cutter
      • 3D Printers
        
      • Soldering 
        
      • Woodwork
        
      • CNC
        
      • Vinyl cutters
        
  • Events
  • Admin Support
    • Opening & Closing
      
    • Snacks
      
    • Accounting
      
    • Web Team
@amcewen

This comment has been minimized.

Copy link
Member Author

commented Nov 10, 2016

Maybe worth people trying to recruit for specific teams.
@DefProc to recruit some people for a workshop team. @huffeec to look at the external events (or exposure) team (and to suggest what it's called). @DoESsean to recruit people for the admin team.

@aubergine10

This comment has been minimized.

Copy link
Contributor

commented May 8, 2017

If we want a simple way to track who is in which team, github has a Teams feature (complete with ability to notify all members of a team): https://github.com/orgs/DoESLiverpool/teams

At the very least there should be a "team" for each piece of equipment, similar to the Cambridge hackspace concept of "Equipment Owners" (people who can provide training, maintenance, etc. for a given machine).

@johnmckerrell

This comment has been minimized.

Copy link
Member

commented Aug 8, 2018

Using the teams in GitHub is a decent idea, I've written up some of the teams on the wiki too: https://github.com/DoESLiverpool/wiki/wiki/People

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants
You can’t perform that action at this time.