From WordPress point of view — not much, beyond plugin’s header (and even there) it is hardly policed. From licensing point of view you obviously need to accommodate requirements of both licenses accordingly. At least — make clear that your combined work is under GPLv3 and which parts of it are based on Apache License … Read more
Here is how you should be updating your plugin. The WordPress install sends data to the repository and the repository sorts out the versioning and talks back to the install. Here is an article by Mark Jaquith on this subject, and the lengths to go though to turn it off. There has been a vigorous … Read more
I guess the following things could be a problem: Adding : after header comment “keys” Not using all possible header comments – WP reads the first 8bit (in a not really pleasent way), but I don’t know how the repo does Move the /* into the same line as the <?php tag If nothing of … Read more
The updater works based on the plugin’s installation path and the name of the file containing the header. I’m guessing both plugins are housed in a /breadcrumbs folder (since that seems to be Yoast’s setup. Though Yoast’s plugin uses yoast-breadcrumbs.php for its main file. I’m assuming you’re using a different filename, so you have indeed … Read more
If it’s the first time you are using the assets folder, do not forget to: svn add assets/* and commit the updates. 😉 I was wondering why my banner image / screenshots were not showing and realized I didn’t even add them to SVN! HTH!
By default the plugins are ranked by “relevance” and the only people who know how that algorithm is weighted work for wordpress.org (it’s doubtful they are going to let anyone in on it). Downloads and rating are not the main components, just one of many including keywords, date, and how many beers you buy Otto. … Read more
No, the wordpres.org SVN repositories are not for development and there are no plans to change this. So you either have to ask on support forum, or if the plugin is on an open GIT repository search for it on GitHub.
Yep, you can pass the initial revision from which to start scanning: git svn clone -s -r387893 http://plugins.svn.wordpress.org/your-plugin/ You can hunt down that revision by using this command: svn log http://plugins.svn.wordpress.org/your-plugin/ The last line shows the earliest revision. Source: http://teleogistic.net/2011/05/revisiting-git-github-and-the-wordpress-org-plugin-repository/
When submitting a plugin, the slug becomes the sanitized plugin name, as submitted. The “Name” of the plugin can change after this, but the slug remains the same forever more. When WordPress needs to check for a plugin update, it gets all the header information of the plugin and the directory name that the plugin … Read more
Step 1 – Make sure things are formatted correctly WordPress itself depends on the headers at the top of your main plugin file. In many cases, if your plugin is “My Cool Plugin” this file is my-cool-plugin.php in the main directory of your folder. Make sure the top part of the file follows this format: … Read more