[TYPO3-typo3org] extensions dissapearing from TER2

Daniel Bruessler info at -remove-patchworking.de
Sat Oct 14 20:29:42 CEST 2006


isn't everything stored in the TER2 an extension-metadata-dataset and
stored as simple file in the filesystem? Sorry, that I don't know it
better and asking yet. Please tell me more about it ;-)

I see that all docs have the path "*/documentation/*", articles have
"/articles/*" and news-items have their subdomain - what I find very good.

>From the wiki it's no problem to link to

But problems are when one wants to set a link from the wiki to an
extension, because there's no "/current/". Linking to an exact
version-number in a documentation-doc is a bad style.

Is it a problem to add this feature? For the moment I use the
"workaround" to link to the searchbox using the right search-keyword Bo)

By the way: when the dashboard-"applications" do exist and should be
available via TER2, they should also be "something". They must relate to
extensions, because they mostly will use extensions, but maybe they'll
need more meta-data in the TER2 than an extension normally needs.

kind regards
Daniel Brüßler

Michael Scharkow schrieb:
> Dmitry Dulepov wrote:
>> Michael, you are talkig like a developer who does not care about users
>> but about one "nice" feature :)
> Actually, I do care about users and that's the *reason* documentation
> does only pop up in *one* place, that's /documentation/
>> May be it is a feature but as soon as it is inconvinient for people,
>> this is a good reason to revise such feature.
> If somebody comes up with a real problem, that's fine with me. But
> please consider that if we open ter_fe for docs only because of some
> mis-categorization of extension XYZ, we will clutter the ter_fe with
> lots of extensions that extend nothing, have no actual code, cannot
> seriously be rated etc. pp. That's a lot of drawbacks for which I am not
> willing to take the blame.
>> Well, this is what many people mean about usability in open source
>> projects: it is defined by developers who think differently than users :)
> Again, I think that given that categories work, having docs only in
> /documentation is what 99,9 % of all people expect, as they don't care
> how it is stored or processed on typo3.org.
>> Decision, which is known only to selected group of people. I heard it
>> for the first time right now, for example. How many other people are
>> unaware of the decision that impacts them? :)
> A decision that was not made nor even endorsed by me. In fact, I still
> think treating documentation as extensions is not-such-a-good idea.
> Cheers,
> Michael

More information about the TYPO3-team-typo3org mailing list