On 05/19/15 15:34, Carsten Haitzler wrote: > On Tue, 19 May 2015 12:49:51 +0200 Tomasz Swierczek <[email protected]> > said: > >> Apart from being a common part of all profiles, this *really is* the base for >> work of Tizen security team. >> >> Without Common we will have a big problem in keeping all our work properly >> tested & released - and we may quickly end up with 3 separate "Tizen's" on >> each profile. >> >> >> Like Stephane wrote, Common's status *needs to be clarified*. Unfortunately, >> I'm not the person with authority to do this. > > the status is the same. the problem is - people don't really care. they are > tasked to work on tizen tv or tizen mobile, so that's what they work on. > everything else is irrelevant. they are not interested in common or any other > profile. it's the reality. > > our core problem is that we HAVE PROFILES (as in separate tizen stacks). this > should cease imho. there should be just "tizen". a tizen MOBILE device may > add/include some extra daemons or packages (or remove some). same for tv or > ivi > etc. etc. - a profile should be nothing more than a list of guaranteed minimum > libraries, services and "ui style".
so we don't have a chance of having maintainers reject patches because "this belongs in Common"? _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
