Hi,
I'm looking to bring a module (import content from 5.x->6.x via services) that I made for a client into a drupal.org release; however, it relies on a couple small services I created:
1) list of content types
2) list of nodes by content type
3) list of organic groups (special version of (2) I guess)
4) nodes by organic group
5) comments by node
#5 is addressed better by #182069: Exposing Commenting Functionality via Services - however, the other four seem to be unaddressed. Looking in the Services group on groups.drupal.org, it would seem all four would fit into 'core functionality' services, and I should submit a patch here. However, since they're kind of specific/advanced type features, I didn't know if I should include them with my module, or possibly create a separate module, similar to the views add-on pack. Which is the appropriate course of action? Looking through the comments issue, I see there's some work I need to do in regards to access & some changes to services, but before I make the patches, etc. for this issue queue, I wanted to check and see what the developers thought would be appropriate in terms of placement.
Thanks for a great module.
Bryan O'Shea
Obsidian Design
Comments
Comment #1
marcingy commentedAny services that don't expose Drupal core functionality should be in a seperate project. You will need to apply for cvs access to be able to do this.
Comment #2
marcingy commented