Posted by rubyji on February 2, 2009 at 7:38pm
Anyone have suggestions about where we should start with this group? Some of the things I think would be helpful are...
- Sharing solutions, tips & tricks we have figured out.
- Recommending specific third-party solutions or modules or whatever.
- Q & A about the Salsa API, Drupal hooks, etc.
- Ranking our needs and priorities so that Drupal and Salsa developers can get a sense of the demand (maybe even pooling money to support creation of the modules we want)
- Developers can talk to each other about they're working on, what they've learned.
- Show off our cool Drupal/Salsa sites.
What else?
Comments
Well if we are really
Well if we are really looking at creating a module or working with APIs i definitally think we should find a salsa developer that can help us with such things.
I know they have a few documentation pages on their various APIs, both internal and external. However with the external stuff, what worked a few months ago for me when i started tinkering, suddenly stopped working and i haven't had time to work on it since then. Perhaps getting someone to update their documentation would help?
What do we have? What do we need?
I like Ruby's idea of "Ranking our needs and priorities so that Drupal and Salsa developers can get a sense of the demand". Basically, determining our "wish-list" of modules. There will likely be some low-hanging fruit that we can knock-out fairly easily.
For example, my org wants to have a module that simply syncs the drupal site login with the Salsa database. So if users come to the site and create a username and password - and also enter their name, email, etc... The name, email and any other pertinent info automatically goes into Salsa.
I'll start a "Module Wish List" thread...