Skip to content
This repository has been archived by the owner on Oct 27, 2020. It is now read-only.

Contribution Guidelines #120

Closed
lukeboi opened this issue Jan 12, 2016 · 10 comments
Closed

Contribution Guidelines #120

lukeboi opened this issue Jan 12, 2016 · 10 comments

Comments

@lukeboi
Copy link

lukeboi commented Jan 12, 2016

As you may know, there are many seasoned programmers (including me) who would like to help make this SDK better. This cannot be done without some basic contribution guidelines. FIRST, please leave an official opinion on this issue.

@magneticflux-
Copy link

@lukethecoder64 So far they have been hostile to contributions. The main code base is obfuscated, and they have numerous posts saying that it is not possible to release source code due to various copyright/licensing issues.

Relavant Issues:
#11
#97

@lukeboi
Copy link
Author

lukeboi commented Jan 12, 2016

I am well aware of the source hogging. However, contributions can still be made. If they are against community help, could they say so in the readme?

@YoshiRulz
Copy link

As this is a symptom of the underlying licensing problems, perhaps the new software and driving systems should be based entirely off open source code? That goes without saying, many veteran teams' software departments would be more than happy to contribute, check for flaws/exploits, maybe run test matches etc.

@magneticflux-
Copy link

@YoshiRulz I highly doubt that they will scrap all current progress on the system. What they have currently is incredibly complex and was a huge undertaking to create. It seems more likely that they will try to press through the licensing issues.

@xyzzycoder
Copy link

I think that they should have gone with Arduino.

Aron

On Jan 12, 2016, at 3:12 PM, Mitchell Skaggs notifications@github.com wrote:

@YoshiRulz https://github.com/YoshiRulz I highly doubt that they will scrap all current progress on the system. What they have currently is incredibly complex and was a huge undertaking to create. It seems more likely that they will try to press through the licensing issues.


Reply to this email directly or view it on GitHub #120 (comment).

@lukeboi
Copy link
Author

lukeboi commented Jan 13, 2016

I absolutely agree they should have gone with arduino, @xyzzycoder. However back to the OP: FIRST, please follow GitHub etiquette and have contribution guidelines.

@PranavMathur
Copy link

@lukethecoder64 I'm not sure whether or not FIRST will agree to having a set of contributor guidelines, but I wholeheartedly agree with the sentiment that they should follow proper git style. Commits should not be made only for major releases, and there should be frequent commits with descriptive messages. Pull requests should also be considered, as some contain code that is useful to every team.

@lukeboi
Copy link
Author

lukeboi commented Jan 30, 2016

Sigh
Oh well. I guess I will ask on the forums.

P.S. Does anyone else find it weird that FTC will not address issues related to open source, such as this one?

@Ernest314
Copy link

Not much I can add that hasn't been said before... It really is very frustrating how cryptic FIRST is being.

@cmacfarl
Copy link
Collaborator

Contribution guidelines are at .github/CONTRIBUTING.md. Further discussion on this topic would likely be better addressed over on the forums where there are a wider variety of FIRST staffers and volunteers participating.

sahithi-thumuluri pushed a commit to 6150FTC/Main-19-20-FTC6150 that referenced this issue Apr 4, 2019
moved code to universal audi from audi angle
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants