Bugzilla – Full Text Bug Listing
| Summary: | Work is needed for Eclipse Corner Articles | ||
|---|---|---|---|
| Product: | Community | Reporter: | Christopher Guindon <chris.guindon> |
| Component: | Website | Assignee: | phoenix.ui <phoenix.ui-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | denis.roy, ian.skerrett, wayne.beaton |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| URL: | http://staging.eclipse.org/articles/ | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 432346 | ||
|
Description
Christopher Guindon
Wayne owns this page and the Resources page. I believe he has agreed to archive both sites. (In reply to Ian Skerrett from comment #1) > Wayne owns this page and the Resources page. I believe he has agreed to > archive both sites. I hesitate to shutdown /articles. There's a lot of good content there. Unfortunately, there's a lot of out-of-date content as well with little or no prospect of anybody coming along to update it. I'm in favour of killing off /resources; while I think that listing the resources is valuable, I'm not convinced that there's great return on investment. FWIW, I share Wayne's thoughts. We won't migrate this page to the Solstice theme; we'll simply leave it as Nova indefinitely and mark the page as stale/out of date/unmaintained/deprecated. (In reply to Denis Roy from comment #4) > We won't migrate this page to the Solstice theme; we'll simply leave it as > Nova indefinitely and mark the page as stale/out of > date/unmaintained/deprecated. I added the deprecated theme to all the pages under /articles. This change is live on production: https://www.eclipse.org/articles/ Closing this bug. Reopening. This isn't the right solution. /articles contains stuff that is under our control and the links are generally good. Some of the articles are stale, but that's always going to be true. /resources can be marked as deprecated (much of the content there is outside of our control), but not /articles (In reply to Christopher Guindon from comment #5) > (In reply to Denis Roy from comment #4) > > We won't migrate this page to the Solstice theme; we'll simply leave it as > > Nova indefinitely and mark the page as stale/out of > > date/unmaintained/deprecated. > > I added the deprecated theme to all the pages under /articles. This change > is live on production: > > https://www.eclipse.org/articles/ > > Closing this bug. (In reply to Wayne Beaton from comment #6) > Reopening. > > This isn't the right solution. /articles contains stuff that is under our > control and the links are generally good. Some of the articles are stale, > but that's always going to be true. > > /resources can be marked as deprecated (much of the content there is outside > of our control), but not /articles It might be under our control but the last article posted was in 2012 when 2 articles were posted and before that was in 2009. it doesn't appear we are actually using this page so does it make sense investing in porting it to the new theme? I also don't believe we are linking to the article page in the new web site so it will be difficult to find. I think this is one piece if technical debt we can eliminate. Perhaps move the list of articles to the Wiki and let the community maintain it? (In reply to Denis Roy from comment #9) > I think this is one piece if technical debt we can eliminate. Perhaps move > the list of articles to the Wiki and let the community maintain it? The articles themselves are all hosted on www.eclipse.org/articles. Many of the articles do not use the website skins, but many of them do. I agree that we can shut down the infrastructure created to manage the articles (a few database tables and some PHP code), but what do you want to do with the articles themselves? > I agree that we can shut down the infrastructure created to manage the
> articles (a few database tables and some PHP code), but what do you want to
> do with the articles themselves?
Perhaps the articles can live on as-is (as-are?) but the index can move to a list on the Wiki?
(In reply to Denis Roy from comment #11) > > I agree that we can shut down the infrastructure created to manage the > > articles (a few database tables and some PHP code), but what do you want to > > do with the articles themselves? > > Perhaps the articles can live on as-is (as-are?) but the index can move to a > list on the Wiki? Works for me. I've created a web page with the current contents of /articles https://wiki.eclipse.org/Eclipse_Corner I've set up redirects from the two entry points in /articles. The directory needs to stay in place as the existing articles all still live there. (In reply to Wayne Beaton from comment #13) > I've created a web page with the current contents of /articles > > https://wiki.eclipse.org/Eclipse_Corner > > I've set up redirects from the two entry points in /articles. > > The directory needs to stay in place as the existing articles all still live > there. Should we plan to retire this? This section is using a lot of custom PHP code. It might be a good idea to remove it eventually if were not going to maintain it.
> Should we plan to retire this?
>
> This section is using a lot of custom PHP code. It might be a good idea to
> remove it eventually if were not going to maintain it.
We should also consider converting this site to static HTML.
(In reply to Christopher Guindon from comment #14) > This section is using a lot of custom PHP code. It might be a good idea to > remove it eventually if were not going to maintain it. Most of the code is in /resources. I'm addressing that with Bug 434242. There is relatively little code left under /articles. I'm not sure how difficult it will be to create static versions of the content here. In order to apply style sheets, printable versions, etc., there are php-based entry-points. If you want to go the static html route, then reopen this bug or create a new one. |