search

daithi-coombes / api-connection-manager

Manages connections and requests to 3rd party providers or services
0 stars 1 forks source link

Github to WordPress plugin repo #15

Open ryanholder opened 11 years ago

ryanholder commented 11 years ago

@david-coombes Have a look in to the following and let me know if it makes sense to use one of the proposed methods to have the api connection manager be available on the WordPress plugin repo.

http://konstruktors.com/articles/wordpress-plugin-svn-to-git

http://markjaquith.wordpress.com/2011/05/26/developing-on-wordpress-using-git/

daithi-coombes commented 11 years ago

@ryanholder yep looks good. Think both have the code on the svn server and then pull it to git. This is just what I need as well, a nice git task ;) I'm down for a git tutorial but it doesn't start till early feb

ryanholder commented 11 years ago

@david-coombes @mrdavidlaing Gary Jones (David you met him at WordCamp Portsmouth) just posted the following link to a repo he has worked on. I would have a look at this method first.

https://github.com/GaryJones/wordpress-plugin-git-flow-svn-deploy

@david-coombes If you have any issues with Git just ask me to help

mrdavidlaing commented 11 years ago

@ryanholder Can you use GaryJones' technique without using git-flow?

daithi-coombes commented 11 years ago

he doesn't seem to use git flow and only calls:

git push origin master
git push origin master --tags

@ryanholder @mrdavidlaing I have just tested it with a (plugin)[http://wordpress.org/extend/plugins/wp-plugin-framework/] and the wordpress repository could take days to have a plugin approved: http://wordpress-hackers.1065353.n5.nabble.com/plugin-request-wait-time-td40115.html

Think we should discuss the description here and submit a request asap.

Title: API Connection Manager
Slug: api-connection-manager

Description:
Manages connections to multiple providers by allowing modules to be built for each provider. 
Plugins can thus connect to the API Connection Manager and make requests for resources 
from 3rd parties easily.
daithi-coombes commented 11 years ago

hmmm...

just got a reply - Rejected - This doesn't seem to be a functional standalone wordpress plugin... which is correct... https://github.com/david-coombes/wp-plugin-framework

wordpress's guidlines http://wordpress.org/extend/plugins/about/guidelines/

mrdavidlaing commented 11 years ago

How ironic.

Perhaps we should bundle auto flow in with API none ton manager?

On Monday, January 28, 2013, david-coombes wrote:

hmmm...

just got a reply - Rejected - This doesn't seem to be a functional standalone wordpress plugin... which is correct... https://github.com/david-coombes/wp-plugin-framework

wordpress's guidlines http://wordpress.org/extend/plugins/about/guidelines/

— Reply to this email directly or view it on GitHubhttps://github.com/david-coombes/api-connection-manager/issues/15#issuecomment-12811748.

David Laing Open source @ City Index - github.com/cityindex http://davidlaing.com Twitter: @davidlaing

daithi-coombes commented 11 years ago

We may have to. The API Connection Manager should be ok but setting up a repository for the modules could be an issue and we could get a similar response "Rejected - This doesn't seem to be a functional standalone wordpress plugin"

I think the best plan of action here is to create the API Connection Manager wp repository and then we can always integrate the modules later if there's an issue.

daithi-coombes commented 11 years ago

@mrdavidlaing @ryanholder

moving modules to api-con folder right away....

the more I think about it the more I think we have no option but to bundle the modules inside the API Connection Manager plugin. The user will then have to upload the modules to:

/wp-content/plugins/api-connection-manager/modules
ryanholder commented 11 years ago

@mrdavidlaing @david-coombes

I would like to see the autoflow kept as a standalone plugin and perhaps our first approach is if we could meet the requirements by bundling a module with the plugin.

A suggestion from my side is one of the following;

  1. If we are going to bundle modules when submitting the plugin for review I feel we should do so with just one module. Perhaps a facebook or twitter one, this way there would be less code for them to have to approve. Updating the plugin once accepted will be easier.
  2. Alternatively we could investigate how difficult it would be to create the module to connect to the WordPress API which is OAuth2 - http://developer.wordpress.com/docs/oauth2/ and then ship the connection manager with this module as it is all related ie WordPress

Either way, I feel we submit to the repo with one module and wait for a response. If it is rejected I do know of some plugin moderators that we could email with an explanation of the plugin.

@david-coombes before submiting the API con manager plugin, get it ready and then let me review the readme file contents.

daithi-coombes commented 11 years ago

@ryanholder will do. The branch for the 'all in one' version is: https://github.com/david-coombes/api-connection-manager/tree/all-in-one

The readme concept is at: https://github.com/david-coombes/api-connection-manager/blob/all-in-one/readme.txt

There doesn't seem to be any api calls that might help us here but seems there might be something in the works: http://wordpress.org/support/topic/plugins-repository-api-for-downloadsrating At the moment think we can only scrape plugin/theme info: http://wp.tutsplus.com/tutorials/creative-coding/interacting-with-wordpress-plug-in-theme-api/

Not sure how much the plugin moderator will test, but judging by the amount of broken plugins and the response I got seems they may be only checking for standards, such as the readme, index.php file and license etc. But just in case I can leave in just one module (facebook module)