Forum Replies Created

Viewing 15 replies - 1 through 15 (of 27 total)
  • Kinda sad to see you haven’t gotten a response to this. This is exactly what I started looking for today. Guess I’ll be coding it myself.

    Thread Starter saintehlers

    (@saintehlers)

    The vast majority of us have debated license issues ad nauseum in the past, and have no desire to get into such debates again.

    I’d prefer an upfront statement of “we don’t really debate that anymore” than the posts that appear to blow off my question without understanding it. I’ve had a long series of very disappointing contacts with the WP dev community. On the whole, most of my questions have not been acknowledged, and I’m kind of soured on it as a whole.

    Okay: how is CC-BY “attribution” being compelled for these images?

    Assuming the images were used in software/web pages, an appropriate place would be in the code comments. If used in some non-digital format, I can’t think of anyway to do it other than on the final product — though in something like a book or magazine there are acknowledgement or front-matter areas where it could unobtrusively be placed.

    From the question, should I infer that the issue is the means by which attribution is enforced? I can see that a front facing link could cause no small amount of consternation, given the other Theme Review requirements about authorship documentation.

    If that assumption is correct, then legally the 2 licenses would not be incompatible (legally speaking, and only given this particular set of circumstances).

    Just to cover my backside, and to reiterate my position, even if anyone agrees that this logic is correct, that doesn’t have any bearing whatsoever on WPORG policy. (Especially since if I’ve inferred correctly, I can see that being a beast to try and get reviewers to apply correctly.)

    Thread Starter saintehlers

    (@saintehlers)

    Yes, in the same sentence you mentioned the mailing list. note that the mailing list is what you linked to. You didn’t express that one was better, and the link implied that’s where I should go.

    Thread Starter saintehlers

    (@saintehlers)

    Chip: once again, that statement applies to software. It doesn’t address the situation I described.

    Thread Starter saintehlers

    (@saintehlers)

    forgive me for assuming that because the WordPress dev community has expressed an opinion on an issue that there would be a reason for that opinion.

    Thread Starter saintehlers

    (@saintehlers)

    Yes, Chip, your unnecessary update to a 10 hour old thread was very helpful. I already went in ticket (after I went to the mailing list and was yelled at there for being in the wrong place — perhaps WordPress moderators and helpers should coordinate to get the correct information out the first time).

    Thread Starter saintehlers

    (@saintehlers)

    Is this all about a theme that was submitted to the Theme Repository but was rejected because of licensing issues?

    No, it isn’t. It was inspired by that, but I’m not trying to get anything done on the ticket because of that. I’m trying to understand the policy itself. The only thing I’m trying to do is understand.

    OK – you’ve already been told that this is NOT the right place to raise these issues. If you have a problem with the Theme Review Team’s finding, then you need to raise it with the Team.

    Right. I’ll remember that when I have an issue with my theme I want to discuss

    Since this question is related to the ticket submitted to trac

    It’s not about the ticket. I know what I need to do and I’m not trying to change that. I’m trying to understand the policy and why WordPress thinks this way.

    According to GNU, CC-BY-SA is not GPL-compatible:

    This is a copyleft free license that is good for artistic and entertainment works, and educational works. Please don’t use it for software or documentation, since it is incompatible with the GNU GPL and with the GNU FDL.

    I could link many other sources that discuss the GPL-incompatibility of all CC licenses, but this should be sufficient.

    Please link the other sources or at least summarize the reasoning presented in them. Because I’m not asking if WordPress.org thinks they’re incompatible. And, if you read my earlier post, that quote is not sufficient. That quote states Please don’t use it for software or documentation. Images within the larger works are not software or documentation, and I have pointed at reasoning from legal experts consulted by WordPress that indicates they are. Given that, what is the reasoning?

    This is a topic I have researched, and I am trying to continue to research. I want to know what makes CC-BY-SA incompatible with GPL in the context I described above. No one, in the mailing list or here has even approached that issue, other than Ipstenu, who asserts that they are not incompatible in that context, which makes the question of “why” moot.

    Let me repeat, I’m not talking about if. Obviously, the WordPress developer community thinks that it is. I’m not asking that. And I’m not asking for a change for my ticket. I’m asking for the why so I can understand. I’m not hoping WP will change. I’m not trying to convince you anyone is wrong.

    Thread Starter saintehlers

    (@saintehlers)

    This post will probably sound like I’m irritated. I’m sorry if that’s so.

    1) Your post doesn’t answer my question. At all. I know that many WordPress users think that they aren’t compatible. That’s not what I wanted to know. I’m not sure that, even on the theme-reviewers mail list, I’ve seen anything that definitively says that CC is against WordPress hosting policy.

    2) From the page you linked: “We try to list the most commonly encountered free software license on this page, but cannot list them all” That is not a comprehensive list. Nor is it intended to be so. Nor does it state that CC is incompatible with GPL except as a license. My scenario above does not propose licensing any software with a CC license. Note also that my original post did link to that same page you linked to. This was not new information.

    3) It may very well be WordPress’s policy not to host any themes that have images with a CC license. However, that does not mean that they are incompatible. In fact, this article (which is on wordpress.org and which I linked to in my original post) indicates specifically that CC licensed images can be compatibly used in GPL software.

    So my question, which was conveniently set apart at the end of my post, still stands.

    And an additional question, who is right, Ipstenu or Esmi? Can CC licensed images be used in WordPress.org hosted themes or not?

    Thread Starter saintehlers

    (@saintehlers)

    Looks like that html 4 code is an IE thing… firefox shows no code at all.

    I’ve updated the files, right now I’m using just the index.php file. The contents:

    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <html>
    <head>
    <title>stuff</title>
    <link rel="stylesheet" href="<?php bloginfo( 'stylesheet_url' ); ?>" type="text/css" media="screen" />
    </head>
    <body>
    Yo momma
    </body>
    </html>

    But I don’t know why it’s not using the index.php file. I’ve verified that it’s in the directory it should be. And there is a css file with the WordPress header information:

    /*
    Theme Name: Monkey Duck
    Theme URI: -
    Description: The first of the "I Am A Genius" themes
    Author: Eric J. Ehlers
    Author URI: http://thelemur.net/
    Version: 1.0
    Tags: blue, two-columns, fixed-width
    
    License:
    License URI:
    
    That is all.
    */
    Thread Starter saintehlers

    (@saintehlers)

    it’s available to be seen: http://wptest.herbertlives.com

    (not that there’s anything to see with the theme activated)

    Thread Starter saintehlers

    (@saintehlers)

    Unfortunately, repairing doesn’t change anything

    The path and user information are correct, but I went ahead into the database and reset the password just to be sure.

    I’ll try to get hold of my host, but if anyone else has any ideas, I’d love to hear them.

    Interesting. I upgraded two sites. One upgraded with no glitches.

    On the other one, the network I was on briefly blocked a page from loading, but then it reloaded and seemed to go through the upgrade just fine. But the site was left locked in maintenance mode.

    There is no .maintenance file. I had to manually rename WPAU’s temporary index page and then change the backup index back to the index.php. Very disappointing.

    Also disappointing is the lack of backup in the native upgrade.

    it appears the js file update has corrected the issue. Thanks a huge bundle for your time and effort on this!

    I went on vacation. Checking out the site now.

    OckGal, may I ask what OS you’re using? I’m using 32bit vista on this computer.

    Just did some tests. I am getting identical behavior with Chrome, Safari, and Opera. (Safari has some other quirks with WordPress that have nothing to do with this plugin as well, reminds me why it’s not my primary browswer).

    All my browser and OS updates are current. But this happens on any computer, so I’m pretty sure it is environment (meaning OS and browser) independent. It’s something between WordPress and the Plugin.

Viewing 15 replies - 1 through 15 (of 27 total)