On Wednesday 02 October 2013 15:09:35 Aurélien Gâteau wrote: > On Wednesday 02 October 2013 14:48:45 Stephen Kelly wrote: > > Aurélien Gâteau wrote: > > > On Wednesday 02 October 2013 12:06:57 Stephen Kelly wrote: > > >> Aurélien Gâteau wrote: > > >> > I don't have any strong opinion on this, but if we allow tier2 > > >> > frameworks to depend on other tier2 frameworks then is there a need > > >> > for > > >> > tier3 at all? Your wiki pages seems to indicate there is no need for > > >> > it. > > >> > > >> That wiki page predates the Randa meeting, where some stuff was made > > >> more- concrete. I don't know of any reason to not let tier2 depend on > > >> tier2 though. > > > > > > Still, what would be the difference between tier2 and tier3 if tier2 > > > frameworks were allowed to depend on other tier2 frameworks? > > > > I don't know. > > > > I don't see any benefit of 3 tiers instead of 2. I'd collapse tier3 into > > tier2 if it was my decision :). > > I agree with this, but I think you should start a separate thread to discuss > this topic, otherwise it is going to be missed by David, Kevin and others.
For the record, I strongly disagree with this. It's one of the design decisions taken during Platform 11 that I think should survive (some other we changed along the way of course). The tiers are here to give information to third parties using our frameworks. Why three for the number of tiers and not two or twenty? It's almost arbitrary of course. Three is an interesting sweet spot from a third parties perspective as it gives a gradual picture of the dependency tree depth you pull while at the same time not overdoing it. At one point conveying the dependency tree depth doesn't bring value anymore hence why it should be kept low. OTOH, with one or two you loose the "gradual effect" (I lack a better word here) completely. So yes, this choice in the number of tiers is mostly for communication with outsiders purpose and marketing (tier 1 easy to reuse, tier 2 a bit more deps but manageable still, tier 3 be ready to be motivated to bring them in your project). Regards. -- Kévin Ottens, http://ervin.ipsquad.net Sponsored by KDAB to work on KDE Frameworks KDAB - proud supporter of KDE, http://www.kdab.com
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel