qertspark.blogg.se - Frostwire download for macs

#FROSTWIRE DOWNLOAD FOR MACS FOR ANDROID#
#FROSTWIRE DOWNLOAD FOR MACS ANDROID#
#FROSTWIRE DOWNLOAD FOR MACS CODE#

We'll code review you, maybe ask you for some more changes, and after we've tested it we'll merge your changes.

Adding (issue #233) to the commit message or in PR comments automatically references them on the issue tracker.

Submit a pull request that's as descriptive as possible.

If you can add tests to demonstrate the issue and the fix, even better.

Code, Commit, Push, Code, Commit, Push, until the feature is fully implemented.

Got lost or added in the middle of hundreds of lines that got shifted. Noise, we are a very small team and we can't waste too much time reviewing if something Good patches will be rejected if there's too much code formatting

Focus on your patch, do not waste time re-formatting code too much as it makes it hard.

If you don't know what to name it and there's an issue created for it, name your branch issue-233 (where 233 would be the number of the issue you're fixing).

Make sure the name of your feature branch describes what you're trying to fix.

Create a branch with a descriptive name of the issue you are solving.

Git remote add your_github_username_here Please follow the following procedure when creating features to avoid unnecessary rejections:ĭo this the first time (Cloning & Forking): If you want to fix a new issue that's not listed there, create the issue, see if If you want to contribute code, start by looking at the open issues on. We prefer well named methods and code re-usability than a lot of comments.Look and test your code well before submitting patches. If it's too hard to explain what you're doing, you're probably making things more complex than they already are. When you submit a pull request try to explain what issue you're fixing in detail and how you're fixing in detail it so it's easier for us to read your patches.If you can include tests for your pull request you get extra bonus points ) We'll review your code and will only merge it to the master branch if it doesn't break the build. All pull requests should come from a feature branch created on your git fork.Try to follow our coding style and formatting before submitting a patch.If you want to help, the Issue tracker is a good place to take a look at.It'll be faster to code, and easier to maintain. ( DRY) Re-use your own code and our code. Coding Guidelinesĥ Object Oriented Programming Principles learned during the last 15 years These repositories will no longer be used. In the past these sources were held at frostwire-android,įrostwire-desktop and frostwire-common respectively.

#FROSTWIRE DOWNLOAD FOR MACS ANDROID#

/common Common sources for the desktop and android client./desktop Sources for FrostWire for Desktop (Windows, Mac, Linux).

#FROSTWIRE DOWNLOAD FOR MACS FOR ANDROID#

/android Sources for FrostWire for Android.

Here you will find the sources necessary to build FrostWire for Android and FrostWire for Desktop Welcome to the main FrostWire repository.