<?xml version="1.0"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>CKAN: Ticket #1319: Require an email address on User registration</title>
    <link>http://localhost/ticket/1319</link>
    <description>&lt;p&gt;
Superticket: &lt;a class="new ticket" href="http://localhost/ticket/1343" title="enhancement: [super] User related improvements (login, user pages etc) (new)"&gt;#1343&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
This avoids difficulties when they forget their password.
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;(?) Email validation (navl does not have one!)
&lt;/li&gt;&lt;li&gt;Require email confirmation to be activated (?) (Answer: no, not at present -- see discussion below)
&lt;/li&gt;&lt;/ul&gt;</description>
    <language>en-us</language>
    <image>
      <title>CKAN</title>
      <url>http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png</url>
      <link>http://localhost/ticket/1319</link>
    </image>
    <generator>Trac 0.12.3</generator>
    <item>
      
        <dc:creator>shevski</dc:creator>

      <pubDate>Thu, 08 Sep 2011 10:00:57 GMT</pubDate>
      <title></title>
      <link>http://localhost/ticket/1319#comment:1</link>
      <guid isPermaLink="false">http://localhost/ticket/1319#comment:1</guid>
      <description>
        &lt;p&gt;
Ideally we should also verify people's email addresses. Do we think that's overkill?
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>dread</dc:creator>

      <pubDate>Tue, 13 Sep 2011 09:03:12 GMT</pubDate>
      <title></title>
      <link>http://localhost/ticket/1319#comment:2</link>
      <guid isPermaLink="false">http://localhost/ticket/1319#comment:2</guid>
      <description>
        &lt;p&gt;
No responses received about this on ckan-discuss, so I'm taking that as no objections to requiring email address on registration.
&lt;/p&gt;
&lt;p&gt;
I think that verifying email address is not worth it in this case, because the value of supplying an email address is only for resetting a password. The chance of needing a password reset AND having inputted an incorrect email address is very low, so I don't think it justifies everyone having to do this extra step. If we used email address more then that may change.
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>rgrp</dc:creator>

      <pubDate>Wed, 12 Oct 2011 13:40:07 GMT</pubDate>
      <title>owner, status, description, milestone changed</title>
      <link>http://localhost/ticket/1319#comment:3</link>
      <guid isPermaLink="false">http://localhost/ticket/1319#comment:3</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;owner&lt;/strong&gt;
              changed from &lt;em&gt;dread&lt;/em&gt; to &lt;em&gt;rgrp&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;
                changed from &lt;em&gt;new&lt;/em&gt; to &lt;em&gt;assigned&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;description&lt;/strong&gt;
              modified (&lt;a href="/ticket/1319?action=diff&amp;amp;version=3"&gt;diff&lt;/a&gt;)
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;milestone&lt;/strong&gt;
                changed from &lt;em&gt;ckan-current-sprint&lt;/em&gt; to &lt;em&gt;ckan-sprint-2011-10-24&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
@dread: hope it is OK to re-assign to me but this is very similar to &lt;a class="closed ticket" href="http://localhost/ticket/1386" title="enhancement: Disallow account creation via openid (closed: fixed)"&gt;#1386&lt;/a&gt; (and is a su bticket of &lt;a class="new ticket" href="http://localhost/ticket/1343" title="enhancement: [super] User related improvements (login, user pages etc) (new)"&gt;#1343&lt;/a&gt;)
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>rgrp</dc:creator>

      <pubDate>Thu, 13 Oct 2011 17:40:13 GMT</pubDate>
      <title>status changed; resolution set</title>
      <link>http://localhost/ticket/1319#comment:4</link>
      <guid isPermaLink="false">http://localhost/ticket/1319#comment:4</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;
                changed from &lt;em&gt;assigned&lt;/em&gt; to &lt;em&gt;closed&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;resolution&lt;/strong&gt;
                set to &lt;em&gt;fixed&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
Fixed in &lt;a class="ext-link" href="https://bitbucket.org/okfn/ckan/changeset/130cad62163c"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://bitbucket.org/okfn/ckan/changeset/130cad62163c&lt;/a&gt;
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>dread</dc:creator>

      <pubDate>Fri, 16 Dec 2011 12:02:27 GMT</pubDate>
      <title></title>
      <link>http://localhost/ticket/1319#comment:5</link>
      <guid isPermaLink="false">http://localhost/ticket/1319#comment:5</guid>
      <description>
        &lt;p&gt;
Goes into release 1.5.1
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item>
 </channel>
</rss>