9

In the end, an open source project is just a bunch of humans, and where there are humans there isn't always harmony. This is a social problem, it is not specific to open source, and there is nothing particular about open source that would help avoid this. However, open source has an escape hatch: any open source license allows you to fork the project. You ...


8

You need all the copyright owners' permission to change license. There's no natural GPL-implied path here because LGPL is more permissive. It allows redistribution of unmodified binaries without the offer of source, explicitly disallowed by GPL. This makes it moderately incompatible in this direction (but you could include LGPL in a GPL work). So in order to ...


6

Deb Nicholson gave an excellent talk at FOSDEM 2017 called "Handle conflict like a boss". I wrote the whole talk up for LWN, and the original talk is likely available on the FOSDEM servers somewhere, but some points I found important included Conflict happens because some people are missing some information She showed a slide with a sign from a local "...


5

You should try to use and offer the communication channels where your target audience - user and developers - resides. This might be the same channels, different ones, or there may be a certain overlap. You do not want to force any of them to use one particular channel, especially if they don't like it. But you do not want to force yourself to use an ...


4

Step 1: document the situation. Put up a notice that explains the problem; but be clear, not alarmist. As discussed on other questions, there's no problem for users of your plugin, only for people who would want to distribute a combined work of your plugin and the host. Step 2: Survey the contributions of the unreachable individuals. Perhaps they are very ...


4

Like, do I have the right to do that? And, is this change legal? I think that anyone who downloaded it with the then open source license is allowed to keep what they downloaded under that license (and can continue to redistribute it according to that license). Assuming you retained your own copyright in your software (as well as publishing it with an open ...


3

IRC is a multi server protocol in that you can use multiple servers to run one IRC network, consider it like load balancing. So as to why the majority of projects are on there is not a question with a simple defined answer. First of all, there are other IRC networks which host projects too, OFTC being the other big one. Why are the majority on Freenode? ...


2

You are allowed to stop offering the source code at any time, though people who have received a copy of the source code already may choose to exercise their right to distribute the code under the terms of the Apache 2 license. The Apache 2 license is explicitly irrevocable so you cannot take away license grants already made to existing recipients. I think ...


2

The method of communication is not relevant. If you don't modify the GPLv2 program, and your proprietary program is developed independently from the GPLv2 program, there is no derivation work, so you can use the GPLv2 program without restrictions. If you modify the GPLv2 program, things are grey. On both side you will have to code the communication part, ...


2

If all you want is a mailing list, you could use FreeLists which specifically states that it is not just free as in beer. They use ecartis as a mailing list manager and not Mailman which you might be familiar with, but they are both free as in freedom.


2

(Q-1) Is Fig.2 the same as Fig.1 in this respect after all? Yes. There is no significant difference between Fig.2 and Fig.1 with regards to determining if they are considered a single combined program or not. (Q-2) Is IPC/shared memory page to purely exchange data counts? It lacks one of function calls AND share data structures, only sharing data ...


1

According to the GPL, you can distribute GPL programs together with closed source programs as long as the programs are separate. The GPL calls such a collection an "aggregate": A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as ...


1

This is primary a personal decision. I would see this more in the software recommendation section. Anyway, on newer projects I would suggest to use modern communications. One way can still be IRC or Mailinglists, but anyway I don't use them often. Even if I'm active in an project. They always had something from the 80th's fro me. If you use Github, you ...


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