Thrift Store Agenda

Thrift store meeting - 12/22/10

Facilitator: Leah Scribe: Sergio (subbing for Michael)

Here: Ian, Francisco, Paul, Leah, Sergio, Michael

Old Commits

1. Leah will add text to the warranty about a 20% restocking fee and add the text 'calendar days' to the return policy - IP: restocking fee is changed, but not the calendar days text. Leah will talk to Richard DONE
2. We can get eyes logins, just need to talk to Richard - IP: Leah and Ian have them. Michael and Paco will talk to Sergio since he can give them accts. DONE
3. Leah COMMITs to talk to Richard about changing the text at the bottom of the receipts. DONE
4. Sergio COMMITs to announcing at staff meeting that we want to give a Better Cycle employees a discount in return. He will also check on the friend discount policy. DONE
5. Sergio COMMITs to adding the stream fishing policy change to the staff agenda. DONE
6. Ian COMMMITs to changing the stream fishing wording on the wiki. DONE
7. Leah COMMITs to talking to Caitlin and Meredith about changing the optical drive spec on high end systems. DONE

Discussion

1. The brochure for PowerPCs with no OS on them...Is it finished? What do we think?: Not done yet, C/O Tickets in the sales queue: now that we've had a chance to look at them is there anything immediate we need to address?: Nope, nothing immediate, I/P
2. Selling advertising on the website: uhhhh.... sorry, I can't remember this discussion at all now. Revisit next meeting?
3. 20% Restocking fee: When are we going to be charging this? We should try to lay out specific guidelines so the process can be clear if we do need to use it. Paul is going to join us in this part of the discussion. We should definitely charge a restocking fee whenever a system is returned for aesthetic reasons and probably for all returns that don't involve a legitimate technical issue (negligence doesn't count). Can we get a list of return reasons that would be subject to the fee on the wiki? COMMIT: Leah will create a wiki page for the list and email a list out, EVERYONE: add examples/reasons for charging 20% restocking fee.
4. Tracking machines that have been returned multiple times - can it be done? How do they get processed? Do returns get entered in the DB? If a system is returned and is run through eval/build again, does the DB remember the old system after components have been changed? We should set up a policy for documenting returned systems. It would be nice to get an immediate report at the point of sale that notifies us COMMIT: Sergio will talk to Ryan about how the DB deals with systems that end up going through build processes multiple times.
5. Safari: we talked about it, and it's too little income for the amount of work that goes into it. Additionally, it potentially places BAN certification in jeopardy. Safari was implemented for serving a particular group of people, and it no longer serves those people anymore. We could explore other avenues for putting stuff into art reuse and specialty projects (grants? partnering with SCRAP?). COMMIT: Ian will write up release explaining the end of Safari to inquiring minds.

Carry-over Discussion:

1. None!

Commits:

1. Leah will create a wiki page for the list and email a list out, EVERYONE: add examples/reasons for charging 20% restocking fee
2. Sergio will talk to Ryan about how the DB deals with systems that end up going through build processes multiple times
3. Ian will write up release explaining the end of Safari to inquiring minds.