Yes ... at least initially. If a Theme author wants to get SVN access then they should understand as much of the process as possible which includes helping with and becoming a regular member of the WPTRT.<br><br><br>Cais.<br>
<br><div class="gmail_quote">On Thu, Jan 20, 2011 at 9:05 AM, Philip M. Hofer (Frumph) <span dir="ltr"><<a href="mailto:philip@frumph.net">philip@frumph.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div bgcolor="#ffffff"><div class="im">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><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: 2px solid rgb(0, 0, 0); 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: none repeat scroll 0% 0% rgb(228, 228, 228);"><b>From:</b>
<a title="edward.caissie@gmail.com" href="mailto:edward.caissie@gmail.com" target="_blank">Edward Caissie</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 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></div><div><div></div><div class="h5">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><li>Child-Theme Guidelines should to be sorted out by the above time-line
(-1 ideally)
</li><li>Theme Author SVN access for "known" authors
<ul>
<li>Trial with WPTRT?<br></li></ul>
</li><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><li>Combine with upcoming Child-Theme introduction and implementation?<br>
</li><li>Make inaccessable via the current Extend repo (i.e: suspend or "Move")
after a certain age? </li></ul>
</li><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" target="_blank">chip@chipbennett.net</a>></span>
wrote:<br>
<blockquote style="border-left: 1px solid rgb(204, 204, 204); 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><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: 1px solid rgb(204, 204, 204); 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" 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 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></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>