Mark Martin wrote:

> The export is available at:
> http://cr.opensolaris.org/~devnull/portal/myfile.del

Hmm, unfortunately I think the data in there will cause the most horrid 
index skew as it is all very similar - plus I've changed the table 
definition slightly - that's less of an issue as the extra fields are 
all optional.

Several other people have contacted me offline with basically the same 
thing.  I really don't want people to end up duplicating work that is 
already being done, so could I please ask that people state their 
intentions on website-discuss *before* starting work on stuff?  I'm 
delighted that people want to help, and I really don't want people to 
put in time and effort that is duplicated, I'd be upset if people got 
annoyed and felt their time had been wasted, I really appreciate the 
people who have come forwards so far.  There is loads of stuff to do, 
but it is probably best if we only do it the once ;-)

> As well, I'm submitting a small diff for the validation.xml for signup to
> match with the DDL on the DB:
> http://cr.opensolaris.org/~devnull/portal/portaldiff.txt
> 
> I would have run webrev on it, but a) it's such a trivial fix and b) I'm
> still getting up to speed on webrev yet.

We don't have any reasonable way of building the portal software that 
doesn't involve it actually being installed on your build machine by the 
build process.  Sorting that out is probably the first priority, if 
anyone is interested in working on it.

And be aware that as I explained in 
http://www.opensolaris.org/os/project/website/website_restructuring/, 
the priority is to get rid of the current webapp as quickly as is 
possible, so if people *do* choose to work on it, they should be aware 
that it is effectively an evolutionary dead end.

*PLEASE* read the stuff under 
http://www.opensolaris.org/os/project/website/, it explains the plans, 
and if it doesn't do so sufficiently clearly, let me know and I'll amend 
as necessary.

-- 
Alan Burlison
--
_______________________________________________
website-discuss mailing list
[email protected]

Reply via email to