-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Contribution Guidelines #120
Comments
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? |
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. |
@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. |
I think that they should have gone with Arduino. Aron
|
I absolutely agree they should have gone with arduino, @xyzzycoder. However back to the OP: FIRST, please follow GitHub etiquette and have contribution guidelines. |
@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. |
Sigh P.S. Does anyone else find it weird that FTC will not address issues related to open source, such as this one? |
Not much I can add that hasn't been said before... It really is very frustrating how cryptic FIRST is being. |
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. |
moved code to universal audi from audi angle
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.
The text was updated successfully, but these errors were encountered: