Please verify Gmane Tag Filtering functionality (mailinglist archive / nntp access)

[ilias@…]

​example message

the tag "![Trac]" is not removed from gmane, as it should:

"...Gmane filters away all mailing list tags from the subject headers. They usually look like [some-mailing-list]. Gmane also removes the standard mailing list trailers that usually appear the the bottom of the message bodies and say how to unsubscribe from the mailing list."
​http://gmane.org/filter.php

please verify.

[ilias@…]

update:

"It seems good for trac-dev and turbogear.
I guess it will be removed if header tag is "[trac-users]"
or list address is trac@... "
​this message

It seems that the tag must be equal to the list name, in this case "trac-users".

[ilias@…]

this one is still not corrected.

Again: bad publicity for the Trac Project (which creates a project-management-tool, but is incapable to setup the mailinglists correctly).

[mgood]

I've tried to correct Gmane's information on Trac's mailing list to recognize the [Trac] identifier used. The form was not descriptive about the intent of the "Identifier" field, but I'm hoping that's what it's used for. I don't know how long it will take to get the changes applied (I also corrected the project URL), but I guess I'll get an email once they've been reviewed.

Please, try to keep your comments constructive. Making claims that the team is "incapable to setup the mailinglists correctly" is quite simply rediculous, since the problem is in Gmane's mirroring of our mailing list and not something we have direct control over.

[ilias@…]

Replying to mgood:

I've tried to correct Gmane's information on Trac's mailing list to recognize the [Trac] identifier used. The form was not descriptive about the intent of the "Identifier" field, but I'm hoping that's what it's used for. I don't know how long it will take to get the changes applied (I also corrected the project URL), but I guess I'll get an email once they've been reviewed.

ok.

(If this does not the work, thThe other solution is to set the tag to "trac-users" or to ask gmane for accepting the "trac" from a "trac-users" group)

Please, try to keep your comments constructive. Making claims that the team is "incapable to setup the mailinglists correctly" is quite simply rediculous, since the problem is in Gmane's mirroring of our mailing list and not something we have direct control over.

No, the problem is on how you use a given, widly used resource (gmane).

I simply state what a rationally thinking individual or evaluator could think (or conclude).

Reducing the priority of this ticket is not correct.

Priorities of this tickets which affect public visible project resources and remain unprocessed should be increased (here: after 2 months) .

The "Severity" to the trac projects reputation is not trivial. The lists are one of the first contact points for an evaluator/decision taker. For sure some of them will use gmane for the list access.

[cboos]

Well, I fail to see how having "[Trac] " in the subject of Trac related mails in GMane could damage the "reputation" of Trac...

I think it's up to matt to decide if this becomes a fix/wontfix depending on the feedback he gets from GMane.

[ilias@…]

Replying to cboos:

Well, I fail to see how having "[Trac] " in the subject of Trac related mails in GMane could damage the "reputation" of Trac...

Then you should possibly invest some more time.

The information is given.

I think it's up to matt to decide if this becomes a fix/wontfix depending on the feedback he gets from GMane.

I will not comment on what a "wontfix" on this issue would imply.

[ilias@…]

Replying to mgood:

I've tried to correct Gmane's information on Trac's mailing list to recognize the [Trac] identifier used. The form was not descriptive about the intent of the "Identifier" field, but I'm hoping that's what it's used for. I don't know how long it will take to get the changes applied (I also corrected the project URL), but I guess I'll get an email once they've been reviewed.

one day after this comment, the same problem has started on the devel list, see#4262

[cboos]

Same thing as #4262.