Pollinate Status and Meeting Agenda 2004-09-30 [message #47181] |
Thu, 30 September 2004 18:59 |
Dan Rubel Messages: 17 Registered: July 2009 |
Junior Member |
|
|
Pollinate Status and Meeting Agenda 2004-09-30
Anyone interested may attend the weekly Pollinate conference call:
Thursday, September 30, 2004
1 pm PDT / 4 pm EDT
1-858-300-3030 (San Diego, CA)
Participant Access Code: 84484
1) News
Congratulations !
Pollinate 1.0 M1 is now available !
The main link to Pollinate is *should* be ready by the end of the day
http://www.eclipse.org/pollinate/
but if it still points to the Pollinate proposal page, then please use t=
he =
alternate link
http://dev.eclipse.org/viewcvs/indextech.cgi/~checkout~/poll inate-home/=
index.html
Content on the new Pollinate site includes:
- Install using update manager, zip files, or CVS
- Walkthrough document for you to "kick the tires"
- Goals, Plans, Links, and of course Bugzilla
Thank you to all who worked hard to get this release out, especially Car=
l =
McConnell and Alexander Smirnoff.
Thanks also goes to Susan Iwai and others at Eclipse and IBM for helping=
=
me get various website site issues ironed out.
2) Development
Ok... time for us to catch our collective breath... evaluate what we've =
accomplished and where we want to go. The theme for Milestone 1 was get =
all the non-UI working for NetUI page flows from start to finish... and =
we =
accomplished that. Even though there are not any fancy editors in place =
yet, M1 can be used to build and execute a page flow based webapp. For =
Milestone 2, I recommend we focus on editors and views for the code that=
=
we build and execute. We'll have to build specialized parts such as a pa=
ge =
flow editor, but perhaps we can pull in other parts, such as a JSP edito=
r, =
from WTP or others.
An of course... respond to Bugzilla entries... :-)
We are looking for additional volunteers to help pull open source =
contributions from elsewhere into Pollinate. For example, it might make =
sense to extract a JSP editor and make it a standalone piece so that =
Pollinate can use it. The work can happen in WTP CVS, or it can happen i=
n =
Pollinate CVS with the idea that it is to be contributed back to WTP. If=
=
you are interested in helping, please feel free to attend our weekly =
conference call (same time, number, and passcode as shown above each and=
=
every week) or send email to the pollinate-dev@eclipse.org mailing list.=
3) Discussion
First, I would like to hear what worked and what did not for our M1 =
release.
Second, there has been a request to reschedule Milestone 2 from =
mid-December to November 12 so that it can be presented together with =
Beehive at ApacheCon. Obviously that will mean cutting back on what we a=
re =
to accomplish in M2, but it seemed like a reasonable request. We'll =
discuss and decide if this is how we want to proceed.
Third, here are some of the things that *could* go into M2 (obviously no=
t =
all of them will)...
- java page flow editor
- other beehive specific editors such as page flow editor
- move to new version of Tomcat(?) and Beehive
- junit tests
- automated nightly build
- move build and update site to proper Eclipse.org download servers
- how do we get rid of our reliance on the "tools.jar" ?
- support files named *.jpf (currently java page flow files have to be =
named *.java)
- new launching UI similar to java launching and external tools launchin=
g =
dialogs?
- review WTP server tooling
- review WTP JSP editor (if there is one) or other existing contribution=
s
4) Tasks
Tasks currently underway:
- evaluate M1 process... what can be improved?
- plan for M2... what do we want to tackle next?
5) Pollinate links
Pollinate Home (*should* be working later today)
http://www.eclipse.org/pollinate/
Alternate Home (in case the link above still points to the proposal)
http://dev.eclipse.org/viewcvs/indextech.cgi/~checkout~/poll inate-home/i=
ndex.html
|
|
|
Powered by
FUDForum. Page generated in 0.03129 seconds