Provide a Component "framework" within trac.edgewall.org

[ilias@…]

The Trac Core is an essential part of the trac sources, thus a dedicated component (core) should be provided, to simplify filing issues against core.

some more infom within thread:

​PROJECT - Decoupling Core (Framework) from Trac (Application)

[cboos]

There are two acceptions for Trac core:

• When we talk about "Trac core" vs. "plugins", as in "should this be part of Trac core or as a plugin?": this describes the whole Trac and therefore the components (excluding project and spamfilter) describes some particular subsystem of Trac core in this acception,
• When we say "Trac core" for talking about the Python module trac.core, i.e. what implements the TracDev/ComponentArchitecture, we use the general component, as we usually do with the various modules residing in the trac folder (config, attachment, db_default, etc. see source:trunk/trac).

There are many subsystems that don't currently have their own component entry, see TracTicketTriage#Keywords "wannabee components".

Some of them could eventually be promoted to "real" components one day, including "core" but currently they are not that many tickets tagged like that (core), so probably others like attachments should become components first.

[ilias@…]

Replying to cboos:

There are two acceptions for Trac core:

• When we talk about "Trac core" vs. "plugins", as in "should this be part of Trac

I understand your elaborations subjecting the name.

the call it 'framework', which would be more concise.

It an essential component, which has of course some priority compared to other 'wannabees'.

Component 'framework' is not a 'wannbee' - It's an essential one, and it's missing.

[ilias@…]

Replying to cboos:
...

Some of them could eventually be promoted to "real" components one day, including "core" but currently they are not that many tickets tagged like that (core),

...

I file them them "CORE" in the subject, others possibly just as Component 'general'.

[ilias@…]

Replying to mgood:

based on which documentation do you change the owner?

'jonas' has obviously not the time to deal with this issue.

I doubt that he's even noticed the existence of it.

Freeing the issue, thus another person which can make the decision can claim it.

[cboos]

Replying to ilias@lazaridis.com:

Replying to cboos:
...

Some of them could eventually be promoted to "real" components one day, including "core" but currently they are not that many tickets tagged like that (core),

...

I file them them "CORE" in the subject, others possibly just as Component 'general'.

Exactly, component general should be used for this.