hyperkitty-devel January 2015

hyperkitty-devel@lists.fedorahosted.org

5 participants
37 discussions

[HyperKitty] #66: Restore ability to export mbox files
by HyperKitty 09 Nov '15

09 Nov '15

#66: Restore ability to export mbox files ------------------------+------------------------------ Reporter: dmw | Owner: Type: enhancement | Status: new Priority: major | Milestone: Beta version Version: | Keywords: mbox export data ------------------------+------------------------------ Hi there, After reading about the project on LWN, I was somewhat disappointed to see there doesn't appear to be mbox export facility yet. As one commenter put it on the LWN story, "Download as mbox" or alternatively "download as maildir" are basically the "liberate the community data" and "allow fast local mirrors of the archive" functionality for email mailing lists... If it doesn't have that, it is a show stopper as far as I'm concerned. Maybe a plugin can fix that, but it is best implemented well integrated with the archive web interface. Do you have plans to implement something like this? Thanks -- Ticket URL: <https://fedorahosted.org/hyperkitty/ticket/66> HyperKitty <http://mm3test.fedoraproject.org> The HyperKitty Django app provides a web interface to access GNU Mailman archives.

1 7

[HyperKitty] #79: Highlight messages with best score from one thread
by HyperKitty 17 Apr '15

17 Apr '15

#79: Highlight messages with best score from one thread ------------------------+-------------------------- Reporter: ttomecek | Owner: Type: enhancement | Status: new Priority: major | Milestone: Beta version Version: | Keywords: ------------------------+-------------------------- If there is a thread on mailing list which consists of hundreds of messages, it's almost impossible to read every one of them. Therefore it could be beneficial to create a view which would contain 3, 5, 10 messages with best score (with a link to thread view to get a context). On the other hand, there could be an another way to sort the thread: by popularity. I'm not sure which way makes more sense. -- Ticket URL: <https://fedorahosted.org/hyperkitty/ticket/79> HyperKitty <http://mm3test.fedoraproject.org> The HyperKitty Django app provides a web interface to access GNU Mailman archives.

1 2

[HyperKitty] #73: Summary page for months and years
by HyperKitty 17 Apr '15

17 Apr '15

#73: Summary page for months and years ------------------------+-------------------------- Reporter: langdon | Owner: Type: enhancement | Status: new Priority: major | Milestone: Beta version Version: | Keywords: ------------------------+-------------------------- I like the summary page a bunch, however, I wish I could see it for a month or a year when I click on those nav elements. When going back through old mailing lists, it is very helpful to get a "sense of the month" or year. Or, maybe a "summary icon" next to the month/year nav element, to not lose the "i just want to get to the emails" feature. -- Ticket URL: <https://fedorahosted.org/hyperkitty/ticket/73> HyperKitty <http://mm3test.fedoraproject.org> The HyperKitty Django app provides a web interface to access GNU Mailman archives.

1 2

[HyperKitty] #39: declassification of private mails feature
by HyperKitty 17 Apr '15

17 Apr '15

#39: declassification of private mails feature ------------------------+-------------------------- Reporter: misc | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Beta version Version: | Keywords: ------------------------+-------------------------- Since HK is a mail archiver, one of my pet peeve is the various usage of private mailing list, and what this implies. While a full ACL system could be nice, I would propre to have a declassification feature. I have 2 use cases in mind, based on the way i think a community distribution should work. First use case is people contacting a project for security reason. While the content must not be public at first, it could IMHO be made public after a while ( like automated declassification after 6 months ). Main reasons are : - less interest for a potential attacker since less stuff are marked as private - more transparency on what happen behind closed doors, reducing the conspiracy ideas, and permit to people who would learn how the project react to security issue how stuff happen, even if not in real time. This is rather important for community growing The second use case is about all the project that have a private board list, to discuss private matters. Here, I would rather see a per thread disclosure feature, after a time. For example, I could see someone either being a disclosure officer, or on demand by a admin. The same benefit as the 1st proposal, this permit to document the decision of any private group for future reference. But unlike the previous one, this would not be automatic. A third way to disclose could be to either just disclose the identity of the poster, or just identity and subject. This would permit to show to people ( if they trust the group ) that nothing was discussed for X months, or who was active ( quite important if the group is elected ). While this is rather high level idea, while redacting this, i think this would be best achieved with a rather complete ACL system, but i fear this is starting to be the sign of feature creep :) ( and i didn't even spoke of having a tool to discuss disclosure ). -- Ticket URL: <https://fedorahosted.org/hyperkitty/ticket/39> HyperKitty <http://mm3test.fedoraproject.org> The HyperKitty Django app provides a web interface to access GNU Mailman archives.

1 2

[HyperKitty] #49: plug-in API
by HyperKitty 17 Apr '15

17 Apr '15

#49: plug-in API ------------------------+----------------- Reporter: nka11 | Owner: Type: enhancement | Status: new Priority: major | Milestone: Version: | Keywords: ------------------------+----------------- Enable plugins and extensions for hyperkitty. Make it extensible and maybe consider to pull out some integrated features which could become plugins - vote +/- - allow web reply - tag - authentication may remains part of core for private lists archives access. This have two advantages : - a well documented plugin API will encourage plugins developers and contributions to small modules - the core gets separated from non-pure-ml-archive feature and gets simpler and easily maintened - so will become the extra features plugin -- Ticket URL: <https://fedorahosted.org/hyperkitty/ticket/49> HyperKitty <http://mm3test.fedoraproject.org> The HyperKitty Django app provides a web interface to access GNU Mailman archives.

1 4

[HyperKitty] #44: 9gag like system for the archive page?
by HyperKitty 17 Apr '15

17 Apr '15

#44: 9gag like system for the archive page? ------------------------+-------------------------- Reporter: pingou | Owner: Type: enhancement | Status: new Priority: major | Milestone: Beta version Version: | Keywords: ------------------------+-------------------------- On the website 9gag.com, the page becomes longer as you scroll down. Would this be something to consider for the archive page instead of the current hard-coded pagination? -- Ticket URL: <https://fedorahosted.org/hyperkitty/ticket/44> HyperKitty <http://mm3test.fedoraproject.org> The HyperKitty Django app provides a web interface to access GNU Mailman archives.

1 2

[HyperKitty] #74: Gravatar & Profile page
by HyperKitty 17 Apr '15

17 Apr '15

#74: Gravatar & Profile page ------------------------+-------------------------- Reporter: langdon | Owner: Type: enhancement | Status: new Priority: major | Milestone: Beta version Version: | Keywords: ------------------------+-------------------------- Might be helpful to indicate on the profile page that "the email address that your redirect is pointed to" is what we search at gravatar... in other words, my gravatar image isn't the one at langdon at fp.o, it actually uses the redirect, langdon at fishjump.c however, "edit at gravatar" isn't very clear on that. -- Ticket URL: <https://fedorahosted.org/hyperkitty/ticket/74> HyperKitty <http://mm3test.fedoraproject.org> The HyperKitty Django app provides a web interface to access GNU Mailman archives.

1 2

[HyperKitty] #83: Easy configuration of list styles
by HyperKitty 17 Apr '15

17 Apr '15

#83: Easy configuration of list styles --------------------+-------------------------- Reporter: sumanah | Owner: Type: task | Status: new Priority: major | Milestone: Beta version Version: | Keywords: --------------------+-------------------------- From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman suite 3.x series. Possibly related to bug #67. -- Ticket URL: <https://fedorahosted.org/hyperkitty/ticket/83> HyperKitty <http://mm3test.fedoraproject.org> The HyperKitty Django app provides a web interface to access GNU Mailman archives.

1 3

[HyperKitty] #78: Hide subthreads with score lower than X
by HyperKitty 17 Apr '15

17 Apr '15

#78: Hide subthreads with score lower than X ------------------------+-------------------------- Reporter: ttomecek | Owner: Type: enhancement | Status: new Priority: major | Milestone: Beta version Version: | Keywords: ------------------------+-------------------------- It would be great if !HyperKitty had a feature to hide messages (and its possible replies) by default which are: * below a specified score * marked as spam * marked as not constructive With this system we could get smaller thread tree with messages which are widely-accepted. On the other hand, this system could hide sensible messages, which may be interesting to read, but community doesn't like them. -- Ticket URL: <https://fedorahosted.org/hyperkitty/ticket/78> HyperKitty <http://mm3test.fedoraproject.org> The HyperKitty Django app provides a web interface to access GNU Mailman archives.

1 2

[HyperKitty] #84: add RSS feeds
by HyperKitty 17 Apr '15

17 Apr '15

#84: add RSS feeds ------------------------+-------------------------- Reporter: sumanah | Owner: Type: enhancement | Status: new Priority: major | Milestone: Beta version Version: | Keywords: ------------------------+-------------------------- Per [http://lists.w3.org/Archives/Public/www-rdf- interest/2003Feb/0047.html] -- add RSS feeds. {{{ I just stumbled across this after an #rdfig discussion about adding RSS support to Mailman, the popular list management and HTML archiving package. Turns out the patch exists already (but wasn't intergrated yet). It took me less than 10 minutes to patch my Mailman installation and rebuild the archives for rdfweb-dev. I now have http://rdfweb.org/pipermail/rdfweb-dev/rss.xml generated automatically. See http://rdfig.xmlhack.com/2003/02/09/2003-02-09.html#1044813421.381747 for the (trivial to apply) patch and related info. Just cd into the Mailman/Archiver/ directory and do 'patch < ~danbri/rss.patch' or whatever, then re-run bin/arch on your archives. The markup exported is fairly basic, but sets things up nicely for future extensions -- you could add in richer descriptions of the mailing lists fairly easily, though I'm not sure how best one would hook such information up to Mailman's www-based frontend. Dan }}} It would be awesome to be able to subscribe to a specific list via RSS; after that, it would also be neat to be able to subscribe via RSS to all public lists on a domain, to mail from a specific user, or to mail to a list on a specific "topic"/thread. I'm taking this idea from http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO/wishlist for the Mailman 3.x series. -- Ticket URL: <https://fedorahosted.org/hyperkitty/ticket/84> HyperKitty <http://mm3test.fedoraproject.org> The HyperKitty Django app provides a web interface to access GNU Mailman archives.

1 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

hyperkitty-devel January 2015