licensing problems

This is not going to be a problem.

Apache 2 software can therefore be included in GPLv3 projects, because the GPLv3 license accepts our software into GPLv3 works. However, GPLv3 software cannot be included in Apache projects. The licenses are incompatible in one direction only, and it is a result of ASF's licensing philosophy and the GPLv3 authors' interpretation of copyright law.

http://www.apache.org/licenses/GPL-compatibility.html

Moving status to closed

Can we publish the theme under GPLv3 ?
Regarding to those links?
http://drupal.org/licensing/faq#q4
http://www.gnu.org/licenses/license-list.html#apache2

no. As stated in http://drupal.org/licensing/faq/#q4 it must be the same license as drupal core to be added to drupal git repositories. If it can't go into the git repo it subsequently can't be distributed from drupal.org

you may only check it into Drupal's Git repositories if you are releasing it under the same license as Drupal itself, that is, GPL version 2 or later. If you are unable or unwilling to do so, do not check it into a Drupal Git repository.

You can release the theme on your own site under GPL3 or another license.

Even if the code is re-licensed, it's still not allowed on Drupal.org under the 3rd party code policy:

http://drupal.org/node/422996

Modules work around this via the Libraries API, but that's unfortunately not available for themes. Probably the best you can do is put instructions in README.txt and make sure the theme displays useful errors when the code is missing.

what have you decided? i think it's worth working on, and would be willing to help with it

by my interpretation of http://drupal.org/licensing/faq#q4 then you can license this theme as GPL3, and thus released on d.o. However, the actual bootstrap library would not be committed to the repo and would have to be downloaded seperately. This still sounds fine to me.

Why not just use
in the theme hosted on drupal.org? And like others have said before, insert additional instructions in the read me file for people that wish to download the CSS.

[edit]my
tag that was taking the css from github is taken out by the input filter... the idea was the same as the one described bellow by darrenmothersele. I agree that this solution can work)

I think the interesting work for this theme is to get Drupal core to play nicely with Twitter Bootstrap CSS. You don't need to include the CSS code to do this. The useful thing to do would be provide form_alters and theme overrides to be able to use Bootstrap without too much work. This could be done as a base theme, providing instructions for users who want to download and customise the CSS.

The Bootstrap GitHub page recommends hotlinking the CSS. Could this be done, as it wouldn't be including the code directly in Drupal's repo?

Simply do not include the bootstrap files inside your project, hundred of other project do the same. The user have to download it after. You can even fail back by hotlinking the CSS.

Made a headstart at: https://github.com/Docc/twitter_bootstrap

Though im happily to contribute back into this project once the licensing problem is settled.

@Docc check also https://github.com/bastnic/mothership_twitter_bootstrap Works with mothership but you can certainly grab some stuff.

Just a heads up for everyone, The repo moved to this project on drupal.org.

Alright twitter bootstrap files are now hotlinked. These files can be overridden from the theme settings page.

Great !
btw, which version of twitter bootstrap are you going to support? v2.0 will be out soon.. you can see its demo here : http://bootstrap.io/Demo/

V2.0 is nearly complete, from what i see on the github issue queue.

The demo link above does not work. I was able to successfully just grab the repo and open the index.html file in docs/ to view the new demo. There are some major changes to 2.0 and I would love to help get these integrated ASAP!

Starting a new issue...

Waiting for v2 myself.
Big change ill open up a new 7.x-2 branch for it soon and continue work there based on V2.

Though this is not what this issue is about. Create a new one if needed.

@rerooting, if you want to help drop me a line.