<div><meta http-equiv="content-type" content="text/html; charset=utf-8">re user sign up-- sorry i wasn't clear. i meant signing up for a course, not an account. he already had an account, but couldn't find where to sign up for a specific course that was open for sign up. for these courses, could we have a bigger button(s) near the top of the course homepage? </div>
<div><br></div>re search, have you thought about something like solr? <meta http-equiv="content-type" content="text/html; charset=utf-8"><a href="http://lucene.apache.org/solr/">http://lucene.apache.org/solr/</a> <div><br>
</div><div>solr indexes along any fields you define (typically multiple), to enable fast real time search given a large variety of potential parameters/filters. it trades off space (ie, the indexes can get big) for speed and scalability, basically. it's used on many "high traffic websites": <meta http-equiv="content-type" content="text/html; charset=utf-8"><a href="http://wiki.apache.org/solr/PublicServers">http://wiki.apache.org/solr/PublicServers</a>. <div>
<br></div><div><a href="http://wiki.apache.org/solr/PublicServers"></a>i set up solr for one of my projects at sunlight and worked a lot with index definitions; if there's interest i would be happy to set it up for us. it's free and open source. index space isn't an issue for us AFAIK, but the main potential drawback i could imagine is that our dev server probably couldn't handle the extra load. thoughts?</div>
<div><div><br></div><div>Jessy</div><div>--</div><div><a href="http://jessykate.com" target="_blank">http://jessykate.com</a></div><br>
<br><br><div class="gmail_quote">On Mon, May 23, 2011 at 1:35 AM, Philipp Schmidt <span dir="ltr"><<a href="mailto:phi.schmidt@gmail.com">phi.schmidt@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<p>Search is a problem we hoped batucada would solve. </p>
<p>Zuzel: could you check with Paul what the status on that is?</p>
<p>To reduce confusion on the courses list page, we could also consider listing draft courses on a separate page. </p>
<p>P</p><div><div></div><div class="h5">
<div class="gmail_quote">On 23 May 2011 12:17 AM, "zuzel.vp" <<a href="mailto:zuzel.vp@gmail.com" target="_blank">zuzel.vp@gmail.com</a>> wrote:<br type="attribution">> Sign up/Registration of new accounts was temporarily hidden on<br>
> purpose. Before the migration occurs we need users not to create new<br>> accounts unless they had never used the old site so they keep their<br>> identities. After the creation of new accounts in the old site is<br>
> disabled we will migrate all user accounts to the new site. At that<br>> point we will not need anymore the current restriction of not allowing<br>> any user to register accounts with username/email from the old site<br>
> (unless they proved that they are the same person by login in with<br>> their username and password from the old site). After the migration we<br>> can make signup more visible again (either by having all the forms on<br>
> the same page or by adding a direct link like in drumbeat/batucada).<br>> <br>> Most of the tickets are not assigned to a milestone now because we had<br>> to re-schedule things in order to move the migration to an early date.<br>
> However even before this, search was assigned I think to milestone 0.9<br>> because it is a feature hard to implement in a way that scales. All<br>> solutions I have seen including search in a django project tend to<br>
> become considerable slow when they are setup in a real world scenario.<br>> One solution could be to rely google for including search capabilities<br>> (<a href="http://www.google.com/cse/" target="_blank">http://www.google.com/cse/</a>).<br>
> <br>> Thoughs?<br>> <br>> -- <br>> Thanks,<br>> Zuzel<br>> <br>> On Sun, May 22, 2011 at 5:13 PM, Alison Jean Cole<br>> <<a href="mailto:alisonjean.cole@gmail.com" target="_blank">alisonjean.cole@gmail.com</a>> wrote:<br>
>> Agree with both of Jessy's suggestions.<br>>><br>>> ALISON<br>>> <a href="http://new.p2pu.org/en/alison/" target="_blank">new.p2pu.org/en/alison/</a><br>>><br>>><br>>><br>
>><br>>><br>
>> On Sat, May 21, 2011 at 10:48 AM, John Britton <<a href="mailto:public@johndbritton.com" target="_blank">public@johndbritton.com</a>><br>>> wrote:<br>>>><br>>>> I also think we should make the signup/signin box happen on the same page<br>
>>> as opposed to redirecting to a new page, less friction overall.<br>>>> --<br>>>> contact info:<br>>>> <a href="http://www.johndbritton.com" target="_blank">http://www.johndbritton.com</a><br>
>>> @johndbritton - <a href="http://twitter.com/johndbritton" target="_blank">http://twitter.com/johndbritton</a><br>
>>><br>>>><br>>>> On Sat, May 21, 2011 at 1:43 PM, Jessy Kate Schingler<br>>>> <<a href="mailto:jessy@jessykate.com" target="_blank">jessy@jessykate.com</a>> wrote:<br>>>>><br>
>>>> 2 pieces of feedback on someone looking at the new.p2pu site.<br>
>>>> i had recommended they create an account in order to sign up for a<br>>>>> specific course. so of course the first thing they looked for was a search<br>>>>> box. there's quite a lot of courses now, so i wonder if the "search box"<br>
>>>> ticket on lighthouse might deserve to be moved up a bit in priority<br>>>>> (currently "unscheduled")?<br>>>>> <a href="http://p2pu.lighthouseapp.com/projects/71002/tickets/149-search" target="_blank">http://p2pu.lighthouseapp.com/projects/71002/tickets/149-search</a><br>
>>>> the other immediate reaction was, "i have no idea where to go to sign<br>>>>> up". he looked over the page a few times, and then i pointed out the<br>>>>> "signup" section. in seeing it through his user behaviour, i agree this<br>
>>>> could be more clear. having a couple of prominent buttons that get displayed<br>>>>> for users who are not already a member of a course (or not logged in)<br>>>>> showing options to follow/participate would be a big help (and probably<br>
>>>> help with user follow through). i don't actually see a ticket for that yet.<br>>>>><br>>>>><br>>>>> Jessy<br>>>>> --<br>>>>> <a href="http://jessykate.com" target="_blank">http://jessykate.com</a><br>
>>>><br>>>>> _______________________________________________<br>>>>> p2pu-dev mailing list<br>>>>> <a href="mailto:p2pu-dev@lists.p2pu.org" target="_blank">p2pu-dev@lists.p2pu.org</a><br>
>>>> <a href="http://lists.p2pu.org/mailman/listinfo/p2pu-dev" target="_blank">http://lists.p2pu.org/mailman/listinfo/p2pu-dev</a><br>
>>>><br>>>><br>>>><br>>>> _______________________________________________<br>>>> p2pu-dev mailing list<br>>>> <a href="mailto:p2pu-dev@lists.p2pu.org" target="_blank">p2pu-dev@lists.p2pu.org</a><br>
>>> <a href="http://lists.p2pu.org/mailman/listinfo/p2pu-dev" target="_blank">http://lists.p2pu.org/mailman/listinfo/p2pu-dev</a><br>>>><br>>><br>>><br>>> _______________________________________________<br>
>> p2pu-dev mailing list<br>>> <a href="mailto:p2pu-dev@lists.p2pu.org" target="_blank">p2pu-dev@lists.p2pu.org</a><br>>> <a href="http://lists.p2pu.org/mailman/listinfo/p2pu-dev" target="_blank">http://lists.p2pu.org/mailman/listinfo/p2pu-dev</a><br>
>><br>>><br>> _______________________________________________<br>> p2pu-dev mailing list<br>> <a href="mailto:p2pu-dev@lists.p2pu.org" target="_blank">p2pu-dev@lists.p2pu.org</a><br>> <a href="http://lists.p2pu.org/mailman/listinfo/p2pu-dev" target="_blank">http://lists.p2pu.org/mailman/listinfo/p2pu-dev</a><br>
</div>
</div></div><br>_______________________________________________<br>
p2pu-dev mailing list<br>
<a href="mailto:p2pu-dev@lists.p2pu.org">p2pu-dev@lists.p2pu.org</a><br>
<a href="http://lists.p2pu.org/mailman/listinfo/p2pu-dev" target="_blank">http://lists.p2pu.org/mailman/listinfo/p2pu-dev</a><br>
<br></blockquote></div><br></div></div>