On Thu, Oct 04, 2018 at 11:27:02PM -0000, Ray Strode wrote:
Unfortunately, all is not rosy there. See this thread on the users' list
from this fall about confusion with hyperkitty quoting:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.o...
It's hilarious reading this thread in Hyperkitty and having absolutely no issue
understanding which quote is from whom.
(Look back at your message I'm replying to here, and note that
the standard
attribution line is missing. And that's not the only issue identified.)
Additionally, when one does reply, it's just using the standard web browser
text box, and to my knowledge that doesn't have an easy "delete by line"
keyboard command, let alone things like smart reflow with quoting.
These sound like good enhancement features that are likely not essential for the core
target user.
So that's
not super-ideal for inline replies. Hyperkitty's threaded view
also is
rudimentary compared to a good mail client.
All of this stuff would be something we could invest development resources
in and make better, but we don't really _have_ those resources,
But we can file bugs against Discourse and they will be magically and quickly fixed to our
satisfaction, yes?
We can invest money and resources into Discourse deployment, and time and effort trying to
convert each ML over to it one by one, dealing with all of the existing docs and pointers
to MLs and updating them, no sweat?
Threading is something I could fix on the front end with some backend help. Is anybody
handy with Django who is interested?
Is that the biggest issue to tackle?
I'm concerned that those proposing Discourse seem to not have used Hyperkitty at
length.
and no
significant outside-of-fedora hyperkitty development community ever
developed. We're left with some pretty awful things like the prominent "Sign
Up" button on every Fedora list leading to a big, ugly "Sign Up Closed: We
are sorry, but the sign up is currently closed" screen — which is not very
inviting, to say the least.
I have no idea what that is, but it sounds like a minor bug that probably isn't
difficult to fix.
But sure let's split our community over that.
~m