Re: [wtp-dev] Proposal for Plans on the WTP Web Site

[David M Williams <david_williams@xxxxxxxxxx>]

I realize there's lots of details to
work out (and on) as we progress, but I'll make two high level comments
on this thread ... 

1. ) Surely we, a J2EE oriented project
won't be "stuck" using PHP for our own web pages, will we? Any
promise 
of using JSP's and webapps? 
(I know the technical answer is that
we can, though I don't know Phoenix's constraints ... I'm just asking 
the rhetorical question to encourage
that we use what we make). 

2.) When we talk about "the community
pages are meant to provide information for end users and ISVs" ...
shouldn't we have
two distinct "areas" ... one
for end-users, and another one for "ISVs" (probably better termed
"adopters" in Eclipse) ?

Lawrence Mandel <lmandel@xxxxxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx

09/14/2005 08:28 PM

Please respond to
"General discussion of project-wide or architectural issues."

To	"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
cc
Subject	Re: [wtp-dev] Proposal for Plans on the WTP Web Site

Hi Tim, 

The plan was to leave those files where they currently are so developers
updating milestone plans will not need to extract them. The sections for
each component are currently located on the subproject pages.

The community pages are meant to provide information for end users and
ISVs so I think this information also fits well there. This information
can either be divided by component (as you suggested) or simply grouped
together for the entire project. You listed sample plugins, tips, and plugin
information. Are there other items that you or others would like to see
on the community pages? 

Lawrence Mandel

Software Developer
IBM Rational Software
Phone: 905 - 413 - 3814   Fax: 905 - 413 - 4920
lmandel@xxxxxxxxxx

Arthur Ryman/Toronto/IBM@IBMCA
Sent by: wtp-dev-bounces@xxxxxxxxxxx

09/13/2005 02:36 PM

Please respond to
"General discussion of project-wide or architectural issues."

To	"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
cc
Subject	Re: [wtp-dev] Proposal for Plans on the WTP Web Site

Tim, 

When we move to Phoenix we'll be using PHP so we can run transforms dynamically,
e.g. to roll up component milestone plans. Therefore there should be no
requirement to rebuild the pages. However, I'd still like everyone to run
a build script to performance validation at least. Otherwise we could get
errors when the pages are served. 

I'll let Lawrence respond to your suggestion about how to organize the
community section. 

Arthur Ryman,
IBM Software Group, Rational Division

blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@xxxxxxx

Timothy Deboer/Toronto/IBM@IBMCA
Sent by: wtp-dev-bounces@xxxxxxxxxxx

09/13/2005 01:29 PM

Please respond to
"General discussion of project-wide or architectural issues."

To	"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
cc
Subject	Re: [wtp-dev] Proposal for Plans on the WTP Web Site

Hi Arthur, 

Can't we just automate the script to run every 15 minutes if there are
changes? That would allow people to check out just what they want, and
it wouldn't require people to refresh or figure out which files changed
and have to be checked in. 

Each Eclipse team has a page where they post developer resources - sample
plugins, tips, plugin information, etc. The community page doesn't have
sections for each team. Are we leaving this type of file in the current
structure and just moving the milestone and test plans out (and if so,
do we still have to run build.xml here?), or are we removing those files
(and if so, where do they go?). 

Thanks, 
Tim deBoer
WebSphere Tools - IBM Canada Ltd.
(905) 413-3503  (tieline 969)
deboer@xxxxxxxxxx

Arthur Ryman/Toronto/IBM@IBMCA
Sent by: wtp-dev-bounces@xxxxxxxxxxx

09/13/2005 08:57 AM

Please respond to
"General discussion of project-wide or architectural issues."

To	Gorkem Ercan <gercan@xxxxxxx>, "General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
cc	"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>, wtp-dev-bounces@xxxxxxxxxxx
Subject	Re: [wtp-dev] Proposal for Plans on the WTP Web Site

Gorkem, 

Lawrence and I thought there would be no need for obsolete tutorials. However,
if you think there is a need, then I suggest we create an archive in the
community section of the Web site. The idea is that tutorials are really
for end users so we want them in the community section, not the development
section. 

Arthur Ryman,
IBM Software Group, Rational Division

blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@xxxxxxx

Gorkem Ercan <gercan@xxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx

09/13/2005 08:40 AM

Please respond to
Gorkem Ercan and "General discussion of project-wide or architectural issues."

To	"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
cc
Subject	Re: [wtp-dev] Proposal for Plans on the WTP Web Site

Arthur, 
Are you planning an area for old versions of the tutorials(esp. for
public versions), for example when we finally released 1.0, for a
strange reason some of the users may still be using the 0.7 and need
those tutorials
Thanks,
Gorkem Ercan

On 9/13/05, Arthur Ryman <ryman@xxxxxxxxxx> wrote:
>  
> Some of you have complained about the current process for updating
the
> milestone and test plans since it involves checking out and building
the
> entire Web site, which is now too bulky. Also, all Eclipse projects
have
> been asked to clean up their sites so that the old plans are not cluttering
> up the Web pages. 
>  
> We have been holding off doing a major reorg of the Web site because
the
> entire Eclipse Web site is going to be upgraded by the Phoenix project.
> However, we need to update our 1.0 and 1.5 plans now and can't wait
any
> longer for Phoenix. 
>  
> This note proposes a new structure, cooked up by Lawrence and me,
that will
> address the build problem and simplify cleanup at the end of each
release.
> Please review it and respond by Thursday. In the absence of any objections
> voiced at our status call on Thursday, we'll proceed with the plan.
>  
> 1. We will keep the 0.7 plans in the current structure to avoid broken
> links. These pages will be moved after Phoenix gives us automatic
> redirection capability. 
>  
> 2. We will create a new directory structure for all current and future
> plans, as follows: 
>  
> /webtools/plans/<release>/<subproject>/<component>/<milestone>/
>  
> The directory will contain only the milestone and test plans for that
> component and milestone. For example, 
>  
> /webtools/plans/1.0/wst/server/M8/milestone_plan.xml 
>  
> contains the milestone plan for M8 of the server component of WST
in WTP
> 1.0. 
>  
> 3. Each release will be a project and have a build script. You'll
only have
> to check out the release portion of the Web site from CVS to update
your
> plans. The build script will roll up your component plans into the
master
> plans. For example, to update the plans for WTP 1.0, check out the
project: 
>  
> /webtools/plans/1.0 
>  
> 4. Tutorials will go into the community part of the Web site and be
kept
> current, i.e. we will not keep tutorials for all milestones, just
the
> current one. Users will be expected to upgrade to the latest milestone.
>  
> 5. There are some very bulky UML models with generated HTML. These
will stay
> in the old directory structure. However, the source for the model
(not the
> generated HTML) should be checked into the development CVS repository,
NOT
> the Web site CVS. The HTML for the model will always be up to date,
i.e we
> will not have versions of the models for each milestone since they
are too
> bulky and are more like Javadoc than normal Web pages. If you need
an old
> version of a model, get it from the dev CVS. 
>  
> 6. Design docs will stay in the old directory structure and always
reflect
> the current milestone, i.e. we do not have per milestone design docs.
The
> source for the design docs should be checked in with the Java source
code in
> the dev CVS. 
>  
> 7. The API Javadoc will be removed from the Web site and packaged
in the
> Eclipse Online Help system Web site. We will add a redirect to the
new
> location. 
>  
> 8. The top level Web pages will point to the current plans. We will
also
> have a page for the archived and future plans. 
>  
> The above guidelines will keep the milestone-dependent parts of the
Web site
> lean and easy to update. 
> 
>  Arthur Ryman,
>  IBM Software Group, Rational Division
>  
>  blog: http://ryman.eclipsedevelopersjournal.com/
>  phone: +1-905-413-3077, TL 969-3077
>  assistant: +1-905-413-2411, TL 969-2411
>  fax: +1-905-413-4920, TL 969-4920
>  mobile: +1-416-939-5063, text: 4169395063@xxxxxxx 
> _______________________________________________
> wtp-dev mailing list
> wtp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
> 
> 
>
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev