Currently this project really miss roadmap. The idea itself to connect different apps together using Rules looks really great. So would be nice to know what the final goal of this project: whether it should be only base API for further custom development of "connectors", or it should be a package of submodules that provides all possible integration with different apps, or maybe other goal.
Anyway, I'd love to hear some ideas regarding future of this module. Please, feel free to update issue summary if you need.
Comments
Comment #1
crizThanks for open this discussion! What the project mostly needs is people joining in and help to move it forward.
As fluxkraft consists of multiple parts we need to distinguish.
The fluxkraft distribution
https://www.drupal.org/project/fluxkraft_distro
https://github.com/crizzirc2/fluxkraft_distro
Goal: Providing a self hosted software to connect and automate web services like Twitter or Facebook (similar to ifttt.com)
Target group: Also non-technical users
Status:There is a full release but it would need some serious work regarding usability, documentation and reliability. Co-maintainers needed. See list of issues further down.
The fluxkraft module suite
Goal: Extending existing or new Drupal sites to integrate external webservices using Rules.
Target group: Site builders.
Status: Needs work. See #2060775: fluxkraft/rules not reachable when installing the module without the distro
There a lot of ideas and usecases here. E.g. post nodes automatically on Facebook or vice versa. Most issues for the distro apply also here.
The fluxservice module
https://www.drupal.org/project/fluxservice
Goal: Having an API for storing authentications.
Target group: Developers
The fluxservice module can be used on its own and function as a way to store service authentications per user or sitewide.
E.g. you can use this authentications to query services like Facebook or Twitter by custom code, you don't need to use rules for this. Also various contributed modules using external service authentications can depend on it.
Status: Healthy. Current maintainers are interested to move it further.
Important issues (please help to complete this list):
Documentation:
Usability:
Reliability:
Other issues:
There are for sure some other issues that needs to be worked on. Feel free to open issues!
There is also a Google Summer of Code project for fluxkraft, but I don't know the current status: https://groups.drupal.org/node/407793#project11
Some ideas about future usecases are also mentioned in this presentation: http://drunomics.github.io/automating-web/#/9
Comment #2
spleshkaThanks for your answer. I will find couple free hours and review all this links. Then we can continue our discussion :-)
Comment #3
dahacouk commentedAlso, it would be great to check in with the Drupal Social Initiative as we have quite a number of interested people in creating harmonised and abstracted social integration APIs. I know we had some discussions a while ago but perhaps would be good to pick up the contact. Cheers!