[Geany-devel] Restructuring the Geany-plugins project?

[Enrico Tröger]

On Wed, 10 Jun 2009 11:56:42 +0200, Frank wrote:

>On Wed, 10 Jun 2009 04:34:08 +0800
>Chow Loong Jin <hyperair at gmail.com> wrote:
>
>> On Sun, 2009-06-07 at 19:07 +0200, Enrico Tröger wrote:
>> > Sounds quite good so far and wouldn't require much more than a 'svn
>> > mkdir other' :).
>> > 
>> > But still the problem what I'm afraid of is that we end up in a
>> > mix of various plugins, plugin releases and users might get
>> > confused where which plugin is how developed and by whom.
>> > OTOH while thinking about, this is already partly the case as it
>> > will be always with independent plugins especially when a plugin
>> > author doesn't use the geany-plugins Sourceforge project and
>> > instead use some other place for hosting.
>> > So, my worries about that are maybe exaggerated. Perhaps it's
>> > enough when we try to keep update to date with the index page at
>> > http://plugins.geany.org and http://www.geany.org/Support/Plugins
>> > as a some kind of reference list of known plugins.
>> > 
>> I'm all for this. So, which plugin developers (and the plugins they
>> develop) are in favour of this move exactly? Perhaps we could have
>> some sort of page on the website documenting this?
>
>I'm afraid I'm not 100% sure which point you are referring here to?
>Having a including-all-plugins-list-on-homepage or the general
>refactoring of svn and geany-pugins release?

Assuming we are talking about the homepage:
I'd say we either create an overview page for the common plugins,
similar to what is now at http://plugins.geany.org/ but instead of
linking to each plugin's own webpage, provide one page with sections
for each included plugin and some common notes about installation,
downloads and such.

Alternatively, we could redirect http://plugins.geany.org to
http://www.geany.org/Support/Plugins and update it accordingly.

I don't mind much how we go in that matter but I'd like to delay this a
bit until the technical (SVN layout changes, proper build system and
code changes) are done or at least basically done.


Regards,
Enrico

-- 
Get my GPG key from http://www.uvena.de/pub.asc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.geany.org/pipermail/devel/attachments/20090610/3e5bc24f/attachment.pgp>