Tag Info

Hot answers tagged

5

Placing your software on Github makes it visible to other developers who would like to help. But when you are looking for users, you need to go where your users are. So unless your users are other developers, Github is not the right website to attract them. Define your target audience, find out which websites they meet on, and announce your project there.


5

The FSF answer this question themselves: Can the US Government release improvements to a GPL-covered program? Yes. If the improvements are written by US government employees in the course of their employment, then the improvements are in the public domain. However, the improved version, as a whole, is still covered by the GNU GPL. There is no ...


4

Integration work is boring, repetitive and never-ending. It takes huge amounts of resources to validate your code works with all the versions of your collaborators that you don't have installed. To do it properly, you need environments with each of them installed (or at least easily reproducable). This requires a lot of machines and a lot of work managing ...


2

The basic idea behind open-source licensing is that anyone who has (legally) obtained a copy of the source code also has the right to make modifications and the right to distribute the modified or original work. The main difference between open-source licenses is in what rights you must give away when re-distributing the work. With one or two exceptions, ...


1

Generally speaking, you should not be modifying the source code files of third party code unless they're the type of changes for which it would make sense to contribute them back upstream (e.g. bug fixes). Obviously, there are exceptional situations where you may wish to go ahead and modify those files anyway, but you usually want to avoid forking the ...



Only top voted, non community-wiki answers of a minimum length are eligible