<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=windows-1252" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18928">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2 face=Arial>The point is for the end user to have a variety of
new design styles available. Nothing more, nothing less. While they
are available at tertiary sites the only real concern is your valid one on it's
point of being an update free situation.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>*which* if possible could be rectified by
having them *not* on the update notification list from the wordpress
repository, but still available. Main themes available to be updated
by child themes not would certainly solve that.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: black"><B>From:</B>
<A title=chip@chipbennett.net href="mailto:chip@chipbennett.net">Chip
Bennett</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A
title=theme-reviewers@lists.wordpress.org
href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Wednesday, January 19, 2011 7:17
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [theme-reviewers] WPTRT =
TSA?</DIV>
<DIV><BR></DIV>Originally, Child Themes were intended to be *update-proof*,
not "more update-proof", than (stand-alone) Themes. They were intended as a
way for the *end user* to add Theme modifications that would be retained when
the Parent Theme was updated.
<DIV><BR></DIV>
<DIV>The point of the Repository (at least, now that it is tied into wp-admin
via automatic updates) is to push Theme updates to end users.</DIV>
<DIV><BR></DIV>
<DIV>Thus, the two purposes - to provide a means of update-proof Theme
modifications and to push Theme updates - conflict, if the code in question is
the same (i.e. a Child Theme).</DIV>
<DIV><BR></DIV>
<DIV>If end users will be asked to change the Name: tag of the Child Theme, in
order to prevent it from being over-written, then what is the point of hosting
that Child Theme in the Repository in the first place?</DIV>
<DIV><BR></DIV>
<DIV>(Now, on the other hand, I can see great advantage in encouraging Child -
rather than derivative - Themes for TwentyTen, TwentyEleven, or whatever
current default Theme.)</DIV>
<DIV><BR></DIV>
<DIV>Chip<BR><BR>
<DIV class=gmail_quote>On Wed, Jan 19, 2011 at 8:54 PM, Philip M. Hofer
(Frumph) <SPAN dir=ltr><<A
href="mailto:philip@frumph.net">philip@frumph.net</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV bgcolor="#ffffff">
<DIV><FONT size=2 face=Arial>Child themes are more update proof then
the standard theme, not sure where you are getting and really would
like an elaboration on the 'intented benefit of child themes'. Which
i'm going to assume you're thinking of the fact that it's good to have a
child theme that is not going to lose it's look when the main parent theme
is updated. In that case I am going to note that a child theme
can still be customized to denote a non-update path by changing the name in
the style.css; just like a theme. If you're going to snag
a child theme or theme and make customizations it would be a benefit to
customize the name to remove it from upgrade notification.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV> </DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV class=im>
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV style="FONT: 10pt arial; BACKGROUND: #e4e4e4"><B>From:</B> <A
title=chip@chipbennett.net href="mailto:chip@chipbennett.net"
target=_blank>Chip Bennett</A> </DIV></DIV>
<DIV class=im>
<DIV style="FONT: 10pt arial"><B>To:</B> <A
title=theme-reviewers@lists.wordpress.org
href="mailto:theme-reviewers@lists.wordpress.org"
target=_blank>theme-reviewers@lists.wordpress.org</A> </DIV></DIV>
<DIV>
<DIV></DIV>
<DIV class=h5>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Wednesday, January 19, 2011
6:42 PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [theme-reviewers] WPTRT
= TSA?</DIV>
<DIV><BR></DIV>I would like to do something about the horribly out-of-date
and obsolete Themes in the repository, but maybe now isn't the right time
- other than trying the positive-reinforcement route (a Theme adoption
program). Maybe once we've had a year or so of Themes passing the Theme
Review process, we'll have enough of a selection to justify arguing to
begin suspending the most egregiously obsolete Themes.
<DIV><BR></DIV>
<DIV>I go back and forth on Child Themes, but at the moment, I'm leaning
*against* having Child Themes in the Repository. I really believe strongly
that Child Themes should be left completely to the *End Users*, as their
means of implementing update-proof Theme modifications. If we start
encouraging the distribution (and, therefore, *update*) of Child Themes,
we encourage depriving the End User of the the primary, intended benefit
of Child Themes.</DIV>
<DIV><BR></DIV>
<DIV>The Frameworks discussion has progressed well, and as you said: now
is probably a good time to move that discussion to a wider audience, via a
post on the Make site. I think we can make some good strides with
Frameworks.</DIV>
<DIV><BR></DIV>
<DIV>I agree regarding SVN-commit access for *trusted* developers -
especially initially (or as a trial run). The potential for abuse is huge
- and SVN-commit access for Themes could be pitched as a form of
award/recognition/achievement for great contributions to the Theme
Repository.</DIV>
<DIV><BR></DIV>
<DIV>(Did I forget to mention Theme Documentation? Darn it; I meant to
talk about it.)</DIV>
<DIV><BR></DIV>
<DIV>Chip<BR><BR>
<DIV class=gmail_quote>On Wed, Jan 19, 2011 at 8:19 PM, Philip M. Hofer
(Frumph) <SPAN dir=ltr><<A href="mailto:philip@frumph.net"
target=_blank>philip@frumph.net</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV bgcolor="#ffffff">
<DIV><FONT size=2 face=Arial>We'll get there with the plans we have
setup ya?, just gotta have da patience.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Donncha's reference reminds me of my
tagline "I'm in your site touching your stuff." kinda brings a new
meaning to it ;/ where's the girl wearing the bikini to try to
circumvent the system, i'd totally let that happen.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>The completeness of Justin's "Great strides
in cleaning up the repository" statement leaves me to think we really
haven't gotten anywhere close to cleaning up the "old" things in the
repository. There is much more we can do to deal with that,
given any abilities that Otto might let us have. Think the
whole 'up to a certain version' those old themes needs to be inacted
upon with the 'adopt' program. (need to continue discussion on it on a
<A href="http://make.wordpress.org/themes"
target=_blank>make.wordpress.org/themes</A> post) </FONT><FONT
size=2 face=Arial>The issue being that this makes work for Otto to move
the ownership of the theme to someone else, if there can be some work
done on that to make his life easier that'd be great, or even some
automation for pross/cais/chip to handle it.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Next is getting the 'flags' set and working
for child themes. This could be done with a bit
of code for the repository to associate one theme with another theme as
it's parent, since this is bbpress couldn't child theme's be just
children post of the parent? Dunno. But we still need
to look into how to make it work without dropping the ball completely
and letting it slide like it has been.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Frameworks - frameworks being 'the code
behind the templetes' we've already been having that as part of
the discussion we just need to finalize it and so far noone really had
any doubts to themes created with framework backends to be put on the
repository it's just the definetions that need to be finished so that
there's a clear cut view of reviewing them.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Chip's SVN itemized in his list brings me
to thinking that there are some serious quality theme designers that
would warrant this ability to have SVN access; .. but not
everyone. If it's possible to enable svn access to 'known
developers of good intent' I'm all for that.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>One of the things that 2011 is missing in
all of those responses is the advent of deeper and more quality
documentation from developers utilizing current and new methods instead
of some of the ../shudder/ code that is currently out
there.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>I'm also believing that Premium Themes will
offer more then just their themes, but direct monthly support contracts
for maintenance; installation and customizations - more so then just the
theme sale.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV> </DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV>
<DIV></DIV>
<DIV>
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV style="FONT: 10pt arial; BACKGROUND: #e4e4e4"><B>From:</B> <A
title=edward.caissie@gmail.com href="mailto:edward.caissie@gmail.com"
target=_blank>Edward Caissie</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A
title=theme-reviewers@lists.wordpress.org
href="mailto:theme-reviewers@lists.wordpress.org"
target=_blank>theme-reviewers@lists.wordpress.org</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Wednesday, January 19, 2011
5:56 PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [theme-reviewers]
WPTRT = TSA?</DIV>
<DIV><BR></DIV>You are correct ... now that you mention it I remember
from reading earlier today.<BR><BR>Still good to be noticed all the
same (*grin*) ... we need something to help generate more interest.
Now if we could only get the "Make" site on the proverbial (social
media) map.<BR><BR>
<DIV class=gmail_quote>On Wed, Jan 19, 2011 at 8:52 PM, Chip Bennett
<SPAN dir=ltr><<A href="mailto:chip@chipbennett.net"
target=_blank>chip@chipbennett.net</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0pt 0pt 0pt 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>Actually, that was Donnacha's description...
<DIV>
<DIV></DIV>
<DIV><BR><BR>
<DIV class=gmail_quote>On Wed, Jan 19, 2011 at 7:48 PM, Edward
Caissie <SPAN dir=ltr><<A href="mailto:edward.caissie@gmail.com"
target=_blank>edward.caissie@gmail.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0pt 0pt 0pt 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>I guess I can't complain ... at least Ryan took
the time to think of and write that description.<BR><BR>... any
notice is better than not being noticed at all.<BR><BR>
<DIV class=gmail_quote>
<DIV>On Wed, Jan 19, 2011 at 8:20 PM, Chip Bennett <SPAN
dir=ltr><<A href="mailto:chip@chipbennett.net"
target=_blank>chip@chipbennett.net</A>></SPAN> wrote:<BR></DIV>
<BLOCKQUOTE
style="BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0pt 0pt 0pt 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV>
<DIV></DIV>
<DIV>Quite the metaphorical description!
<DIV><BR></DIV>
<BLOCKQUOTE
style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0px; MARGIN: 0pt 0pt 0pt 40px; PADDING-LEFT: 0px; PADDING-RIGHT: 0px; BORDER-TOP: medium none; BORDER-RIGHT: medium none; PADDING-TOP: 0px">
<DIV><SPAN
style="LINE-HEIGHT: 22px; FONT-FAMILY: 'Helvetica Neue',Arial,Helvetica,'Nimbus Sans L',sans-serif; COLOR: rgb(68,68,68); FONT-SIZE: 14px">The
gates to the official WordPress.org theme repository are now
guarded by a hardcore volunteer militia, the Theme Review
Team, with all the no-nonsense attitude of a cranky TSA
junk-fondler whose hasn’t yet had his afternoon box of
donuts.</SPAN></DIV></BLOCKQUOTE>
<DIV>
<DIV><BR></DIV>
<DIV>I<A
href="http://wpcandy.com/presents/the-future-of-wordpress-themes-in-2011"
target=_blank>nteresting read from WPCandy
today</A>.</DIV></DIV>
<DIV><BR></DIV>
<DIV>(Although my attitude is generally more driven in indirect
proportion to my daily coffee intake...)</DIV>
<DIV><BR></DIV><FONT color=#888888>
<DIV>Chip</DIV></FONT><BR></DIV></DIV>
<DIV>_______________________________________________<BR>theme-reviewers
mailing list<BR><A
href="mailto:theme-reviewers@lists.wordpress.org"
target=_blank>theme-reviewers@lists.wordpress.org</A><BR><A
href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers"
target=_blank>http://lists.wordpress.org/mailman/listinfo/theme-reviewers</A><BR><BR></DIV></BLOCKQUOTE></DIV><BR><BR>_______________________________________________<BR>theme-reviewers
mailing list<BR><A
href="mailto:theme-reviewers@lists.wordpress.org"
target=_blank>theme-reviewers@lists.wordpress.org</A><BR><A
href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers"
target=_blank>http://lists.wordpress.org/mailman/listinfo/theme-reviewers</A><BR><BR></BLOCKQUOTE></DIV><BR></DIV></DIV><BR>_______________________________________________<BR>theme-reviewers
mailing list<BR><A href="mailto:theme-reviewers@lists.wordpress.org"
target=_blank>theme-reviewers@lists.wordpress.org</A><BR><A
href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers"
target=_blank>http://lists.wordpress.org/mailman/listinfo/theme-reviewers</A><BR><BR></BLOCKQUOTE></DIV><BR></DIV></DIV>
<P></P>
<HR>
<DIV>
<P></P>_______________________________________________<BR>theme-reviewers
mailing list<BR><A href="mailto:theme-reviewers@lists.wordpress.org"
target=_blank>theme-reviewers@lists.wordpress.org</A><BR><A
href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers"
target=_blank>http://lists.wordpress.org/mailman/listinfo/theme-reviewers</A><BR></DIV>
<P></P></BLOCKQUOTE></DIV><BR>_______________________________________________<BR>theme-reviewers
mailing list<BR><A href="mailto:theme-reviewers@lists.wordpress.org"
target=_blank>theme-reviewers@lists.wordpress.org</A><BR><A
href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers"
target=_blank>http://lists.wordpress.org/mailman/listinfo/theme-reviewers</A><BR><BR></BLOCKQUOTE></DIV><BR></DIV></DIV></DIV>
<P></P>
<HR>
<DIV class=im>
<P></P>_______________________________________________<BR>theme-reviewers
mailing list<BR><A href="mailto:theme-reviewers@lists.wordpress.org"
target=_blank>theme-reviewers@lists.wordpress.org</A><BR><A
href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers"
target=_blank>http://lists.wordpress.org/mailman/listinfo/theme-reviewers</A><BR></DIV>
<P></P></BLOCKQUOTE></DIV><BR>_______________________________________________<BR>theme-reviewers
mailing list<BR><A
href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</A><BR><A
href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers"
target=_blank>http://lists.wordpress.org/mailman/listinfo/theme-reviewers</A><BR><BR></BLOCKQUOTE></DIV><BR></DIV>
<P>
<HR>
<P></P>_______________________________________________<BR>theme-reviewers
mailing
list<BR>theme-reviewers@lists.wordpress.org<BR>http://lists.wordpress.org/mailman/listinfo/theme-reviewers<BR></BLOCKQUOTE></BODY></HTML>