Django Trac Migration Considerations

Based on the Django documentation about bug reporting and ticket tracking, I can provide some insights about important features that should be considered when migrating from Trac to another platform like GitHub Issues.

Key Trac Features to Consider

From the Django documentation, the ticket tracker is described as "the central hub for managing issues, improvements, and contributions to Django." This suggests several critical features that should be preserved:

1. Ticket Metadata and Classification

The Django ticket system relies on various metadata fields for effective triaging and management:

• Severity/priority levels
• Version information
• Component categorization
• Status tracking (e.g., "wontfix", stages of triage)
• Type classification (bug, feature, etc.)

2. Ticket Workflow Support

The documentation mentions a specific triage workflow with different stages:

• Initial reporting
• Triage process
• Decision-making process
• Closing tickets with appropriate resolution

3. Security Considerations

The documentation emphasizes security reporting through private channels:

• Any new system must maintain the separation between public issues and security vulnerabilities
• Security issues should remain private until addressed

4. Community Engagement

The current system supports:

• Community-based triaging
• Public visibility of ticket status
• Integration with mailing lists (django-updates)

5. Query and Reporting Capabilities

The documentation references:

• Custom queries for searching existing tickets
• The ability to check if bugs/features have already been reported

Recommendations for Migration

When evaluating GitHub Issues or other alternatives, ensure they can support:

1. Equivalent or improved metadata fields for proper ticket classification
2. A workflow that maintains Django's established triage process
3. Private reporting channels for security issues
4. Community participation in ticket management
5. Robust search and filtering capabilities

The migration should also consider how historical data will be preserved, as the documentation references the importance of being able to track the evolution of features and understand past decisions.

I hope this information helps with your DEP for the Trac migration. For more specific details about which reports are essential, you would need feedback from active Django contributors who regularly use these features.