Quote:
Originally Posted by mgrouch
It seems even for small things which can be part of OpenCPN people write separate plugins.
NMEA debugger, Current plugins for different areas, NMEA converters, etc
At the end it just increases maintenance for everyone.
Just brainstorming…
Thanks
|
Can you define "everyone", please? OpenCPN core devs have zero maintanence
work with the plugins, which I consider to be a good thing.
I, as author of (or contributor to) quite a few plugins, do not see any difference in fixing the functionality of plugins out of OpenCPN core or in it, but I certainly like having the flexibility of being able to release them whenever I (or the maintainer) want or need instead of having to wait and coordinate for the next OpenCPN release.
I, as a frequent contributor to the OpenCPN core, do not want to deal with users expecting me or anybody else in similar position to address local issues with stuff like changes to individual tide API endpoints (As you probably know I am also the maintainer of the worldwide freely downloadable chart catalog data, which suffers the same volatility, for years, so I believe I am kind of qualified to have an oppinion here.)
The plugin system exists to make the plugin development feasible, that's it's purpose. If you consider some plugin is so universally beneficial that it should be included in the core application, simply submit a pull request doing it. If it makes sense it will be accepted as it was with WMM and the chart downloader in the past.
Pavel