I consider use discourse in my future website (thanks for making the great software). In case I make some modifications (not necessarily as a plugin), does that require my modifications be GPL ? the modification is only for my website. I’m aware GPL only applies to distribution. However, software…

[이미지] hbm: In case I make some modifications (not necessarily as a plugin), does that require my modifications be GPL ? Everyone who has done that has been very sorry. You want to make your modifications in plugins and themes. You can use plugins and themes that are not publicly distributed. …

Thanks. How about the case if developer makes a larger web application with discourse being part of it, e.g., a social media app with a forum component use discourse differently from a typical forum app, e.g., use it as a comment section for an article. will the full app be mandated to use GPL. …

Jay’s point was not a legal one I suspect. You want to retain the ability to one-click upgrade and redeploy Discourse from scratch. All technical modifications should be plugins or theme components. There is an existing API, SSO, Oauth, webhook support and you always have the discretion to host t…

Well keep in mind say with your social Media App you could have a plugin to facilitate connecting to your Discourse Forum. There are already a variety of plugins created to use things like: Facebook Authentication Steam WeChat And more. Problem with modifying/forking is you end up with potentia…

My response was a technical one. Unless you plan to have a team of several people who are doing nothing but merging new changes, you’ll want to develop plugins to solve your problem. Your legal concerns are then moot.

I’m not sure it’s material either way. The fundamental issue will be that you fork Discourse we can’t offer any support whatsoever. The only supported means of extensibility are plugins, themes and using the hooks in the container yml. There’s no limit to what they will allow you to achieve, forkin…

Thank you all for inputs. I found this article with a good discussion. The client side code should be GPLed, but not the server side.

I think you might be missing the point? If you create a plugin on GitHub and place it in a Private Repo, you have full control over modifying Discourse (albeit with plugin approach) and have full ownership and control over those changes. No-one else will see them and you don’t need to fear any leg…

Robert might be better to give him links to Discourse highly customized setups to improve his understanding and/or some of the more powerful plugins & themes.

자체 웹사이트용 수정된 Discourse의 GPL 라이선스

개발

pfaffman (Jay Pfaffman) 3월 22, 2020, 4:51오후 2

그렇게 해본 사람들은 모두 후회했습니다. 수정 사항은 플러그인과 테마에서 수행해야 합니다.

공개적으로 배포되지 않는 플러그인과 테마를 사용할 수 있습니다.

글		댓글	조회수
Why GNU License? Development	45	19656	3월 18, 2019
A question on GPL licensing and the current WordPress debacle General	15	10364	11월 19, 2022
Does the use of private plugins breach the terms of the GNU GPL v2? Support	18	6520	6월 23, 2017
Are paid plugins with undisclosed license allowed to exist on meta? Site feedback	28	4836	8월 30, 2017
Question about GNU license General	1	908	11월 16, 2022

자체 웹사이트용 수정된 Discourse의 GPL 라이선스

Related topics