More components in Trac for non-technical aspects

[Markus Amalthea Magnuson]

Another idea spawned during DjangoCon Europe:

Would it make sense to have more non-technical components in Trac? I'm thinking of e.g. "Inclusion" that tracks how the project presents itself to new users, "Diversity" for tracking improvements to various such aspects, etc. etc. These are just a couple of examples, there's surely more along the same lines, and better ones than mine.

Thoughts?

[Tim Graham]

I think we should keep Trac focused on tracking bugs. The dsf-members mailing list seems like a natural place to raise these ideas, although that's a more limited audience, so I'd feel free to raise them here unless someone else can suggest a better place.

[Russell Keith-Magee]

On Thu, Jun 4, 2015 at 4:19 PM, Tim Graham <timog...@gmail.com> wrote:

I think we should keep Trac focused on tracking bugs. The dsf-members mailing list seems like a natural place to raise these ideas, although that's a more limited audience, so I'd feel free to raise them here unless someone else can suggest a better place.

There's a DSF Volunteers list as well that is open to all; however, there's almost no traffic on that list. 

I agree that Trac should be focussed on tracking bugs. More specifically, it needs to be things that have a defined point of completion. 

If there's a specific inclusion-related activity that needs to be performed (e.g., the renaming of database replication terms from a while back), that can easily be raised as a bug and closed when it's resolved. More vague targets like "improve inclusivity in the community", while being completely worthwhile activities, don't lend themselves to a ticket tracker.

Russ %-)