Howdy, I would like to say that I share japhb++'s slight concerns in copying in code without original copyright notices. I wanted Tapir to live in ext/ in the same way as pmichaud++'s NQP. I think fperrad added some features and renamed various files, so it is hard to say what percentage of code Tapir on github and TAP::* in parrot core share. If fperrad++ could describe what modifications he made, that would be very helpful. My hope would be to incorporate all his new modifications, with his permission, into the Tapir on github and then get Tapir installed into ext/.
With this setup, developers have the freedom to work on Tapir and Parrot gets to choose exactly which version of Tapir it considers stable and wants to tie to a specific release. As it seems that Parrot is going in the direction of git, slowly but surely, NQP and Tapir can be submodules, so that parrot.git will control the exact commit of each that it wants, and there will not be any "copy into parrot and commit" stuff. A git submodule is roughly equivalent to an svn external. Duke On Thu, May 13, 2010 at 11:26 AM, Geoffrey Broadwell <[email protected]> wrote: > Starting at http://irclog.perlgeek.de/parrot/2010-05-13#i_2327099 we had > a short discussion regarding the fact that at least twice recently code > from an external project has been copied directly into the parrot > repository, without retaining a copyright notice or reference to the > original project/repo that the code came from. > > As Coke said, "We cannot just copy code we don't own into the repo and > claim it." I think in both cases (code from Plumage and from Tapir), > neither of the owners had a problem with Parrot using the code -- in > fact we had both hoped to eventually keep snapshots in ext/ as nqp-rx > does today -- but that wasn't the point. > > As a matter of copyright management we can't just import code from other > projects without a copyright notice (and probably a link to the original > project). As a matter of supportability it's important to keep in touch > with the upstream project regarding bugfixes and the like. And as a > matter of good manners, it's nice to at least talk to the original > project before copying the code. At the very least they may suggest how > they'd prefer it be done, or in fact already have a process for working > with downstream projects harmoniously. > > Does PaFo have an official policy on copying external code? (Assuming > the license is already compatible, of course.) > > > -'f > > > _______________________________________________ > http://lists.parrot.org/mailman/listinfo/parrot-dev > -- Jonathan "Duke" Leto [email protected] http://leto.net _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
