[Cwo] 2014 Summary Before Voting

Tue Sep 17 13:13:22 PDT 2013

I can see a year when there is a joint FOC - CWops QSO Party.  Until that happens, which may be the first year after pigs fly, we avoid FOC.

There is interesting division regarding the impact of NA Sprint on CWO and vice versa.  I wish it were just a a matter of a handful of operators shaved from CWO  participation in one session.  It likely will impact all three sessions to some degree.  Let's say 20 members are lost to CWO overall and 50 are lost to the adjoining CWops session.   At the same time, we don't know how many CWops members will be lost to the OH, HI and KS QSO parties. Might there be 20 such members?  My guess is fewer.  But as Rob has noted pointedly, and as has John, at least with NA Sprint there is no direct time conflict. Not selecting Aug 23 means the sponsors of the three QSO parties will not be annoyed with us.  Also, we won't be tangling with whoever is in fact playing in those state QSO parties, including numerous non-CWops operators (some of whom could be potential CWops nominees if they don't get pissed at us!).  That alone might be a deciding factor.  It is no fun for guys to be contesting different contests at the same time.   Sept 6  also means no political issues with JA and thus no negative impact on our efforts to bring more of them into the CWops fold. On rethinking this with the forgoing weighting, I need to shift to thinking Sept 6 as ever so marginally better for us for 2014 CWO.

Jim, N3JT

Sent from my Verizon Wireless 4G LTE Smartphone

-------- Original message --------
From: John Miller <webaron at gmail.com> 
Date: 09/17/2013  2:48 PM  (GMT-05:00) 
To: D Faklis <dfaklis at yahoo.com> 
Cc: cwo at kkn.net 
Subject: Re: [Cwo] 2014 Summary Before Voting 

Although I still prefer 13-September, I'm aware of the potential drama with FOC --- so set that date aside.

23-August:  
a.  The OH and HI QSO parties conflict.
b.  Based on 2013 dates, the KS QSO party will likely also be held the weekend of 23-August:  http://qsoparty.eqth.net/
c.  I happen to enjoy these 3 QSO parties.  All are well-run and fun to operate.
d.  Tokyo Ham Fair?  Hard to factor it in or out but if we avoid this weekend -- at least we can cleanly promote CWO for a different weekend.

06-September:
a.  Labor Day is Monday, September 1, 2014.  So if CWO is held Friday night/Saturday = 05/06-September, it would be after Labor Day weekend -- a good thing.
b.  Sprint CW analysis:  This Sept. there were 166 NA Sprint CW logs submitted:  http://www.ncjweb.com/cwsprintlogs.php
Cross-checking with the CWops roster, shows that of the 166 participants,  57 were CWops members = 34%.  Depending on your viewpoint, you could argue that's a large or a small percentage of overlap.  Either way, there's no overlap in time with CWO.
c.  No conflict with the Tokyo Ham Fair.

If we're down to these two dates, my preference would be 06-September.

73,
John K6MM

On Sep 17, 2013, at 4:34 AM, D Faklis wrote:

I have tried to capture the meat of the concensus building process.  I'm sure I missed some of the discussions.  Please check me carefully.  This email was sent to CWO at KKN.net and I assume that everyone involved receives reflector emails. 

Starting at the beginning:

What is the "new date?" Is it last zulu Friday in August? Or zulu Friday of first (partial) weekend in September? Or ... ?
73, Hank, W6SX

Good question Hank.  I think we decided on the first (partial) weekend in Sept. Be it Sat Aug 31 (zulu) like this year or first Sept Saturday (zulu).  Need to look at the 2014 contest calendar and see if that's a problem or not.  I haven't done that. Might be we were just lucky this year with the split weekend.
73, Alan, AD6E

If we make it last weekend of August, it would be Aug 30 2014. If we keep it first full or partial weekend in September, it will be Sep 6 2014.
Rob K6RB

Then, for these dates, YODX and NA Sprint are identified as concerns by the group.  A search for a new date begins.  Conflicts are identified by the group.

Primary conflicts:  Tokyo Ham Fair (23 AUG 14), YODX (30 AUG 14), NA Sprint (7 SEP 14), FOC (13 SEP 14), SAC CW (20 SEP 14), CQWW RTTY (27 SEP 14)

Secondary conflicts: HIQP and OHQP (23 AUG 14), WAQP (20 SEP 14), TXQP (27 SEP 14)

Unknown potential conflicts: KSQP (23 AUG 14)

YODX, FOC and CQWW RTTY achieve "keep out" status by the group:  30 AUG, 13 SEP, 27 SEP are essentially deemed no good by the group.

This leaves 23 AUG, 6 SEP, and 20 SEP as possibilities around this timeframe.

Review 23 AUG:  Tokyo Ham Fair, HIQP and OHQP are conflicts.  KSQP may be a conflict.
Review 6 SEP:  NA Sprint conflict.  No overlap in time; Sprint begins when CW Open would end.
Review 20 SEP:  SAC CW and WAQP are conflicts

Analysis 23 AUG:  In 2013, there was no conflict with Tokyo Ham Fair and 6 JA logs have been received out of a total of 246 for Session 1.  >90 logs from EU/W.Asia.  Remainder NA.  I have not processed Session 2 or 3.  HI and OH QPs take in about 200 logs each.  Most of the group feels that concurrent state QPs will not impact the CWO greatly.  
Analysis 6 SEP:   45% overlap in operators Sprint/CWO.  W6SX, NW2K, N3JT weigh this data against a 6 SEP CWO.  K6RB and AD6E are leaning OK with 6 SEP.  I can't find evidence on where W1RM, K6MM, NO5W stand on this date. 
Analysis 20 SEP:  SAC CW seems to be a late addition to the discussion.  Here is a link to some stats:  http://www.sactest.net/blog/statistics/  1200 logs received in 2012.  92 logs from NA.  874 logs from EU.  146 logs from Asia.  RST and serial number.

Proposed Cull:  20 SEP (SAC CW) seems more occupied than 30 AUG (YODX)

Please comment on this email and its assumptions and please decide if 20 SEP should be removed from consideration.  After the comment period, I'd like to convene a vote.

Thanks!
73, Dean, NW2K 

_______________________________________________
Cwo mailing list
Cwo at kkn.net
http://www.kkn.net/mailman/listinfo/cwo

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.kkn.net/pipermail/cwo/attachments/20130917/3afbae92/attachment.html 