It would be worthwhile to provide support for multiple
licenses, potentially even a completely custom license
provided for each package. This will be a function of
the indexing engine.
Also categories of license. Eg. Open Source (must comply
with definition), free beer, free for non-profit use, non-
free open-source (like you can see the source if you give
all your changes back to owner), commercial but available
for time limited trialing etc.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2002-03-28
Logged In: YES
user_id=55979
I don't think CJAN should host commercial packages,
personally. I'd suggest that all archives on CJAN use one
of the following approved licenses:
The indexing engine should index from a separately provided set of licenses, where one option "custom" implies look in the package.
But the management of licenses should be separate from the
indexing engine.
[ Yes multiple licenses. Yes index on license. Yes custom license. ]
Of course a "custom" license that gets re-used a lot may get added to the list of separate identified licenses.
[ The major corporate variants - IBM, Sun, MS, Netscape, Apple, ... - may get listed to begin with. ]
As with material indexing I suggest that a hierarchical classification be used, for example:
Logged In: YES
user_id=60940
Also categories of license. Eg. Open Source (must comply
with definition), free beer, free for non-profit use, non-
free open-source (like you can see the source if you give
all your changes back to owner), commercial but available
for time limited trialing etc.
Logged In: YES
user_id=55979
I don't think CJAN should host commercial packages,
personally. I'd suggest that all archives on CJAN use one
of the following approved licenses:
http://www.opensource.org/licenses/index.html
However, I would leave the door open in the future to
change this, if the community thinks it makes sense.
Logged In: NO
The indexing engine should index from a separately provided set of licenses, where one option "custom" implies look in the package.
But the management of licenses should be separate from the
indexing engine.
[ Yes multiple licenses. Yes index on license. Yes custom license. ]
Of course a "custom" license that gets re-used a lot may get added to the list of separate identified licenses.
[ The major corporate variants - IBM, Sun, MS, Netscape, Apple, ... - may get listed to begin with. ]
As with material indexing I suggest that a hierarchical classification be used, for example:
opensource - approved
- GPL
- Full
- Lesser
- BSD
- 2 clause
- 3 clause
- unapproved
- not applied
- rejected
- clean-room poluting
non-commercial
- education
- evaluation
- time period
- cripple
- nag
- research
- personal
shareware
...
adware
postcard-ware
commercial
public-domain
...
At each level of the license index a description should be available; at the bottom level this will typically be a copy of the license.
- JonT