BluePrint and admin

[Michael Bishop]

As it seems khaled is quite busy, I was discussing with h0bbel on IRC
about the fact that we are using BP .5, and .6 is out. Apparently,
khaled made changes to the core .5 files, so upgrading to .6 borks the
admin. Christian (h0bbel) suggested doing a diff of our BP CSS files
against default BP .5 CSS files, and moving those changes to our
admin.css so upgrading wouldn't be an issue. Any objections to doing
such, and upgrading our version to .6? I know some discussion was had
to using a svn external, but I'm not sure using their trunk would be
in our best interest.

~miklb

[Matthias Bauer]

Go ahead with merging the changes. svn:externals isn't suited for what
we're doing, I think, but I also think it might be nice if it were. That
is to say, if we can use stock Blueprint from their SVN, and keep all
our changes in local files, that'd be nice.

But, merging is more pressing, the rest is just nice to have.

-M

[Owen Winkler]

On 10/15/07, Matthias Bauer <moe...@moeffju.net> wrote:
>
> Go ahead with merging the changes. svn:externals isn't suited for what
> we're doing, I think, but I also think it might be nice if it were. That
> is to say, if we can use stock Blueprint from their SVN, and keep all
> our changes in local files, that'd be nice.

svn:external would work fine if we chose a tag from their repo to
attach to. There's no reason to use trunk when a tag is what we're
after, and there's no reason to keep in our repo what is stored in
theirs just fine.

I agree -- We should go ahead with moving the specific changes out
into the admin.css so that we can upgrade by using svn:external to
include a tag with our distribution.

Owen

[broke...@gmail.com]

Just got back from holiday in Japan so I am still sifting through 500 plus emails however this sounds like a good idea. Also the latest BP has got s Plugin architecture set up so that if we want we can have a specific file that is effectively a Habari file that superceeds the core files making upgrading a real small issue

I am planning on getting back into the swing of things this weekend but if you guys want to begin that process that would be most excellent

------------------

-----Original Message-----
From: "Owen Winkler" <epi...@gmail.com>

Date: Mon, 15 Oct 2007 20:07:12
To:habar...@googlegroups.com
Subject: [habari-dev] Re: BluePrint and admin

[Chris J. Davis]

Welcome back Khaled. I hope your time in Japan was good. Lucky sod.

It is going to be a very interesting place to be around next week.
There should be a lot of movement where the admin is concerned.

Chris

[Michael Bishop]

Glad to see you back. Indeed these changes have been made, there's
another thread outlining what freakerz and I did last night, or you
can check the commit logs. Looking forward to getting moving forward
more quickly with your return.

~miklb

On Oct 17, 12:44 pm, brokenk...@gmail.com wrote:
> Just got back from holiday in Japan so I am still sifting through 500 plus emails however this sounds like a good idea. Also the latest BP has got s Plugin architecture set up so that if we want we can have a specific file that is effectively a Habari file that superceeds the core files making upgrading a real small issue
>
> I am planning on getting back into the swing of things this weekend but if you guys want to begin that process that would be most excellent
>
> ------------------
>
> -----Original Message-----
> From: "Owen Winkler" <epit...@gmail.com>
>
> Date: Mon, 15 Oct 2007 20:07:12
> To:habar...@googlegroups.com
> Subject: [habari-dev] Re: BluePrint and admin
>

[Michael Bishop]

Just a quick question about licensing. I just read that BP's next
version will be dual licensed under MIT and GPL, and wonder how that
would effect it's inclusion in Habari. The current license is much
different. I'm assuming this will be acceptable, as jquery has done a
similar thing, and offers both the MIT license as well as GPL, but
thought it worthy to bring up before embarking on the overhaul.

A brief discussion in the BP google group related to where I found it
http://groups.google.com/group/blueprintcss/browse_thread/thread/290f0aecedae1cc1.

The license for Blueprint in their head http://blueprintcss.googlecode.com/svn/blueprint/trunk/License

Jquery's page http://docs.jquery.com/Licensing

~miklb

[Andrew da Silva]

Indeed we just choose to use MIT license.

I can't remember if Blueprint was specially released to us in AL2?

On Oct 17, 11:41 pm, Michael Bishop <miklb.onl...@gmail.com> wrote:
> Just a quick question about licensing. I just read that BP's next
> version will be dual licensed under MIT and GPL, and wonder how that
> would effect it's inclusion in Habari. The current license is much
> different. I'm assuming this will be acceptable, as jquery has done a
> similar thing, and offers both the MIT license as well as GPL, but
> thought it worthy to bring up before embarking on the overhaul.
>

> A brief discussion in the BP google group related to where I found ithttp://groups.google.com/group/blueprintcss/browse_thread/thread/290f....

[Christian Mohn (h0bbel)]

I don't think it was specifically released to Habari, as it was MIT
licensed to start with.

[Michael Bishop]

I don't believe it was MIT to start, but generic enough that we could
use it. Either way, I don't think it's an issue, but wanted to be
sure.

~miklb

On Oct 18, 2:42 am, "Christian Mohn (h0bbel)" <h0b...@gmail.com>
wrote:

[Christian Mohn]

http://ars.userfriendly.org/cartoons/?id=20071030

-----Original Message-----
From: habar...@googlegroups.com [mailto:habar...@googlegroups.com] On
Behalf Of Michael Bishop
Sent: 18. oktober 2007 17:06
To: habari-dev
Subject: [habari-dev] Re: BluePrint and admin