<?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: trip - Recent Posts</title>
		<link>http://wordpress.org/plugins/tags/trip</link>
		<description>WordPress Plugins &#187; Tag: trip - Recent Posts</description>
		<language>en-US</language>
		<pubDate>Wed, 19 Jun 2013 21:13:58 +0000</pubDate>
		<generator>http://bbpress.org/?v=1.1</generator>
				<atom:link href="http://wordpress.org/plugins/rss/tags/trip" rel="self" type="application/rss+xml" />

		<item>
			<title>Where I&#039;m Going</title>
			<link>http://wordpress.org/plugins/where-im-going/#post-52722</link>
			<pubDate>Tue, 30 Apr 2013 00:41:48 +0000</pubDate>
			<dc:creator>Ipstenu (Mika E.)</dc:creator>
			<guid isPermaLink="false">52722@http://wordpress.org/plugins/</guid>
			<description><![CDATA[<p>Emailed Author: You have two issues with your plugin.</p>
<p>== The Anytime code is licensed CC ==</p>
<p>Sadly this is not compatible with WordPress's GPLv2 (or later).</p>
<p>Plugins are, and have always been, required to be GPL (or compatible) licensed, as clearly stated at <a href="http://wordpress.org/extend/plugins/about/" rel="nofollow">http://wordpress.org/extend/plugins/about/</a></p>
<p>Anyone should be able to download any plugin in the repository, confident that they can use and adapt that code as they see fit, within the strictures of GPL. By including code that is not GPL, this undermines the rights of the person whose code was used and violates the repository guidelines.</p>
<p>Please remove the code and alter the plugin so it is not required. If you cannot alter the code, we suggest you find alternate code that is GPL compatible and use that instead. For more information on what types of licenses are compatible with GPL, please review the following links:</p>
<p><a href="http://www.gnu.org/licenses/license-list.html" rel="nofollow">http://www.gnu.org/licenses/license-list.html</a><br />
<a href="http://www.gnu.org/licenses/gpl-faq.html#AllCompatibility" rel="nofollow">http://www.gnu.org/licenses/gpl-faq.html#AllCompatibility</a></p>
<p>== Missing readme ==</p>
<p>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>Keep in mind, a readme.MD is not the same as a readme.TXT - the formatting for markup is different.</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. As this is for a new plugin request, please reply within seven days of this email or we will reject your plugin.
</p>]]></description>
					</item>
		<item>
			<title>Where I&#039;m Going</title>
			<link>http://wordpress.org/plugins/where-im-going/#post-52711</link>
			<pubDate>Mon, 29 Apr 2013 18:56:48 +0000</pubDate>
			<dc:creator>skustes</dc:creator>
			<guid isPermaLink="false">52711@http://wordpress.org/plugins/</guid>
			<description><![CDATA[This plug-in allows you to input your travel destinations and the dates you&#039;ll be there, then easily output those dates to your readers.]]></description>
					</item>
		<item>
			<title>Plot My Posts and Tweets</title>
			<link>http://wordpress.org/plugins/plot-my-tweets-and-posts/#post-36226</link>
			<pubDate>Wed, 28 Mar 2012 11:37:10 +0000</pubDate>
			<dc:creator>phy9pas</dc:creator>
			<guid isPermaLink="false">36226@http://wordpress.org/plugins/</guid>
			<description><![CDATA[Plot your blog posts and/or tweets on a Google Map in date order with a path tracing your route.]]></description>
					</item>
		<item>
			<title>LogMyTrip</title>
			<link>http://wordpress.org/plugins/logmytrip/#post-25207</link>
			<pubDate>Tue, 15 Mar 2011 20:59:25 +0000</pubDate>
			<dc:creator>ajohnwaters</dc:creator>
			<guid isPermaLink="false">25207@http://wordpress.org/plugins/</guid>
			<description><![CDATA[Viewing your posts as a route plotted on a Google map is simple with this plugin.
Just add the shortcode [logmytripmap] to a page to see the map.]]></description>
					</item>
		<item>
			<title>Travelmap</title>
			<link>http://wordpress.org/plugins/travelmap/#post-21470</link>
			<pubDate>Mon, 11 Oct 2010 09:01:32 +0000</pubDate>
			<dc:creator>mediascreen</dc:creator>
			<guid isPermaLink="false">21470@http://wordpress.org/plugins/</guid>
			<description><![CDATA[Generates a map of your travels in any post or page based on a list of places.]]></description>
					</item>

	</channel>
</rss>
