Community
Participate
Working Groups
As more projects move to the Phoenix style, the remaining "old school" pages really start to stand out. Some of the most prominent old style pages are those under http://dev.eclipse.org. It would be nice for these to be migrated to the Phoenix look and feel. The most prominent of these are: http://dev.eclipse.org/bugs/ (aka bugs.eclipse.org) http://dev.eclipse.org/viewcvs/ Also, these should probably just redirect to the new mail page: http://www.eclipse.org/mail/index.html http://dev.eclipse.org/mailman/listinfo Apologies if there are existing bugs for these.
Of course, old links to http://dev.eclipse.org/ also need fixing. Currently this redirects into the wiki. The most prominent being the "Committers" link in the nav bar of the main eclipse.org page.
Agreed. These need to be cleaned up and/or moved. I moved most of the dev.eclipse.org content under the wiki because I think it belongs to our committers - unfortunately, they didn't have access to change it when it was on dev. Let's hope the Wikified pages get a bit of TLC :) If you find more stale links, please post them here. D.
*** Bug 153970 has been marked as a duplicate of this bug. ***
Target for Q4
http://dev.eclipse.org/bugs/ (aka bugs.eclipse.org) http://dev.eclipse.org/viewcvs/ Both those have been skinned. I won't be touching anything related to mailman (http://dev.eclipse.org/mailman/listinfo) because it's simply not designed to be skinned, with HTML being scattered throughout a bunch of python scripts. Also, individual bug pages for bugs.eclipse.org won't receive any specific Phoenix treatment, other than having the standard purple logo/banner at the top. Outside of projectland, are there any other "old school" web pages left?
Created attachment 54204 [details] Screen of dev.eclipse.org/bugs dev.eclipse.org/bugs has layout problems now. This screen shot is how it looks in both Firefox 1.5 and Firefox 2.0.
Must be a proxy/cache issue, as the page looks nothing like that... grrr... Can you try hitting the shift/refresh a couple of times? Thanks
This page is referenced by some of the old-school project pages: http://www.eclipse.org/articles/index.html It should be replaced with a redirect to: http://www.eclipse.org/articles/
It doesn't seem to be a caching problem - I tried on three different machines, hitting F5, etc, and I still see what you see in the screenshot. Same problem on Internet Explorer, so it's not a Firefox issue.
(In reply to comment #8) > This page is referenced by some of the old-school project pages: > > http://www.eclipse.org/articles/index.html > > It should be replaced with a redirect to: > > http://www.eclipse.org/articles/ > I've added a redirect so that any requests for index.html will automatically be redirected to index.php.
(In reply to comment #7) > Must be a proxy/cache issue, as the page looks nothing like that... > > grrr... Can you try hitting the shift/refresh a couple of times? > > Thanks > I see what John sees.
The only remaining "old-school" pages I see, other than projects that have not migrated to the new look, are the newsgroups and mailing list archives. For instance, http://dev.eclipse.org/newslists/news.eclipse.newcomer/msg12097.html I could think of three courses of action : 1. modify the archiver template and regenerate all the archives pro: great looking pages pro: for the most part, same URLs con: need to regenerate all the archives from scratch, which will take a few days (450,000 news and mail posts to re-archive) con: need to regenerate all the archives from scratch next time we change the template con: some message ID's may change if we were asked to remove some messages from the archives, because personal info was submitted, or SPAM. This could break a lot of links 2. add an Apache RewriteRule to intercept the page request, redirect it to a Phoenix page that puts the html archived message in the body. pro: great looking pages pro: same URLs pro: all future changes to Phoenix are done on-the-fly con: need to hack some RewriteRules con: need to parse the HTML page on-the-fly to extract the page title and other elements con: as the archives pages are quite popular (104,000 pages/day, or 1.2/second) this processing will add some load on our servers 3. We leave them alone, plain-jane style pro: no work! con: looks plain My vote is solution 1 as it's the path of least resistance. Thoughts?
I doubt anyone will lose sleep over old archived messages having a banner that's a different shade of blue. I suggest just updating the template so that newly archived messages have more phoenixy colours, but don't bother updating the old ones. Keeping the archive pages really simple means updating their look isn't essential. Note all article pages have the same look.
Hmmm, I hadn't proposed that because I wasn't sure how people would feel about having 2 different looks for mail/news archives.
(In reply to comment #12) > con: some message ID's may change if we were asked to remove some messages from > the archives, because personal info was submitted, or SPAM. This could break a > lot of links Mhm. I see this as a show stopper for solution 1. URLs should not change and still point to the correct posting. > My vote is solution 1 as it's the path of least resistance. Thoughts? It's an archive and the importance about it is to get the page content. Nobody needs to Phoenix header there. :P +1 for solution 3 +0.5 for what John proposed in comment 13
I'm with Gunnar in that I think it's perfectly acceptable for the mail and news archives to stay in a plain format. I've seen many sites where this is the case. Perhaps if I add an Eclipse logo and an "Eclipse archives" title to the page that would help identify the page better (for those hitting them via Google)? I'll attach a screenshot in a minute.
Created attachment 54773 [details] Proposed screenshot
Or something along the Bugzilla header (https://bugs.eclipse.org/bugs/query.cgi?format=specific) PS: There is a FireFox logo in attachment 54773 [details].
(In reply to comment #18) > Or something along the Bugzilla header But that makes it *really* dependent on the Phoenix look. Older messages won't have the big purple banner. > PS: There is a FireFox logo in attachment 54773 [details]. My screenshot app grabbed the Firefox mouse cursor.
Created attachment 54783 [details] Bugzilla Header >(In reply to comment #19) >But that makes it *really* dependent on the Phoenix look. Older messages won't >have the big purple banner. Really? I just meant that simple banner attached.
I'm going to close this as fixed, as all the old-school pages have been Phoenixized. The Mailing List and News archives pages will be redone in Q1 as part of bug 98404.
