Libxml2 Enterprise Edition (AGPL, from the previous maintainer)
1–10 of 19 posts
Re: Libxml2 Enterprise Edition (AGPL, from the previous maintainer)
#2Re: Libxml2 Enterprise Edition (AGPL, from the previous maintainer)
#3"Enterprise edition" is usually a sign of parody projects. But this seems to be serious?
Re: Libxml2 Enterprise Edition (AGPL, from the previous maintainer)
#4"Enterprise edition" is usually a sign of parody projects. But this seems to be serious?
When has "enterprise edition" ever been the sign of parody projects?
Re: Libxml2 Enterprise Edition (AGPL, from the previous maintainer)
#5Re: Libxml2 Enterprise Edition (AGPL, from the previous maintainer)
#6"Enterprise edition" is usually a sign of parody projects. But this seems to be serious?
When has "enterprise edition" ever been the sign of parody projects?
Re: Libxml2 Enterprise Edition (AGPL, from the previous maintainer)
#7"Enterprise edition" is usually a sign of parody projects. But this seems to be serious?
When has "enterprise edition" ever been the sign of parody projects?
Re: Libxml2 Enterprise Edition (AGPL, from the previous maintainer)
#8Re: Libxml2 Enterprise Edition (AGPL, from the previous maintainer)
#9This has me puzzled to the point of being dumbfounded: If libxml2-ee has fixed many security and other flaws in libxml2, then what's the point of directing people back to a project that is relatively flawed?
Licencing it as AGPL is also interesting, since the original was MIT, though I'm not sure they've worked out all of the kinks, given this example from one of the M4 files:
# LICENSE
#
# Copyright (c) 2011 Maarten Bosmans
#
# Copying and distribution of this file, with or without modification, are
# permitted in any medium without royalty provided the copyright notice
# and this notice are preserved. This file is offered as-is, without any
# warranty.Re: Libxml2 Enterprise Edition (AGPL, from the previous maintainer)
#10> Sorry, we don't accept code contributions and direct you to the original libxml2 project. This has me puzzled to the point of being dumbfounded: If libxml2-ee has fixed many security and other flaws in libxml2, then what's the point of directing people back to a project that is relatively flawed? Licencing it as AGPL is also interesting, since the original was MIT, though I'm not sure they've worked out all of the…