<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none"><!--P{margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>I believe this one is in the pipe for version 4.4 but could be wrong.</p>
<p><br>
</p>
<p>JP Pitout<br>
</p>
<div style="color: rgb(33, 33, 33);">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" face="Calibri, sans-serif" color="#000000"><b>From:</b> Xymon <xymon-bounces@xymon.com> on behalf of Ralph Mitchell <ralphmitchell@gmail.com><br>
<b>Sent:</b> 08 March 2019 17:40<br>
<b>To:</b> Axel Beckert<br>
<b>Cc:</b> xymon@xymon.com<br>
<b>Subject:</b> Re: [Xymon] RES: Is the xymon Dead? Future</font>
<div> </div>
</div>
<div>
<div dir="auto">I'd still like to see encrypted connections for Xymon client messages going to the server.
<div dir="auto"><br>
</div>
<div dir="auto">Ralph Mitchell</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, Mar 8, 2019, 10:09 AM Axel Beckert <<a href="mailto:abe@deuxchevaux.org">abe@deuxchevaux.org</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
Hi,<br>
<br>
On Fri, Mar 08, 2019 at 01:31:35PM +0000, John Horne wrote:<br>
> On Fri, 2019-03-08 at 12:09 +0000, SebA wrote:<br>
> > Many years ago, I pushed for Xymon to be moved from VCS to SVN to promote<br>
> > community contributions.<br>
<br>
I think you meant CVS instead of VCS. VCS (Version Control System) is<br>
the general term for CVS, SVN, Git, Mercurial, etc.<br>
<br>
> > Git, specifically GitHub, has replaced SVN as the best thing to<br>
> > promote community contributions, and I think it would be<br>
> > beneficial if the official Xymon code repos are migrated to<br>
> > GitHub.<br>
<br>
Definitely, but it's also not the only thing which is needed for<br>
getting contributions from external contributors. It's also a social<br>
thing.<br>
<br>
Reviewing and accepting contributions — or maybe even giving<br>
trustworthy contributors commit access is also necessary for a FLOSS<br>
project. But as far as I can tell, this happens in the Xymon project,<br>
although not on a daily base.<br>
<br>
> but github would allow the community to report issues,<br>
<br>
SF does allow that, too, it's just not enabled for the Xymon project<br>
on SF. Example of an SF project where it is enabled:<br>
<a href="https://sourceforge.net/p/nfsen/bugs/" rel="noreferrer noreferrer" target="_blank">https://sourceforge.net/p/nfsen/bugs/</a><br>
<br>
> provide updates/patches via pull requests,<br>
<br>
Exists on SF, too, example: <a href="https://sourceforge.net/p/nfsen/patches/" rel="noreferrer noreferrer" target="_blank">
https://sourceforge.net/p/nfsen/patches/</a><br>
<br>
> and download either released versions via the tags<br>
<br>
Possible, too, example:<br>
<a href="https://sourceforge.net/p/xymon/code/HEAD/tarball?path=/branches/4.3.27" rel="noreferrer noreferrer" target="_blank">https://sourceforge.net/p/xymon/code/HEAD/tarball?path=/branches/4.3.27</a><br>
<br>
> if necessary or the latest code via the 'develop' (or<br>
> whatever) branch.<br>
<br>
<a href="https://sourceforge.net/p/xymon/code/HEAD/tarball?path=/branches/4.x-master" rel="noreferrer noreferrer" target="_blank">https://sourceforge.net/p/xymon/code/HEAD/tarball?path=/branches/4.x-master</a><br>
<a href="https://sourceforge.net/p/xymon/code/HEAD/tarball?path=/trunk" rel="noreferrer noreferrer" target="_blank">https://sourceforge.net/p/xymon/code/HEAD/tarball?path=/trunk</a><br>
<br>
Don't get me wrong: I think SF degraded from once the best place to<br>
host FLOSS to a website with tons of outdated trash and the most<br>
horrible UI I ever saw from a code hosting site. Not to mention that<br>
it is far too overladen with ads and popup.<br>
<br>
My personal preference in VCS hosters is also GitHub as — from my<br>
point of view — they currently provide the best user experience. OTOH<br>
there might be some qualms about Github being not completely open<br>
source and being owned by Microsoft.<br>
<br>
And with regards to being dead or not: Development greatly sped up<br>
when J.C. Cleaver took over release management, but it indeed seems to<br>
have stalled a little bit again. Then again, IIRC J.C. mostly took<br>
over release management so that Henrik can focus on long-time<br>
development. And if there is not much to fix in the current stable<br>
releases, not having a stable release every few months is not<br>
necessarily "dead", but might also be "stable, no relevant open<br>
issues".<br>
<br>
(And yes, I'm still hoping and waiting for IPv6 support, too,<br>
especially in xymonnet-based checks. Reporting to IPv6-only servers is<br>
no issue though, if you anyways use stunnel to encrypt the<br>
client-reporting traffic.)<br>
<br>
Kind regards, Axel<br>
-- <br>
PGP: 2FF9CD59612616B5 /~\ Plain Text Ribbon Campaign, <a href="http://arc.pasp.de/" rel="noreferrer noreferrer" target="_blank">
http://arc.pasp.de/</a><br>
Mail: <a href="mailto:abe@deuxchevaux.org" target="_blank" rel="noreferrer">abe@deuxchevaux.org</a> \ / Say No to HTML in E-Mail and Usenet<br>
Mail+Jabber: <a href="mailto:abe@noone.org" target="_blank" rel="noreferrer">abe@noone.org</a> X<br>
<a href="https://axel.beckert.ch/" rel="noreferrer noreferrer" target="_blank">https://axel.beckert.ch/</a> / \ I love long mails:
<a href="https://email.is-not-s.ms/" rel="noreferrer noreferrer" target="_blank">
https://email.is-not-s.ms/</a><br>
_______________________________________________<br>
Xymon mailing list<br>
<a href="mailto:Xymon@xymon.com" target="_blank" rel="noreferrer">Xymon@xymon.com</a><br>
<a href="http://lists.xymon.com/mailman/listinfo/xymon" rel="noreferrer noreferrer" target="_blank">http://lists.xymon.com/mailman/listinfo/xymon</a><br>
</blockquote>
</div>
</div>
</div>
<br>
<p class="MsoNormal"><b><span lang="EN-ZA" style="font-size:11.0pt;font-family:
"Calibri",sans-serif;color:#1F497D;mso-ansi-language:EN-ZA">"This email is confidential. If you have received it in error, you are on notice of its status. Please notify us immediately
by reply email and then delete this message from your system. Please do not copy it or use it for any purpose, or disclose its contents to any other person as to do so could be a breach of confidentiality. Thank you for your co-operation. "<u5:p></u5:p></span></b><span style="color:black"><o:p></o:p></span></p>
<br>
“The information contained in this message is intended solely for the individual to whom it is specifically and originally addressed. This message and its contents may contain confidential or privileged information from MTN Group. If you are not the intended
recipient, you are hereby notified that any disclosure or distribution, is strictly prohibited. If you receive this email in error, please notify MTN Group immediately and delete it. MTN Group does not accept any liability or responsibility if action is taken
in reliance on the contents of this information . Note that all personal emails are not authorized by MTN Group. ”
</body>
</html>