|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools |
Rating:
|
Display Modes |
|
#46
|
||||
|
||||
|
Re: FRC Blog - My Bad Call
Is there a post somewhere detailing what happened in Orlando? This is the first I've heard about it, searching isn't turning up anything useful, and I'm curious...
|
|
#47
|
||||
|
||||
|
Re: FRC Blog - My Bad Call
If you go to Youtube and look up the Orlando Regional, both 233 and 179 were interviewed by TheRoboShow about the incident.
|
|
#48
|
||||
|
||||
|
Re: FRC Blog - My Bad Call
Quote:
Quote:
|
|
#49
|
|||||
|
|||||
|
Re: FRC Blog - My Bad Call
Quote:
+1 for Frank. Nice to see that HQ takes issues like the SVR one seriously, and fixes them quickly. |
|
#50
|
|||||
|
|||||
|
Re: FRC Blog - My Bad Call
Thanks to Frank for explaining the situation and trying to make it right. Mistakes happen to everyone, and it is how we deal with them that shows our true character. We can all learn a lot about how to deal with a bad situation from the actions of 1323 and Frank these past couple of days.
It stinks for other teams that, for one reason or another, also had their seasons prematurely shortened. I am not in a position to say that these teams are any less deserving of a spot at the Championships, but I am just glad that in this case FIRST got it right. |
|
#51
|
|||
|
|||
|
Re: FRC Blog - My Bad Call
Several are wondering why Frank/FIRST have not addressed other seemingly similar situations publicly as has been done here.
While I have no specific 'inside' information regarding any of the situations, lets give Frank/FIRST/HQ the benefit of the doubt here. It is clear that when the situation lends itself, a public explanation such as today's is given and the resolution is a good one. It could be that circumstances around other situations are such that a public 'airing' of the situation and its resolution is not in the best interest when all affected parties are considered. That doesn't mean that a best case resolution hasn't been made in ways that are not made public. FIRST has had more transparency in recent times, but that does not mean they can always be fully transparent on all matters. The directly affected parties for such issues deserve to have their concerns considered and typically will communicate directly with FIRST. The rest of the FIRST community is not entitled to have all matters and their resolutions explained to them as doing so may compromise some confidential information or have other undesirable effects. In some cases, parties are asked not to discuss resolutions with others as part of the resolution. This is the way it works in the real world, folks. Again, I am in no way saying that anything like this HAS happened in any situation (I have no clue), just saying that hearing nothing doesn't always mean you can assume nothing has happened. If you are not a directly effected party, assume that you do not have all the facts and your conclusions are suspect. This was the case for some CD posters concerning the SVR issue, prior to Frank's blog post. Thank you Frank for all you do for FRC. |
|
#52
|
||||
|
||||
|
Re: FRC Blog - My Bad Call
Since there seems to be some lingering confusion on the Orlando situation I'm posting the link to the thread that has posts from 1902, 624, and 233.
http://www.chiefdelphi.com/forums/sh...127083&page=12 Judge for yourselves how similar or not the situation is compared with SVR. It seems in both situations Frank was asked to make a decision with incomplete or incorrect information. **EDIT** 233 is the only alliance member left who does not currently have a spot at Championship. (They were also the alliance captain of that #1 seed) Last edited by sbrierty : 08-04-2014 at 14:16. |
|
#53
|
||||||
|
||||||
|
Re: FRC Blog - My Bad Call
Quote:
I am not asking for the Wild Card to be removed. I just want people to understand that this tough decision did not come without consequences. Quote:
The Championship still offered an open enrollment phase back then, so perhaps the "stakes" weren't as high. Quote:
Quote:
I caution everyone to not so easily underestimate the collective emotional pressure boiling underneath the surface of this season. If HQ doesn't take suitable steps to see that it is properly relieved, and similar mistakes are made again in subsequent seasons, don't be surprised to see the endgame erupt into something that no one - teams, volunteers, and HQ - wants to see. I think all people are asking for is a public acknowledgment from HQ along the lines of "We made mistakes in developing and deploying significant game management aspects of the Aerial Assist season, and we fully own them. The responsibility for correcting them is ours. We apologize for the added stress this season has brought to teams and volunteers, and we assure you that we will do everything in our power this offseason to improve our internal quality control measures such that the competitive experience will be better for all involved." I honestly, truly, do not think that is too much to ask. It would go very far in alleviating the pressure I mentioned above. Last edited by Travis Hoffman : 08-04-2014 at 16:10. |
|
#54
|
|||
|
|||
|
Re: FRC Blog - My Bad Call
Quote:
Are you expecting a public statement after each week of competition for the major transgressions that occurred and/or 'went viral'? Consider a rookie team that is exposed to one event, doesn't follow CD, but then sees public apology statements through the blog (or an email blast) each week. Without a lot of context, they might think "what kind of organization have we gotten into?" If there is to be another public acknowledgement of troubles and intent to address them (and there very well might be), I'd expect it to come after the season is over, not before. It has already been acknowledged in a blog post that things are not as they had hoped and that they intend to work to incorporate lessons learned for future game design. |
|
#55
|
||||
|
||||
|
Re: FRC Blog - My Bad Call
There may be another issue here that wasn't addressed by Frank's post...
How did he end up in a position to make a decision without adequate information? Should this have been handled by a call between the head ref and Aiden (not sure of his title, but let's call him the head head ref) and not escalated to Frank? I was trying to look at the manual for guidance and this was the best I could find. Quote:
|
|
#56
|
||||
|
||||
|
Re: FRC Blog - My Bad Call
Quote:
|
|
#57
|
|||||
|
|||||
|
Re: FRC Blog - My Bad Call
Quote:
|
|
#58
|
|||||
|
|||||
|
Re: FRC Blog - My Bad Call
I am so, so proud of Frank for this post.
Yes, the wrong call was made, and he apologized for it and explained how he was going to fix it. Frank's really good at this transparency thing we're all begging for. However, it doesn't fix the issue that anyone thought it was at any point okay to penalize a team for an honest mistake, nor does it excuse the alleged statement made re: 'pulling the team out of championships'. Things need to change somewhere in the chain of command to avoid the overpowered-entitled-volunteer behavior that's become unfortunately all too common in the FIRST community. A big step in the right direction. All in all, the right thing to do for now. Good Guy Frank strikes again! ![]() |
|
#59
|
|||||
|
|||||
|
Re: FRC Blog - My Bad Call
Quote:
Quote:
. |
|
#60
|
||||
|
||||
|
Re: FRC Blog - My Bad Call
Buy low, sell high! I like it.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|