|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
To share or not to share
So our team is having a debate about whether to share our designs and ideas with the world or to keep everything close to the vest and only let the world see tiny snippets of what we are working. We won’t go into detail about our thought just yet but we are curious what your thoughts might be? Click here to take our facebook survey. http://www.facebook.com/questions/24...627/?qa_ref=qd
|
|
#2
|
||||
|
||||
|
Re: To share or not to share
Our team plan to be pretty public [blog in sig].
We don't plan to give out CAD files or anything but share general photos/videos. |
|
#3
|
||||
|
||||
|
Re: To share or not to share
You don't have to share schematics or CAD drawings, but sharing your design concepts is definitely GP. Yes it opens the door for someone potentially "stealing" the idea, but hey, imitation is the best form of flattery. Don't worry about it, share what you want to make public.
|
|
#4
|
|||
|
|||
|
Re: To share or not to share
In general, our team has decided to 'share' some of our concepts on our facebook page. Not too many details, but enough to inform our sponsers which are encouraged to visit. Plus it's open to views to everyone so we aren't really hiding anything.....or are we.....
![]() |
|
#5
|
||||
|
||||
|
Re: To share or not to share
One would hope you're building a robot and strategy that can win whether or not everyone knows about it.
![]() I personally like to see other teams' robots coming together, and hope to show off at least some of our build season progress this year, too. good luck! |
|
#6
|
||||
|
||||
|
Re: To share or not to share
Strictly speaking, there reaches a point in the season where the risk of another team stealing your idea becomes a bit of a non-issue, as it's a bit too late for other teams to successfully change track to copy you.
It's a team specific quandry, but if nothing else I wouldn't worry about sharing ideas once you're about three weeks in. At that point, only the most skilled teams will be in a position to really take your idea and you'll still have a chance to get interesting suggestions and/or feedback. -$0.02 |
|
#7
|
||||
|
||||
|
Re: To share or not to share
Quote:
But yet, I'd still rather not have other teams seeing too much about our ideas so early. Every team is going to feel differently about secrecy, ranging from posting CADs nightly of their robot to banning taking pictures for personal use due to fear of leakage. It's about what you're comfortable with. |
|
#8
|
||||
|
||||
|
Re: To share or not to share
I agree with everything that has been said. While our team, to our knowledge, isn't going to be all happy-go-lucky this-is-exactly-what-we-did in our sharing, we're still going to share the general thought process and give some insight. Then, there's also the traditional teaser pictures week 4ish or so.
Primarily, FIRST isn't a competition. It's a learning experience. Share the knowledge, and you'll learn more because there's bound to be someone who sees something about your project that even your own team didn't realize it can do. It's happened before to us. |
|
#9
|
|||||
|
|||||
|
Re: To share or not to share
We're usually pretty open about our build with frequent updates on our Photobucket albums.
|
|
#10
|
||||
|
||||
|
Re: To share or not to share
Thanks It looks like we are going to share. We will have something up in a day or so
|
|
#11
|
||||
|
||||
|
Re: To share or not to share
I can't wait to see what you guys have come up with!!
|
|
#12
|
|||||
|
|||||
|
Re: To share or not to share
When it comes down to it, if the thing your team is "showing" will have a significantly greater advantage at you winning regionals/champs then I personally wouldn't show it. If it were to be other miniscule things then I wouldn't have a problem. However, disclosure of such things would take me awhile before it either becomes deemed as miniscule or highly competitive.
![]() |
|
#13
|
|||||
|
|||||
|
Re: To share or not to share
I like to be surprised by different robot configurations and strategies.
I don't want to show up and see 7 clones of the same robot that got put up early in build at a regional, like in 2008 when there were Rhode Warrior clones all over. I also don't want to get beat by someone who executes my design better than I do, which is why we didn't bring our minibot to Suffield Shakedown last year, it was to easy to duplicate so we didn't show it until WPI week 2. However given the current witholding allowance/COTS rules I can probably replicate any good robot design I see and assemble it at an event anyway. In any event we keep our robot generally secret from the public until Suffield Shakedown the Saturday before ship and I encourage you to do the same. I want to be surprised by creativity not bored by a bunch of group think communally designed robots. |
|
#14
|
|||
|
|||
|
Re: To share or not to share
Coopertition, right? You want to help the new people. I'd recommend not putting up the design for the whole robot, but if you see someone's been having problems with something, go ahead and show them how you did it. That's how my team is doing it.
|
|
#15
|
||||
|
||||
|
Re: To share or not to share
I think being open is an awesome thing, as long as you're actually open and not giving us useless "teaser" photos of gears, sprocket, wheels, etc. People want to see pictures of something important if your going to share something. I think a great team to emulate in that fact is 842.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|