Tweet Like [Mandatory] PFC-Developers and the GPL

Not open for further replies.


Staff member

Hello Everyone,


So what does this mean for the average user?


If you are a developer what does this mean for you?

It doesn't matter if you are creating a whole rom or just the kernel, the process of being GPL compliant is a very simple one to explain. Basically, we expect you to either link the source that you have chosen to use or upload the source you have created into a format that can be viewed by everyone and anyone. Below are the 3 most common situations that developers run into when needing to stay GPL compliant under PFC rules.

1. If you are using a stock kernel you MUST mention where you obtained your source. Also, having a link leading to where the manufacturer has uploaded their source is always helpful.


3. If you are forking a repository that is similar to the examples listed above in #2, you MUST publish and link your entire kernel source. This includes any and all changes that you have made. Two of the most common ways developers publish their source on PFC is either with Gerrit, or GitHub. While these two methods are recommended, they are not the only routes you can choose to accomplish this. All that is required is that the source can be viewed and downloaded by anyone who wishes to do so. When releasing an update, your repository must be updated the moment you release your kernel on PFC. If you can post your update to PFC, there should be no reason as to why you cannot release your source.


In a perfect world this would not happen but unfortunately, this is not the case. Pulser-G2 recently wrote a portal article explaining a certain situation that has come across our desks.

Not open for further replies.
Help Users

You haven't joined any rooms.

    You haven't joined any rooms.