<p dir="ltr">I understand Tammie. I disagree that's it's complicated, but I do agree that's it's an extra level of administration for those not yet comfortable with Grunt or the command line. My previous response was addressing the specific concern that adding it meant any change for users regarding multiple files etc. Getting it on the repo itself is the main task here. </p>
<p dir="ltr">Can someone with WPTRT admin access on Github please claim ownership on getting the repo setup, at some point convenient to them? </p>
<p dir="ltr">----<br>
Gary Jones<br>
Web Developer, Gamajo Tech</p>
<div class="gmail_quote">On 16 Oct 2014 22:38, "Tammie Lister" <<a href="mailto:karmatosed@gmail.com">karmatosed@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
Gary,<br>
<br>
My concern is it's adding a level of contribution and administration
complication for the first steps we could do without. Never say
never, but lets leave it from the start.<br>
<br>
Thanks<br>
Tammie<br>
<br>
<div>On 16/10/2014 22:36, Gary Jones wrote:<br>
</div>
<blockquote type="cite">
<p dir="ltr">And with my proposal, it would. <br>
dist/theme-unit-tests.xml would be the same as the file now, and
dist/theme-unit-tests-wpcom.xml for those who need to test the
extra WP.com bits Lance mentioned. All from the same source. </p>
<p dir="ltr">----<br>
Gary Jones<br>
Web Developer, Gamajo Tech</p>
<div class="gmail_quote">On 16 Oct 2014 21:36, "Edward Caissie"
<<a href="mailto:edward.caissie@gmail.com" target="_blank">edward.caissie@gmail.com</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">The Theme Unit Test (TUT) data needs to stay as
easy to acquire as it is prior to being moved from its
current repository. Simply put, it should remain as a single
file download for theme designers ready to be used without
any additional work aside from importing it into a WordPress
installation.
<div><br>
</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br clear="all">
<div>Edward Caissie<br>
aka Cais.</div>
<br>
<div class="gmail_quote">On Thu, Oct 16, 2014 at 3:27 PM,
Tammie Lister <span dir="ltr"><<a href="mailto:karmatosed@gmail.com" target="_blank">karmatosed@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"> Hi<br>
<br>
My opinion would be no Grunt because we're adding
complexity - lets get things working without things
extra first. <br>
<br>
Thanks<span><font color="#888888"><br>
Tammie</font></span>
<div>
<div><br>
<br>
<div>On 16/10/2014 20:04, Gary Jones wrote:<br>
</div>
<blockquote type="cite">
<p dir="ltr">Thanks Lance. </p>
<p dir="ltr">Any opinions on a little Grunt file
for the purpose of easily and consistently
removing the WP.com bits? (and whatever other
tasks on the file might need doing between
source and distributable file). </p>
<p dir="ltr">Note that this isn't introducing
any NodeJS dependency for *using* the XML
file, but it reduces the task of searching and
replacing several regex strings down to a
single command line call. </p>
<p dir="ltr">I'd envisage a structure of
something like:</p>
<p dir="ltr">* src/theme-unit-tests.xml<br>
* dist/theme-unit-tests.xml<br>
* dist/theme-unit-tests-wpcom.xml<br>
* gruntfile.js<br>
* package.json<br>
* README.md</p>
<p dir="ltr">The dist files would be updated by
Grunt from the src file, and adapted by Grunt
for WP.com and everyone else accordingly. <br>
----<br>
Gary Jones<br>
Web Developer, Gamajo Tech</p>
<div class="gmail_quote">On 16 Oct 2014 18:45,
"Emil Uzelac" <<a href="mailto:emil@uzelac.me" target="_blank">emil@uzelac.me</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thanks kind
lady :)<span></span><br>
<br>
On Thursday, October 16, 2014, Tammie Lister
<<a href="mailto:karmatosed@gmail.com" target="_blank">karmatosed@gmail.com</a>>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
Sure, I'll pop it over next week.<br>
<br>
Thanks<br>
Tammie<br>
<br>
<div>On 16/10/2014 18:42, Emil Uzelac
wrote:<br>
</div>
<blockquote type="cite">Tammie would you
like to start?<span></span><br>
<br>
On Thursday, October 16, 2014, Tammie
Lister <<a>karmatosed@gmail.com</a>>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"> Hi<br>
<br>
I'm down with putting it on GH but
we do need to make sure we have a
process and particularly how it's
prepared.<br>
<br>
Thanks<br>
Tammie<br>
<br>
<div>On 16/10/2014 18:29, Edward
Caissie wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Fine by me ...
<div><br>
</div>
</div>
<div class="gmail_extra"><br clear="all">
<div>Edward Caissie<br>
aka Cais.</div>
<br>
<div class="gmail_quote">On
Thu, Oct 16, 2014 at 1:23
PM, Emil Uzelac <span dir="ltr"><<a>emil@uzelac.me</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Awesome
and thanks. So guys should
we push over to TRT GH or?
<div>
<div><span></span><br>
<br>
On Thursday, October
16, 2014, Lance
Willett <<a>nanobar@gmail.com</a>>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Here's
the checklist for
preparing a new XML
file, next time you
need to do it.<br>
<br>
Often when I get the
new XML file from<br>
<a href="http://wpthemetestdata.wordpress.com/" target="_blank">http://wpthemetestdata.wordpress.com/</a>
it needs a bit of
massaging<br>
before commit to our
pub repo.<br>
<br>
Here’s the process<br>
<br>
1. WPTRT admins make
changes to the test
site on WP.com.<br>
2. Go to <a href="http://wpthemetestdata.wordpress.com/" target="_blank">http://wpthemetestdata.wordpress.com/</a>
and export the full
XML<br>
file, and open it
locally in a text
editor.<br>
3. Clean it up.<br>
4. Diff it with the
previous version to
be sure of no weird
changes or<br>
additions, other
than the expected
ones.<br>
5. Push to GitHub.<br>
6. Go to <a href="http://codex.wordpress.org/Theme_Unit_Test" target="_blank">http://codex.wordpress.org/Theme_Unit_Test</a>,
edit the page,<br>
change the UTC
timestamp to “now”
to show the most
current update<br>
timestamp. **You can
stop doing this
probably since
GitHub will have a<br>
history going
forward.**<br>
<br>
Notes for the XML
clean up, step 3.<br>
<br>
Remove the following
metadata elements
that are specific to
WP.com.<br>
<br>
superawesome<br>
_edit_last<br>
email_notification<br>
_searchme<br>
jabber_published<br>
geo_public<br>
_elasticsearch_indexed_on<br>
<br>
I look for these
patterns using a
text editor like
TextMate or Sublime<br>
Text, with regex
search turned on:<br>
<br>
1. <a href="https://gist.github.com/lancewillett/a7c849026e2e403399a0" target="_blank">https://gist.github.com/lancewillett/a7c849026e2e403399a0</a><br>
2. <a href="https://gist.github.com/lancewillett/127085c444ec6ff398d1" target="_blank">https://gist.github.com/lancewillett/127085c444ec6ff398d1</a><br>
<br>
Then search/replace
with an empty string
to remove from the
XML file.<br>
<br>
It's not end of the
world if they make
it into the Unit
Test XML file,<br>
but it's just
clutter.<br>
<br>
– Lance<br>
<br>
On Thu, Oct 16, 2014
at 11:15 AM, Lance
Willett <<a>nanobar@gmail.com</a>>
wrote:<br>
> The history of
the file changes is
public, it's part of
our WP.com<br>
> public themes
SVN repo.<br>
><br>
> You can see the
history by doing
something like:<br>
> svn log <a href="https://wpcom-themes.svn.automattic.com/demo/theme-unit-test-data.xml" target="_blank">https://wpcom-themes.svn.automattic.com/demo/theme-unit-test-data.xml</a><br>
><br>
> I'm totally
happy for the file
to move to GitHub.
If WPTRT has an<br>
> account and
you'd like to
maintain it going
forward—please just
grab<br>
> the latest copy
and start from
there; I don't need
to do anything<br>
> further.<br>
><br>
> Then edit the
Codex page at <a href="http://codex.wordpress.org/Theme_Unit_Test" target="_blank">http://codex.wordpress.org/Theme_Unit_Test</a><br>
> to point to the
GitHub repo instead
of the SVN repo.<br>
><br>
> Done. :)<br>
><br>
> – Lance<br>
_______________________________________________<br>
theme-reviewers
mailing list<br>
<a>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>
</blockquote>
</div>
</div>
<br>
_______________________________________________<br>
theme-reviewers mailing
list<br>
<a>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>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
theme-reviewers mailing list
<a>theme-reviewers@lists.wordpress.org</a>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a>
</pre>
</blockquote>
<br>
<pre cols="72">--
Thanks
Tammie Lister</pre>
</div>
</blockquote>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
theme-reviewers mailing list
<a>theme-reviewers@lists.wordpress.org</a>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a>
</pre>
</blockquote>
<br>
<pre cols="72">--
Thanks
Tammie Lister</pre>
</div>
</blockquote>
<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>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
theme-reviewers mailing list
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a>
</pre>
</blockquote>
<br>
<pre cols="72">--
Thanks
Tammie Lister</pre>
</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>
<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>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
theme-reviewers mailing list
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a>
</pre>
</blockquote>
<br>
<pre cols="72">--
Thanks
Tammie Lister</pre>
</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>