Pau Espin Pedrol <[email protected]> writes:
> Nah, now seriously, I think that's there's not a "single" plan because
> we spending our efforts in lots of different places.
Indeed. In particular, we are dividing our efforts between SHR-T and
SHR-U - in terms both of developer resource and of community attention.
Since posting my questions I've reflected a bit more and I think this is
my main underlying concern.
Especially given that SHR-U - which I've been running now for a couple
of months - actually seems very stable, and as far as know has no
significant downsides compared to SHR-T.
Therefore I wonder if SHR-T is still worthwhile....?
But, when trying to finalize that question, I realize that it depends on
what is likely to happen - in terms of stability - to SHR-U in the
future. And that in turn depends on what the overall plan for SHR is;
hence my questions.
> I would say there's a roadmap
> (or not) for each of this sections. For instance imho that would be:
>
> 1) Web -> Get better access to web server and clean wiki + show
> everything more user friendly.
OK, although that wasn't what I had in mind. I was really thinking of
just the phone software.
> 2) OE -> I think JaMa is working on an shr layer (Which I don't know exactly
> what's for :P) so I suppouse that's the plan.
I have no idea yet what that means.
> 3) UI -> work on Elfe + on screen kb
Elfe? (Google hasn't helped me here...)
> 4) Devices -> add support for devices.
Can you be more specific? For myself, lack of device support hadn't
occurred to me as a problem....
> So it seems the plan now is basically to cross out things from a TODO list
> which is in our heads.
>
>
> I would say this is decided by people which does it.
That is of course fine; but I still think it would be nice for the plan
to be more widely known.
Neil
_______________________________________________
Shr-devel mailing list
[email protected]
http://lists.shr-project.org/mailman/listinfo/shr-devel
