James Legg wrote: > hugin-ptx is the only list linked to on hugin.sourceforge.net, and > sourceforge makes the lists it hosts difficult to find. Could all the > lists be listed there and at sourceforge.net/projects/hugin/?
I am not sure what can and can't be listed on sf.net/projects/hugin. We control hugin.sf.net and so we can list anything there. Yes the lists are difficult to find and part of this process will end in better documentation on where to find what - lists, RSS feeds, etc. > To encourage public conversations I think the reply-to address on > hugin-cvs (and other notification lists) should be hugin-ptx rather then > the commiter's sourceforge address. I'm not sure if (a) it makes sense for all notifications lists and (b) if it is possible with the current mailing list infrastructure (SF). I do see an added value with the reply to committs notification going to hugin-ptx (or a dev-list). it defintely should not go to the committer. What scares me a bit is replies to bug tracker notifications. This may defeat the purpose of keeping follow up information attached to the bug tracker ticket, rather than a discussion on a mailing list. > A few emails quoting bits of a > commit message posted to hugin-ptx will bring more attention to > hugin-cvs and more public developer talk. it's a matter of signal-to-noise ratio - for most users commit messages are noise. for me they are a wonderful way to learn as the project goes along, by reading what experts are doing and learning from their commit. Although I admit I don't always have the bandwidth to read and understand in full detail every single commit. I am still on the learning curve. Also I don't think it is possible to limit this to "a few", unless the forward to hugin-ptx is manual and intentional. if we subscribe hugin-ptx to the commit notification we get every single commit in its full detail. >> * A single developers mailing list that includes all the notifications, >> like [VLC devel] (used by the VideoLAN developers). > > I don't like this approach. I subscribe to hugin-cvs and hugin-ptx, but > only use the RSS feeds for the trackers. The volume of traffic is high, > and forcing people who want some development talk to receive svn commits > and tracker updates in their inbox as well can only make the volume > greater. I don't think this approach will happen. I rather think that we will have one separated list for notifications (tracker and commits), and one separated list for talk (which can very well be hugin-ptx if the users tolerate more dev talk). Help me understand how you use RSS feeds to track notifications. RSS feeds have not worked for me so far. I found that most of them carry just the last ten or so messages, and I found no RSS reader that checks them automatically and regularly enough to guarantee that I don't miss an update (e.g. when I'm away for a few days). What's the point of incomplete information? Furthermore: what's the difference between a feed and an in-box? to me they are conceptually exactly the same: a list of subject lines that I skim through, very often just with the delete key. Messages in mailboxes I can sort automatically into subfolders; or I can have (as I do) two or more different mailboxes with different priority. The only difference I see between RSS feeds and mailboxes is that once something is on my mailbox on the server, it waits for me and it can't be taken back or accidentally forgotten. Polling a mailbox or polling an RSS feed, I don't see much difference. > Would the individual lists for automatic notifications still be > available when there is a combined list? I've tried to set up something like that - with a combined list that hooks up on the existing lists. It does not really work (yet), and it probably won't work with a GoogleGroup (my preferred mailing list tool). But it should work with mailman, i.e. it can problably be set up on SF (with all the disadvantages of SF). > As a developer I would join a dev-talk list if it were created, but I'm > happy to continue discussing developmental matters here. It's really up > to people who would classify themselves as users or translators to > decide if they consider development chatter as signal or noise. exactly - this is why I want to read opinions from users. Yuv --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx -~----------~----~----~----~------~----~------~--~---
