By aaaaa on

Hello,
I am looking for someone to develop a few very simple custom modules for me. My site uses drupal csv version. This is a paying job. If interested, Please contact me : sse_fr @ yahoo.com

Thank you,

Comments

gatezone’s picture

gatezone commented

I know there is a services area. Isn't there someway that custom or so-called custom development/improvements in modules could benefit Drupal.org as well as the developer? Maybe a section where a nominal paypal donation is required or requested? Obviously developers work hard on the core and the modules and 'micro donations' could add up and help provide developer tools, server space, testing/demo site hosting. I'd be willing to donate or heavily discount hosting space for drupal developers as part of a process that would provide support for developers.

I realize it would be difficult to differentiate between custom and 'normal' modules, but one distinction would be if a module was commissioned it would be in the donation section. Organizations or individuals requesting customization would donate a certain amount but they would agree to the module being included in the donated module section because it would help keep their initial 'donation' lower than it would be otherwise.

Just some thoughts as I know I will have a need for 'custom' work at sometime and would be happy to share the results, but why not do it in a way that puts more resources or cash in the pocket of developers. It's ok to use that four letter word on an open source site isn't it }:-) ?

adrinux’s picture

adrinux commented

As I understand it, Drupal is licensed under the GPL and all modules must therefore also be licensed under the GPL. Thus anybody developing a custom module, either from scratch or by modifying an existing one is duty bound to share it with the community. It's in this way that Drupal gains, by gaining more code, modules and patches. The money goes to keeping a roof over the head and food on the table for the developer writing the code.

A donation system as described really isn't necessary, and what about all the work setting up and maintaining such a system?

adrinux
adrinux@ntlworld.com

Adrian Simmons
adrinux@anaath.at

gatezone’s picture

gatezone commented

Well that sounds definitive... donation systems are not difficult to set up. Sounds like from your perspective end users, administrators, and end-users have everything they need in the current system and module process.

On the other hand, maybe there are other ways of approaching development, innovation, motivation, stadandards, and coordinated timing of releases, modules, and patches. Just so I am not misunderstood, I'm not suggesting charging money for GPL software - just thinking outloud about the process of end users or administrators (different breed than developers) who need something and can't sit around waiting.

The more Drupal is in use at organizations and in mission critical situations the more important it will be for core (not system core) modules to be available in 'concert' with releases. Also for end-users and administrators to understand how they can, or cannot, have an impact on the process.

bertboerland’s picture

bertboerland commented

From what I understand from the GPL and some googeling, it is correct to state that all modules have to be GPL licences as well, unless the dont share datastructures or calls to the GPL core product, which makes it a program on it's own; not a module IMHO. Or you could license the module under a GPL compatible license.

See the short note regaring modules in the faq of the GPL page.

In the X-nuke community, this issue has been discussed in many threads, not all based on knowlegde. But this pdf describes the modules vs license in (relative) depth.

Hope this helps.


(not, I'm just intersted in IP, you probably want to get some real legal advice from a pre)

--
groets

bertb

--
groets
bert boerland

cel4145’s picture

cel4145 commented

Isn't that a little misleading, though? There is no clause in the GPL which implies that it has to be shared, only that if distributed, it has the GPL.

So if someone was paid to write a custom module, the client would receive a GPL licensed version. But neither the programmer nor the client are under obligation to share it with anyone else.

That being said, I do think it's a good idea to do so. It makes more sense to share it, for a lot reasons (thinking, for instance, of Eric Raymond's The Cathedral and the Bazaar).

Gunnar Langemark@www.langemark.com’s picture

Gunnar Langemark@www.langemark.com commented

Lots of people seems to think that GPL equals "source must be distributed for free and product cannot be commercial". That is not so. You can charge for your work AND for your module, but once you distribute it you MUST distribute the source with it - free of charge!

It is ONLY if you choose to distribute your work (module, enhancement or other) that the GPL consequences kick in.

There is NOTHING in the GPL which prevents you from charging money for your module.

Dropping in from Langemarks Cafe.

boris mann’s picture

boris mann commented

OpenSourceXperts has infrastructure in place to ask for bids. There is a category for Drupal developers (yes, I am on the list).

You might want to consider creating an account there, putting together your requirements, and then posting here to let people know that you are open for bids. If you desire, you can also have a "feature fund" where multiple people fund a particular feature.

gatezone’s picture

gatezone commented

Whatever... for those of us who need to deliver rational systems to organizations with the most basic security and self-administering design/graphics requirements it's a challenging process. I'm hard-pressed to plan what I could deliver to organizations (let alone when). And as I've said before there are a lot of organizations that could benefit from the backbone taxonomy features of Drupal.