Talk:Requests for comment/Distribution and deployment

Wordpress
I notice that Wordpress has a really nice extension (aka "plugin") management system; maybe that would be good to use as an example. Tisane 04:54, 25 May 2010 (UTC)

Thanks for the suggestion :) It indeed has a very nice system (from the users point of view anyway), and I'm planning to have a good look at it. Do you know any high level developer docs on this though? I have not been able to find any, and have heard some rather bad things about how easy it is to reverse engineer wp...

-- Jeroen De Dauw 10:37, 25 May 2010 (UTC)
 * Perhaps you'll want to check out pages such as http://codex.wordpress.org/Developer_Documentation and http://codex.wordpress.org/Function_Reference#Action.2C_Filter.2C_and_Plugin_Functions, if you haven't already? I wasn't thinking so much that you would want to try to cannibalize actual code, but rather that the concepts could be replicated with MediaWiki. This actually doesn't strike me as being a particularly difficult project, by the way. Isn't it just a matter of inserting/deleting/modifying lines of code in LocalSettings.php through a web-based interface? Oh, and I guess searching for and downloading extensions, and keeping track of all the configuration parameters. OK, that could be a pain in the neck. Tisane 12:47, 25 May 2010 (UTC)
 * Reading more carefully over this page, I see that you had already mentioned Wordpress. Great minds think alike! Tisane 12:48, 25 May 2010 (UTC)


 * Thanks for the pointers :)


 * I don't think the goal of this project is easy to achieve. The concept is simple, actually implementing it with MediaWiki is not. Otherwise it would have happened long ago.


 * -- Jeroen De Dauw 16:25, 25 May 2010 (UTC)
 * Yeah, you're right. Sorry, I didn't mean to minimize the magnitude of the work you're doing. Tisane 16:50, 25 May 2010 (UTC)

Perhaps another useful resource would be /wp-admin/includes/ -> plugin.php at http://phpxref.ftwr.co.uk/wordpress/nav.html?_functions/index.html Tisane 14:07, 26 May 2010 (UTC)

Standardization of extension data
If we're going to emulate the Wordpress model, the wiki owner should be able to search for plugins by keyword, author, or tag. An extension matrix is already automatically generated by a bot, but as you can tell from looking at that matrix, the extension data on this wiki is not in a sufficiently informative and standardized form. E.g., some extensions are lacking basic data, or have it only in the text and not in the infobox. A way is needed to make it sufficiently informative and standardized and keep it that way. I'm thinking that a bot could be used to detect such issues and automatically tag extensions as being not in compliance.

Following up can be done either similarly to WildBot (i.e. simply putting a notification template on the article talk page and then removing it when the issue is fixed) or more aggressively, by putting a message on the author's talk page. The author could be identified using the infobox, or, if the author info is not available there, the bot could look at the page history and contact the person who created the extension page. Since not everyone checks their MediaWiki.org watchlist regularly, an email might be sent if, after the notification is posted, they don't make any edits to MediaWiki.org within a certain time (say, a week). Ideally, we will want to contact these authors right after they make the edits; therefore, a bot that checks the MediaWiki.org RecentChanges IRC feed (if such a thing exists) and responds immediately to these issues would be good. We might also use Extension:Semantic Forms to encourage the filling out of basic extension info.

How might tags be generated? Categories could be used for that purpose. E.g., everything in Category:Facebook extensions will get the "Facebook" tag. Since some categories have subcategories, these categories should be recursively crawled in order to obtain these tags. The category pages themselves could include an infobox or Semantic MediaWiki item noting the appropriate tag that the extensions in that category should go under.

What about keywords? There should probably be a standardized list of keywords, much like what Bugzilla uses. The list will be editable, but if a keyword deviates from what is in the list, then the bot will automatically flag it as non-standard and follow up. Template:Extension can be revised to have keyword1, keyword2, etc. just like it currently has hook1, hook2, etc. Maybe a similar_extension1, similar_extension2, etc. item should also be added.

Extension:ExtensionDistributor should collect statistics on how often each extension is downloaded, and/or reliable means of assessing how many wikis use an extension should be used to determine an extension's popularity, so that the interface can flag certain extensions as being popular. SVN should also provide information on new and recently updated extensions. Wiki owners should also be told by the interface if an extension is experimental, beta, etc. and if it has any significant known problems. E.g., Extension:FBConnect is not really something a wiki owner should install at this time, unless he is willing to do some troubleshooting and/or development on it to work out the kinks. Maybe there should be an extension rating system as well (e.g. 1-5 stars).

The extension manager should compare the MediaWiki version of the present installation to the versions that are compatible with the extension. Thus, if the user has MediaWiki 1.16, and the extension is known to not work with anything later than 1.14, the user should be apprised of that fact, or the extension should be filtered entirely out of the search results if the user elects to do so. This project should also be done in conjunction with a switch to a totally web-based upgrading functionality replacing the need to run update.php from the command line. Tisane 13:18, 26 May 2010 (UTC)