Re: Suggestion and help offer for redesign re. dynamic conference and user group system and calendar
| From: | Hannes Magnusson | Date: | Tue, 28 Feb 2012 11:54:53 +0000 |
| Subject: | Re: Suggestion and help offer for redesign re. dynamic conference and user group system and calendar | ||
| References: | 1 2 3 4 5 6 7 8 9 10 | Groups: | php.webmaster |
| Request: | Send a blank email to php-webmaster+get-13124@lists.php.net to get a copy of this message | ||
On Mon, Feb 6, 2012 at 22:44, Hannes Magnusson
<hannes.magnusson@gmail.com> wrote:
> On Thu, Jan 12, 2012 at 21:19, Mike van Riel <mike.vanriel@naenius.com> wrote:
>> On Thu, 2012-01-12 at 20:41 +0100, Hannes Magnusson wrote:
>>> Sure, you offer much more functionality that would benefit from having
>>> registered users.
>>> Thats fair enough, and adding other various login solutions would be great.
>>>
>>> Thats not my biggest issue with using joind.in though.
>>> It was hard to get people to like using flickr for images, outsourcing
>>> our entire calendar listing and conference news isn't going to be
>>> easypeasy.
>>>
>>> I'm liking the idea more and more though...
>>>
>>> How do you see it work in practice?
>>
>> One such scenario could be that php.net were to add a calendar widget
>> into their own branding in which the same information can be represented
>> with the currently available information, whether a CfP is in progress
>> and additional geo-location information when practical.
>>
>> Each shown event will have a summary as part of the calendar widget but
>> for a full view can the user click on a link and be redirected to the
>> show page at joind.in.
>>
>> For event submissions I would propose to have a 'crafted' link on the
>> php.net website that directly links to the event submission page of
>> joind.in.
>>
>> When the user is not logged in they will be presented with the
>> authentication form where they have the option of logging in using
>> their joind.in, twitter or facebook credentials.
>>
>> Once they have entered their submission will they be redirected to the
>> php.net event calender page.
>>
>> Events submitted from the php.net domain will automatically have a tag
>> 'php' or 'php.net'; with which the calendar widget can filter the
>> relevant events.
>>
>> In the illustrated scenario above would the user spend most of the time
>> browsing the php.net website and only when they want details beyond a
>> summary they would be directed to the joind.in website.
>
>
> Okidoki. I'm game, and I don't see anyone else around here disagreeing :]
Any progress on the updates on the joind.in side?
-Hannes