Comments (3)
My sentiment there is that it shouldn't be supported (aka not included on main repo, nor receiving support about it in dev channels) unless the dev behind the fork respected some guidelines, as :
- The plugin must have been abandoned for X months OR
- The original developer accepted the fork to take over the spot of the new current existing version of the plugin OR
- The original developer explicitely asked for someone to take over the project indefinitely
In addition to these, if they submit it to replace the original plugin on main repo :
- The plugin must follow main repo guidelines (and abide by the general rules of the main repo)
- The fork developer abides by the guidelines (if they exist) that the original developer may have laid down
- The fork developer may not add a ko-fee/patreon/monetization thing in it without the consent of the original developer
I will, of course, have forgotten some edge cases, but most of them should be within this territory, feel free to add anything about it that I have covered yet
from faq.
I somewhat disagree with Khayle's opinion.
Personally, I don't think there's hard in helping someone make a personal fork of a plugin provided their fork would also match our plugin guidelines. Otherwise, we'd effectively be locking users out from contributing to the plugins they enjoy.
Ideally, plugin forks should be treated and expected to be upstreamed in most cases, unless the developer/maintainer has already made a clear stance on not accepting outside help. (But that kinda defeats the purpose of FOSS and may need to be discussed separately).
In terms of forks as user should:
- Fork the code
- Make their personal dev branch[es]
- Compile and test as a devPlugin
- Push their changes to their repo
- If it's something that they think could/should/would be upstreamed, make a PR
We have multiple plugins that can do some of the same things. (Owofy vs SillyChat is an easy example). I feel like forks of maintained plugins could in same cases be treated similarly, but further discussion on how to best separate "personal fork" from "fork and rebrand" may be needed.
In the event that the plugin in question is no longer being maintained, that's an entirely different topic and should be directed to discussion on incompatible plugins that @kalilistic has been working on.
from faq.
I think we should allow for a scenario where someone makes significant changes to an existing plugin to the point it has novel features.
This will help bring healthy variety to our plugins and gives users more choice. For example, I haven't touched Price check in awhile. If someone came out with a new version with more display options and polish that would be okay to me. If they added one option and renamed it - that would not be.
from faq.
Related Issues (20)
- How do I arrange my SamplePlugin and configure my Dev Plugin Locations to load my plugin without using DevPlugins? HOT 1
- How do I actually use DalamudPackager to package up my plugin? HOT 1
- Is there somewhere I can look at ImGui elements easily?
- What's the cool [Signature] annotation everyone's using? HOT 1
- Why should I contribute the findings of my own reverse engineering to Dalamud/ClientStructs?
- Where do I find all of the events I can subscribe to?
- Adjust wording on ClientStructs FAQ to deprioritise bundling your own
- Why do we use dependency injection instead of singletons?
- Reorganisation of existing FAQ entries HOT 1
- Include a link to the log location
- What is the object table? How do I find all the entities on-screen? HOT 1
- What are the specifications for plugin icons? HOT 2
- What is the best way to handle configuration migration? HOT 4
- How do I interact with the game's UI?
- Optimised settings for attaching the debugger in VS
- "Discover Store" Is an unexplained thing in the FAQ (Moved from FFXIVQuickLauncher #1156) HOT 1
- How do I import *.fea hotbar/settings backups from the official client? HOT 3
- update available services in plugin dev section
- Error in migration path in the xl_troubleshooting faq
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from faq.