[HyperKitty] #31: Admin interface
by HyperKitty
#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.
8 years, 1 month
[HyperKitty] #33: Navigation bar
by HyperKitty
#33: Navigation bar
------------------------+--------------------------
Reporter: abompard | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone: Beta version
Version: | Keywords:
------------------------+--------------------------
Make a navigation bar like linuxfr.org to go to new posts in an existing
thread. It requires some database changes to link read posts to the user.
--
Ticket URL: <https://fedorahosted.org/hyperkitty/ticket/33>
HyperKitty <http://mm3test.fedoraproject.org>
The HyperKitty Django app provides a web interface to access GNU Mailman archives.
9 years, 11 months
Activity graph on the overview page
by Pierre-Yves Chibon
Hi all,
I was quickly looking at the code today to try to see why the activity
graph from the overview page did not reflect really the current activity
we see in the devel mailing list these days.
>From what I saw and if I understood things correctly it is showing the
number of active threads for each days. Is this the intended behavior?
Do we prefer the evolution of the active threads or the evolution of the
numbers of emails on the list?
I'm fine with both, but we need to pick one and somehow document it
(which might come when we change this js visualization library).
Pierre
10 years, 3 months
Move to Git and Github
by Aurelien Bompard
Hi devs,
You probably already heard of it, we're switching to Git as a VCS, and
moving the sources to Github. The wiki and ticketing system stay on
fedorahosted.org.
The main reason is our familiarity with Git vs Bazaar.
The new address is : https://github.com/hyperkitty. Just ask to be
added to the committers group if you want to.
I've update the wiki page.
Cheers !
Aurélien
10 years, 4 months
hyperkitty's hackability
by Michael Burns
Greetings hyperkitty-devel,
As I mentioned in a recent Fedora Infra thread [0], Mozilla is keenly interested in Mailman 3 and HyperKitty in particular. As we make plans for the new year, I'd love to get a feel for the state of HyperKitty and what its outlook is for 2013.
Obviously, bugs 21 [1] and 22 [2] are the big ticket items that require a lot of groundwork to be laid before they get tackled. That being said, is there a plan of attack for getting those features developed, or is that too far in the future still?
Besides those biggies, I'd love to hear how hackable y'all think the codebase is to outsiders that might want to contribute. Are there any architectural changes in the pipeline that we might want to wait to land into Trunk before getting involved?
Put another way: if you could snap your fingers and get an extra set of development hands, what kind of work would it be most helpful for those hands to get dirty working on? UX/UI frontend stuff, python hacking on hyperkitty's backend, or are there still improvements needed in mailman3 itself to make hyperkitty's job easier?
Cheers!
[0] https://lists.fedoraproject.org/pipermail/infrastructure/2012-December/01...
[1] https://fedorahosted.org/hyperkitty/ticket/21
[2] https://fedorahosted.org/hyperkitty/ticket/22
--
Michael Burns
Mozilla IT
10 years, 5 months
