No subject
Wed Aug 17 18:42:36 UTC 2011
*review* will be far more manual.
Chip
On Fri, Oct 28, 2011 at 2:23 PM, Edward Caissie <edward.caissie at gmail.com>wrote:
> I like the theme-slug white-list, versus the author white-list, in
> conjunction with a tag/keyword.
> Also, the reviewer(s) will need to be able to easily see the theme would
> require special attention after the first approved version goes live.
>
> I take it this would be a completely manual process into the repo, or would
> we be going with a proper submission after the theme passes the
> niche/non-niche criteria and the white-list(s) have been updated?
>
>
> Cais.
>
>
>
> On Fri, Oct 28, 2011 at 3:03 PM, Otto <otto at ottodestruct.com> wrote:
>
>> On Fri, Oct 28, 2011 at 2:00 PM, Chip Bennett <chip at chipbennett.net>
>> wrote:
>> > So, same thing, except for white-listed *usernames*, rather than
>> > *theme-slugs*?
>> > My issue with that idea is that, then, even that user's *non-niche*
>> Themes
>> > would bypass the checks (and most likely, the Reviewer will have no idea
>> of
>> > this occurrence - unless the Trac ticket includes some relevant
>> > notification). Thus, if we're going to go to the trouble of
>> white-listing, I
>> > think theme-slug makes more sense than username.
>> > And speaking of Trac handling: I like the idea of appending a relevant
>> > *ticket keyword* for such Themes, so that we can process them
>> separately.
>>
>> Theme slug would work too.
>>
>> Tags or keywords could be added too.
>>
>> -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
>
>
--90e6ba5bbb1b41e9a404b060e9ed
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Here's how I'm currently envisioning it:<div><ol><li>User requests =
theme-slug whitelist</li><li>Otto/Pross adds theme-slug to bypass white-lis=
t</li><li>User uploads Theme, using the Uploader</li><li>Ticket created</li=
>
<li>Ticket keyword "niche" (or "uploader-bypass" or wha=
tever) appended</li><li>Ticket gets sorted into new Queue (just like BuddyP=
ress Themes have their own queue)</li></ol></div><div>From there, the proce=
ss is pretty much the same, except that the actual *review* will be far mor=
e manual.</div>
<div><br></div><div>Chip<br><br><div class=3D"gmail_quote">On Fri, Oct 28, =
2011 at 2:23 PM, Edward Caissie <span dir=3D"ltr"><<a href=3D"mailto:edw=
ard.caissie at gmail.com">edward.caissie at gmail.com</a>></span> wrote:<br><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex;">
I like the theme-slug white-list, versus the author white-list, in conjunct=
ion with a tag/keyword.<br>Also, the reviewer(s) will need to be able to ea=
sily see the theme would require special attention after the first approved=
version goes live.<br>
<br>I take it this would be a completely manual process into the repo, or w=
ould we be going with a proper submission after the theme passes the niche/=
non-niche criteria and the white-list(s) have been updated?<br><br><br clea=
r=3D"all">
Cais.<div><div></div><div class=3D"h5"><br>
<br><br><div class=3D"gmail_quote">On Fri, Oct 28, 2011 at 3:03 PM, Otto <s=
pan dir=3D"ltr"><<a href=3D"mailto:otto at ottodestruct.com" target=3D"_bla=
nk">otto at ottodestruct.com</a>></span> wrote:<br><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex">
<div>On Fri, Oct 28, 2011 at 2:00 PM, Chip Bennett <<a href=3D"mailto:ch=
ip at chipbennett.net" target=3D"_blank">chip at chipbennett.net</a>> wrote:<b=
r>
> So, same thing, except for white-listed *usernames*, rather than<br>
> *theme-slugs*?<br>
> My issue with that idea is that, then, even that user's *non-niche=
* Themes<br>
> would bypass the checks (and most likely, the Reviewer will have no id=
ea of<br>
> this occurrence - unless the Trac ticket includes some relevant<br>
> notification). Thus, if we're going to go to the trouble of white-=
listing, I<br>
> think theme-slug makes more sense than username.<br>
> And speaking of Trac handling: I like the idea of appending a relevant=
<br>
> *ticket keyword* for such Themes, so that we can process them separate=
ly.<br>
<br>
</div>Theme slug would work too.<br>
<br>
Tags or keywords could be added too.<br>
<div><div></div><div><br>
-Otto<br>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a href=3D"mailto:theme-reviewers at lists.wordpress.org" target=3D"_blank">th=
eme-reviewers at lists.wordpress.org</a><br>
<a href=3D"http://lists.wordpress.org/mailman/listinfo/theme-reviewers" tar=
get=3D"_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers<=
/a><br>
</div></div></blockquote></div><br>
</div></div><br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href=3D"mailto:theme-reviewers at lists.wordpress.org">theme-reviewers at list=
s.wordpress.org</a><br>
<a href=3D"http://lists.wordpress.org/mailman/listinfo/theme-reviewers" tar=
get=3D"_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers<=
/a><br>
<br></blockquote></div><br></div>
--90e6ba5bbb1b41e9a404b060e9ed--
More information about the theme-reviewers
mailing list