search

frc461 / rowdy-15

This is the code for Rowdy 15, our robot for the 2013-2014 season.
0 stars 0 forks source link

Public? #2

Closed cg505 closed 9 years ago

cg505 commented 10 years ago

Given that we're in offseason now, is there any reason to keep this private?

Sammidysam commented 10 years ago

Yes. Off-season competitions exist.

samontea commented 10 years ago

Well more yes, off season competitions that still matter exist. See IRI. I think we can be all public for CAGE.

Sammidysam commented 10 years ago

It's probably safer just to stay private until the robot is retired from actual competition.

rye commented 10 years ago

234 released their code, why can't we? It's not like releasing our code to the public is going to lose us competitions.

Sammidysam commented 10 years ago

I'm pretty indifferent, but maybe an argument against releasing it publicly is that other teams could use it as reference, and thus be better than without. The chances of this are really unlikely, though.

rye commented 10 years ago

Especially since we've got two and a half weeks between now and the competition.

// Kristofer "four04" Rye kristofer.rye@gmail.com

On Sun, Jun 29, 2014 at 7:31 PM, Sam Craig notifications@github.com wrote:

I'm pretty indifferent, but maybe an argument against releasing it publicly is that other teams could use it as reference, and thus be better than without. The chances of this are really unlikely, though.

— Reply to this email directly or view it on GitHub https://github.com/frc461/rowdy-15/issues/2#issuecomment-47483090.

rye commented 10 years ago

They wouldn't get invited to IRI if they needed other people's help that much, pretty sure.

// Kristofer "four04" Rye kristofer.rye@gmail.com

On Sun, Jun 29, 2014 at 7:32 PM, Kristofer Rye kristofer.rye@gmail.com wrote:

Especially since we've got two and a half weeks between now and the competition.

// Kristofer "four04" Rye kristofer.rye@gmail.com

On Sun, Jun 29, 2014 at 7:31 PM, Sam Craig notifications@github.com wrote:

I'm pretty indifferent, but maybe an argument against releasing it publicly is that other teams could use it as reference, and thus be better than without. The chances of this are really unlikely, though.

— Reply to this email directly or view it on GitHub https://github.com/frc461/rowdy-15/issues/2#issuecomment-47483090.

braddoeswebdev commented 10 years ago

I agree with keeping it private until it's done with competitions. There's that thing Sam just said, the fact that it can reveal strategic information that we may not necessarily want to reveal to the public, ... It might not be the end of the world in this particular case, but as a matter of policy robot code should be kept private until we're done competing with it. What do we gain by releasing it earlier?

cg505 commented 10 years ago

We look good. "other teams could use it as reference, and thus be better than without" (@Sammidysam). This is a good thing! We flaunt our open source approach, and this is because we want to help other teams. Coopertition®, man.

braddoeswebdev commented 10 years ago

Why not make the robot code public from the start then? Or after the real season is over? I'm not terribly opposed to either of those in theory, but I'm not sure the rest of the team would be too happy about it (think 2 ball auton scenario).

Those good vibes will still come our way in 2 weeks.

Sammidysam commented 10 years ago

We should bring this up for discussion at the next meeting. We should not only decide among ourselves.

braddoeswebdev commented 10 years ago

Agreed.

rye commented 10 years ago

If we get the same turnout that we got last week, we probably won't have much feedback at all. Still a good idea to open it up, though.

// Kristofer "four04" Rye kristofer.rye@gmail.com

On Sun, Jun 29, 2014 at 8:42 PM, Brad Thompson notifications@github.com wrote:

Agreed.

— Reply to this email directly or view it on GitHub https://github.com/frc461/rowdy-15/issues/2#issuecomment-47486687.

samontea commented 10 years ago

@cg505 the socialist in my 100% agrees with you, and realistically it won't matter that much... That being said ask people. I was just perpetuating the status quo and restating our last specifications for when we will open source. That being said my morals are completely anti that so... you know.

@Sammidysam I'm sorry, but I don't think many people outside of us will really care. Considering the attendance at the meetings we will still be a majority of the people who care. That all taken into consideration if we can get a super majority I see no problem with open sourcing it.

Also Karma man. :moneybag: :moneybag: :money_with_wings: :money_with_wings: :moneybag: :moneybag:

:shipit:

So do we want to just vote?

rye commented 9 years ago

I'd say the code could be open-sourced now. Besides CAGE, there's not much opportunity for someone to rip this off.

The codebase should definitely be cleaned up and prepared for release before then, though. There're .d and .o files floating around that should probably be removed, and commented code that will no longer be used should be completely removed.

rye commented 9 years ago

Besides, if a team is already going to CAGE, they're probably not going to steal our stuff. We didn't have any unique things either--it's not like we actually wrote anything for vision.

cg505 commented 9 years ago

At this point it doesn't matter what the team thinks really, and we can ask them for this upcoming year. (Can we develop Rowdy 16 open source?)

Also, @rye, what are you still doing here?

samontea commented 9 years ago

I like the idea of Rowdy 15 being open source.

rye commented 9 years ago

I'm not leaving this organization, that's what I'm doing. If you kick me out, that's okay, but I see no reason to not do anything, considering the copious amounts of free time I have. Our team had a meeting yesterday, and it has been reaffirmed that I basically get to code the entire robot for next year by myself.

For open-sourcing stuff, we should definitely clean stuff up before we actually release. We need to comment stuff very vigorously, remove unnecessary (.d, .o) files, and document stuff.

cg505 commented 9 years ago

Okay surely we can do it now.

Sammidysam commented 9 years ago

Yeah go ahead.

-Sam, sent on his iPod. You should be proud of him; typing on that thing is hard.

On Feb 16, 2015, at 5:06 PM, cg505 notifications@github.com wrote:

Okay surely we can do it now.

— Reply to this email directly or view it on GitHub.

rye commented 9 years ago

Since this hasn't been done yet, shall I do it for you guys?

Sammidysam commented 9 years ago

If you want.

On Feb 17, 2015, at 12:36 PM, Kristofer Rye notifications@github.com wrote:

Since this hasn't been done yet, shall I do it for you guys?

— Reply to this email directly or view it on GitHub.

rye commented 9 years ago

Okay. I will do this shortly.

rye commented 9 years ago

Actually, no, since I'm perceived as a threat (I guess?) and am not on the "Owners" team. That's nice.

Sammidysam commented 9 years ago

Oh lol. Thanks for offering though.

-Sam, sent on his iPod. You should be proud of him; typing on that thing is hard.

On Feb 17, 2015, at 1:16 PM, Kristofer Rye notifications@github.com wrote:

Actually, no, since I'm perceived as a threat (I guess?) and am not on the "Owners" team. That's nice.

— Reply to this email directly or view it on GitHub.

braddoeswebdev commented 9 years ago

Try again.

Brad Thompson West Lafayette Jr/Sr High School CIT Teacher, Systems Analyst, Web Developer, & Linux Administrator FRC Team 461 Assistant Coach & Website/Programming Mentor ZERO Robotics Sponsor FLL Team Coach WL Athletics Video/Tech Specialist Phone: 765-746-0400 http://apps.wl.k12.in.us/u/~thompsonb/

On Tue, Feb 17, 2015 at 1:16 PM, Kristofer Rye notifications@github.com wrote:

Actually, no, since I'm perceived as a threat (I guess?) and am not on the "Owners" team. That's nice.

— Reply to this email directly or view it on GitHub https://github.com/frc461/rowdy-15/issues/2#issuecomment-74720061.

rye commented 9 years ago

There we go. Closing this issue due to irrelevance (it's now public; no need to question publicness)