I talked to Matt "Misery" Washington on Saturday. I don't want to put words in his mouth, but it sounded like he was making progress on setting up the PXE server.
I tried updating the mirror over the holiday break, but had problems.
Supposedly I had downloaded the whole repo to a VM on my laptop. I transferred the packages to the apt-mirror, but somehow I'm missing 90 GB worth of archives.
We can try to download the files again, but it's going to take a couple of weeks to get it down.
What would help here would be 1) someone with a fast connection willing to help us download the packages or 2) someone with more apt-mirror knowledge than I have who can help figure out what went wrong last time.
ATA (Advanced Technology Attachment): refers to an attachment which was "Advanced" back in the days of the PC-AT computer, but now is standard.
Dan MCapacitor (or "Cap"): A component soldered into virtually all motherboards and many other Printed Circuit Boards. Must look at to see if they're broken.
PCI-e (PCI Express): More advanced version of PCI.
Optical Drive: device for playing and recording CD, DVD and/or Blu-Ray discs. It is "optical" because it reads the disc with a laser beam.
Printed Circuit Board (aka PCB): A flat component (often green, though other colors exist) with assorted other components soldered and/or printed onto it. The Motherboard is an example of a PCB.
Port: A place to plug something in.
Power Supply(or PSU): supplies power to the computer and components.
ROM (Read Only Memory): not the opposite of RAM, this is memory that cannot be changed, only accessed. Commercial CDs and DVDs are ROMs. The computer's BIOS is on a ROM chip permanently attached to the motherboard.
Computer Parts, what they do, and how they go together
HDD: Holds OS, data files, resumes, games, videos, etc. Demo opened drive. Non-volatile: holds data even when unplugged. "Storage" (HDD) vs "Memory" (RAM) even though both are types of memory. Show opened HDD, what it looks like inside.
Master/slave. Device on far end is master, device on middle is slave. It's OK if your main OS is on "slave," it's just a word. Except: every slave needs a master, though not every master needs a slave. Set jumper to tell computer which is master and which is slave (if any).
Victor: We need to inventory everything that belongs to FGC, and everything that is for sale/is sold. Desktops, laptops, parts. Inventoried as they come in.
Howard: We should be able to sell that stuff, not just stored for years. Janet: I will get Matt [staff member, here on Saturdays] to talk to the people doing this, see what's up.
Janet: I said to a few volunteers that this would be our last meeting, going forward we'd organize an "advisory council" meeting once a month. Ken was thinking of a system with a three part membership: some paid staff, some volunteers, and board. They'd advise the board on issues. The treasurer says that the Board shouldn't be involved in this. Staff and CC should have own individual groups. Their groups should decide something, bring it to the board for a final ruling.
Janet: I have some research about bylaws. Advisory members may attend a board meeting but they have no vote.
Erick: So who is outlining this? Janet: This is one example of how bylaws are written. Got it off the internet. Ken: I got it from a particular place, don't recall it but can find it again.
Erick: When I asked last time about how the CC's attendance to the 3/3/3 "board" would be constructed I didn't get an answer; but if the board is going to make the final decision, what's the point of limiting the advisory membership? Why not just let the people who come express their opinion? Since they don't have voting powers anyway.
Ken: It's Advisory. Erick: But why limit it to three people? Ken: That was off the top of my head, as a three part board. Three from each (staff, volunteers, board). It's still open for debate. That was an example.
Victor: CC should be an advisory board, because technically you can't make any decisions because they're not legally responsible for the organization. But it's important to have CC because they know decisions. They can bring issues to board to resolve issues. Board would consult with staff, who would be the ones who implement any decision.
Erick: Again, who is going to "decide" this? We've got the three board members here right now. They can make the decision. Victor: That's exactly my issue with board being in CC, if we're here we're forced to make a decision right now. If we're not here, we can take the time to make sure it's legal and appropriate. That's why I don't vote in CC. I'm a board member, not a CC member.
Janet: So have we decided that we're going to go with an advisory council? Ken: That's really the way it has to be. CC has no legal standing. Because of the constitution we act like it has authority, but outside this building only the Board have legal standing. We need to have our paperwork line up with the legal requirements. Need to do ASAP.
Ken: My reason for bringing it up here & now is not to beat a dead horse, but to let people know whats going on instead of it being seen as a coup. Consent of the governed.
Janet: So when are you going to meet, who are you going to send to the board? Erick: the regular CC people can continue to meet, have a record of what has gone on, we have a record of what decisions we make to bring to the Board.
Ken: Whatever number of AB attendees are going to be there, my suggestion was to meet once a month. In the board meeting today, we reduced it to quarterly board meetings. Janet: Whatever the advisory board decides on, about anything, bring it to the next board meeting (April).
Jason: We could have CC meetings without board members, and draft our concerns to bring to the Board.
Dan: Based on the discussion today, the end of CC is fait acompli. It's a done deal. No need to discuss that any further. re Advisory Board, we don't need to finalize today how we'llorganize it. It's going to happen, that's the takeawy from today. Advisory board (fka CC) can meet again to figure out organization. Point of AB is to finalize our issues to bring to the BoD.
Victor: CC can continue as is, but change title to Advisory board and get the process streamlined. Bring ideas to the board, and most of the time the Board will probably do it the way AB wants (barring craziness or other issues).
Dan: Short term, AB will meet in two weeks just like old-fashioned CC.
Streamlining installation process (Jason)
Howard: Many websites still use Flash and java.
Victor: So when they get donated, we should ask them for the discs too? Jason: We can burn the discs in house. Use them to wipe personal data.
Ken: how many macs do we have ready to go through this process? Jason: I don't know. Many of the macs here now, their drives have been wiped already. Going forward we can do this process instead.
Dan: History lesson: we have wiped Mac OS and replaced with Linux since before my time. It wasn't any one person's decision to do this, it was a policy developed via group effort based on FG's operating philosophy which includes using and promoting FLOSS OSes, which Mac OS isn't. Jason: Other Free Geeks sell stuff with Mac OS, we can do it too. Per Apple's Terms of Service, people are allowed to sell a used Mac provided it has the same OS it came with originally.
Jason: From what I've heard, Macs are what make us money. They sell for more $ than the other (formerly Windows) PCs. Is that true? Answer: we don't have a good system to know that right now. Goes back to the lack of an inventory system.
Dan: We (someone specific) need to investigate and make sure we're legally allowed to do that. Trust but verify. We shouldn't just take someone's word for it no matter how trusted that person is.
Ken: so next time we have macs come in, we can have them set aside for Jason to experiment on. Maybe the next three, as a test.
All CC attendees: Please review the meeting notes on hackpad later and if necessary edit for accuracy re the discussion that took place.
Non-CC attendees: These notes are to document what happened at the meeting. Please don't add commentary or other things that didn't happen at the meeting itself. If you wish to respond to something, please start a new hackpad doc or discuss it on FGC's google talk list.
Dan MI'm working with Rick and Dan developing the schedule for the command line class. Soon we will let peole know. We'll do a basic class a couple of times, and then an advanced one. Some people need really basic instructions while others are more advanced. Rick and I are co-teaching, so maybe we'll split the class between the two so we can teach most effectively.
Ken: Educators are going to have a meeting next Sunday at 3 to firm up ideas about classes and stuff like that, organizing schedule, etc.
Dan MFuture of FreeGeek Chicago and its Community Council:
Ken: We previously talked abouot, is CC going to stay and/or in what form it's going to stay. We need to take action because it's the new year, legal docs will be rewritten ec. I've asked for input from the community. I haen't heard any concrete reasons why we shoulnd't do it this way.
Mario: We should keep CC meetings ecause it's informative to people. I'ts a reat benefit.
Ken: Details can continue to be filled out. The core of my proposal is: three reps from each group (board, staff, community) gets together 1x/mo. Required to meet. If the community wants to get together and have a meeting for their reps, but the 1x/mo meeting all groups would be represented so that the governance of the community will be legal.
Gab: how would staff & volunteer reps be selected? Ken: Details to be worked out. If you want to nominate or whatever, that's fine. As long as 3 from community nd 3 from staff show up that's the thing. Point is, it's not going to be board takeover and that's it. I don't want that, nobody wants that. Staff would advise the board. Volunteer reps would advise the board. But board must be the ones to make decisions. Not little stuff (what toilet paper to buy), it's policy What goals or the year, how we're goint to operate, etc.
It's coming. We need to be on board. Community needs to be on board with change because we're making legal changes We need to be as fair as possible.
Erick: How are you going to establish membership of the groups? Ken: I'm still working on details on that. The board needs to take legal responsibility. Will be done with staff & communiy input. This chane won't happen tomorrow, but it will be soon.
It's the new year now, it's time for action. We'll hammer out details. Upshot is, we're going to change to a more traditional board governance with legal responsibility.
Erick: But who is going to autorize this? Ken: Ultimately, the board. Unofficially with community input, but it must be the board bwecause it's the board that is the legal entity. Internally, the community has input.
Ken: Must be done by legal guidelines. We need to nail this down,.
Gabe: The quesiotn is, whats going to happen to CC with this? Ken: I"m still hammering out detaiols. We will discuss it at a future date. We'll let yoy know and ask for input and passage. BUt it must be done for legal reasons.
K: We're not going to throw the community out the window. The community wil have a voice.
Janet: We may have one more CC meeting before we go to this once a month thing.
G: What if designated representatives aren't available for the meeting? Ken: ommunity can ave a meeting to decide their reps and issues, same with staff, then the thrtee groups will get together and meet when they can.
Final decisions will be board. Hight levels. Financwes. Strategies. NOt day-to-day stuff.
Ken: expect it withing 30 days.
Ken: We son't get bogged down in muntae "I didn't get to do such and such." "Can we do monitors soon?" Etc. We need to get things accomplished rather than talking things to death.
Community can meet and discuss, and get organized to britn things to the staff.
Janet: per Victor, we've only got 5-7 people meet at CC on a regular basis. Amongst those who wold meet regularly, those people would be chosen.
I've been geting a lot of tongue lashing about getting this done. We need to get things moving, to a "higher plane." Once I see something is good, I can help i be better and put foeth that effort. I'm asking for ful participation about authority over paid staff. I didn't get anything. Now push has come to shove. I need people's input aboiut advisory board and hash out wording for new bylaws and constitution for FGC.
Gabe: We understand the purpose, but until we get specifics, we can't tell how we feel about it.
We just hae to comply with our legal status.
Gabe: Once we have a concrete idea about what this advisory board will look like we'll have more input.
Gabe: Is there a tie frame for this proposal/new details/speficitcs? When are we going to hear more? Ken: Ideally within the next 30 days. Not official. Janet: I"d like it for the next CC meeting so we can start doing meeitngs once a month.
Added Agenda Items
Visitors to the space (Gabriel)
Now I realize they weren't visitorys, they were shoppers. They wandered about, all the way to the parts department. I approaced them and helped them. Let them know what we have available, but that it's a staff area. Nobody caugt that. Concern in the future.
Maybe remind the helpers about looking out for wanderers, and make sure to help them but keep them from ambling.
Mike: The bototm line is, safety factor.
Gabe: We can ask volunteers to schedule for the rolses of front desk and parts. Just a suggestion.
Changing distros (Steve)
We're relying on when the server is upgraded then? Gabe: Yes. Alex has prepped the file server and will be ready to test soon.
Steve: Do we need to wait for server? Can't we just start using 16.04? Gabriel: we'll Start doing stuff soon. I like mint, it's pleasing without being resource intensive Also supported for 5 years. If you want to help us out with that great. Officially we'd be switini to X/Kubuntu 16.04 while testing other possible distros to switch to.
I'm trying to organize for a proposal for IT management. We want documentation for disaster recovery. Priority is servers are running and healthy. It's in the works.