<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="bbPress/1.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
		>
	<channel>
		<title>WordPress Plugins &#187; Tag: musician - Recent Posts</title>
		<link>http://wordpress.org/extend/plugins/tags/musician</link>
		<description>WordPress Plugins &#187; Tag: musician - Recent Posts</description>
		<language>en-US</language>
		<pubDate>Sat, 18 May 2013 12:43:17 +0000</pubDate>
		<generator>http://bbpress.org/?v=1.1</generator>
				<atom:link href="http://wordpress.org/extend/plugins/rss/tags/musician" rel="self" type="application/rss+xml" />

		<item>
			<title>Events byMike</title>
			<link>http://wordpress.org/extend/plugins/eventsbymike/#post-46381</link>
			<pubDate>Thu, 29 Nov 2012 18:40:59 +0000</pubDate>
			<dc:creator>mordauk</dc:creator>
			<guid isPermaLink="false">46381@http://wordpress.org/extend/plugins/</guid>
			<description><![CDATA[<p>Emailed Author: WordPress includes its own version of jquery, which has been rigorously tested with WP and many of the most common plugins. In order to provide the best compatibility and experience for our users, we ask that you not package your own (especially not an older version) and instead use wp_enqueue_script() to pull in WordPress’s version.</p>
<p>Please review <a href="http://codex.wordpress.org/Function_Reference/wp_enqueue_script" rel="nofollow">http://codex.wordpress.org/Function_Reference/wp_enqueue_script</a> and update your plugin accordingly.</p>
<p>Keep in mind: Offloading the default jquery and other scripts to Google is similarly disallowed. If your code doesn't work with the built-in jQuery, it's most likely a noconflict issue. If you can't guess, we -really- want you to use our jquery, and if you can't, we need to know why so we can fix things for everyone.</p>
<p>When you've corrected your code, reply to this email with the updated code attached, or provide a link to the new code.
</p>]]></description>
					</item>
		<item>
			<title>Events byMike</title>
			<link>http://wordpress.org/extend/plugins/eventsbymike/#post-46354</link>
			<pubDate>Thu, 29 Nov 2012 10:26:25 +0000</pubDate>
			<dc:creator>byMike</dc:creator>
			<guid isPermaLink="false">46354@http://wordpress.org/extend/plugins/</guid>
			<description><![CDATA[Ein PlugIn zur Anzeige von Auftrittsterminen.]]></description>
					</item>
		<item>
			<title>Bizarski Cute Gigs</title>
			<link>http://wordpress.org/extend/plugins/bizarski-cute-gigs/#post-45671</link>
			<pubDate>Tue, 13 Nov 2012 02:16:54 +0000</pubDate>
			<dc:creator>Ipstenu (Mika Epstein)</dc:creator>
			<guid isPermaLink="false">45671@http://wordpress.org/extend/plugins/</guid>
			<description><![CDATA[<p>Emailed Author: Your plugin is incomplete and is missing a valid readme.txt file. Please create one based on this:<br />
<a href="http://wordpress.org/extend/plugins/about/readme.txt" rel="nofollow">http://wordpress.org/extend/plugins/about/readme.txt</a> </p>
<p>Alternately, you can use this tool to generate one:<br />
<a href="http://tools.trepmal.com/wp-readme-generator/" rel="nofollow">http://tools.trepmal.com/wp-readme-generator/</a> </p>
<p>A readme.txt is needed so your plugin will display correctly in our repository, but also so we can make sure you're providing the users with all the information they need before they install your plugin. Our goal with this is to make sure everyone knows what they're installing and what they need to do before they install it. No surprises :)</p>
<p>This is especially important if your plugin is making calls back to your own servers. For the most part, we do not permit offloading of images or code, however in the case where you are providing a service (like Disqus or Akismet or Twitter), we permit it. The catch is you have to actually explain this to the layman in your readme, so they know where data is going.</p>
<p>Please send a link so the completed plugin can be downloaded. Alternately you can reply to this and send a .zip or .rar file.
</p>]]></description>
					</item>
		<item>
			<title>Bizarski Cute Records</title>
			<link>http://wordpress.org/extend/plugins/bizarski-cute-records/#post-45670</link>
			<pubDate>Tue, 13 Nov 2012 02:16:54 +0000</pubDate>
			<dc:creator>Ipstenu (Mika Epstein)</dc:creator>
			<guid isPermaLink="false">45670@http://wordpress.org/extend/plugins/</guid>
			<description><![CDATA[<p>Emailed Author: Your plugin is incomplete and is missing a valid readme.txt file. Please create one based on this:<br />
<a href="http://wordpress.org/extend/plugins/about/readme.txt" rel="nofollow">http://wordpress.org/extend/plugins/about/readme.txt</a> </p>
<p>Alternately, you can use this tool to generate one:<br />
<a href="http://tools.trepmal.com/wp-readme-generator/" rel="nofollow">http://tools.trepmal.com/wp-readme-generator/</a> </p>
<p>A readme.txt is needed so your plugin will display correctly in our repository, but also so we can make sure you're providing the users with all the information they need before they install your plugin. Our goal with this is to make sure everyone knows what they're installing and what they need to do before they install it. No surprises :)</p>
<p>This is especially important if your plugin is making calls back to your own servers. For the most part, we do not permit offloading of images or code, however in the case where you are providing a service (like Disqus or Akismet or Twitter), we permit it. The catch is you have to actually explain this to the layman in your readme, so they know where data is going.</p>
<p>Please send a link so the completed plugin can be downloaded. Alternately you can reply to this and send a .zip or .rar file.
</p>]]></description>
					</item>
		<item>
			<title>Bizarski Cute Records</title>
			<link>http://wordpress.org/extend/plugins/bizarski-cute-records/#post-45635</link>
			<pubDate>Mon, 12 Nov 2012 14:56:34 +0000</pubDate>
			<dc:creator>sparxdragon</dc:creator>
			<guid isPermaLink="false">45635@http://wordpress.org/extend/plugins/</guid>
			<description><![CDATA[Showcase your albums and tracks. Great for artists and record labels.]]></description>
					</item>
		<item>
			<title>Bizarski Cute Gigs</title>
			<link>http://wordpress.org/extend/plugins/bizarski-cute-gigs/#post-45634</link>
			<pubDate>Mon, 12 Nov 2012 14:56:06 +0000</pubDate>
			<dc:creator>sparxdragon</dc:creator>
			<guid isPermaLink="false">45634@http://wordpress.org/extend/plugins/</guid>
			<description><![CDATA[An elegant way for artists to showcase their concerts, shows, and gigs.]]></description>
					</item>
		<item>
			<title>MF Gig Calendar</title>
			<link>http://wordpress.org/extend/plugins/mf-gig-calendar/#post-40157</link>
			<pubDate>Thu, 05 Jul 2012 20:34:38 +0000</pubDate>
			<dc:creator>Ipstenu (Mika Epstein)</dc:creator>
			<guid isPermaLink="false">40157@http://wordpress.org/extend/plugins/</guid>
			<description><![CDATA[<p>Emailed Author: Hi,</p>
<p>All plugins are expected to be submitted with the code complete and ready to go, including a valid readme.txt file.  Could you please reply with a link so the plugin can be downloaded? Alternately you can reply to this and attach your .zip or .rar file.</p>
<p>Please reply with 7 days. If a reply is not received the submission will be rejected and you will have to submit the plugin again, with code, should you want your plugin hosted.</p>
<p>Thanks.
</p>]]></description>
					</item>
		<item>
			<title>MF Gig Calendar</title>
			<link>http://wordpress.org/extend/plugins/mf-gig-calendar/#post-40131</link>
			<pubDate>Thu, 05 Jul 2012 15:50:03 +0000</pubDate>
			<dc:creator>Matthew Fries</dc:creator>
			<guid isPermaLink="false">40131@http://wordpress.org/extend/plugins/</guid>
			<description><![CDATA[A simple event calendar created for musicians but useful for anyone. Supports multi-day events, styled text, links, images, and more.]]></description>
					</item>
		<item>
			<title>Reverberation</title>
			<link>http://wordpress.org/extend/plugins/reverberation/#post-40079</link>
			<pubDate>Wed, 04 Jul 2012 13:37:08 +0000</pubDate>
			<dc:creator>wcjcs</dc:creator>
			<guid isPermaLink="false">40079@http://wordpress.org/extend/plugins/</guid>
			<description><![CDATA[Add ReverbNation&#039;s HTML5 widgets to your WordPress with versatile shortcodes, visual editor button, and several customization options.]]></description>
					</item>
		<item>
			<title>WP VibeDeck</title>
			<link>http://wordpress.org/extend/plugins/wp-vibedeck/#post-30594</link>
			<pubDate>Tue, 27 Sep 2011 14:47:35 +0000</pubDate>
			<dc:creator>ecurtain</dc:creator>
			<guid isPermaLink="false">30594@http://wordpress.org/extend/plugins/</guid>
			<description><![CDATA[Play and sell your music online, for free.  Embed the VibeDeck audio player &#38; store using a simple shortcode or widget.]]></description>
					</item>
		<item>
			<title>ArtistDataPress</title>
			<link>http://wordpress.org/extend/plugins/artistdatapress/#post-26443</link>
			<pubDate>Tue, 10 May 2011 02:19:16 +0000</pubDate>
			<dc:creator>slushman</dc:creator>
			<guid isPermaLink="false">26443@http://wordpress.org/extend/plugins/</guid>
			<description><![CDATA[ArtistDataPress displays your ArtistData feed on a page, post, or as a sidebar widget.]]></description>
					</item>
		<item>
			<title>Gigs Calendar</title>
			<link>http://wordpress.org/extend/plugins/gigs-calendar/#post-2772</link>
			<pubDate>Thu, 03 Jan 2008 05:20:07 +0000</pubDate>
			<dc:creator>DanCoulter</dc:creator>
			<guid isPermaLink="false">2772@http://wordpress.org/extend/plugins/</guid>
			<description><![CDATA[Manage and display a calendar of your gigs/shows/performances.]]></description>
					</item>
		<item>
			<title>Discography</title>
			<link>http://wordpress.org/extend/plugins/discography/#post-2681</link>
			<pubDate>Mon, 17 Dec 2007 05:55:08 +0000</pubDate>
			<dc:creator>DanCoulter</dc:creator>
			<guid isPermaLink="false">2681@http://wordpress.org/extend/plugins/</guid>
			<description><![CDATA[Organize your discography; and offer downloads, streams and ways to buy your music.]]></description>
					</item>

	</channel>
</rss>
