[hyperkitty-devel] hyperkitty's hackability
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