[Xastir] Xastir development source now on github, sourceforge CVS now closed to new commits.

[Lee Bengston]

On Fri, Jul 8, 2016 at 7:44 PM, Tom Russo <russo at bogodyn.org> wrote:

> On Fri, Jul 08, 2016 at 04:38:24PM -0700, we recorded a bogon-computron
> collision of the <xastir at trinnet.net> flavor, containing:
> >
> > Hello Tom,
> >
> > I'm working on updating my Xastir documentation for Centos here to now
> > use Github/Git vs. sf.net/CVS:
> >
> >
> http://www.trinityos.com/HAM/CentosDigitalModes/hampacketizing-centos.html#19b.xastir
> >
> > In doing that update, I noticed the current xastir.spec file which is
> > seemingly 13 years old (see change log at the end of the file) shows:
> >
> >     %configure --without-graphicsmagick --with-rtree
> >
> >        That seems BAD since we know that GraphicsMagick support is
> > probably more reliable than say ImageMagick today.
>
> Yep.
>
> Here's the thing.  Folks come and go on this project, contributing little
> things for their favorite operating system, scripts that have made their
> own lives easier, etc.  And they got committed into CVS, even though the
> developers themselves don't use them.
>
​
Wouldn't a developer still have to commit stuff like that into CVS?​

​I've written Xastir related scripts before, but I've never tried to get
them into the repository.  I did show Curt a revised version of the ads-b
script a while back, but that was an attempt to get him to incorporate some
or all of my changes into his - not to add a separate script to the repo.
Did some non-Developers have the rights to commit changes into CVS?

​----- < snip>​ ----


​Lee - K5DAT​