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
Serendipity Composer Update | Uniify plugins in core and additional_plugins #821
I believe the reasoning at some point was to "bundle" important plugins with our core release. The better way would've been to do this via on-release bundling - which we weren't able to do "back in the days". Also I think we did some things with the plugins that affected their core compatibility, but I'm not sure of this.
A problem is that when we now move plugins outside of the core, they'll not get deleted when people update.
So maybe the best course of action is to "just" synchronize the affected plugins?
The ideal way of course would be to make plugins be composer packages, migrate the core to use composer for plugins too, and then create a proper release architecture.... I did some initial work for a composer move (see the git branch), but I can't do it alone and need some motivation (&time). 🥹
@stevleibelt That would be terriffic, and might get me involved somehow. It's just so much that I'm seeing a steep hill I'd have to climb alone. Serendipity has a very small userbase and I'm just not sure there is "public demand" for that. But the task at hand would be a cool one, and we'd all learn a lot from it. So... if there are volunteers (LIKE YOU? :-)) then please do get in touch.
I'm still on the s9y.slack.com, but the more transparently public we can communicate this, the better.
changed the title [-]Duplicate plugins in Serendipity/additional_plugins[/-][+]Serendipity Composer Update | Uniify plugins in core and additional_plugins[/+]on Feb 21, 2024
I synced serendipity_event_gravatar in s9y/additional_plugins@640af83. Interestingly enough it was backwards: The gravatar version in the s9y repo was the newer one and contained two commits of fixes. Backwards, because the plugin is in the two repos to have it 1) as a bundled plugin and 2) to still be able to update it without a s9y release. Seems like that wasn't all that useful, if it was never used.
Maybe we remove those four plugins from spartacus instead and only keep them in the core? It was probably a misjudgement to think that we need the capability to upgrade them without a release, they are stable enough.
Oh, this is solved! In s9y/additional_plugins#176 we removed the spartacus plugins, only the core versions (synced) remain. Thank you @surrim for triggering this!
Activity
stevleibelt commentedon Feb 15, 2024
Just for the four eyes principle, @surrim is right. All mentioned plugins are available in additional_plugins and plugins.
garvinhicking commentedon Feb 15, 2024
I believe the reasoning at some point was to "bundle" important plugins with our core release. The better way would've been to do this via on-release bundling - which we weren't able to do "back in the days". Also I think we did some things with the plugins that affected their core compatibility, but I'm not sure of this.
A problem is that when we now move plugins outside of the core, they'll not get deleted when people update.
So maybe the best course of action is to "just" synchronize the affected plugins?
The ideal way of course would be to make plugins be composer packages, migrate the core to use composer for plugins too, and then create a proper release architecture.... I did some initial work for a composer move (see the git branch), but I can't do it alone and need some motivation (&time). 🥹
stevleibelt commentedon Feb 16, 2024
@garvinhicking Is there a list or "howto"-Section you can point volunteers to support you on the composer task?
garvinhicking commentedon Feb 16, 2024
@stevleibelt That would be terriffic, and might get me involved somehow. It's just so much that I'm seeing a steep hill I'd have to climb alone. Serendipity has a very small userbase and I'm just not sure there is "public demand" for that. But the task at hand would be a cool one, and we'd all learn a lot from it. So... if there are volunteers (LIKE YOU? :-)) then please do get in touch.
I'm still on the s9y.slack.com, but the more transparently public we can communicate this, the better.
I've just updated https://github.com/s9y/Serendipity/blob/feature/composer/README.markdown#concept again to add some thoughts...
( @onli )
onli commentedon Feb 19, 2024
@garvinhicking Just to make sure you have seen it, @mmitch also volunteered to help at https://www.onli-blogging.de/2323/comments.html#c10436
[-]Duplicate plugins in Serendipity/additional_plugins[/-][+]Serendipity Composer Update | Uniify plugins in core and additional_plugins[/+]onli commentedon Feb 1, 2025
I synced serendipity_event_gravatar in s9y/additional_plugins@640af83. Interestingly enough it was backwards: The gravatar version in the s9y repo was the newer one and contained two commits of fixes. Backwards, because the plugin is in the two repos to have it 1) as a bundled plugin and 2) to still be able to update it without a s9y release. Seems like that wasn't all that useful, if it was never used.
Maybe we remove those four plugins from spartacus instead and only keep them in the core? It was probably a misjudgement to think that we need the capability to upgrade them without a release, they are stable enough.
onli commentedon Jun 30, 2025
Oh, this is solved! In s9y/additional_plugins#176 we removed the spartacus plugins, only the core versions (synced) remain. Thank you @surrim for triggering this!