On Saturday 13 February 2010 16:08:12 Ian Clarke wrote:
> On Sat, Feb 13, 2010 at 10:02 AM, Ximin Luo <xl269 at cam.ac.uk> wrote:
> 
> > On 02/13/2010 03:38 PM, Ian Clarke wrote:
> > > She can and will not do this if she has to work with FProxy because
> > FProxy
> > > is an ungodly mess, and her expertise is with GWT.
> >
> > I think really the main issue is switching out FProxy. This will take a lot
> > of
> > effort and people aren't ready to commit to it, especially people that are
> > used
> > to working with FProxy.
> 
> They will be able to continue to work with FProxy, the new UI will be
> designed in parallel and will only become the default when it has reached a
> sufficient level of functionality.

Which practically means that any work to improve the current UI is shelved 
because eventually we might have a shiny new one. This is bad, because it is 
the developers who will be maintaining the new UI in the long term.
> 
> > For this reason, I think it'd be easier to have someone completely new to
> > the
> > project, to work on what you're suggesting; maybe a couple of GSoC
> > students.
> > There needs to be a lot of base stuff done before pupok can start with her
> > stuff, and this will take a long time to do.
> 
> Several problems:
> 
> We've had a lot of GSoC students, but we've never had a designer.

I agree this is far too big a job for a SoC.
> 
> Pupok is only available now because her current employer is shutting down
> and she doesn't have much work to do for them.  She almost certainly will
> not be available to work on this after April.

There is very little chance that she will come up with a full UI redesign 
complete with code by the end of April. It's just way too big. And it will be 
dependant on us providing clean APIs to access everything. And if it's only a 
partial UI, yet it is architected as a full redesign, what happens? We either 
take it on and do a huge amount of work to finish it, or we throw it out.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 835 bytes
Desc: This is a digitally signed message part.
URL: 
<https://emu.freenetproject.org/pipermail/devl/attachments/20100213/55236d78/attachment.pgp>

Reply via email to