On Wed, 2019-08-21 at 14:51 -0700, Patrick David wrote:
> Howdy all!
Hello and goodbye.
I've retired from Hugin for years. Lack of time. When I saw this
thread, I had a few thought that I first kept to myself. After all, we
want the project to thrive beyond the lives of individual contributors.
TLDR: Discourse is IMHO a defective piece of junk. My opinion is the
result of joining a community that unfortunately communicates mostly on
Discourse. [
https://discuss.linuxcontainers.org/c/lxd]
The deal killer for me is that the "simulated" mailing list behaviour
is useless. The HTML mails are unreadable on mobile devices, and are
top-posted, making reading/following extremely cumbersome. I can
criticize further, but this is not a Discourse development list.
SOME MORE THOUGHTS FOR THOSE WHO CARE
* there is a real concern: GoogleGroups are stagnating and Google is
known for pulling the plug rather quickly on tools that do not fit
their portfolio. At some point in the future, near or far, this group
will need a new home. For now, it can just be a low burner backup plan
discussion.
* there is another real concern: many of us, and particularly people
who have contributed to Hugin for a long time, have a very strong
preference for e-mail based communication. Mailing list. There are
good reasons for that. HTML and the web are great for websites, blogs,
bug trackers, but IMHO anything that I have seen so far for group
communication that is web-based is inefficient.
* nothing prevents community members or third parties from collecting
the wisdom from the flow of communication and put it in nicely designed
websites, blogs, wikis, etc.
* with regard to
PIXLS.US: it *looks* good, but how viable is it? how
do you pay for all of this? this community has experience with
Sourceforge, the original home of Hugin (that still hosts the source
code and website) being sold to Slashdot Media and monetized in
abhorrent ways. Google may be a big advertising beast, but at least it
is not desperate nor stupid enough to covertly add spyware to hosted
software
https://arstechnica.com/information-technology/2016/06/under-new-management-sourceforge-moves-to-put-badness-in-past/
> I don't think we've formally approached the Hugin project, but
> consider this an invitation! Many of us in the community already use
> Hugin and I think it'd be wonderful to have even more knowledgable
> users join us.
You are welcome to write articles and blogs about Hugin like any other
third party. Do not take it personally: I will not join
PIXLS.US. It
is a neatly designed publication, but it is just that, a publication.
What I need is a forge. Sourceforge used to have mailing lists.
Github was promising before it was taken over by Microsoft. Right now,
*if* Hugin has to move anywhere, my recommendation would be to move to
Gitlab. And maybe by the time Hugin moves to Gitlab, it will have
mailing list functionality.
https://gitlab.com/gitlab-org/gitlab-ce/issues/4272
Already now, Gitlab's issues tracker has a much better email interface
than Discourse.
Last but not least: do not change what is working. Change for
change's sake is a waste of resources. Only change if the change
brings some advantage, or if the change is inevitable (such as the
pending loss of an existing resource). I have not seen a valid
argument to move away from Google-Groups; so even if I do not like
Google, I vote to stay here until Google turns the lights off, and to
reconsider the real concerns when Google shuts down, or when a tool
becomes available that does not sacrifice proper email functionality
and does not add burden the group's admins.
Yuv
P.S.: my interest in LXD is because early July my Sandy Bridge PC
broke down on a weekend and I absolutely needed a working PC on Monday.
I was waiting for Ryzen 3000 and the only CPU available at the local
computer store was the 3900x. Running a lawyer's desk on 12 cores is a
bit of a waste. So I have virtualized the metal with KVM and I am
slicing up further one of the VMs with LXD for different applications.
With so much idling computing power, I intend to use some seasonal
downtime to process years and terabytes of pictures and videos. Tons
of other virtualized applications at different stage of implenentation,
including a complete Android and F-Droid build chain / store. A backup
solution for my public cloud presence. Hardened Nextcloud for my
clients. Running a mailing list in one container on the side will not
be much of an effort.