hyperkitty-devel April 2015

hyperkitty-devel@lists.fedorahosted.org

5 participants
60 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

Mailman Suite 3.0rc1 awaiting an upstream fix
by Sumana Harihareswara 20 Apr '15

20 Apr '15

At the PyCon sprint last week, we made a lot of progress towards a 3.0 release and we discussed next steps. I'm very glad so many of us could make it and pitch in. The 3.0rc1 depends on a new Falcon release because there's a bugfix awaiting release in Falcon that fixes a blocker bug for us: https://bugs.launchpad.net/postorius/+bug/1444504 Once that's out, we can put out a release candidate. In order to release 3.0.0 final, we need core native releases for all 5 components of the Mailman suite, with tested installation instructions and with all the components tagged, tested, and on PyPI. We'd also like some infrastructure and workflow improvements before we do that -- for one thing, we ought to set up continuous integration to run our automated tests on every merge. We will probably request a CI server/VM from the Python Software Foundation. We could actually set up CI for HyperKitty (and probably our other components as well) right away using the (no guarantee of uptime/service level) Jenkins installation at http://jenkins.cloud.fedoraproject.org/ if someone followed the instructions at https://fedoraproject.org/wiki/Jenkins@infra#Can_I_add_my_project_to_Jenkin… and add ticket to https://fedorahosted.org/fedora-infrastructure/ . We need to have an i18n setup and I've agreed to take lead on that. And there's further potential wrangling around Launchpad, branches, Bazaar, Git, etc. that I'll write up tomorrow. Hope this helps keep everyone up to date. -- Sumana Harihareswara http://brainwane.net

3 3

[HyperKitty] #100: subject in threadview should be the most-used subject
by HyperKitty 19 Apr '15

19 Apr '15

#100: subject in threadview should be the most-used subject ------------------------+----------------- Reporter: sumanah | Owner: Type: enhancement | Status: new Priority: minor | Milestone: 1.2 Version: | Keywords: ui ------------------------+----------------- When I am viewing a thread, if the subject line of the thread has changed and there are multiple possible subject lines, we should choose to display (at the top/title) the subject that the most messages used. -- Ticket URL: <https://fedorahosted.org/hyperkitty/ticket/100> HyperKitty <http://mm3test.fedoraproject.org> The HyperKitty Django app provides a web interface to access GNU Mailman archives.

1 0

[HyperKitty] #99: Consider moving to SASS
by HyperKitty 16 Apr '15

16 Apr '15

#99: Consider moving to SASS ------------------------+----------------- Reporter: abompard | Owner: Type: enhancement | Status: new Priority: minor | Milestone: 1.2 Version: | Keywords: ------------------------+----------------- LESS is a pain to install, and Bootstrap supports SASS officially now. SASS has a libsass component with python bindings, so it may we worthwhile to investigate switching to that if all features are supported. -- Ticket URL: <https://fedorahosted.org/hyperkitty/ticket/99> HyperKitty <http://mm3test.fedoraproject.org> The HyperKitty Django app provides a web interface to access GNU Mailman archives.

1 0

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

16 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 16 Apr '15

16 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 16 Apr '15

16 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 16 Apr '15

16 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 16 Apr '15

16 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 16 Apr '15

16 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

hyperkitty-devel April 2015