Forum OpenACS Development: Re: Porting Project/Open (Intranet Module) to OpenACS 5.0

<blockquote> I don't think we have any problem with proprietary
code on top of OpenACS, but generally you're not going
to interest very many other people in working with
your code unless you release your code under some sort
of open source license.
</blockquote>

Let's asume the "Translation Workflow" module: Do you think anybody in this community cares whether this module is GPL or a "Partner License"? Do you think they would help if it were GPL? Or what about the "Translation Freelance & Quality" module implementing provider management and statistical process control?... 😊

This is the type of modules nobody in the community cares about, but that provide a complete solution to a translation company, so that they are willing to pay for the system.

A more critical example is the timesheet/cost module, but this is GPL because it's based on the original ACS 3.4 Intranet code.

I hope it's getting a bit clearer where a PL makes sense and where not, right?

Frank