Tags:
create new tag
, view all tags

Archived Discussion for PluginsInSubversion

Discussions

This is a strategic move that will simplify the Plugins maintenance.

Crawford, could you elaborate on "DakarRelease has a different, more extensive plugins API"? Are there any incompatibilities that would prevent existing Plugins that play nice to run properly under Dakar?

-- PeterThoeny - 24 Jul 2005

Thanks for reminding me, Peter. The interested reader is referred to DakarReleaseNotes, where the changes to the Plugins API are described.

-- CrawfordCurrie - 24 Jul 2005

Well, I can activate and deactivate plugins from within configure now, but how do I actually 'install' them from their latest svn source? - Hm, maybe a stupid question.

-- FranzJosefSilli - 25 Jul 2005

the idea was that you wounldn't have to, but there are one or two technical issues that we are still trying to resolve (the topics, templates and pub data)

  • Oh, I see. Good luck with this. smile - FJ
-- SvenDowideit - 26 Jul 2005

Franz, short-term, working within an SVN checkout tree, you can use the mklinks.sh script to link the plugins into the core using softlinks.

-- CrawfordCurrie - 27 Jul 2005

First, Can we come to a common point where all plugins in svn are the latest versions published. Right now, some are imported from cvs, some are drawn from twiki.org. Most probably, those published on twiki.org are more recent. They should be imported into svn no matter if they are ready for dakar or not.

Second, can the svn activities on a plugin be notified to its Dev topic automatically.

Third, what's the process of keeping svn and twiki.org plugin sources in sync. Is there any endeavor in keeping them in sync?

-- MichaelDaum - 02 Aug 2005

What's the mechanism to maintain both the Cairo and Dakar version of a plugin? Maintain the Cairo version in CVS and Dakar (and future) version in SVN?

-- RafaelAlvarez - 02 Aug 2005

My advise would be for you guys to develop a suggested strategy here, I'm swamped, and the net access at WikiMania is going to get less useable as more people get here over the week. Similarly, Crawford is unavailable for the next week smile

-- SvenDowideit - 02 Aug 2005

Anyone know whether there exists an alternative to using mklinks.sh? e.g. by setting a path?

WordPress very simply allows plugin installation to be separate to enablement. TWiki could find everything on the path and offer checkboxes as to whether to enable them.

-- MartinCleaver - 02 Aug 2005

That's what configure does (the checkbox stuff), the problem is with the template, pub and data dir that need to be "physically" present in the instalation.

The last version of mklinks.sh has an option to copy the files instead of creating the symlink.

-- RafaelAlvarez - 03 Aug 2005

How does the unsuspecting, but inpatient TWiki admin get to the plugins svn? I'd like to update some plugins to 4.0.2 but can't find a link...

-- JosMaccabiani - 13 Apr 2006

With

svn co http://64.38.10.58:8181/svn/twiki/branches/TWikiRelease04x00
you will get the whole tree including plugins. Use
svn co http://64.38.10.58:8181/svn/twiki/branches/DEVELOP
for the latest development code.

-- ArthurClemens - 13 Apr 2006

It should be mentioned that plugins are primarily developed in TWikiRelease04x00. While the two branches were 100% in sync around ~9200 (with regards to plugins), most plugin development is now done in TWikiRelease04x00 only.

In other words: Avoid doing plugin work in DEVELOP branch - unless your plugin is DEVELOP (Edinburgh) specific.

-- SteffenPoulsen - 14 Apr 2006

Ah, that explains why I don't get the latest plugins when doing a simple svn up on my DEVELOP based install.

-- FranzJosefSilli - 14 Apr 2006

I would like to point out that the two-branch Plugins dev model has been introduced without consensus. And against the wish of the developer who wrote the largest number of Plugins. I see a lot of issues with the multi-branch approach:

  • Confusion where to develop (some use DEVELOP, some use TWikiRelease04x00, some use Plugins web)
  • Promotes a developer centric "one Plugin for each release" view, with "click here to download for Cairo, here for Dakar" message to user
    • Compare that with a user centric "download this Plugin and it will work in your TWiki" view
  • Suggests that divergence and Plugins API changes are OK, e.g. planning for incompatibilities (that hurt the TWiki project)

Moved to HandlingCairoDakarPluginDifferences

-- PeterThoeny - 14 Apr 2006

So in the mean time Steffen published his updated plugins on twiki.org, so my search for the correct svn folder is over for now (glad to see that it wasn't just me who was confused ;). And thank you ScottHoge for the excellent support through e-mail!

-- JosMaccabiani - 15 Apr 2006

See discussions on moving back to a SingleBranchPluginDevelopment model.

-- PeterThoeny - 30 Apr 2006

Topic revision: r1 - 2006-05-13 - RafaelAlvarez
 
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.