From steffen at steffen-gebert.de Sun Nov 1 15:32:08 2009 From: steffen at steffen-gebert.de (Steffen Gebert) Date: Sun, 01 Nov 2009 15:32:08 +0100 Subject: [TYPO3-ect] Owner of key "colorbox" Message-ID: Hi! colorbox [1] is a easy customizable jQuery-based Lightbox implementation. I'm currently working on a TYPO3 port of this library. Unfortunately sb. else has registered the EXT key "colorbox". Can you tell me, who's the owner or ask him, if he's still planning to release the extension? Otherwise it would be great, if he could transfer the key to me. Thanks Steffen [1] http://colorpowered.com/colorbox/ From steffen at steffen-gebert.de Sat Nov 21 17:35:32 2009 From: steffen at steffen-gebert.de (Steffen Gebert) Date: Sat, 21 Nov 2009 17:35:32 +0100 Subject: [TYPO3-ect] Owner of key "colorbox" References: Message-ID: Am 01.11.2009, 15:32 Uhr, schrieb Steffen Gebert : > Hi! > > colorbox [1] is a easy customizable jQuery-based Lightbox implementation. > I'm currently working on a TYPO3 port of this library. > > Unfortunately sb. else has registered the EXT key "colorbox". > > Can you tell me, who's the owner or ask him, if he's still planning to > release the extension? > > Otherwise it would be great, if he could transfer the key to me. > > Thanks > Steffen > > [1] http://colorpowered.com/colorbox/ Is anybody willing to help me, please? Thanks Steffen From snf at dkm.dk Sun Nov 22 15:55:24 2009 From: snf at dkm.dk (=?ISO-8859-15?Q?Stig_N=F8rgaard_F=E6rch?=) Date: Sun, 22 Nov 2009 15:55:24 +0100 Subject: [TYPO3-ect] Owner of key "colorbox" In-Reply-To: References:

Message-ID: Steffen Gebert skrev: > Am 01.11.2009, 15:32 Uhr, schrieb Steffen Gebert > : > >> Hi! >> >> colorbox [1] is a easy customizable jQuery-based Lightbox implementation. >> I'm currently working on a TYPO3 port of this library. >> >> Unfortunately sb. else has registered the EXT key "colorbox". >> >> Can you tell me, who's the owner or ask him, if he's still planning to >> release the extension? >> >> Otherwise it would be great, if he could transfer the key to me. >> >> Thanks >> Steffen >> >> [1] http://colorpowered.com/colorbox/ > > Is anybody willing to help me, please? Maybe the persons who could help doesn't read this group? /Stig From sebastian.gebhard at gmail.com Tue Nov 24 10:48:08 2009 From: sebastian.gebhard at gmail.com (Sebastian Gebhard) Date: Tue, 24 Nov 2009 10:48:08 +0100 Subject: [TYPO3-ect] Owner of key "colorbox" In-Reply-To: References: Message-ID: Steffen Gebert schrieb: I think it would be helpful if you could get this info from typo3.org. I think an open source community needs transparency. You don't have to implement a whole new WHOIS-Interface, but "Sorry, the extension key you have chosen already exists. Just try another one." could be easily extended to somethink like "Sorry, the extension key you have chosen already exists. Just try another one or get in contact with the key owner Sebastian Gebhard". What do you think? Any concerns regarding privacy? From steffen at steffen-gebert.de Tue Nov 24 11:51:45 2009 From: steffen at steffen-gebert.de (Steffen Gebert) Date: Tue, 24 Nov 2009 11:51:45 +0100 Subject: [TYPO3-ect] Owner of key "colorbox" References:

Message-ID: Am 24.11.2009, 10:48 Uhr, schrieb Sebastian Gebhard : > Steffen Gebert schrieb: > I think it would be helpful if you could get this info from typo3.org. I > think an open source community needs transparency. > You don't have to implement a whole new WHOIS-Interface, but > > "Sorry, the extension key you have chosen already exists. Just try > another one." > > could be easily extended to somethink like > > "Sorry, the extension key you have chosen already exists. Just try > another one or get in contact with the key owner mailto="...">Sebastian Gebhard". > > What do you think? Any concerns regarding privacy? May be it could be an anonymous contact form. Steffen P.S: Are you the owner of colorbox? :D From sebastian.gebhard at gmail.com Tue Nov 24 14:11:59 2009 From: sebastian.gebhard at gmail.com (Sebastian Gebhard) Date: Tue, 24 Nov 2009 14:11:59 +0100 Subject: [TYPO3-ect] Owner of key "colorbox" In-Reply-To: References:

Message-ID: > May be it could be an anonymous contact form. > > Steffen > > P.S: Are you the owner of colorbox? :D Sorry, no :D I used my name just as an example. From news at ringerge.org Tue Nov 24 14:41:11 2009 From: news at ringerge.org (Georg Ringer) Date: Tue, 24 Nov 2009 14:41:11 +0100 Subject: [TYPO3-ect] Remove obsolete extensions from TER Message-ID: Hi, This is a request to remove all extensions from TER which got the status "obsolete" because of the following reasons: * Probably the extensions won't be supported by the author * There is no need for the extension because either it won't work or functionality is in a different extension or even the core. * A bit cleaner TER And 2 important reasons concerning the security team which I am a member of. * Chances are high that those extensions got some holes * Less work for the security team because of extensions which are hardly used anyway This could be IMO also a part of the Collective Security Bulletin (CSB) to announce the extensions which are not longer are supported. What is your opinion? Georg From sebastian.gebhard at gmail.com Tue Nov 24 14:50:14 2009 From: sebastian.gebhard at gmail.com (Sebastian Gebhard) Date: Tue, 24 Nov 2009 14:50:14 +0100 Subject: [TYPO3-ect] Remove obsolete extensions from TER In-Reply-To: References: Message-ID: 95% agree. But obsolete does not neccessarily mean that an extension is totally crap. E.g. I wrote an extension that creates ARP-Classes for Database tables[1], which is kind of a model object. With the release of 4.3 i might set my extension to obsolete because i recommend using extbase instead. However i'd still maintain it with minor bug fixes and security fixes if needed for those who use it with 4.2. This is just one example. Of course a huge part of the obsolete extensions will never be useful anymore, but it might be wrong to remove all. [1] http://typo3.org/extensions/repository/view/createarp/current/ From news at ringerge.org Tue Nov 24 14:55:28 2009 From: news at ringerge.org (Georg Ringer) Date: Tue, 24 Nov 2009 14:55:28 +0100 Subject: [TYPO3-ect] Remove obsolete extensions from TER In-Reply-To: References:

Message-ID: Sebastian Gebhard schrieb: > However i'd still maintain it with minor bug fixes and security > fixes if needed for those who use it with 4.2. So it is not obsolete because still used in 4.2! Just because rgsmoothgallery doesn't work with latest t3mootools / mootools it doesn't mean that this extension is obsolete. This would also be a nice way as an author to let an extension be removed from ter: Waiting for the next csb and it is gone. Currently there is no way for that Georg From typo3 at rvt.dds.nl Tue Nov 24 15:05:34 2009 From: typo3 at rvt.dds.nl (Ries van Twisk) Date: Tue, 24 Nov 2009 09:05:34 -0500 Subject: [TYPO3-ect] Remove obsolete extensions from TER In-Reply-To: References: Message-ID: On Nov 24, 2009, at 8:41 AM, Georg Ringer wrote: > Hi, > > This is a request to remove all extensions from TER which got the > status > "obsolete" because of the following reasons: > > * Probably the extensions won't be supported by the author > * There is no need for the extension because either it won't work or > functionality is in a different extension or even the core. > * A bit cleaner TER > > And 2 important reasons concerning the security team which I am a > member of. > > * Chances are high that those extensions got some holes > * Less work for the security team because of extensions which are > hardly > used anyway > > > This could be IMO also a part of the Collective Security Bulletin > (CSB) > to announce the extensions which are not longer are supported. > > What is your opinion? Notify the extension owner prior to removal, if you don't get a response in let's say 4 weeks, then remove the extension. If you get a response then may be he has a good reason to keep it, or he will say 'throw away'. But it sounds polite to me if we notify the owner of an extension.... Ries > > Georg regards, Ries van Twisk - Join us on #TYPO3 on freenode | irc://chat.freenode.net/#typo3 ------------------------------------------------------------------------------------------------- tags: Freelance TYPO3 Glassfish JasperReports JasperETL Flex Blaze-DS WebORB PostgreSQL DB-Architect email: ries at vantwisk.nl web: http://www.rvantwisk.nl/ skype: callto://r.vantwisk From hagelstein at shr.cc Tue Nov 24 15:09:05 2009 From: hagelstein at shr.cc (Nikolas Hagelstein) Date: Tue, 24 Nov 2009 15:09:05 +0100 Subject: [TYPO3-ect] Remove obsolete extensions from TER References:

Message-ID: Hi there, > Notify the extension owner prior to removal, > if you don't get a response in let's say 4 weeks, then > remove the extension. > > If you get a response then may be he has a good reason to keep it, or > he will say 'throw away'. > But it sounds polite to me if we notify the owner of an extension.... +1 :). BTW: i you are about to notify owner of obsolete extensions, what about notifying those who own extensions that haven't been update for a certain time period. Especially those containing xclasses are likely to be obsolete even if not marked ;). Cheers, Nikolas From jigal at alternet.nl Tue Nov 24 15:31:34 2009 From: jigal at alternet.nl (Jigal van Hemert | alterNET internet BV) Date: Tue, 24 Nov 2009 15:31:34 +0100 Subject: [TYPO3-ect] Remove obsolete extensions from TER In-Reply-To: References:

Message-ID: Hi Nikolas, 2009/11/24 Nikolas Hagelstein > what about > notifying those who own extensions that haven't been update for a > certain time period. > So, you want to remove for example feuser_admin? It's stable, has a security check, but hasn't been updated since 2002... The reason is quite simple: it's almost entirely a configuration of fe_adminLib (which is part of the core). Sorry, but this will lead to all kinds of strange situations (until recently automaketemplate was also not updated for many years, but it was in the top 10 most downloaded extension list). -- Regards, Jigal. From hagelstein at shr.cc Tue Nov 24 15:38:48 2009 From: hagelstein at shr.cc (Nikolas Hagelstein) Date: Tue, 24 Nov 2009 15:38:48 +0100 Subject: [TYPO3-ect] Remove obsolete extensions from TER References:

Message-ID: Hi Jigal, you got me wrong. I was saying "notify the owner of outdated extensions" as well. Not delete them silently. And except for a few ones most extension switch haven't been updated for quite a while are either obsolete or broken (Especially those containing xclasses - as already mentioned). So there nothing to be said against kindly notifying the owner and asking for further processing. Cheers, Nikolas > -----Original Message----- > From: typo3-team-extension-coordination-bounces at lists.typo3.org > [mailto:typo3-team-extension-coordination-bounces at lists.typo3.org] On > Behalf Of Jigal van Hemert | alterNET internet BV > Sent: Tuesday, November 24, 2009 3:32 PM > To: TYPO3 extension coordination team > Subject: Re: [TYPO3-ect] Remove obsolete extensions from TER > > Hi Nikolas, > > 2009/11/24 Nikolas Hagelstein > > > what about > > notifying those who own extensions that haven't been update for a > > certain time period. > > > > So, you want to remove for example feuser_admin? It's stable, has a > security check, but hasn't been updated since 2002... The reason is > quite > simple: it's almost entirely a configuration of fe_adminLib (which is > part > of the core). > > Sorry, but this will lead to all kinds of strange situations (until > recently > automaketemplate was also not updated for many years, but it was in the > top > 10 most downloaded extension list). > > -- > > Regards, Jigal. > _______________________________________________ > TYPO3-team-extension-coordination mailing list > TYPO3-team-extension-coordination at lists.typo3.org > http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-team-extension- > coordination From franz at ttproducts.de Tue Nov 24 18:03:04 2009 From: franz at ttproducts.de (Franz Holzinger) Date: Tue, 24 Nov 2009 18:03:04 +0100 Subject: [TYPO3-ect] Remove obsolete extensions from TER In-Reply-To: References: Message-ID: Georg Ringer a ?crit : > Hi, > > This is a request to remove all extensions from TER which got the status > "obsolete" because of the following reasons: > > * Probably the extensions won't be supported by the author > * There is no need for the extension because either it won't work or > functionality is in a different extension or even the core. > * A bit cleaner TER > > And 2 important reasons concerning the security team which I am a member of. > > * Chances are high that those extensions got some holes > * Less work for the security team because of extensions which are hardly > used anyway > > > This could be IMO also a part of the Collective Security Bulletin (CSB) > to announce the extensions which are not longer are supported. > > What is your opinion? -1 Some obsolete extensions are needed by other extensions. 'obsolete' means only that users should upgrade. Nobody should force them to upgrade. - Franz From mail at ringerge.org Tue Nov 24 18:12:20 2009 From: mail at ringerge.org (Georg Ringer) Date: Tue, 24 Nov 2009 18:12:20 +0100 Subject: [TYPO3-ect] Remove obsolete extensions from TER In-Reply-To: References:

Message-ID: Franz Holzinger schrieb: > -1 > Some obsolete extensions are needed by other extensions. 'obsolete' > means only that users should upgrade. Nobody should force them to upgrade. > > - Franz nobody is forced! nobody says that those exts are unsecure but they just not maintained, otherwise they wouldn't be obsolete georg From braulio at solsoft.co.cr Tue Nov 24 20:32:09 2009 From: braulio at solsoft.co.cr (Braulio =?iso-8859-1?Q?Jos=E9_Solano_Rojas?=) Date: Tue, 24 Nov 2009 13:32:09 -0600 (CST) Subject: [TYPO3-ect] Remove obsolete extensions from TER In-Reply-To: References:

Message-ID: On Tue, 24 de Noviembre de 2009, 7:50 am, Sebastian Gebhard wrote: > > But obsolete does not neccessarily mean that an extension is totally crap. > E.g. I wrote an extension > that creates ARP-Classes for Database tables[1], which is kind of a model > object. With the release > of 4.3 i might set my extension to obsolete because i recommend using > extbase instead. However i'd > still maintain it with minor bug fixes and security fixes if needed for > those who use it with 4.2. IMHO, since your extension is not obsolete, maybe, you should unmark your extension as obsolete and add a comment in the description saying that the extension is deprecated in favor of extbase. Best regards, B. From marcus#exp2009 at t3sec.info Sat Nov 28 01:22:52 2009 From: marcus#exp2009 at t3sec.info (Marcus Krause) Date: Sat, 28 Nov 2009 01:22:52 +0100 Subject: [TYPO3-ect] Owner of key "colorbox" In-Reply-To: References: Message-ID: Steffen Gebert schrieb am 11/01/2009 03:32 PM Uhr: > Hi! > > colorbox [1] is a easy customizable jQuery-based Lightbox implementation. > I'm currently working on a TYPO3 port of this library. > > Unfortunately sb. else has registered the EXT key "colorbox". > > Can you tell me, who's the owner or ask him, if he's still planning to > release the extension? I'll take care of it and will try to establish communication between you and the ext key owner. Marcus. -- TYPO3 Security blog: http://secure.t3sec.info/ From steffen at steffen-gebert.de Sat Nov 28 09:25:48 2009 From: steffen at steffen-gebert.de (Steffen Gebert) Date: Sat, 28 Nov 2009 09:25:48 +0100 Subject: [TYPO3-ect] Owner of key "colorbox" References:

Message-ID: Am 28.11.2009, 01:22 Uhr, schrieb Marcus Krause : > Steffen Gebert schrieb am 11/01/2009 03:32 PM Uhr: >> Hi! >> >> colorbox [1] is a easy customizable jQuery-based Lightbox >> implementation. >> I'm currently working on a TYPO3 port of this library. >> >> Unfortunately sb. else has registered the EXT key "colorbox". >> >> Can you tell me, who's the owner or ask him, if he's still planning to >> release the extension? > > I'll take care of it and will try to establish communication between you > and the ext key owner. Thanks, I already wrote a mail to Sebastian yesterday, but got no answer, yet. Steffen