[theme-reviewers] A Question About Theme Review/Submission

Tue May 24 21:55:41 UTC 2011

Chip/Otto/Shawn,
  Thanks for the info and perspective.  I see why it would be a bit odd to put such themes in the General Repo.

--
> The other issue with Custom Post Types is that the data become locked into the Theme. Since we do not want to encourage Theme lock-in of data, our current stance is to request that the CPT functionality be developed as a Plugin (hosted in the Plugin repository), that can be used by the Theme, or incorporated into other Themes.
--
> This is not to say that there's not a place for such themes, however, that place is not currently within the general repository. Again, if you are determined to release the theme with support for the extended functionality, my suggestion would be to implement the core requirements into the theme and have that pass as a general theme, and then create a custom plugin which will control the extended functionality. 
--
  I don't disagree with any of your points of view and appreciate the input.  We have quite a few of these 'application' type WordPress themes that are GPL in development so it is a bit disheartening that they can't be included in the General Repo.  Maybe one day there will be an 'Application Repo' that clearly states they use Custom Post types and are not Regular blog, magazine, news, portfolio, etc, etc (sweet WordPress), themes.  In my view, sites like Trac, FogBugz, Bugzilla etc wouldn't be a plugin as much as the Core of the site.  There is no other content but the tickets.

  I see what you are saying about data lock-in.  Even with a plugin and a custom post type the data would be locked into that post type. As I think about it, if you add any Custom Taxonomy you have already automatically locked-in that data too.   It seems to me that creating a plugin that adds this functionality doesn't really solve the problem with the data being 'stuck' except that a user can switch their theme.  They would still be stuck to our plugin so it just pushes the problem deeper down.  

  We definitely don't want to create anything that makes the Users not able to use their data after they decided they don't want to use the theme anymore.  While I could make the theme use actual Post type it doesn't seem to make sense logically.  A 'Post' infers a much different thing then a 'Ticket'.  You would also only be locked in by terminology.  You could still export the info and change any post-type or taxonomies you would like.

> The idea of "themes" as being
> "apps" is relatively new, so there's bound to be some core changes to
> segregate and explain these types of things before they get in.
--

Well, if you all ever need some help with anything regarding these types of thing I know some people that would be more then willing to help out.  I think application type themes are going to be coming along in the WP domain and it would be too bad to not have a good place to disburse the GPL stuff.

Hopefully, I haven't wasted to much of your and everyone else's time on here.

-Ryan

On May 24, 2011, at 5:21 PM, Chip Bennett wrote:

> It depends on how you "make it pass".
> 
> If you find a way within the design intent of the Theme to incorporate the required functionality, then absolutely: yes, it would pass.
> 
> But, if you tried to "game" or work around the requirements, then it would be failed.
> 
> The other issue with Custom Post Types is that the data become locked into the Theme. Since we do not want to encourage Theme lock-in of data, our current stance is to request that the CPT functionality be developed as a Plugin (hosted in the Plugin repository), that can be used by the Theme, or incorporated into other Themes.
> 
> Chip
> 
> On Tue, May 24, 2011 at 4:17 PM, Ryan Frankel <ryan.frankel at gmail.com> wrote:
> Otto,
>  Does this also mean if I make it pass all of the tests it would still be rejected by the Theme Review team?
> 
> -Ryan
> 
> On May 24, 2011, at 5:06 PM, Otto wrote:
> 
> > On Tue, May 24, 2011 at 2:35 PM, Ryan Frankel <ryan.frankel at gmail.com> wrote:
> >>  I am trying to submit a ticket task/management theme to the WordPress repo
> >
> > Custom purpose-built themes cannot be submitted to the repository at
> > this time. Themes must currently support a standard blogging platform
> > or CMS type of system.
> >
> > Heck, right now we're not even allowing child themes due to a lack of
> > core support for them (will very likely be in WP 3.3). Before allowing
> > this sort of thing into the repository, it would have to be discussed
> > and considered by the core dev team. It might be worth bringing it up
> > when the 3.3 features discussion takes place around early-mid July
> > (after 3.2 is released).
> >
> > -Otto
> > _______________________________________________
> > theme-reviewers mailing list
> > theme-reviewers at lists.wordpress.org
> > http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> 
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> 
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers