Trac Component Cleanup
As discussed in yesterday’s meetup, here’s a list of proposed changes to the Components in Trac:
1. Merge Optimization into Performance: they’re basically the same
2. Remove JavaScript: tickets should be moved to specific features, like Menus, Widgets etc.
3. Create Libraries component: tickets dealing with upgrading third party libraries, like jQuery or SimplePie, should go there.
4. Merge TinyMCE into Editor: there should be a single component that deals with the editor as a whole.
Thoughts?
After this is done, I plan to document each component in the Codex, so that we have a clear description of what goes where.
Mr mist 9:54 am on July 23, 2010 Permalink
Megre Export and Import into one?
Dion Hulse 10:16 am on July 23, 2010 Permalink
Some generic terms could also be renamed to fit their purpose, For example, is “HTTP” for HTTP-level responses? Or as it was originally intended as, tickets for the WP_HTTP class, perhaps “WP_HTTP” could be used instead.
Another one, is Upgrade/Install, Originally intended for Automated systems bugs, but now, often includes DB Upgrade issues. The 2 are similar, and so can live together really, but that just goes back to the Generic names sometimes.
scribu 10:21 am on July 23, 2010 Permalink
Perhaps a clearer name would be HTTP API?
Regarding Upgrade/Install, the problem is that the automated upgrade feature involves several other components: HTTP & Filesystem.
Dion Hulse 10:24 am on July 23, 2010 Permalink
Actually, make that 3 types in the HTTP component. WP_HTTP Issues, Outgoing Header issues, and also SSL URL’s, #14360
HTTP API would probably suit more, but not entirely sold on it either.
I agree with the Upgrade/Install though, The problem with some of these is that its entirely possibly to have a bug in the Upgrade, but its due to a bug in HTTP, and same for other areas. Categorizing by ‘Components’ in such interlinked systems is often confusing. I wont go into what it should be though
Ryan McCue 1:01 pm on July 23, 2010 Permalink
+1 for tagging libraries. Being able to see SimplePie issues via a feed would be better than how I currently do it (search, which can have broken feeds). Even better if you could auto-cc me to all SimplePie issues (I’m not sure if that’s possible though).
Alex M. 6:36 pm on July 23, 2010 Permalink
If we had a SimplePie component, it’s easy to auto-assign all tickets to you.
Ryan McCue 9:11 pm on July 23, 2010 Permalink
Even better.