<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18928">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>Commision designs for the WPTRT Uniform and badges in a
much more fashionable style than the TSA
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>- Leiderhosen, definately leiderhosen.
Nothing says respect like leiderhosen.. and monkeys.. monkeys in
leiderhosen.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>\/--- Trial with WPTRT but if i'm recognizing what
you're saying is that they have to donate time to the WPTRT in order to get svn
ya? (woot)</FONT></DIV>
<DIV> </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=edward.caissie@gmail.com
href="mailto:edward.caissie@gmail.com">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">theme-reviewers@lists.wordpress.org</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Thursday, January 20, 2011 5:44
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [theme-reviewers] WPTRT =
TSA?</DIV>
<DIV><BR></DIV>Just recapping the above discussion for my own clarification
...<BR><BR>
<UL>
<LI>Child-Themes are an eventuality, the time-line is the only real unknown
at this point.
<LI>Child-Theme Guidelines should to be sorted out by the above time-line
(-1 ideally)
<LI>Theme Author SVN access for "known" authors
<UL>
<LI>Trial with WPTRT?<BR></LI></UL>
<LI>We need to address the existing repository (pre-WPTRT) Themes and how
best to handle them going forward
<UL>
<LI>"Adoption" program, as in ownership transfer?
<LI>Combine with upcoming Child-Theme introduction and implementation?<BR>
<LI>Make inaccessable via the current Extend repo (i.e: suspend or "Move")
after a certain age? </LI></UL>
<LI>Commision designs for the WPTRT Uniform and badges in a much more
fashionable style than the TSA
<UL>
<LI>Issue challenge coins!</LI></UL></LI></UL>Of course, the last
point/sub-point are the most important issues to be discussed but I imagine we
could focus on the first points to start with
(*grin*)<BR><BR><BR>Cais.<BR><BR>PS: Looks like the makings of a WPTRT meeting
agenda ...<BR><BR>
<DIV class=gmail_quote>On Wed, Jan 19, 2011 at 10:29 PM, Chip Bennett <SPAN
dir=ltr><<A
href="mailto:chip@chipbennett.net">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>Well fair enough, then... I withdraw my philosophical
complaint. :)
<DIV><BR></DIV>
<DIV><FONT color=#888888>Chip</FONT>
<DIV>
<DIV></DIV>
<DIV class=h5><BR><BR>
<DIV class=gmail_quote>On Wed, Jan 19, 2011 at 9:23 PM, Otto <SPAN
dir=ltr><<A href="mailto:otto@ottodestruct.com"
target=_blank>otto@ottodestruct.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>
<DIV>On Wed, Jan 19, 2011 at 8:48 PM, Chip Bennett <<A
href="mailto:chip@chipbennett.net"
target=_blank>chip@chipbennett.net</A>> wrote:<BR>> Except that, by
*what*, I really mean *if*: as in, is it a foregone<BR>> conclusion
that Child Themes will be in the Repository?<BR><BR></DIV>I'm more
focusing on making it capable of doing it. Guidelines on what<BR>are kinda
your problem. ;)<BR><BR>But yes, child themes will be allowed eventually.
The reasons have<BR>been technical, not philosophical.<BR>
<DIV><BR>On Wed, Jan 19, 2011 at 9:17 PM, Chip Bennett <<A
href="mailto:chip@chipbennett.net"
target=_blank>chip@chipbennett.net</A>> wrote:<BR>> Originally,
Child Themes were intended to be *update-proof*, not "more<BR>>
update-proof", than (stand-alone) Themes. They were intended as a way
for<BR>> the *end user* to add Theme modifications that would be
retained when the<BR>> Parent Theme was updated.<BR><BR></DIV>Yeah, I
thought that too, and said so last week. Matt corrected me,<BR>and said
that that was not the intended purpose of child themes. The<BR>intended
purpose was to allow themes to be extended, as they were<BR>doing lots of
CSS-only type competitions at the time (with things like<BR>the Sandbox
theme and so on), and child themes were intended to<BR>facilitate
that.<BR><BR>In Matt's words (or pretty close, I was not recording at the
time):<BR>"if we had intended to make themes capable of retaining
modifications<BR>through upgrades, we've have done it
differently".<BR><BR>So yes, child themes are not end-user-only from the
.org's<BR>perspective, and will be allowed in the repo,
eventually.<BR><FONT color=#888888><BR>-Otto<BR></FONT>
<DIV>
<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></DIV></DIV></BLOCKQUOTE></DIV><BR></DIV></DIV></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>
<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>