We like to keep the Trac website fresh, clean and up to date. Furthermore, it helps in attracting new developers. Finally, the mechanism could be extended to local Trac installs, so that very large programmes relying on Trac for their tickets and milestones could be kept equally clean and inviting. This would obviously help in cross-team communication and onboarding new hires.
On Monday, 21 December 2015 07:04:40 UTC, F@lk wrote: > > Hi, > Generally a good idea, but why that effort? What is it worth for? Your > spent time should have a good cost-value ratio. :-) > CU, F...@lk <javascript:> > > Am Mittwoch, 16. Dezember 2015 03:06:00 UTC+1 schrieb figaro: > >> I am looking for feedback on the following proposal for the Trac website. >> The proposal regards a list of links to pages that require cleanup. The >> resulting page could be integrated in HowToContribute or TracDev/ToDo#Wiki >> >> >> Site maintenance >> >> The following is a list of pages that help in maintaining the Trac site. >> Maintaining the site involves routine cleanup of wiki pages, so that the >> site's content remains consistent and fresh. The pages that need to be >> maintained are not marked as 'deprecated' or 'pending-deletion'. The same >> site maintenance guidelines and links can be added to your Trac >> installation. >> >> Dusty pages: pages which have not been edited in at least 5 years usually >> require a cleanup or can be marked for deletion. See RecentChanges. >> >> Pages with obsolete macros: there are some obsolete macros still >> circulating in the wiki, such as TagIt[[()]], and they need to be removed >> from the page. >> >> Images: a list of all images on the Trac installation is useful for the >> following purposes: >> - if a list of the wiki pages or ticket pages that they are used in is >> provided also, then obsolete (ie unused) or duplicate images can be more >> easily detected. >> - if thumbnails are automatically generated also, then detection of >> irrelevant images: someone may have uploaded an image in the past that is >> irrelevent to the use or development of Trac. >> - jpgs may have been used, where png or svg is the norm. >> >> Attachments: a list of all attachments on the Trac installation is useful >> for the following purposes: >> - if a list of the wiki pages or ticket pages that they are used in is >> provided also, then obsolete (ie unused) or duplicate attachments can be >> more easily detected. >> - someone may have uploaded an attachment in the past that is irrelevant >> to the use or development of Trac. >> >> Acronyms: misused or accidental acronyms where spelling them out would >> make the text clearer: from db to database, from regex to regular >> expression, from " to ". >> >> Short pages: pages with little text are usually the result of a test or >> have been abandoned and are therefore candidates for deletion. >> >> Dead links: dead links in the wiki show up as grey links if they are >> internal links and need to be corrected or removed. Dead links to external >> sites have no special highlighting, but still require correction or removal. >> >> Protected pages: pages that are read-only may need to have their status >> reviewed. >> >> Pages without table of contents: pages should have either >> `[[TracGuideToc]]` or `[[PageOutline(2-5,Contents,pullout)]]` in them for >> navigational purposes. >> >> Undocumented Python objects: functions and classes in Python that do not >> have any code comments. >> >> -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
