TLC Meeting March 13, 2007

The TLC met by teleconference on March 13, 2007 at 1:00 PM EDT.

Agenda

1. Ticket SPAM on Trac

2. Update on project management guidelines.

3. Update on creation of new project acceptance checklist (see ProjectAcceptanceChecklist).

4. Update on CoinUtils

5. Update on mailing list issues

6. Next step for static Web pages (Google Analytics)

7. Update on standardizing the content and location of README, INSTALL, and AUTHORS files (see StandardizeReadmeInstallAuthors)

8. Installation verification tests

9. Project review and classification

Notes

Meeting attendance was light, so a number of agenda items were skipped.

1. The tickets of several projects have been spammed recently and there is no easy way to delete such SPAM when it occurs. Matt will install a Trac plug-in that will enable PMs to delete individual changes to tickets in order to undo the damage from these attacks. However, we should talk about a longer-range solution at the next TLC meeting.

TracTicketDelete is onstalled. We've taken other measures in the past to control spam, but there are apparently some new spammers out there that the old methods don't detect. I've updated TracSpamFilter to the latest version. --mjs

2. Francois will take a stab at further improvements to the PM guidelines. It was agreed that having a "classification manager" (someone in charge of considering requests to change the classification of a project) is probably needed, as the number of projects is growing. Francois will incorporate this into the guidelines.

3. It was decided that the next step in organizing the mailing lists is to add the ones that are missing (after notifying the affected PMs). Francois will take care of this. Renaming of lists to conform with the previously agreed up on convention (see MailingLists) will require taking down the mail server for a while to set up forwarding. This will be down sometime in April at a time when traffic should be light.

4. Now that PMs have the ability to create static Web pages, the issue of what these Web pages should look like and what they should contain was discussed. There was a concern that if the static pages are not maintained, then they will be less useful than the Trac pages they are replacing. The general consensus was that The static page should contain basic project information, such as the current version, a pointer to the project's Trac site, and other information helpful for new users. Matt agreed to peruse the current project sites and to determine what projects have existing static sites that do not have this information. Ted will create a template similar to the one used by CppAD and create a Trac page for PM "best practices," including things that should be on the project Web site and template files for creating a project static site.

See attached list of the current state of home pages. --mjs

---

Attachments:

• Static-Web-Pages.html