Follow-up Comment #1, sr #111315 (group administration): [comment #0 original submission:] > 0 After I log in, I don't see anything like /"groups I'm interested in"/. > There's no "watch this group", except by subscribing to the applicable > mailing list, and *that* doesn't give a link to the group's pages. So either > I keep some bookmarks on my PC, or I have to search for each group.
Savannah lets group admins create mailing lists on lists.gnu.org, but they are
really managed by Mailman (technically, the mailing lists are out of scope of
Savannah at all). List admins can put any links they wish to the description
of the lists.
On "watching the group": in tracker notification settings, one can list
addresses and Savannah users who should get notifications on any posts, though
only group admins can configure that. In many cases, directing the
notifications to a mailing list will do.
> 0 When a mailing list notifies me that there's a ticket that interests me, I
> get a link to it, but there's no "watch to this ticket" facility. (I've since
> been told that I should simply post an empty comment to the ticket, but that
> strikes me as quite antisocial; do people subscribed to tickets really *want*
> to be notified whenever someone starts merely watching a ticket?)
I don't think I understand the process. If Savannah sends a notification
about the original submission to a mailing list, it will also send follow-ups
there unless the 'Send on all updates' checkbox is reset. In particular, both
original submissions and follow-ups from this support tracker are sent to
savannah-help-public@.
> 0 Having done that, there's then the question of how to *stop* receiving
> updates on a ticket. I looked around for ages and couldn't find anything.
> (Again, I was subsequently informed that the section heading "Mail
> Notification Carbon-Copy List" is collapsed by an "accordion"; from my
> perspective, the UI is an utter failure, see below.)
Probably Savannah is better with JavaScript disabled.
> 0 For the groups that I'm following, there seems to be an awkward disjunction
> between the ticket tracker and the mailing list that receives "new ticket"
> announcements. Replies on the mailing list are never seen by the the original
> poster unless they're an experienced user who has already subscribed to the
> list. On of the groups - bash - gives end-users a tool to submit bug reports
> by email, but those wind up going to the list and not into the ticketing
> system.
>
> Is there a recommended group configuration that would ensure all issue
> submissions and their responses are organised in a coordinated manner? Is
> there a way to have replies on the mailing list be treated as comments to add
> to a ticket, and/or create a new ticket, without imposing additional
> requirements beyond what's normally needed to participate in a mailing list
> (ie, not requiring everyone to register GPG keys)?
If anonymous posts are allowed on the tracker, it arguably requires even less
than what's normally needed to participate in a mailing list---when posting
via the Web UI. The integration of the trackers with mailing lists is quite
loose, and I don't think I see how to integrate them fully.
What is currently possible is sending notifications to the mailing lists and
posting follow-ups authenticated with GPG keys.
...
> I felt more angry at Savane than at them, especially when I discovered I'd
> tripped over an intentional mine-fieldin
> *frontend/php/css/internal/base.css*:
>
> .minusorplus { font-size: xx-small }
> which dates back to 2006.
Or a few years earlier.
...
> Secondly, I don't really understand why this content needs to be hidden in
> the first place.
Neither do I.
> Lastly, two issues I discovered as I was writing this ticket:
> 0 There's no markup for "inline code sample", aka fixed pitch span rather
> than div. I tried various permutations of markdown (``) and HTML (<code>) to
> see if it was merely undocumented, but to no avail.
No; anything except bugs is documented. It has bold and italics, I'd rather
not add more styles.
> 0 if you hit refresh (or go back and then forward again) while composing a
> ticket, you're dumped out and have to start again; there isn't even a "start
> again" link, you have to go back far enough to find the "submit new" button.
> (Oh, and heaven forbid that you hit that button whilst in the middle of
> composing a ticket.)
Good point.
> In short, _please_ can we have a CSS overhaul? If I were to submit patches to
> make it look more in line with modern expectations, how likely are they to be
> accepted? Or would this just generate endless arguments about how it doesn't
> need changing and/or how my choices are ugly?
You can only try and see.
> PS: I appreciate I'm bundling up multiple issues here, but I really don't
> feel like torturing myself repeatedly to submit multiple tickets.
You are welcome.
_______________________________________________________
Reply to this item at:
<https://savannah.nongnu.org/support/?111315>
_______________________________________________
Message sent via Savannah
https://savannah.nongnu.org/
signature.asc
Description: PGP signature
