Opened 17 years ago
Closed 17 years ago
#4316 closed task (worksforme)
Provide a Component "framework" within trac.edgewall.org
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | project | Version: | none |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
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)
Attachments (0)
Change History (8)
follow-ups: 2 3 comment:1 by , 17 years ago
comment:2 by , 17 years ago
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.
follow-up: 8 comment:3 by , 17 years ago
comment:4 by , 17 years ago
| Summary: | Provide a Component "core" within trac.edgewall.org → Provide a Component "framework" within trac.edgewall.org |
|---|
comment:5 by , 17 years ago
| Owner: | removed |
|---|
follow-up: 7 comment:6 by , 17 years ago
| Owner: | set to |
|---|
comment:7 by , 17 years ago
| Owner: | removed |
|---|
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.
comment:8 by , 17 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
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.
There are two acceptions for Trac core:
projectandspamfilter) describes some particular subsystem of Trac core in this acception,trac.core, i.e. what implements the TracDev/ComponentArchitecture, we use thegeneralcomponent, as we usually do with the various modules residing in thetracfolder (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
attachmentsshould become components first.