HowTo: Contribute Services Code

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
toursheet's picture

What is the best way to organize and commit patches back to Drupal modules for Services?

Examples:
* comment.load
* comment.user
* inbox.getmessages
* node.load
* node.save
* node.delete
* user.login
* user.logout
* aggregator.load

User g10 starts the discussion with there should be a consensus bout this:

  • Scott mentioned the other time not to post patches for new services that does not belong to the core, only services that expose core functionality should be in the Service module (thus contributed thru a patch), services exposing module APIs do not belong in the Service module… IMO valid point
  • setting up a new project/module for every service that expose a custom modules API will fastly become a mess (cfr. imagefield, viewfield, etc, for cck… for services that could potentially lead to much more extra modules, who sometimes only wraps the API into a service)
  • adding those services to the custom module itself?? (not accustomised to drupal enough to see how this could be done)

Note: I was off topic so I decided to move the discussion to a new thread.

Maybe contacting the module manager is a option. Request them to have the Services patch added to the project module .tar.gz file. Also request them to update the project page to alert users that it includes services code? This idea seems like a quick fix but there should be a repository of some type or a plan to merge Services into the complete module package.

Comments

related post

g10's picture

related post on this matter

the consensus there seems to go towards:
- services for the core: submit patches that will be added to the service module
- services for custom modules: add these to the custom module itself (thus submit a patch for the custom module)

Services

Group organizers

Group categories

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: