<p dir="ltr">I would like to voice my protest to socks. As the proud owner of not one, but 2 size 16 feet, I have a feeling I would be left out in the cold. </p>
<br><div class="gmail_quote"><div dir="ltr">On Thu, Mar 9, 2017, 9:04 PM Hriday Balachandran <<a href="mailto:bala@socallinuxexpo.org">bala@socallinuxexpo.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Next year, everyone gets socks. Unisize...<br class="gmail_msg"><div class="gmail_quote gmail_msg"><div dir="ltr" class="gmail_msg">On Thu, Mar 9, 2017 at 9:45 PM Lei Zhang <<a href="mailto:leiz@socallinuxexpo.org" class="gmail_msg" target="_blank">leiz@socallinuxexpo.org</a>> wrote:<br class="gmail_msg"></div><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Is it really that much slower to write "M2XL" vs making a chicken<br class="gmail_msg">
scratch on a sheet of paper? What if I pre-printed some sizes on the<br class="gmail_msg">
coupon and put checkboxes next to them?<br class="gmail_msg">
<br class="gmail_msg">
I'd be scanning the same barcode as the one on the attendee badges, to<br class="gmail_msg">
verify it is a valid badge, and inputting the hand written size /<br class="gmail_msg">
checked box at the same time. Basically doing what we did this year,<br class="gmail_msg">
but deferring the actual scanning because some people insist that's<br class="gmail_msg">
what slows down the t-shirt pick up process.</blockquote></div><div class="gmail_quote gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br class="gmail_msg">
<br class="gmail_msg">
On Wed, Mar 8, 2017 at 10:12 PM, David Lang <<a href="mailto:david@lang.hm" class="gmail_msg" target="_blank">david@lang.hm</a>> wrote:<br class="gmail_msg">
> writing the size on lots of separate pieces of paper and then trying to scan<br class="gmail_msg">
> them will be far slower than just keeping a tally on paper as they are<br class="gmail_msg">
> handed out.<br class="gmail_msg">
><br class="gmail_msg">
> What would you be scanning? not the size they were given (that's<br class="gmail_msg">
> hand-written). The only thing you could scan is identification of who got a<br class="gmail_msg">
> shirt.<br class="gmail_msg">
><br class="gmail_msg">
> On Wed, 8 Mar 2017, Lei Zhang wrote:<br class="gmail_msg">
><br class="gmail_msg">
>> Date: Wed, 8 Mar 2017 22:04:13 -0800<br class="gmail_msg">
>> From: Lei Zhang <<a href="mailto:leiz@socallinuxexpo.org" class="gmail_msg" target="_blank">leiz@socallinuxexpo.org</a>><br class="gmail_msg">
>> Reply-To: SCALE Planning List <<a href="mailto:scale-planning@lists.linuxfests.org" class="gmail_msg" target="_blank">scale-planning@lists.linuxfests.org</a>><br class="gmail_msg">
>> To: SCALE Planning List <<a href="mailto:scale-planning@lists.linuxfests.org" class="gmail_msg" target="_blank">scale-planning@lists.linuxfests.org</a>><br class="gmail_msg">
>> Subject: Re: [Scale-planning] Did you like having SCALE t-shirt pick up on<br class="gmail_msg">
>> the<br class="gmail_msg">
>> expo floor?<br class="gmail_msg">
>><br class="gmail_msg">
>><br class="gmail_msg">
>> Thanks for your observations. They make a lot of since.<br class="gmail_msg">
>><br class="gmail_msg">
>> For coupon vs badge scanning, I thought of a compromise - coupons with<br class="gmail_msg">
>> barcodes on them. Attendees just hand them in and we can write down<br class="gmail_msg">
>> the size on them. Someone, likely me, can scan them into the computer<br class="gmail_msg">
>> afterwards and detect abuse, if any, after the fact.<br class="gmail_msg">
>><br class="gmail_msg">
>> Based on my experience, scanning badges is pretty fast, but we can try<br class="gmail_msg">
>> coupons and see if that makes a difference.<br class="gmail_msg">
>><br class="gmail_msg">
>> On Wed, Mar 8, 2017 at 4:48 AM, Nadia Morales <<a href="mailto:tauntria@gmail.com" class="gmail_msg" target="_blank">tauntria@gmail.com</a>> wrote:<br class="gmail_msg">
>>><br class="gmail_msg">
>>> Good Morning All,<br class="gmail_msg">
>>><br class="gmail_msg">
>>> I helped hand out shirts in the evening on Sat. BTW thanks for having me!<br class="gmail_msg">
>>> :)<br class="gmail_msg">
>>> I enjoyed giving back and it was a lot of fun. Here is my feedback if it<br class="gmail_msg">
>>> helps any.<br class="gmail_msg">
>>><br class="gmail_msg">
>>> Benefits of scanning<br class="gmail_msg">
>>> - Inventory control<br class="gmail_msg">
>>> - Double dipping prevention<br class="gmail_msg">
>>><br class="gmail_msg">
>>> Cons of scanning<br class="gmail_msg">
>>> - Time consuming<br class="gmail_msg">
>>><br class="gmail_msg">
>>> Benefits of using a coupon<br class="gmail_msg">
>>> - Provides faster tee pickup<br class="gmail_msg">
>>> - Decreased wait time<br class="gmail_msg">
>>><br class="gmail_msg">
>>> Cons of using a coupon<br class="gmail_msg">
>>> - No Inventory control<br class="gmail_msg">
>>> - No double dipping prevention ( people can just say I lost it )<br class="gmail_msg">
>>><br class="gmail_msg">
>>> An alternative to both: Just marking a big black X on the back of the<br class="gmail_msg">
>>> badge<br class="gmail_msg">
>>> with a sharpie. It’s fast, they can’t say they lost the coupon. Con: No<br class="gmail_msg">
>>> inventory control, an alternative would need to be implemented.<br class="gmail_msg">
>>><br class="gmail_msg">
>>> List of my observations. The following led to increased tee shirt<br class="gmail_msg">
>>> selection<br class="gmail_msg">
>>> delay.<br class="gmail_msg">
>>><br class="gmail_msg">
>>> - Unable to decide on a size by the time the attendees approached the<br class="gmail_msg">
>>> table.<br class="gmail_msg">
>>> - Unable to easily view the size while standing in line. (tees were flat<br class="gmail_msg">
>>> on<br class="gmail_msg">
>>> the table) Attendees had to wait till it was their turn to get a good<br class="gmail_msg">
>>> look.<br class="gmail_msg">
>>> - No mirrors for the ladies. Most would never buy a dress without seeing<br class="gmail_msg">
>>> what it looks like. Same applies to tees for some women.<br class="gmail_msg">
>>><br class="gmail_msg">
>>> Proposed possible solutions to decrease wait time:<br class="gmail_msg">
>>> - Tack the tees on the wall kinda like a teeshirt shop. That way people<br class="gmail_msg">
>>> can<br class="gmail_msg">
>>> see the sizes from a far and have an idea of what size they need by the<br class="gmail_msg">
>>> time<br class="gmail_msg">
>>> they get to the table.<br class="gmail_msg">
>>> - Small mirror for those like like to see the fit.<br class="gmail_msg">
>>><br class="gmail_msg">
>>> Additional comments:<br class="gmail_msg">
>>> I saw somewhere down below someone commented on the material. I washed &<br class="gmail_msg">
>>> dried it. I agree that softness is everything. The scale tee was (Gildan<br class="gmail_msg">
>>> Heavy Cotton 100% cotton) The orange endless (Gildan Softstyle Ring Spun)<br class="gmail_msg">
>>> was a lot softer I liked it better.<br class="gmail_msg">
>>><br class="gmail_msg">
>>> Nadia<br class="gmail_msg">
>>><br class="gmail_msg">
>>> On Mar 7, 2017, at 11:35 PM, Mx Siltanen <<a href="mailto:mrsiltanen@gmail.com" class="gmail_msg" target="_blank">mrsiltanen@gmail.com</a>> wrote:<br class="gmail_msg">
>>><br class="gmail_msg">
>>><br class="gmail_msg">
>>> "Did anyone actually find the badge scanning to be slow?"<br class="gmail_msg">
>>><br class="gmail_msg">
>>> Went well when I went with a friend.<br class="gmail_msg">
>>><br class="gmail_msg">
>>> On Tue, Mar 7, 2017 at 10:44 PM, Lei Zhang <<a href="mailto:leiz@socallinuxexpo.org" class="gmail_msg" target="_blank">leiz@socallinuxexpo.org</a>><br class="gmail_msg">
>>> wrote:<br class="gmail_msg">
>>>><br class="gmail_msg">
>>>><br class="gmail_msg">
>>>> We had 4 people there when the crowd came. During off peak hours,<br class="gmail_msg">
>>>> there were oftentimes only 1 or 2 people there.<br class="gmail_msg">
>>>><br class="gmail_msg">
>>>> Did anyone actually find the badge scanning to be slow?<br class="gmail_msg">
>>>><br class="gmail_msg">
>>>> On Tue, Mar 7, 2017 at 2:32 PM, Ken <<a href="mailto:scalezz@kemasa.com" class="gmail_msg" target="_blank">scalezz@kemasa.com</a>> wrote:<br class="gmail_msg">
>>>> > Are you sure about that? Since there were 4 people at the t-shirt<br class="gmail_msg">
>>>> > booth<br class="gmail_msg">
>>>> > and<br class="gmail_msg">
>>>> > there were at least 2 at registration, that seems to me to be more<br class="gmail_msg">
>>>> > than<br class="gmail_msg">
>>>> > what<br class="gmail_msg">
>>>> > is normally at registration when the shirts are given out there. Then<br class="gmail_msg">
>>>> > when<br class="gmail_msg">
>>>> > you add someone to play traffic cop to make the line go faster and<br class="gmail_msg">
>>>> > less<br class="gmail_msg">
>>>> > of a<br class="gmail_msg">
>>>> > mess, including preventing those who don't realize that there is a<br class="gmail_msg">
>>>> > line<br class="gmail_msg">
>>>> > from<br class="gmail_msg">
>>>> > upsetting those who have been waiting in line, it seems to be more<br class="gmail_msg">
>>>> > people and<br class="gmail_msg">
>>>> > more of a problem, especially with two booths based on size.<br class="gmail_msg">
>>>> ><br class="gmail_msg">
>>>> > It also seems to be slower since all of the badges have to be scanned,<br class="gmail_msg">
>>>> > which<br class="gmail_msg">
>>>> > means it takes more time for the people. If there was a "coupon" on<br class="gmail_msg">
>>>> > the<br class="gmail_msg">
>>>> > badge<br class="gmail_msg">
>>>> > sheet, it could make the handout go faster instead of scanning the<br class="gmail_msg">
>>>> > badge.<br class="gmail_msg">
>>>> _______________________________________________<br class="gmail_msg">
>>>> Scale-planning mailing list<br class="gmail_msg">
>>>> <a href="mailto:Scale-planning@lists.linuxfests.org" class="gmail_msg" target="_blank">Scale-planning@lists.linuxfests.org</a><br class="gmail_msg">
>>>> <a href="https://lists.linuxfests.org/cgi-bin/mailman/listinfo/scale-planning" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.linuxfests.org/cgi-bin/mailman/listinfo/scale-planning</a><br class="gmail_msg">
>>><br class="gmail_msg">
>>><br class="gmail_msg">
>>><br class="gmail_msg">
>>> _______________________________________________<br class="gmail_msg">
>>> Scale-planning mailing list<br class="gmail_msg">
>>> <a href="mailto:Scale-planning@lists.linuxfests.org" class="gmail_msg" target="_blank">Scale-planning@lists.linuxfests.org</a><br class="gmail_msg">
>>> <a href="https://lists.linuxfests.org/cgi-bin/mailman/listinfo/scale-planning" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.linuxfests.org/cgi-bin/mailman/listinfo/scale-planning</a><br class="gmail_msg">
>>><br class="gmail_msg">
>>><br class="gmail_msg">
>>><br class="gmail_msg">
>>> _______________________________________________<br class="gmail_msg">
>>> Scale-planning mailing list<br class="gmail_msg">
>>> <a href="mailto:Scale-planning@lists.linuxfests.org" class="gmail_msg" target="_blank">Scale-planning@lists.linuxfests.org</a><br class="gmail_msg">
>>> <a href="https://lists.linuxfests.org/cgi-bin/mailman/listinfo/scale-planning" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.linuxfests.org/cgi-bin/mailman/listinfo/scale-planning</a><br class="gmail_msg">
>><br class="gmail_msg">
>> _______________________________________________<br class="gmail_msg">
>> Scale-planning mailing list<br class="gmail_msg">
>> <a href="mailto:Scale-planning@lists.linuxfests.org" class="gmail_msg" target="_blank">Scale-planning@lists.linuxfests.org</a><br class="gmail_msg">
>> <a href="https://lists.linuxfests.org/cgi-bin/mailman/listinfo/scale-planning" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.linuxfests.org/cgi-bin/mailman/listinfo/scale-planning</a><br class="gmail_msg">
><br class="gmail_msg">
><br class="gmail_msg">
> _______________________________________________<br class="gmail_msg">
> Scale-planning mailing list<br class="gmail_msg">
> <a href="mailto:Scale-planning@lists.linuxfests.org" class="gmail_msg" target="_blank">Scale-planning@lists.linuxfests.org</a><br class="gmail_msg">
> <a href="https://lists.linuxfests.org/cgi-bin/mailman/listinfo/scale-planning" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.linuxfests.org/cgi-bin/mailman/listinfo/scale-planning</a><br class="gmail_msg">
_______________________________________________<br class="gmail_msg">
Scale-planning mailing list<br class="gmail_msg">
<a href="mailto:Scale-planning@lists.linuxfests.org" class="gmail_msg" target="_blank">Scale-planning@lists.linuxfests.org</a><br class="gmail_msg">
<a href="https://lists.linuxfests.org/cgi-bin/mailman/listinfo/scale-planning" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.linuxfests.org/cgi-bin/mailman/listinfo/scale-planning</a></blockquote></div>
_______________________________________________<br class="gmail_msg">
Scale-planning mailing list<br class="gmail_msg">
<a href="mailto:Scale-planning@lists.linuxfests.org" class="gmail_msg" target="_blank">Scale-planning@lists.linuxfests.org</a><br class="gmail_msg">
<a href="https://lists.linuxfests.org/cgi-bin/mailman/listinfo/scale-planning" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.linuxfests.org/cgi-bin/mailman/listinfo/scale-planning</a></blockquote></div>