Hi,
I agree with the use cases proposed. I don't think the technology
used to create the website matters. It can be .net, Spring MVC or any
thing. I think the convenience of the developer who ever takes the
responsibility should be deciding factor for now. When the library is
released and is doing good, if required the website can be modified if
required. I don't think this website is complex.
I think some one needs to create a wire-frame sketches on how the website
would look so that every one can have a look at them and provide the
feedback. It would make the life easier for who ever is implementing the
web site and reduce rework.
While we are discussing the options to make this library more user
friendly, I think we need to look at the code bases also. The structure in
which they are committed to svn are confusing(partly make be due to lack of
documentation). If possible each component in this should have its own
repository. Is this some thing that can be considered ?
Thanks,
--Kiran
