Re: JEDI website project

Hello,

> I am in favor for anything which is W3C-standard compliant. The 
> current version of XOOPS isn't.

Well, lets say the current version of "our homepage" isn't W3C
compliant. XOOPs allows to write W3C compliant websites afaict. 

> > 1. Add a link to the www.delphi-jedi.org which explains where the 
> > new homepage is and why people should visit it :-)
> Is a HTTP redirect unfeasible? I think this would be the best method
> despite mod_rewrite, of course.

The idea behind that was to have all the "old" content available until
we have decided what to do with it. It is just a short term solution -
as something that can be done now (read within a few hours). In a few
weeks we can then turn off the old homepage and redirect our users.


[Darth]
> His proposal was SF.net. I said I could create a project but never 
> got a reply from Alan after it.

Alan?
 

[APILib]
> I am for an archive plus removal of those which are contained 
> in the current API Library. This is mainly to not confuse anyone. 
> Perhaps we could move those files under MPL to the FRS of 
> jedi-apilib to create the archive?

Sounds good to me. Additionaly it should be our goal to migrate the
ones which are not in the current API Library to it (if they are up to
date). 

> Actually I think that we should perhaps create some kind of 
> "JEDI-style" for the homepages which will be adopted by all the 
> project websites.

Replace "will be" by "can" and I am with you. Our plan was to give
each project complete control about how and where they want to present
themselves. If they want to use something else than our "corporate
idendity" then its their decision.


> Leaving the website for each project to the respective teams allows
> to keep up a website without having to grant access to the main 
> website. Furthermore each project will develop some kind of identity
> and updates may occur more often.

That is what we have now :-) 


> For news we could have some group of news "posters" who 
> are known to all teams. Whenever a team feels the need to post 
> news to the main site they have to contact this group and the 
> fastest of them will take over the task
> of actually posting the news. Alternatively one could create some 
> mechanism to allow posting to anyone, but the changes appear only
> after approval.
> Perhaps embedding the whole website into some kind of Wiki and 
> protecting
> some areas would also do.

Why so complicated? Create an account for each team and allow them to
post news directly. I do not see a high risk of "nonsense" posts. 
 

- Matthias




------------------------ Yahoo! Groups Sponsor --------------------~--> 
<font face=arial size=-1><a href="http://us.ard.yahoo.com/SIG=12h05jusk/M=362131.6882499.7825260.1510227/D=groups/S=1705115362:TM/Y=YAHOO/EXP=1124842007/A=2889191/R=0/SIG=10r90krvo/*http://www.thebeehive.org
">Get Bzzzy! (real tools to help you find a job) Welcome to the Sweet Life - brought to you by One Economy</a>.</font>
--------------------------------------------------------------------~-> 

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/Delphi-JEDI/

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/