<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Sun, 19 May 2013 01:59:02 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[7PHP.com: Interview With Musketeers.me On Taking Over PHP|Architect]]></title>
      <guid>http://www.phpdeveloper.org/news/18986</guid>
      <link>http://www.phpdeveloper.org/news/18986</link>
      <description><![CDATA[<p>
On 7PHP.com today <i>Khayrattee Wasseem</i> has <a href="http://7php.com/interview-musketeers-phparchitect/">posted an interview with Musketeers.me</a> about their recent move to being the owners of the <a href="http://phparch.com">php|architect</a> brand and all of its products/events.
</p>
<blockquote>
If you were having a sky-diving on planet Mars since the past months, or if you were too enthusiastic in getting lost within The Hobbit's World - wake up Sid! There's news concerning PHP Land! On "its" 10th birthday, last December 2012, your "PHP Magazine for PHP Professionals"  (The one & only <a href="http://www.phparch.com/">PHP|Architect</a>) announced on its portal that it's brand, owned by BlueParabola,  is being 'safely & soundly' handed over to <a href="http://musketeers.me/about-us/">The PHP Musketeers</a> aka Musketeers.me for a smooth and more dynamic life. 
</blockquote>
<p>
In <a href="http://7php.com/interview-musketeers-phparchitect/">the interview</a> they talk about things like:
</p>
<ul>
<li>The motivation behind the acquisition
<li>Positives and negatives of the brand as they see them
<li>Future plans for the magazine and brand
<li>What they see as the overall goals for php|architect
<li>What kind of challenges they see in the road ahead
</ul>
<p>
You can read the full interview <a href="http://7php.com/interview-musketeers-phparchitect/">here</a> and find out more about this change <a href="http://www.phparch.com/2012/12/musketeers-me-to-acquire-phparchitects-brand-and-products-effective-january-1st/">on the php|architect site</a>.
</p>]]></description>
      <pubDate>Thu, 03 Jan 2013 09:22:31 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Marco Tabini's Blog: How we failed the PHP brand]]></title>
      <guid>http://www.phpdeveloper.org/news/4846</guid>
      <link>http://www.phpdeveloper.org/news/4846</link>
      <description><![CDATA[In his <a href="http://blogs.phparch.com/mt/?p=125">latest blog entry</a>, <i>Marco Tabini</i> talks about how we, the community, have "failed the PHP brand" through its overuse (such as in application names of things written in the language).
<p>
<quote>
<i>
This is, I believe, a major point of failure for the PHP community. As many have pointed out to me more than once (not that I had anything to do with it, or that I would be able to do anything about it), allowing PHP-related applications to contain the word "PHP" is a major mistake, because it dilutes the value of the brand itself by allowing the quality of PHP to be associated with the value of products that have nothing to do with PHP proper.
</i>
</quote>
<p>
He <a href="http://blogs.phparch.com/mt/?p=125">mentions</a> that searches for things like "php vulnerabilities" come up more with things for apps written in PHP and less with results about PHP itself. He even suggests that there isn't a really useful application type that has a PHP-written option that doesn't use the PHP "brand" in its title. He finishes it off with three simple rules that he suggests will help to dilute the PHP brand - don't use it in your application title, always reference that PHP is a trademark of the PHP group (and that there's no association between you), and use the PHP logo in only a descriptive way.]]></description>
      <pubDate>Wed, 15 Feb 2006 07:05:27 -0600</pubDate>
    </item>
  </channel>
</rss>
