Anthony Elder wrote:
wsif.apache.org sounds fine to me, probably everyone who liked
xml.apache.org/wsif would be happy with that also.

I think our main concern should be how long this will all take. We want to
have an Apache WSIF release this year and would like something better than
the current
http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-axis-wsif/java/readme.htm

Presumably with the ok of AXIS people we could create something at
xml.apache.org/axis/wsif very quickly? But wsif.apache.org or
xml.apache.org/wsif would take longer? Sam, can you verify any of this and
give us any idea if its feasible to be doing this in the time frame of this
release?
My assessment of the timescales:

http://xml.apache.org/axis/wsif.... now. Simply check in what you want here: http://cvs.apache.org/viewcvs.cgi/xml-site/targets/axis/. I have a cron job which updates the main site from this source four times a day. You already have access to this cvs site. As this was proposed on the axis-dev mailing list with no dissenters, you have permission. Go for it.

http://ws.apache.org/wsif or http://wsif.apache.org/... late next month. The people who create DNS entries are on vacation, backups are in place but really should only be used for emergencies. We may have a board meeting this month, but it will take time to hammer out a proposal for a PMC. The big question is whether we collectively want to pursue a web services PMC, or if WSIF would prefer to be independent.

http://xml.apache.org/wsif... hard to gauge. My guess is that most XML PMC members would prefer if one of the two alternatives above were pursued, and therefore would require convincing.

- Sam Ruby



Reply via email to