1000 and 1 extension

[Jonas Dübi-2]

Hi everybody

Most people agree with me, that there are to many Extensions in TER
which are not maintained and are not ment for wide use in the community.

Extensions which are often just for one project useful.

I am really carefully with publishing extensions, just because I don't
want to publish extensions which are not community ready. An extension
without nice documentation, or without flexible enough documentation is
not usefully to the masses...

I would like to use the TER for our extensions to update them on the
projects we use them, but I would like to hide them.

Another question would be if there is kind of a private function in TER,
it does not have to be secured, but just not shown by default. Or if
there is a possibility to make a own TER?

Is the TER backend source available to built up a TER Proxy?

Best regards
Jonas

_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

[Franz Holzinger-2]

Jonas Dübi a écrit :

> Another question would be if there is kind of a private function in TER,
> it does not have to be secured, but just not shown by default. Or if
> there is a possibility to make a own TER?

AFAIK this feature has been removed.

If the failure on typo3.org to manage the extension keys has been fixed,
then everybody will be able to assign his extension keys to somebody
else. Maybe a reminder shall be sent automatically one year after the
latest upload into TER, that the extension owner should look for other
persons. He should have the right to claim the extension key back later
again under some conditions.

> Is the TER backend source available to built up a TER Proxy?

Maybe this one:

     TYPO3 Extension Repository
Extension key ( ter ) by Robert Lemke

- Franz
_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

[Feodor Rykhtik]

Hi Jonas,

It's true that sometimes there is some many extension when we are make
basic request querry, in the same time sometimes even not-documented
extensions could help in development. I propose to hide them from
default search, but to have possibility to find all the extensions
through Advanced search. In this case when an extension is publishied
- it's not visible through Basic search, but after the validation of
TER Manager, extension could be directly visible.

Regards,
Feo

> Most people agree with me, that there are to many Extensions in TER
> which are not maintained and are not ment for wide use in the community.
> ...
> I would like to use the TER for our extensions to update them on the
> projects we use them, but I would like to hide them.
>
> Best regards
> Jonas
_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

[Jonas Dübi-2]

Hi Freo

The framework for that already exists with the extension review process,
the problem is that there are to many extensions to review. I did my
self some reviews and it needs a lot of time, and you have to review
every version.

Also sometimes you need extensions which won't get a review, because of
missing things.

I think a checkbox 'community ready' which could be checked for the
whole extension and not for every version would help alot.

Best regards,
Jonas

Feodor Rykhtik schrieb:

> Hi Jonas,
>
> It's true that sometimes there is some many extension when we are make
> basic request querry, in the same time sometimes even not-documented
> extensions could help in development. I propose to hide them from
> default search, but to have possibility to find all the extensions
> through Advanced search. In this case when an extension is publishied
> - it's not visible through Basic search, but after the validation of
> TER Manager, extension could be directly visible.
>
> Regards,
> Feo
>

_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

[Jonas Dübi-2]

Hi Franz

Thank you for the answer.

I remember that feature now, but I didn't when I was writhing this mail.

I also saw the ter extensions, but with a closer Look at it I saw that
it will be very difficult to implement it as a proxy on an own server.
A sources.list as debian has it would be great for that purpose. This
way you could add your own repository.

The ter extension was not updated since 2006 by the way, does it still work?

Will you be at the swiss TYPO3 conference?

Best regards,
Jonas

Franz Holzinger schrieb:

> Jonas Dübi a écrit :
>
>> Another question would be if there is kind of a private function in
>> TER, it does not have to be secured, but just not shown by default. Or
>> if there is a possibility to make a own TER?
>
> AFAIK this feature has been removed.
>
> If the failure on typo3.org to manage the extension keys has been fixed,
> then everybody will be able to assign his extension keys to somebody
> else. Maybe a reminder shall be sent automatically one year after the
> latest upload into TER, that the extension owner should look for other
> persons. He should have the right to claim the extension key back later
> again under some conditions.
>
>> Is the TER backend source available to built up a TER Proxy?
>
> Maybe this one:
>
>     TYPO3 Extension Repository
> Extension key ( ter ) by Robert Lemke
>
> - Franz

_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination