I just made a new project release for http://drupal.org/project/fall and the message said it would take up to 12 hours for it to process. Is the system backtracked because its been way over 12 hours. Thank you,
Dan Silver

Comments

Jeff Burnz’s picture

I think all new projects might be going through a vetting stage, if you made release node from head it comes up within 12 hours.

If the theme was created with artiseer or similar expect it to be removed, as generated themes, afaict, are not permitted in the drupal repo.

silverhosting’s picture

as I understand, Artisteer themes are allowed, just not bulk uploading. I plan to have this theme, my only theme for now, my prime goal. So is there any problem with that? Frankly, I don't see how it matters how I made my theme.

Jeff Burnz’s picture

Hey man I don't make the rules around here, if I did they would *definitely* all be deleted.

WorldFallz’s picture

I don't see how it matters how I made my theme

Of course it matters. drupal.org is not sourceforge-- hosting code on drupal.org is a privilege not a right and we're not obligated to host any old code someone cares to post just because it works with drupal.

The fact is artiseer enables anyone to create a drupal theme, without knowing anything about drupal or theming, with a couple of keyclicks in a couple minutes. There's nothing wrong with that in itself, but there's certainly nothing that suggests such a theme belongs on drupal.org. Also, in many cases the person posting such a theme is likely incapable of supporting it and probably won't. Not that long ago someone tried to spam drupal.org with 27 (yes, twenty seven) artiseer themes in the space of a couple of hours.

We're currently trying to come up with a policy for themes hosted on drupal.org-- see http://groups.drupal.org/node/24465 for more info.

silverhosting’s picture

so just because I like to use Artisteer and other people like to use code means that I can't use my method. This is crazy, i'm not posting it "because it works with Drupal" , I'm posting it for the same reason you would post a theme. To give back to the community and help other webmasters have a nice looking site, as well as a variety of theme options. But, if Drupal.org wants to discriminate against people that use different methods other than code, whatever.

Jeff Burnz’s picture

You can share your theme in many places including your own site where you can amass a huge collection of these themes and simply give them away - no one is preventing you from doing so.

You have already created two project pages - Fall and Autumn, so one assumes you are about to add Summer and Winter also? Four cookie themes that any user with Artiseer could replicate tomorrow and add to the repo again, complete with links to their hosting service and "web development" services.

Themes are looking like d.o's new spam, and these cookie cutter themes are just too easy to generate, upload and spam d.o with. That is the problem. If we let one in where do we draw the line. I personally am not against artiseer per se, what I and many others are concerned about is giving Drupal users the best selection of themes, that are not just cookie cutter back-link laden Trojan horses - I'm not saying yours are, but be sure that this is exactly what will happen if we let these themes in. Not everyones intent is altruistic.

Please don't diss out community decisions, this is a serious issue that is being debated - get involved with the debate, contribute, evolve. Learn how to theme, port your artiseer design to be a Genesis subtheme adn contribute that (at least that shows you at least know the rudiments of theming and could support your CSS).

WorldFallz’s picture

There is a big difference between a 'designer's method' and using a 'factory' like artiseer. All anyone needs to recreate an artiseer theme is a click recipe-- they don't need you, your particular skills, or any other designer. Just 'click here and click there". Sorry, but there's no reason to host such a theme on drupal.org. And as jb says-- there's nothing preventing you from giving back to the community by setting up your own repository and posting all the artiseer themes you want.

Let's at least be honest here-- we all know the google juice drupal.org has. Don't be disingenuous by suggesting you're merely doing it to 'give back'. Going by your sig, as well as both your usernames, posting themes or modules to drupal.org amounts to significant sef free advertising for your businesses. Which is also fine. But you should have to do more then click a couple of buttons in a ui for it.

EDIT: I would also like to add the I actually like and use artiseer-- I'm completely graphically challenged and it saves me a great deal of time creating a theme (though I don't consider the drupal theme usable without some help, the graphics and layout are a life saver). However, I would never think of submitting one of those themes to drupal.org. Besides the reasons I describe above, artiseer themes are extremely obvious, and I wouldn't want to use it to showcase myself on drupal.org.

silverhosting’s picture

So is someone going to delete my themes or have me waiting forever until they are approved and people can download them?

vm’s picture

likely neither until such time as a webmasters issue is created.

silverhosting’s picture

i will do that now

silverhosting’s picture