Posted by aaronbauman on October 25, 2010 at 5:09pm
5 followers
| Project: | Parser Salesforce |
| Component: | Code |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Initial version was posted to the salesforce queue:
#453846-10: FeedAPI Integration -- needs maintainer
This should probably be turned into some kind of release on the module page.
Comments
#1
Let me know if you are having issues with CVS, and I can try to help.
#2
I cleaned up some of the code comments, added in a version number, and a basic README with a link to a screencast from the original module author for how to configure this module. No code was available in CVS head so I used the file that had previously been posted in this issue #453846: FeedAPI Integration -- needs maintainer as my starting point.
#3
Thanks, kostajh - I think that what Aaron means is for an actual release to be made on the project page, which would require code to be committed to CVS head first.
#4
Yeah I know, just thought putting up the code here would be helpful until code is committed to CVS head.
#5
I understand. The code is up on the other issue, as well, but maybe people will find it more easily here.
I appreciate the changes you made, although I don't know if I will have personal use for this module, at least not at this time, so I haven't reviewed.
#6
I spent some time today working on porting this module to Feeds, although porting is not really an accurate description since the integration with Feeds is very different from FeedAPI. The project is up on Github here: https://github.com/kostajh/feeds_salesforce. The module is functional but it needs work.
What I would propose is that we create a 1.x branch that works with FeedAPI (using the old parser_salesforce code) and a 2.x branch for the code that works with Feeds. If it's okay with you @pearlbear, I would like to request CVS access to work on this here rather than on Github. Please let me know how you'd like to move forward.
#7
Sorry I haven't gotten to this before hand. I think it makes a lot of sense to create the 1.x as well as 2.x branches. I'm happy to have @kostajh as co-maintainer to work on this module.
#8
FYI, kostajh is now co-maintainer of this project.
#9
Thanks, kiam!
#10
Hey all,
Before tagging a release for this project, I wanted to see what folks think about renaming it. The name "Parser Salesforce" would be misleading for the 2.x branch of this project because with feeds.module, importers, processors, and parsers are all separate components. The 2.x code I shared in this thread provides an importer and a processor but not a parser. So having it exist under the name Parser Salesforce might be a bit confusing to people.
What I would suggest is:
If this sounds okay, I will create the new project and deprecate this one.
-Kosta
#11
@kostajh: I think that sounds reasonable. Too bad you can't just rename a project on d.o...
#12
The only thing you can do is to create another project, and move all the code to the new project.
#13
Thankfully, there is no code for this yet. But it would be nice someday to be able to delete old projects.
#14
A new project has been created, http://drupal.org/project/salesforce_feeds. The 1.x branch compatible with FeedAPI has been committed, and I'll be committing the 2.x branch that works with Feeds later this week. Thanks everyone!