RE: [PHP-PEAR] something I noticed re:licenses.
| From: | Colin Viebrock | Date: | Fri, 19 Jan 2001 21:00:18 +0000 |
| Subject: | RE: [PHP-PEAR] something I noticed re:licenses. | ||
| References: | 1 | Groups: | php.pear |
| Request: | Send a blank email to php-pear+get-1084@lists.php.net to get a copy of this message | ||
> in every file in pear, I'm seeing this:
>
> // Copyright (c) 1997, 1998, 1999, 2000 The PHP Group
>
> is this a prerequisite to being part of PEAR?
>
> I have no intention of ever releasing copyright on the
> binarycloud code that was generated at turing.
>
> also, what is the justification behind enforcing a licensing scheme?
>
> for example, if I contribute something, I want it to be GPL.
No offense Alex, but I think 13 emails from you in the last 45 minutes
is getting a bit silly.
First, read the earlier posts (mostly from Rasmus) about licensing
and PEAR.
Second, I don't know about the copyright issue, but I imagine that
the general consensus is if you "have no intention of ever releasing
copyright on the binarycloud code", then you simply won't be making that
code part of PEAR.
I sensing that we're all beating a dead horse here. Most people seem
to think that PEAR should be a repository of useful code classes. They
don't (won't?) dictate the way users should program their end applications.
Larger applications -- and framework applications that let you develop
other applications -- should build upon PEAR classes, but shouldn't
be a *part* of PEAR.
It's not quite analagous, but all Perl modules don't have to be part of
CPAN. I'm know there are companies that release proprietary modules
that follow the standard format (in terms of installation, documentation,
etc.).
Just like you aren't going to contribute binarycloud code, I'm not about
to contribute all of the work I've done for easyDNS to PEAR. However, I
will contribute some of it, because a) I think it's useful to others and
b) I'd like to "share the burden" of maintaining it ... or atleast get
other people's opinions on how to improve it. Apart from all this, I may
choose to use PEAR's standard format when coding my own applications.
And I certainly will use other PEAR modules to build my apps.
PEAR should be this "standard format", but whatever high-quality code
people want to contribute to the cause.
I think we are all saying the same thing. My 2.5 cents.
--
Colin Viebrock
Co-Founder, easyDNS Technologies
http://www.easyDNS.com/