Slashdot Mirror


Convincing Your Superiors to GPL the Code?

jakobgrimstveit asks: "At work I've been developing an intranet/extranet portal framework in PHP based on many other peoples work, including quite a few PEAR modules. I've always wanted to release the coding framework as GPL and publish it on SourceForge, and my boss has - impressively enough - not been too negative about this. This has been going around in the organization for quite a while now, and finally the reply from the company's president was (not surprisingly): 'Why should we do so?' I now have the task of writing a document listing the main reasons for GPLing the code, and this is where I turn to the highly competent Slashdot crowd: How do I convince my bosses to GPL the code I've written? I assume many other developers have the same problems trying to convince their bosses to open up their code."

2 of 139 comments (clear)

  1. Don't by Anonymous Coward · · Score: 0, Flamebait

    We don't want another fucking PHP portal system.

  2. Oh Come On... by Anonymous Coward · · Score: -1, Flamebait
    ...intranet/extranet portal framework in PHP based on many other peoples work...

    Just what we all need, another portal app. No, seriously, why worry about GPLing it? There's no demand.