Is there any issue tracking system provided for plugins, in addition to the subversion repository? Just wondering... — Sam Wilson 01:55, 28 Sep 2007 (UTC)
This page suggests to "submit to both wp-plugins.net and wp-plugins.org", but these two sites appear to be controlled by WP now and no longer independent. Is submission to these two sites still recommended or for that matter even possible? Should this section be edited/removed? User:Jeremyshapiro
I know. SVN is for developers. But WP plugin API will be more liked if the SVN instructions include the point of view of a semi-developer.
I bet the number of non-professional developers who have a great idea for a plugin is higher than the number of developers who can actually code without a mouse (command-line)
Even higher the number of EXPECTED new developers who will become developers just by using WP API.
So, the API rocks, and the reason why it was created: to allow more people, not programming engineers, to develop a PlugIn. More work for you, less for Us.
SVN also rocks and that's the right way to manage the files. BUT that SVN page is the bottle-neck of the Plugin API.
There are apps out there for that! There are even ways to do it IN OUR DESKTOP and then using the app to commit only. But this page instructions don't say a word. It's scary.
So please, don't force us, users, to win our wings to share the programmers pain. You can keep managing SVN the geeky way, and let us manage the files in our Finder (Explorer? for Windows)
They'll still be uploaded (committed) the required way, but allow us to make that SVN page a little… less geeky.
Beyond this page, I can't edit a thing.
Please add a few NON-GEEKY how-to's, or unlock the page for changes :)
Thanks.
SocialBlogsite 19:20, 3 February 2012 (UTC)
One of those websites was abandoned one year ago but anyway I don't think codex should favor any external page (this could generate a lot of irrelevant discussions).
Jordi Cabot 16:55, 8 August 2014 (UTC)