Changes between Version 10 and Version 11 of TracIdeas
- Timestamp:
- Jan 11, 2015, 3:30:04 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracIdeas
v10 v11 3 3 Organized by topics, this is a new //free for all// discussion area in the Trac wiki. Typically, these pages should collect **short**, **precise** and **actionable** items, a bit like a giant structured !TODO list. 4 4 5 If you notice typos in the code, a glitch in the CSS, an annoying behavior ...but don't feel this is worth creating a ticket, then this is the place!5 If you notice typos in the code, a glitch in the CSS, an annoying behavior, but don't feel this is worth creating a ticket, then this is the place! 6 6 7 7 - [./DefaultTheme] -- all things about the CSS and the default layout 8 8 - [./TracAttachments] -- how to improve the attachments feature 9 9 - [./TracBrowser] -- how to improve the Trac source browser 10 - [./TracChangeset] -- ...the changeset view, diffs, etc.10 - [./TracChangeset] -- how to improve the changeset view, diffs, etc. 11 11 - [./TracTickets] -- ideas for the single ticket view and edit 12 - [./TracQuery] -- ideas for the custom query view, batch edit, TicketQuery macro ...12 - [./TracQuery] -- ideas for the custom query view, batch edit, TicketQuery macro, etc. 13 13 - [./TracWiki] -- ideas for the Wiki, WikiFormatting, TracLinks 14 14 - [./TracSearch] -- ideas for improving the search … … 17 17 \\\\ 18 18 ---- 19 Note: //the TracDev/ScratchPad pages are similar in intent insuch that they try to address sub-systems as a whole instead of focusing on a particular issue like we usually do in a single ticket, but they are more **developer** oriented. They are better used for discussing technicalities, how to refactor the code for greater flexibility or performance, or write API proposals, etc.//19 Note: //the TracDev/ScratchPad pages are similar in such that they try to address sub-systems as a whole instead of focusing on a particular issue like we usually do in a single ticket, but they are more **developer** oriented. They are better used for discussing technicalities, how to refactor the code for greater flexibility or performance, or write API proposals, etc.// 20 20 21 //By contrast, the present !TracIdeas/ pages are really meant to collect constructive feedback **from the users** (or from the developers with their user hat on!)//21 //By contrast, the present !TracIdeas/ pages are meant to collect constructive feedback **from the users** or from the developers with their user hat on!//
