[OpenID] Changes to the website coming soon ...

[tom calthrop]

"Does anyone else on this mailing list feel strongly one way or the
other considering the current implementation is almost done?"

I feel strongly that the site is due for an update ASAP;) We really need 
it to support our activities...

Sorry to say it David, but "too little too late". There was a discussion 
on list several weeks ago about the site and suggestions were pitched in 
then. That was the time to present technical options.

I look forward to seeing the site next week Scott - thanks for your 
efforts!!

Tom



Scott Kveton wrote:
>>> The Vidoop folks appear to be pretty far along with the WordPress
>>> theme as well as the accompanying PHP scripts to drive some of the
>>> forms for getting an OpenID, etc.  We're pretty far along here I think
>>> and switching gears this late in the game (when we have 3 days)
>>> doesn't make a lot of sense to me.  I just want this done.
>>>       
>> Agreed, I want this done too.
>>     
>
> I feel like you're inserting yourself into this process at a rather
> late stage when a lot of the work is already done.  I mentioned that
> we would use WordPress during the board calls and the board agreed (or
> didn't have anything to say otherwise).  If you had had a problem,
> then would have been the time to discuss it.  Now I feel like you're
> creating more work for the volunteers that are trying to get this done
> in a timely fashion.
>
>   
>> I don't see a reason why MovableType would prohibit the PHP scripts
>> they've been developing.  MT supports both static and dynamic
>> publishing of templates.  With static publishing we can make MT
>> publish the files directly as ".php" (or any other language we'd
>> like) and use MT in that situation to manage the PHP source files.
>> This still allows MT to automatically include the traditional
>> template header, footer, sidebar, etc when statically publishing the
>> file.  When working with dynamic publishing, MT actually use the PHP
>> engine to render the pages.  This allows us to easily include
>> snippets of raw PHP within our templates.  MT then allows us to
>> choose static vs dynamic on a per-template basis.  http://
>> www.sixapart.com/about/news/index is an example of dynamic publishing
>> where we pull out excerpts of each post and add email, subscribe,
>> Digg links.
>>     
>
> My point is that we're creating more work than is absolutely necessary
> because you want to use MovableType.  I still haven't heard you give
> me a compelling reason (other than they support OpenID out of the
> box).
>
> Does anyone else on this mailing list feel strongly one way or the
> other considering the current implementation is almost done?
>
>   
>>> What language is MovableType in?  I also like the idea of PHP for the
>>> CMS (WordPress) and PHP for the wiki (MediaWiki) ... keeps things
>>> pretty simple for us from an upgrade/management perspective.
>>>       
>> It is Debian, "apt-get upgrade" ;) :)
>>     
>
> Actually its significantly harder than that.  The current
> configuration is a mess today because we made poor decisions when we
> first built out openid.net.  Any changes we make to PHP, Perl, SVN,
> etc are quite difficult to implement without affecting other parts of
> the infrastructure.  You have to admit that the current setup is like
> spaghetti with two instances of apache running, etc to accommodate
> BML.
>
> - Scott
> _______________________________________________
> general mailing list
> general at openid.net
> http://openid.net/mailman/listinfo/general
>
>