For the record, I don't really think the discussion here is regarding personal likes/dislikes of Blueprint. The discussion is regarding the recent changes in the Blueprint development infrastructure and how we should handle it. All I'm saying is that if we use Blueprint, by all means include it. If we don't, well, then don't. It's pretty simple.
If this turns into a discussion about semantics etc, count me out. I'll leave that to the more pig-headed and verbal amongst us. Christian From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Arthus Erea Sent: 28. august 2008 00:04 To: [email protected] Subject: [habari-dev] Re: Vote: Blueprint Inclusion On Aug 27, 2008, at 5:59 PM, Chris Meller wrote: On Wed, Aug 27, 2008 at 4:56 PM, Christian Mohn <[EMAIL PROTECTED]> wrote: So, why should we then include blueprint at _all_, if we don't use any of it? We don't bundle software from others just because we can. We did include it since the admin used it and we thought that this was something that could benefit theme developers. If the decision now (made by who?) is that we won't use Blueprint, I can't find a single reason why we should bundle it _at all_. Can someone please clarify my confusion? The admin *does* use it, and I personally think it should use it more to standardize the way we do layouts. And I still think it will be useful to theme developers. It seems Heilemann is the only one who doesn't like / doesn't see the point of BP. That, in itself, does not constitute a decision to not use it. For the record, I don't like BP either. I think the #1 thing to be pointed out is that Monolith, as is, doesn't rely on BP for anything beyond baselining (which we could easily do ourselves). I don't see a reason to include an external framework which we don't really need. I don't have a vote. --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/habari-dev -~----------~----~----~----~------~----~------~--~---
