Bugzilla – Full Text Bug Listing
| Summary: | [website] Website owner and website developers needed | ||
|---|---|---|---|
| Product: | [WebTools] WTP Website | Reporter: | Tim Wagner <twagner> |
| Component: | website | Assignee: | Bob Fraser <bob.fraser> |
| Status: | CLOSED FIXED | QA Contact: | Lawrence Mandel <lmandel> |
| Severity: | normal | ||
| Priority: | P3 | CC: | david_williams, ryman |
| Version: | unspecified | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
| Bug Depends on: | 129098 | ||
| Bug Blocks: | |||
|
Description
Tim Wagner
I'll help. FYI, bug 129098 describes requirements for the Phoenix conversion. I'm interested in doing what I can to help. I am ready for this activity. Nitin M. Mandolkar Thanks for volunteering Nitin and welcome aboard. Can you give me a rundown of some of the Web technologies you already know (or want to learn) and what type of work you're interested in contributing to the site (update look and feel, manage a certain section, update content, etc.)? Just assigning it to Lawrence to move it out of the inbox. Tim's been handling the drive to create a website team. I'm reassigning to him. All, Thanks for expressing interest in helping to support and improve the Eclipse WTP website. We have a number of challenges ahead of us: • Converting to the new (“Phoenix”) look and feel, including adhering to standard nav bar conventions for top-level projects • Making it easier for new users to navigate our site and get started (this and the preceding item have been stressed by the Board of Directors as critical to achieve) o This includes more and improved/updated tutorials, additional “getting started” pages, etc. • Routine maintenance o Eliminating dead links and old information (request from planning council) o Keeping news and presentation links up to date o Release activities • Updated IP log and committer information; “who to go to for what” help, etc. • Better adopter pages – adopter logos and information are now sanctioned for use, so we can actually list people who build on WTP and provide links back to their respective organizations or companies. • Improved accessibility and cross-browser support I’ll make sure everyone is cc’ed on https://bugs.eclipse.org/bugs/show_bug.cgi?id=153085, and copy the updated list above there as well. Let’s use that as a forum to establish how we’ll move forward, who’s working on what, etc. Thanks for your interest! Tim Wagner Tim, As we move to Phoenix we need to have a strategy for not breaking links into WTP from outside. I described an approach in bug 129098. I think we can either provide redirects for the existing URLs, or provide html wrappers that load the new PHP content (via JavaScript). Remember, Cool URLs Don't Change. [1] [1] http://www.w3.org/Provider/Style/URI (In reply to comment #8) > ... I think we can > either provide redirects for the existing URLs, or provide html wrappers that > load the new PHP content (via JavaScript). > I believe we should use re-directs if possible. In the past, there has been security holes when scripts load content by arguments passed on a URL ... I'm sure _we_ could do it safely :) but its better if there's no question. +1 to David's comment. Denis sent out a committer e-mail a while back highlighting this problem and how it lead to an attack on the Eclipse infrastructure. I am helping out with the Phoenix conversion as per bug 129098. Bob Fraser So, I am happy to be website lead. Do I close this or leave it open in the hopes that other website developers will help? Bob, thanks again for taking ownership of the website. I think this bug should be closed. A bug doesn't seem to be the right mechanism for ongoing recruitment of new contributors. I would suggest a promotion campaign on the website itself highlighting areas of WTP, such as the website, that needs help. The campaign can instruct people that want to contribute to send an e-mail to wtp-dev or contact the component owners directly. Resolving Closing |