Hi,

So, previously we had rsync, now we have web based access. Let me try to
describe why I think it's not move in the right direction.

a) rsync was simple
Not hard to setup. Just account on opensolaris.org and manage your ssh
keys

b) fast
20 seconds to upload a webrev?

c) command line - simple to automate
well, I had a script which uploaded me the webrev automatically to
cr.opensolaris.org . Just a single word 'wxwebrev' and all the magic
happened which told me url for my new webrev.

d) accessible
If I wanted to upload a webrev, all I needed was a terminal


Instead now we'll have


a) Account on opensolaris.org, for each project you have to ask leader
to add you as developer (I haven't found yet how)

b) don't know yet (cr.opensolaris.org does not think I'm worthy yet),
but you have to open a browser, find project and there will be few
clicks more to upload a webrev

c) every time you make user click, god kills a kitten. Remember that.
And every time you want to automate gui you must enslave monkey. Sure
eventually I could write wget/curl wrapper to upload the webrev using
http, but why bother?

d) I'm making my changes on a remote Solaris server. My notebook is
using Windows. So I'll have to find a way to transfer the webrev from
Solaris to Windows (or other devices I may use) and then I'll be able to
upload using some browser. Accessible? Hardly. Slow? Sure.


I have no say in how cr.opensolaris.org will work. But why should I use
that instead of ~/public_html inside Oracle network?


Out of curiosity, what was the motivation to make uploading of webrevs
harder? Let me guess, make reviewing harder by forcing people to use
some web interface instead of mailinglist? If yes, I'm starting to see
the pattern ...

Cheers
-- 
        Vlad
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Reply via email to