Gutenberg is a raw (unstyled) theme intended for use with CSS-based Movable Type layout styles.

This sentence is from the project home. From the discussion in #416022: Theme requires download of non-GPL files for CC licensing reasons of the DATA parts of theme the theme does not comply to the d.o rules. The screen shot does not show the theme how it looks like after the installation and therefore break users experience. See project http://drupal.org/project/gutenberg

Comments

dman’s picture

dman CreditAttribution: dman commented
Status: Active » Closed (won't fix)

Don't be silly.
I know you are just trying to make an argument, but Gutenberg is exactly what it says it is.
Trying to damage a good project because you think a decision reached on another issue is not fair is not a useful way to make your point.

hass’s picture

hass CreditAttribution: hass commented
Status: Closed (won't fix) » Active

No, I'd only think rules need to apply to all themes in the same way. The screenshot need to be removed or represent how it looks like after installation.

Gerhard Killesreiter’s picture

Gerhard Killesreiter CreditAttribution: Gerhard Killesreiter commented
Project: Drupal.org infrastructure » Drupal.org site moderators
Component: Other » Content moderation

moving

chx’s picture

chx CreditAttribution: chx commented
Status: Active » Closed (won't fix)

anyone seeing that screenshot will obviously realize that's not how it looks. Do not be silly. We are not a bureocratic multi that does comply with rules to the last dot. Rules are to protect us.

hass’s picture

hass CreditAttribution: hass commented

The screenshot used on drupal.org must accurately represent the theme.
In conjunction with the previous guideline, all screenshots used as part of the theme's project page must represent the theme exactly as hosted on drupal.org and not another version of the theme available elsewhere.

See http://groups.drupal.org/node/24465#comment-90217

So - you say - others are more similar than others? If we have rules, we need to enforce them. Otherwise all rules make no sense!

dman’s picture

dman CreditAttribution: dman commented

*sigh*
That text is not yet published because it's part of a current discussion drafting out what guidelines are appropriate.
Guidelines do not over-rule common sense. The guidelines are there to provide the best results, for everybody.
Clearly removing the pictures as you propose here would make the project, the information about it, and the information provided to users on drupal.org worse than it currently is.
So forget it.

I think that Gutenberg demonstrates why that draft wording and maybe even the policy should be revised a little bit before it is finished. But trying to prove your point by attacking innocent parties is just childish.
Trying to get Gutenberg unpublished is a purely negative and deliberately destructive idea.
Just stop it.

chx’s picture

chx CreditAttribution: chx commented

hass, I warn you to stop. Only your contributions have protected you from a ban in the past and i have not forgot the "this case is opened to waste testers and reviewers time" issue with you.

I was always against written rules here because of pricks like you.

bago’s picture

bago CreditAttribution: bago commented

I think that Gutenberg demonstrates why that draft wording and maybe even the policy should be revised a little bit before it is finished. But trying to prove your point by attacking innocent parties is just childish.

I agree that this issue is more a proof that current policy require more analysis in order to be used to decide what can be published and what not. That's why I'm discussing in the policy group trying to point any "weird" consequence of some "weird" proposed policy.

Trying to get Gutenberg unpublished is a purely negative and deliberately destructive idea.
Just stop it.

I agree. The point is that the policy needs tuning. Maybe "frameworks"/"bridges"/"base-themes"/"tutorial-themes" should better not use screenshot or maybe the policy should allow them (describing how to classify them) to use artistic screenshots or logos or a collage of the screenshots.

Maybe a good solution would be to classify themes in "ready to use" and "frameworks/bridges/tutorial" and then use different policies (and maybe different browsing pages on d.o.) for the 2 groups, but I guess someone is already thinking about this and how to improve d.o. with this regard.