#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.
#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.
#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.
#50: Handling of users changing Subject lines of threads
------------------------+--------------------------
Reporter: ianweller | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: Beta version
Version: | Keywords:
------------------------+--------------------------
Sometimes you see this subject line in threads:
Subject: Re: Bar (was: Foo)
My understanding from abompard is that HyperKitty currently does not show
the subject change at all to the user. It should probably at least show
the new subject to the user.
Two ways of potentially dealing with this:
* Where the subject changes in the thread, add it above the first message
(what most mail clients do)
* Make it a different thread (what in some cases might make more sense --
and if it did break a thread incorrectly, you could reattach it, but then
you still want to show the subject line change).
--
Ticket URL: <https://fedorahosted.org/hyperkitty/ticket/50>
HyperKitty <http://mm3test.fedoraproject.org>
The HyperKitty Django app provides a web interface to access GNU Mailman archives.
#30: Translations (i18n)
------------------------+--------------------------
Reporter: abompard | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: Beta version
Version: | Keywords:
------------------------+--------------------------
First, the strings in the python code, in the templates and in Javascript
code should be marked for translations.
Django reference : https://docs.djangoproject.com/en/1.4/topics/i18n/
Then, we'll be able to translate the strings. Consider using
[https://www.transifex.com/ Transifex].
--
Ticket URL: <https://fedorahosted.org/hyperkitty/ticket/30>
HyperKitty <http://mm3test.fedoraproject.org>
The HyperKitty Django app provides a web interface to access GNU Mailman archives.
#31: Admin interface
------------------------+--------------------------
Reporter: abompard | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone: Beta version
Version: | Keywords:
------------------------+--------------------------
Add admin interface to do the following tasks:
* delete a post from the archives
* move a post between lists
--
Ticket URL: <https://fedorahosted.org/hyperkitty/ticket/31>
HyperKitty <http://mm3test.fedoraproject.org>
The HyperKitty Django app provides a web interface to access GNU Mailman archives.
Le 2013-11-29 16:42, Aurelien Bompard a écrit :
> Yeah the configuration key in your mailman config file is wrong. It
> should not point to the django config file directly, it should point
> to another config file with this content:
>
> [general]
> base_url: http://yourserver.example.com/hyperkitty
> django_settings: /home/mailman/hyperkitty_standalone/settings.py
>
> Did you follow some documentation which said to put the path to the
> django settings file there? Because that's how it used to work some
> months ago, and I may have forgotten to update something.
>
> Aurélien
ok, changed to some correct values, but still unusable.
exploring quickly mailman, i was at rev 7229 which brings recent
changes on archiving (7228 allows per-list archiver, quite a new feature
and maybe a bit unstable)
went back to beta3 for testing, but still not archiving
Which mailman version do you use ?
Hi!
I pulled down the latest from kittystore, hyperkitty, and
hyperkitty_standalone today and got this error when trying to run the app:
'SchemaUpgradeNeeded at /'
I couldn't figure out how to upgrade the schema (the manage.py migrate
command didn't seem to work) so I just blew away my db and re-imported
from scratch.
Is there a better way to do this or is reimporting the best thing to do
for now?
~m
Hi again,
I have configured archiver for mailman3 as told in install doc,
but i'm not able to verify if messages are delivered.
Is there a directive or a directory to look into for this component
logs ?