You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Is the standard/community plugin split (H-RFC-1/2) still active?
#1870
While building a plugin for my fork, I noticed a few gaps between H-RFC-1/H-RFC-2 and current reality:
Export and Informative are still in core, despite H-RFC-1 proposing removal.
GeosuiteExport was flagged for community-plugin conversion but is still bundled in core; vtsearch just disappeared rather than following the proposed migration path.
The "waiting room" fork under hajkmap never materialized.
Also worth flagging: the client's plugin loader (import.meta.glob over src/plugins/) can't load anything outside the source tree at build time. So even a "community" plugin has no real decoupled distribution — everyone still copies the source into their own fork and rebuilds, standard or not.
Is this split still considered active guidance? Curious whether there's appetite to revisit the plugins above, or to make "community" status mean something more concrete in practice.
Thanks @jacobwod / @Hallbergs for the original write-up — trying to figure out where a small OSM-search plugin I built should live before I go further.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
While building a plugin for my fork, I noticed a few gaps between H-RFC-1/H-RFC-2 and current reality:
ExportandInformativeare still in core, despite H-RFC-1 proposing removal.GeosuiteExportwas flagged for community-plugin conversion but is still bundled in core;vtsearchjust disappeared rather than following the proposed migration path.hajkmapnever materialized.Also worth flagging: the client's plugin loader (
import.meta.globoversrc/plugins/) can't load anything outside the source tree at build time. So even a "community" plugin has no real decoupled distribution — everyone still copies the source into their own fork and rebuilds, standard or not.Is this split still considered active guidance? Curious whether there's appetite to revisit the plugins above, or to make "community" status mean something more concrete in practice.
Thanks @jacobwod / @Hallbergs for the original write-up — trying to figure out where a small OSM-search plugin I built should live before I go further.
All reactions