|Version 7 (modified by rjollos, 21 months ago) (diff)|
Site Upgrade Proposal
This page documents the proposed work for upgrading trac-hacks.org from 0.10.6dev to 0.12.3 or 1.0.
- Many plugins don't have a license. An idea outlined in #9805 is to force the user to either specify a license or accept a default license when creating a NewHack.
- Spam continues to be a problem. Upgrading to the t:SpamFilter might improve the issue, but captcha used there can be frustrating experience and we don't want to risk driving away users.
- A related issue is that many tickets are created by anonymous and anonymous often does not follow-up when more information or feedback is requested. We could require users to create an account before they can create a ticket, which might cut down on newticket spam as well as these abandoned tickets.
- There are a number projects that are no longer maintained, have been supplanted by another project and are just taking up space at this point.
- We should have a process for removing old projects. Perhaps we should have a policy of reviewing and voting on them, a notification should be placed on the page and then a prescribed waiting period elapsed before eventually deleting them. Obsolete plugins with no license would have even more reason to be deleted (see also #9805).
- Projects that have no source, often because the links to an external site are dead, are being tagged with tag:nosource.
On several occasions questions have come up about proper use of the site and how it should be administered. This suggests we need more site policies, and the philosophy of trac-hacks suggests that these policies be formed by the community.
- LicensingPolicies page that describes the proper way to document the license for a plugin.
- Page that describes proper promotion and what types of external links are allowed, similar to t:TracUsers#guidelines.
- Hosting the #trac IRC logs using the IrcLogsPlugin (mailing list discussion).
- Hosting a pastebin using the TracPastePlugin (mailing list discussion).
- Tools to facilitate code reviews, such as the CodeReviewerPlugin.