To be honest, I just don't want our project to be in the middle of this given the situation;
- we're in 1.0-beta* phase right now receiving community input on the API as we build toward 1.0
- our last beta release was January 1st 2008, licensed under the GPLv3, so it can't be used to test the AGPLv3 here
- 1.0-beta2 is completely obsolete now with many API changes/additions, making support difficult, and feedback from beta2 is no longer constructive
- svn trunk (licensed under AGPLv3) is currently unstable due to known threading issues on multicore systems, and thus should not be packaged
- 1.0-beta3 is /at least/ 6 weeks off
I've been told that other AGPLv3 licensed projects in a greater state of stability are in the pipeline toward ftpmasters, which will set precidence. If they approve them, we'll get back in that pipeline ourselves.
I believe we'll be able to offer Debian packages via our Launchpad PPA (where the Ubuntu packages will be distributed from at least until intrepid+1), so it's not like Debian users are going to be excluded. Most Debian users I've known have non-free disabled by default in any case, and maintaining our packages via PPA is less work not to mention sans being put in the proprietary software repository.
On Wed, Aug 27, 2008 at 4:55 PM, Ian Jackson <firstname.lastname@example.org>
Miriam Ruiz writes ("Re: Is AGPLv3 DFSG-free?"):
I think this is a shame.
> 2008/8/25 Arc Riley <email@example.com
> > I respectfully request that PySoy not be packaged in Debian if the AGPLv3 is
> > confirmed as non-free in the eyes of your project, as this would be
> > considered by our project as false advertising in grouping us along side
> > blatently proprietary apps.
> I closed my ITP ( http://bugs.debian.org/495172
). That doesn't mean
> that someone else might in the future not want to maintain a package
> for it in Debian anyway.