On 04/11/09 22:11 +0100, Hartmut Goebel wrote: > Cédric Krier schrieb: > > > First, I'm not affraid of people who will run a modified version of Tryton > > as > > service. Because they will have a lot of work to follow us with release as > > they will need to patch each time. I think contributing is the cheapest way > > to > > maintain your code. > > Let's imagine a SaaS-Provider implementing a complete adoption to German > requirements. This provider has put quite some effort into his extension > modules and offers services to small and medium companies. As programs > like Lexware or Sage show, many of these companies are quite happy even > with a fixed function set like in this case. > > Such a company will not contribute the code, since these extensions / > adoptions are the asset. This is what makes up the business case.
GPL or AGPL does never constrain to contribute the code. It gives just some rights to the user. > > > So with an AGPL software, we are required to distribute the > > code to at least all employees of the company. This can prevent us to work > > with > > those companies. > > As I read the AGPL we do not need to *distribute*, but only to give > access to the source. And I'm unsure if this really includes the users > in a company. One may argue, the licencee is the company and there is no > licence agreement between the software vendor and the employee. Thus the > employee doe not gain any rights nor does he have any obligations -- as > he does not have to fulfil any obligations out of the licence. As I'm not a lawer and for me it is not clear. I prefer to not use a license that I don't understand clearly. > > > Third, AGPL software needs to provide the source code through the network. > > That means we must develop some way to create an archive of the running code > > and so we must have the source code on the server not only pyc files. And > > what > > about data that are in xml file but have restricted access right? > > Most of Tryton is already available through the network: via the > mercurial repository :-) So custom modules can simply be provided using > another mercurial repository -- a simple clone of the staging repos. In the AGPL, it is question to give an url to fetch the running code. And what about custom code that you don't want to publish? And what about a patch that is applied not yet released? ... -- Cédric Krier B2CK SPRL Rue de Rotterdam, 4 4000 Liège Belgium Tel: +32 472 54 46 59 Email: [email protected] Jabber: [email protected] Website: http://www.b2ck.com/
pgpbQIYFXXtmk.pgp
Description: PGP signature
