On Mon, 14 Oct 2002, David Kaufman wrote: > the way to avoid your two concerns (permissions and support) is to > participate in the community, join the mailing list of the system you like > best, and would want to contribute to, listen a while, and suggest your > changes. most likely they will be welcomed if they come with specific > patches to show the community and maintainers what benefit they provide. > this is pretty much the way open source works: you get permission if the > community wants your features, the maintainers accept your patches, > incorporate your changes, and the community continues to support the > package, with your changes.
I agree that's probably the best way to go about things if I wanted to change an existing system. But I don't know if that's the path I want to take. In my case, the code for Text::UberText is already written. To reverse engineer those changes into an existing module would require more work. In some cases, depending on the module being re-written, it may leave none of the original module code intact. -------------------- Christopher Josephes [EMAIL PROTECTED]
