On 10/19/18 6:43 AM, Neal Gompa wrote: > On Fri, Oct 19, 2018 at 9:16 AM Gerald B. Cox <gbcox@xxxxxx> wrote: >> >> Again, I believe some are trying to do an apples to apples comparison with Discourse and mailing list technologies. Discourse was build from the ground up with the goal of fostering communication and collaboration. Hyperkitty is a bolt on HTML to mailing list archives. It's good for what it is, but it isn't Discourse - and usage numbers tend to bear that out. >> > > That's an unfair characterization. HyperKitty was designed from the > ground up with that goal in mind too. The _sole_ difference is the > backend approach. Discourse uses a database system while HyperKitty > uses a mail list engine. > > You know why the usage numbers bear that out? Because the upgrade to > HyperKitty was mishandled and delayed over and over. We were screwed > over by the fact that our infrastructure doesn't run on Fedora, so > that made it harder to get it working. The initial deployment was very > slow and unoptimized. Bugs in the UI remained unfixed in Fedora's > installation even though upstream fixed them. I would not be surprised > if upstream ignores us because we don't seem to be upgrading. Huh, you do realize that things take as long as they take, and there's no magic wand for 'it's magically done'. mailman3 was a massive undertaking with a very small group of developers, many of whom were wanting things to be really done before releasing them. Much of our infrastructure does run on Fedora, and mailman3 could too if we needed it to. It just wasn't the decision at the time. Bugs remain unfixed because there's not too much bugfixing going on. I see two commits in this month, 2 last month, 1 the month before... You can always ask why we aren't upgrading. In this case it's because we are moving stuff to python36 from 34. If these fixes are urgent let us know and we can re-evaluate and try and get things faster. I was under the impression that the fixes were pretty minor. ...snip... > We have not taken good care of our mail list infrastructure. I don't > blame our infra team. I blame the fact our infra runs on RHEL, and > RHEL has handicapped us in so many ways because of their own choices. > Fedora can't control its own (infrastructure) destiny because we have > no power to influence RHEL at all. And that's broken. Thats simply not the case. We run many things on Fedora. We do so where it makes sense and RHEL where that makes sense, and increasingly OpenShift when that makes sense. ;) I attempted to use the discourse rss feeds this last week, and they were... not great. I still need to try mailing list mode before speaking much more on it. kevin
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
