<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Patrick Ziegler</title>
    <description>The latest articles on DEV Community by Patrick Ziegler (@patrick).</description>
    <link>https://dev.to/patrick</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F17953%2Fc0f8de01-eb5a-48a7-b63e-e51a23dd26ed.jpg</url>
      <title>DEV Community: Patrick Ziegler</title>
      <link>https://dev.to/patrick</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/patrick"/>
    <language>en</language>
    <item>
      <title>Open source Maintainers: How do you deal with feature requests?</title>
      <dc:creator>Patrick Ziegler</dc:creator>
      <pubDate>Tue, 14 Aug 2018 16:44:10 +0000</pubDate>
      <link>https://dev.to/patrick/open-source-maintainers-how-do-you-deal-with-feature-requests-46mn</link>
      <guid>https://dev.to/patrick/open-source-maintainers-how-do-you-deal-with-feature-requests-46mn</guid>
      <description>&lt;p&gt;I'm a co-maintainer of a fairly popular open source project in its space and we get lots of feature requests and I'm not always sure what to do with them. For some, I can clearly see the merits and they're also something, I'd like to see in the project but just haven't thought of and I'll happily add them to our 'Feature Requests' github project. For others I can clearly say that it's not something that's going to be added to the project because it's very niche or something totally outside of the project's domain.&lt;/p&gt;

&lt;p&gt;But then there are the ones in between, and most of them fall into this category, where I'm not a fan but can't quite articulate and defend why that feature shouldn't be added.&lt;/p&gt;

&lt;p&gt;How do you folks handle these kinds of requests? Do you just add them to a list of feature requests like we do or do you have some kind of guideline as to what type of feature requests you will accept? Also how do you close those feature requests without the user feeling shut down or ignored?&lt;/p&gt;

&lt;p&gt;Thanks for your inputs, I'm really looking forward to the discussion and to finding out how you deal with these sorts of things.&lt;/p&gt;

</description>
      <category>discuss</category>
      <category>opensource</category>
    </item>
    <item>
      <title>Hi, I'm Patrick Ziegler</title>
      <dc:creator>Patrick Ziegler</dc:creator>
      <pubDate>Tue, 02 May 2017 20:01:06 +0000</pubDate>
      <link>https://dev.to/patrick/hi-im-patrick-ziegler</link>
      <guid>https://dev.to/patrick/hi-im-patrick-ziegler</guid>
      <description>&lt;p&gt;I have been coding since 2009 (wow that long already O.o).&lt;/p&gt;

&lt;p&gt;I'm currently pursuing a Bachelor's degree in Computer Science at ETH in Zurich.&lt;/p&gt;

&lt;p&gt;Due to my studies, I don't have quite as much time as I'd like to code for myself but when I do I'm most likely hacking around my Linux installation or my dev workflow.&lt;/p&gt;

&lt;p&gt;It's really nice to be here and maybe I'll even write a post or two ;)&lt;/p&gt;

&lt;p&gt;If you want, you can follow me on Twitter &lt;a href="https://twitter.com/patrick96MC" rel="noopener noreferrer"&gt;@patrick96MC&lt;/a&gt;&lt;/p&gt;

</description>
      <category>introduction</category>
    </item>
  </channel>
</rss>
