Serendipity Forums

Could any of you give exact advice, how we should handle *end of live* plugins - which should get removed, IMO. How will sourceforge and furthermore spartacus handle this?

I would - for example - like to *declare* the fckeditor plugin (totally unusable by now) and the xinha plugin as not available and remove them from lists (now!). There are always users trying to install such plugins, just because they are there and not being removed.

I remember we also had others ...
http://board.s9y.org/viewtopic.php?f=4& ... #p10427778
http://board.s9y.org/viewtopic.php?f=11&t=18228

Hi!

In our spartaucs SF.Net repository, it is not possible to delete directories. We can however delete files there.

To remove a plugin, we need to first remove it in github, and then also seperately in CVS on the SF.Net servers.

About the FCKEditor, I was still hoping of someone contributing to patch it up. For Xinha, I think it did add some options that are not in our core so that a use for that plugin could be there.

Regards,
Garvin

Yes I know, but is it adviced to remove obsolet plugins from github. What happens with the sync...?
[btw, sf has git too!]

garvinhicking wrote:About the FCKEditor, I was still hoping of someone contributing to patch it up. For Xinha, I think it did add some options that are not in our core so that a use for that plugin could be there.

Really? The Plugin (Spartacus online) itelf says: Warung: XINGHA ist experimentell! Es wird mindestens Serendipity Version 0.9 benätigt. Nach der Installation sollte die Installationsanleitung im Konfigurationsfenster dieses Plugins gelesen werden. Ab Version 1.4 ist XINHA standardmäßig in S9Y enthalten. Dieses Plugin wird dafür nicht mehr benötigt., while http://spartacus.s9y.org does not have the last.

What do you mean with patch FCK..? This plugin comes with a download URL, which is not any longer available and supported, since they completely changed to CKE. The latter is the one I am currently writing on and this will be a new Serendipity Plugin soon.

Totally out of context, but didn't we at some point discuss hosting spartacus on GitHub and getting rid of SF.net altogether? Or was that not possible because of bandwidth considerations?

YL

yellowled wrote:Totally out of context, ..

Pssst! You might get re-moved quicker than you can think off..!

Hi!

Hm, I think it could be worthwile to leave the xinha plugin in, in case it gets updated in the future and before putting it in the core we want to check it out via a plugin. Also it's a good demo experience on how to integrate a WYSIWYG editor. Same applies to fckeditor; wouldn't it be good to be able for some interested person to improve the plugin? I see no real benefit in removing the plugin if it still has some inspection value and can be used for improvements...

Regards,
Garvin

Well, the point is, it is just a plugin without any content happening. You need to download the content manually, which does not exist any more in the official download pages. How do you think it should or could get improved?
So IMO this plugin is obsolet and will be replaced by the new plugin event_ckeditor.

Timbalu wrote:Well, the point is, it is just a plugin without any content happening. You need to download the content manually, which does not exist any more in the official download pages. How do you think it should or could get improved?
So IMO this plugin is obsolet and will be replaced by the new plugin event_ckeditor.

But the FCKEditor is available on http://sourceforge.net/projects/fckeditor/ ... ?!?

Anyhow. Once ckeditor is up and running well for a few weeks, I agree, we can remove fckeditor.

Regards,
Garvin

Oh yeah, true..., but

https://github.com/s9y/additional_plugi ... nc.php#L13
points to http://www.fckeditor.net/, which gets redirected to http://ckeditor.com/ and in there you can't find any older downloads of fckeditor. This is quite understandable, since CKEditor is the new development of the (very) old fckeditor, not being supported & developed any more (same as xinha btw *).

Ok, maybe we should just note this somewhere and change the manual download url to sf.net.

(*) oh well, the sourceforge one still gets updates..