Migrating away from SourceForge?
list Benjamin Smith
With all the brouha and SourceForge now loading malware into installers, I wonder about the viability of SourceForge. Is there a plan to migrate to something more stable? At the very least is there a backup of the project for when they bite the dust? Relevant info here: http://www.reddit.com/r/linuxadmin/search?q=sourceforge
list Markus Stoll
yes, why not migrate to github or something like it. Probably I am not aware of all aspects how things are handled currently, but I would expect better contribution handling and issue tracking with github. For example what I do not understand, why is there a patched version of xymon in Debian, enhancing time resolutions, and why did these patches never make it back into xymon? Markus
Am 18.06.2015 um 19:23 schrieb Benjamin Smith <user-bd60c1f964ce@xymon.invalid>:
▸
With all the brouha and SourceForge now loading malware into installers, I wonder about the viability of SourceForge. Is there a plan to migrate to something more stable? At the very least is there a backup of the project for when they bite the dust? Relevant info here: http://www.reddit.com/r/linuxadmin/search?q=sourceforge
list Mark Felder
▸
On Wed, Jul 1, 2015, at 10:20, Dr. Markus Stoll, junidas GmbH wrote:
For example what I do not understand, why is there a patched version of xymon in Debian, enhancing time resolutions, and why did these patches never make it back into xymon?
Debian either never sent them upstream or Henrik was very busy and they were just lost to the depths of the INBOX... Do you have a direct link to the patches Debian has applied? Perhaps they can be imported if they don't cause problems on non-Linux platforms.
list Markus Stoll
the current debian source packet http://http.debian.net/debian/pool/main/x/xymon/xymon_4.3.21.orig.tar.gz contains a subfolder "patches" I was referring to „rrd_net_granularity", which should useful for all targets But other patches like "fix-spelling-errors" should be considerable as well Markus
Am 01.07.2015 um 20:52 schrieb Mark Felder <user-db141d317836@xymon.invalid>:
▸
On Wed, Jul 1, 2015, at 10:20, Dr. Markus Stoll, junidas GmbH wrote:For example what I do not understand, why is there a patched version of xymon in Debian, enhancing time resolutions, and why did these patches never make it back into xymon?Debian either never sent them upstream or Henrik was very busy and they were just lost to the depths of the INBOX... Do you have a direct link to the patches Debian has applied? Perhaps they can be imported if they don't cause problems on non-Linux platforms.
list Werner Maier
URL Update. seems to be the wrong link, the debian patches are here: <http://mirror.unitedcolo.de/debian/pool/main/x/xymon/xymon_4.3.21-1.debian.tar.xz>; nevertheless: a migration to github/bitbucket/gitlab or similar would also ease contributions a lot as you don't need to send patches but can easily fork and create create pull requests. but that must be left to the decission of the maintainers as it touches their workflow (which is greatly appreciated!). regards, Werner --"Markus Stoll, junidas GmbH" <user-137482a60f79@xymon.invalid> Donnerstag, 2. Juli 2015 08:33 +0200:
▸
the current debian source packet http://http.debian.net/debian/pool/main/x/xymon/xymon_4.3.21.orig.tar.gz contains a subfolder "patches" I was referring to „rrd_net_granularity", which should useful for all targets But other patches like "fix-spelling-errors" should be considerable as well Markus
--
Dipl.-Ing. Univ. Werner Maier http://www.maiers.de/
list Japheth Cleaver
Interesting. Some of these Debian patches in the set definitely do need to be applied; I'll see if I can get some of these in today. On the larger question of moving to something like Github, I think the question more comes down to the various tool sets on each site. SF has the dev mailing list and is the site home page... If we just wanted git itself, I believe there's a git module for SF which allows us to use that for submissions (much like the original flip from CVS to SVN). The SF re-packaging controversy wasn't really relevant to us, so IMO, moving to Github would be more because it's a popular place to be hosting code at than too much else. Henrik has the final call regardless :) Regards, -jc
▸
On Thu, July 16, 2015 5:31 am, Werner Maier wrote:URL Update. seems to be the wrong link, the debian patches are here: <http://mirror.unitedcolo.de/debian/pool/main/x/xymon/xymon_4.3.21-1.debian.tar.xz>; nevertheless: a migration to github/bitbucket/gitlab or similar would also ease contributions a lot as you don't need to send patches but can easily fork and create create pull requests. but that must be left to the decission of the maintainers as it touches their workflow (which is greatly appreciated!). regards, Werner --"Markus Stoll, junidas GmbH" <user-137482a60f79@xymon.invalid> Donnerstag, 2. Juli 2015 08:33 +0200:the current debian source packet http://http.debian.net/debian/pool/main/x/xymon/xymon_4.3.21.orig.tar.gz contains a subfolder "patches"
I was referring to ârrd_net_granularity", which should useful for all
▸
targets But other patches like "fix-spelling-errors" should be considerable as well Markus-- Dipl.-Ing. Univ. Werner Maier http://www.maiers.de/
list Markus Stoll
Hi, unfortunately this issue is lost somehow. I am far from blaming anyone, I know how hard it is to find some spare time for open source projects like this. But I think, moving to something like github could really improve the current situation, as other people could prepare change proposals as pull requests. This should really make things easier for the project maintainers. Markus
Am 16.07.2015 um 16:11 schrieb J.C. Cleaver <user-87556346d4af@xymon.invalid>:
▸
Interesting. Some of these Debian patches in the set definitely do need to be applied; I'll see if I can get some of these in today. On the larger question of moving to something like Github, I think the question more comes down to the various tool sets on each site. SF has the dev mailing list and is the site home page... If we just wanted git itself, I believe there's a git module for SF which allows us to use that for submissions (much like the original flip from CVS to SVN). The SF re-packaging controversy wasn't really relevant to us, so IMO, moving to Github would be more because it's a popular place to be hosting code at than too much else. Henrik has the final call regardless :) Regards, -jc On Thu, July 16, 2015 5:31 am, Werner Maier wrote:URL Update. seems to be the wrong link, the debian patches are here: <http://mirror.unitedcolo.de/debian/pool/main/x/xymon/xymon_4.3.21-1.debian.tar.xz>; nevertheless: a migration to github/bitbucket/gitlab or similar would also ease contributions a lot as you don't need to send patches but can easily fork and create create pull requests. but that must be left to the decission of the maintainers as it touches their workflow (which is greatly appreciated!). regards, Werner --"Markus Stoll, junidas GmbH" <user-137482a60f79@xymon.invalid> Donnerstag, 2. Juli 2015 08:33 +0200:the current debian source packet http://http.debian.net/debian/pool/main/x/xymon/xymon_4.3.21.orig.tar.gz contains a subfolder "patches" I was referring to ârrd_net_granularity", which should useful for all targets But other patches like "fix-spelling-errors" should be considerable as well Markus-- Dipl.-Ing. Univ. Werner Maier http://www.maiers.de/
list Japheth Cleaver
▸
On Wed, September 9, 2015 2:50 am, Dr. Markus Stoll, junidas GmbH wrote:
Hi, unfortunately this issue is lost somehow. I am far from blaming anyone, I know how hard it is to find some spare time for open source projects like this. But I think, moving to something like github could really improve the current situation, as other people could prepare change proposals as pull requests. This should really make things easier for the project maintainers. Markus
I'm somewhat agnostic personally on a move to github -- it would
definitely make it easier for social interaction within patches, partially
due to its features and partially due to its simple popularity. Again,
that would be up to Henrik for the final call.
The slowdown in commits over the last three months was actually somewhat
intentional. With the large number of versions out there, I wanted time
for stabilization with the 4.3.21 release, and to get us closer to a more
current baseline.
There were a lot of patches and feature adds going in up until right
before that tarball was cut.
Regards,
-jc