[theme-reviewers] Theme Names (Kenya)

Thu Jun 26 22:13:35 UTC 2014

I have nothing against that :)

On Thursday, June 26, 2014, Kenya Sullivan <kenya at papernpen.com> wrote:

> "Policing" Theme Names is not a go idea, because it is ambiguous. Is A
> theme named Solar the same as a theme name Solar Panel, it's a matter of
> opinion. Ambiguity when establishing standards is not a good idea.   I
> think Chips' approach is best. Unless it's a direct name duplication.
>
> > On Jun 26, 2014, at 3:14 PM, theme-reviewers-request at lists.wordpress.org
> <javascript:;> wrote:
> >
> > Send theme-reviewers mailing list submissions to
> >    theme-reviewers at lists.wordpress.org <javascript:;>
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> >    http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> > or, via email, send a message with subject or body 'help' to
> >    theme-reviewers-request at lists.wordpress.org <javascript:;>
> >
> > You can reach the person managing the list at
> >    theme-reviewers-owner at lists.wordpress.org <javascript:;>
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of theme-reviewers digest..."
> >
> >
> > Today's Topics:
> >
> >   1. Re: Theme Names (Emil Uzelac)
> >   2. Re: Theme Names (Emil Uzelac)
> >
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Thu, 26 Jun 2014 14:12:41 -0500
> > From: Emil Uzelac <emil at uzelac.me <javascript:;>>
> > To: "Discussion list for WordPress theme reviewers."
> >    <theme-reviewers at lists.wordpress.org <javascript:;>>
> > Subject: Re: [theme-reviewers] Theme Names
> > Message-ID:
> >    <CAEytdhc7xf2ikxtK5oXhM-xfYjAeLqU4Ft8iDUEs8GF9h2xHcQ at mail.gmail.com
> <javascript:;>>
> > Content-Type: text/plain; charset="utf-8"
> >
> > I don't think that protection is at stake or in question. Confusion is!
> >
> >
> >> On Thu, Jun 26, 2014 at 2:09 PM, Srikanth Koneru <tskk79 at gmail.com
> <javascript:;>> wrote:
> >>
> >> I think Chip's opinion/decision on make blog about using generic names
> at
> >> your own risk is best way forward, If you want protection don't use
> generic
> >> names.
> >>
> >>
> >>> On Fri, Jun 27, 2014 at 12:33 AM, Emil Uzelac <emil at uzelac.me
> <javascript:;>> wrote:
> >>>
> >>> Let's just not become this:
> >>> https://www.google.com/search?q=themeforest+html5
> >>>
> >>> The only way we won't have any conflicts is to "enforce" no similar
> names
> >>> period.
> >>>
> >>>
> >>>
> >>> On Thu, Jun 26, 2014 at 1:59 PM, Catch Themes <info at catchthemes.com
> <javascript:;>>
> >>> wrote:
> >>>
> >>>> The best will be, like @Emil said. First come first basis. For any new
> >>>> themes they shouldn't not be allowed to chose the existing theme
> names.
> >>>>
> >>>>
> >>>> On Fri, Jun 27, 2014 at 12:42 AM, Chip Bennett <chip at chipbennett.net
> <javascript:;>>
> >>>> wrote:
> >>>>
> >>>>> If the end goal is to "avoid...conflicts", then a rule such as "no
> >>>>> dictionary words" is the equivalent of using a nuclear warhead to
> swat a
> >>>>> fly.
> >>>>>
> >>>>> Saying that non-English dictionary words would sound "made up" and
> >>>>> would result in few conflicts is a rather Anglocentric view. :)
> >>>>>
> >>>>>
> >>>>> On Thu, Jun 26, 2014 at 1:54 PM, Srikanth Koneru <tskk79 at gmail.com
> <javascript:;>>
> >>>>> wrote:
> >>>>>
> >>>>>> We can't do anything about existing themes, we should try and avoid
> >>>>>> these conflicts in future if we can.
> >>>>>> I was thinking of only English dictionary, other language words will
> >>>>>> sound made up and will result in few conflicts if any.
> >>>>>>
> >>>>>>
> >>>>>> On Fri, Jun 27, 2014 at 12:20 AM, Chip Bennett <
> chip at chipbennett.net <javascript:;>>
> >>>>>> wrote:
> >>>>>>
> >>>>>>> But my point is that such a guideline is demonstrably implausible,
> >>>>>>> because, if applied to the current set of hosted Themes, would
> result in
> >>>>>>> almost every single one failing. Thus, the likelihood of *future*
> Themes
> >>>>>>> failing the Guideline would be expected to be commensurate.
> >>>>>>>
> >>>>>>> Also: what dictionary? Just English dictionaries? What about
> >>>>>>> dictionaries of other languages? What about dead languages?
> >>>>>>>
> >>>>>>>
> >>>>>>> On Thu, Jun 26, 2014 at 1:45 PM, Srikanth Koneru <tskk79 at gmail.com
> <javascript:;>>
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>> not with retrospective effect ofcourse.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On Fri, Jun 27, 2014 at 12:12 AM, Chip Bennett <
> chip at chipbennett.net <javascript:;>
> >>>>>>>>> wrote:
> >>>>>>>>
> >>>>>>>>> ...which would eliminate about 99% of the Themes in the
> directory?
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> On Thu, Jun 26, 2014 at 1:39 PM, Srikanth Koneru <
> tskk79 at gmail.com <javascript:;>>
> >>>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>>> no dictionary words?
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> On Fri, Jun 27, 2014 at 12:08 AM, Chip Bennett <
> >>>>>>>>>> chip at chipbennett.net <javascript:;>> wrote:
> >>>>>>>>>>
> >>>>>>>>>>> Back to my previous question: what would you suggest as the
> >>>>>>>>>>> objective, enforceable guideline for Theme names?
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> On Thu, Jun 26, 2014 at 1:23 PM, Catch Themes <
> >>>>>>>>>>> info at catchthemes.com <javascript:;>> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>>> Many of theme shop use common names like Box, Responsive,
> >>>>>>>>>>>> Awesome and so on. So, this means we can play with theses
> name by adding
> >>>>>>>>>>>> word before or after.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Yes Otto, I agree with you that Box is common name and I am
> just
> >>>>>>>>>>>> asking this question so that we are clear about the naming
> rules. This will
> >>>>>>>>>>>> help me in further Theme Reviews as well.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Thank you all for your reply. I hope we will have clear
> >>>>>>>>>>>> guideline in this soon.
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Fri, Jun 27, 2014 at 12:00 AM, Otto <otto at ottodestruct.com
> <javascript:;>>
> >>>>>>>>>>>> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>>> On Thu, Jun 26, 2014 at 1:05 PM, Catch Themes <
> >>>>>>>>>>>>> info at catchthemes.com <javascript:;>> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> It's the matter of choices of theme name and manipulation. I
> >>>>>>>>>>>>>> feel The Box is so much manipulating Catch Box name.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> If you can definitively show that to be true, then you have a
> >>>>>>>>>>>>> point, however, I don't see what your evidence for this
> could possibly be.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> If you're reacting based just on the similarity of the name,
> >>>>>>>>>>>>> then I have to point out that "Box" is a pretty normal and
> commonplace
> >>>>>>>>>>>>> English word, popular even in movies:
> >>>>>>>>>>>>> http://youtu.be/0cmqwbZa6_w
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> So, other than the name being similar, how is it
> "manipulating"
> >>>>>>>>>>>>> anything? Is it using the same code? Is it a derivative of
> the other Box
> >>>>>>>>>>>>> theme? Is there *anything else in common at all* other than
> the name and
> >>>>>>>>>>>>> the fact that they're both, you know, themes?
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> The name may not be a good choice, but this is not really
> >>>>>>>>>>>>> evidence of anything other than both parties lack of
> creativity in naming
> >>>>>>>>>>>>> things.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> -Otto
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> _______________________________________________
> >>>>>>>>>>>>> theme-reviewers mailing list
> >>>>>>>>>>>>> theme-reviewers at lists.wordpress.org <javascript:;>
> >>>>>>>>>>>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >>>>>>>>>>>> _______________________________________________
> >>>>>>>>>>>> theme-reviewers mailing list
> >>>>>>>>>>>> theme-reviewers at lists.wordpress.org <javascript:;>
> >>>>>>>>>>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >>>>>>>>>>>
> >>>>>>>>>>> _______________________________________________
> >>>>>>>>>>> theme-reviewers mailing list
> >>>>>>>>>>> theme-reviewers at lists.wordpress.org <javascript:;>
> >>>>>>>>>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >>>>>>>>>>
> >>>>>>>>>> _______________________________________________
> >>>>>>>>>> theme-reviewers mailing list
> >>>>>>>>>> theme-reviewers at lists.wordpress.org <javascript:;>
> >>>>>>>>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >>>>>>>>>
> >>>>>>>>> _______________________________________________
> >>>>>>>>> theme-reviewers mailing list
> >>>>>>>>> theme-reviewers at lists.wordpress.org <javascript:;>
> >>>>>>>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >>>>>>>>
> >>>>>>>> _______________________________________________
> >>>>>>>> theme-reviewers mailing list
> >>>>>>>> theme-reviewers at lists.wordpress.org <javascript:;>
> >>>>>>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >>>>>>>
> >>>>>>> _______________________________________________
> >>>>>>> theme-reviewers mailing list
> >>>>>>> theme-reviewers at lists.wordpress.org <javascript:;>
> >>>>>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> theme-reviewers mailing list
> >>>>>> theme-reviewers at lists.wordpress.org <javascript:;>
> >>>>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >>>>>
> >>>>> _______________________________________________
> >>>>> theme-reviewers mailing list
> >>>>> theme-reviewers at lists.wordpress.org <javascript:;>
> >>>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >>>> _______________________________________________
> >>>> theme-reviewers mailing list
> >>>> theme-reviewers at lists.wordpress.org <javascript:;>
> >>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >>>
> >>> _______________________________________________
> >>> theme-reviewers mailing list
> >>> theme-reviewers at lists.wordpress.org <javascript:;>
> >>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >>
> >> _______________________________________________
> >> theme-reviewers mailing list
> >> theme-reviewers at lists.wordpress.org <javascript:;>
> >> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> > -------------- next part --------------
> > An HTML attachment was scrubbed...
> > URL: <
> http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20140626/a91421f4/attachment-0001.html
> >
> >
> > ------------------------------
> >
> > Message: 2
> > Date: Thu, 26 Jun 2014 14:14:49 -0500
> > From: Emil Uzelac <emil at uzelac.me <javascript:;>>
> > To: "Discussion list for WordPress theme reviewers."
> >    <theme-reviewers at lists.wordpress.org <javascript:;>>
> > Subject: Re: [theme-reviewers] Theme Names
> > Message-ID:
> >    <CAEytdhc2UGSbOnQCBSQfJV+MogZC5hs4zypW_su-LgMOrKNpaQ at mail.gmail.com
> <javascript:;>>
> > Content-Type: text/plain; charset="utf-8"
> >
> > Fine by me :)
> >
> >
> >> On Thu, Jun 26, 2014 at 2:12 PM, Chip Bennett <chip at chipbennett.net
> <javascript:;>> wrote:
> >>
> >> It's really Otto's opinion; I just happen to agree with it. :)
> >>
> >>
> >>> On Thu, Jun 26, 2014 at 2:09 PM, Srikanth Koneru <tskk79 at gmail.com
> <javascript:;>> wrote:
> >>>
> >>> I think Chip's opinion/decision on make blog about using generic names
> at
> >>> your own risk is best way forward, If you want protection don't use
> generic
> >>> names.
> >>>
> >>>
> >>>> On Fri, Jun 27, 2014 at 12:33 AM, Emil Uzelac <emil at uzelac.me
> <javascript:;>> wrote:
> >>>>
> >>>> Let's just not become this:
> >>>> https://www.google.com/search?q=themeforest+html5
> >>>>
> >>>> The only way we won't have any conflicts is to "enforce" no similar
> >>>> names period.
> >>>>
> >>>>
> >>>>
> >>>> On Thu, Jun 26, 2014 at 1:59 PM, Catch Themes <info at catchthemes.com
> <javascript:;>>
> >>>> wrote:
> >>>>
> >>>>> The best will be, like @Emil said. First come first basis. For any
> new
> >>>>> themes they shouldn't not be allowed to chose the existing theme
> names.
> >>>>>
> >>>>>
> >>>>> On Fri, Jun 27, 2014 at 12:42 AM, Chip Bennett <chip at chipbennett.net
> <javascript:;>>
> >>>>> wrote:
> >>>>>
> >>>>>> If the end goal is to "avoid...conflicts", then a rule such as "no
> >>>>>> dictionary words" is the equivalent of using a nuclear warhead to
> swat a
> >>>>>> fly.
> >>>>>>
> >>>>>> Saying that non-English dictionary words would sound "made up" and
> >>>>>> would result in few conflicts is a rather Anglocentric view. :)
> >>>>>>
> >>>>>>
> >>>>>> On Thu, Jun 26, 2014 at 1:54 PM, Srikanth Koneru <tskk79 at gmail.com
> <javascript:;>>
> >>>>>> wrote:
> >>>>>>
> >>>>>>> We can't do anything about existing themes, we should try and avoid
> >>>>>>> these conflicts in future if we can.
> >>>>>>> I was thinking of only English dictionary, other language words
> will
> >>>>>>> sound made up and will result in few conflicts if any.
> >>>>>>>
> >>>>>>>
> >>>>>>> On Fri, Jun 27, 2014 at 12:20 AM, Chip Bennett <
> chip at chipbennett.net <javascript:;>>
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>> But my point is that such a guideline is demonstrably implausible,
> >>>>>>>> because, if applied to the current set of hosted Themes, would
> result in
> >>>>>>>> almost every single one failing. Thus, the likelihood of *future*
> Themes
> >>>>>>>> failing the Guideline would be expected to be commensurate.
> >>>>>>>>
> >>>>>>>> Also: what dictionary? Just English dictionaries? What about
> >>>>>>>> dictionaries of other languages? What about dead languages?
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On Thu, Jun 26, 2014 at 1:45 PM, Srikanth Koneru <
> tskk79 at gmail.com <javascript:;>>
> >>>>>>>> wrote:
> >>>>>>>>
> >>>>>>>>> not with retrospective effect ofcourse.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> On Fri, Jun 27, 2014 at 12:12 AM, Chip Bennett <
> >>>>>>>>> chip at chipbennett.net <javascript:;>> wrote:
> >>>>>>>>>
> >>>>>>>>>> ...which would eliminate about 99% of the Themes in the
> directory?
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> On Thu, Jun 26, 2014 at 1:39 PM, Srikanth Koneru <
> tskk79 at gmail.com <javascript:;>
> >>>>>>>>>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>>> no dictionary words?
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> On Fri, Jun 27, 2014 at 12:08 AM, Chip Bennett <
> >>>>>>>>>>> chip at chipbennett.net <javascript:;>> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>>> Back to my previous question: what would you suggest as the
> >>>>>>>>>>>> objective, enforceable guideline for Theme names?
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Thu, Jun 26, 2014 at 1:23 PM, Catch Themes <
> >>>>>>>>>>>> info at catchthemes.com <javascript:;>> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>>> Many of theme shop use common names like Box, Responsive,
> >>>>>>>>>>>>> Awesome and so on. So, this means we can play with theses
> name by adding
> >>>>>>>>>>>>> word before or after.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Yes Otto, I agree with you that Box is common name and I am
> >>>>>>>>>>>>> just asking this question so that we are clear about the
> naming rules. This
> >>>>>>>>>>>>> will help me in further Theme Reviews as well.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Thank you all for your reply. I hope we will have clear
> >>>>>>>>>>>>> guideline in this soon.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Fri, Jun 27, 2014 at 12:00 AM, Otto <
> otto at ottodestruct.com <javascript:;>>
> >>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Thu, Jun 26, 2014 at 1:05 PM, Catch Themes <
> >>>>>>>>>>>>>> info at catchthemes.com <javascript:;>> wrote:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> It's the matter of choices of theme name and manipulation. I
> >>>>>>>>>>>>>>> feel The Box is so much manipulating Catch Box name.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> If you can definitively show that to be true, then you have
> a
> >>>>>>>>>>>>>> point, however, I don't see what your evidence for this
> could possibly be.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> If you're reacting based just on the similarity of the name,
> >>>>>>>>>>>>>> then I have to point out that "Box" is a pretty normal and
> commonplace
> >>>>>>>>>>>>>> English word, popular even in movies:
> >>>>>>>>>>>>>> http://youtu.be/0cmqwbZa6_w
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> So, other than the name being similar, how is it
> >>>>>>>>>>>>>> "manipulating" anything? Is it using the same code? Is it a
> derivative of
> >>>>>>>>>>>>>> the other Box theme? Is there *anything else in common at
> all* other than
> >>>>>>>>>>>>>> the name and the fact that they're both, you know, themes?
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> The name may not be a good choice, but this is not really
> >>>>>>>>>>>>>> evidence of anything other than both parties lack of
> creativity in naming
> >>>>>>>>>>>>>> things.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> -Otto
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> _______________________________________________
> >>>>>>>>>>>>>> theme-reviewers mailing list
> >>>>>>>>>>>>>> theme-reviewers at lists.wordpress.org <javascript:;>
> >>>>>>>>>>>>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >>>>>>>>>>>>> _______________________________________________
> >>>>>>>>>>>>> theme-reviewers mailing list
> >>>>>>>>>>>>> theme-reviewers at lists.wordpress.org <javascript:;>
> >>>>>>>>>>>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >>>>>>>>>>>>
> >>>>>>>>>>>> _______________________________________________
> >>>>>>>>>>>> theme-reviewers mailing list
> >>>>>>>>>>>> theme-reviewers at lists.wordpress.org <javascript:;>
> >>>>>>>>>>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >>>>>>>>>>>
> >>>>>>>>>>> _______________________________________________
> >>>>>>>>>>> theme-reviewers mailing list
> >>>>>>>>>>> theme-reviewers at lists.wordpress.org <javascript:;>
> >>>>>>>>>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >>>>>>>>>>
> >>>>>>>>>> _______________________________________________
> >>>>>>>>>> theme-reviewers mailing list
> >>>>>>>>>> theme-reviewers at lists.wordpress.org <javascript:;>
> >>>>>>>>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >>>>>>>>>
> >>>>>>>>> _______________________________________________
> >>>>>>>>> theme-reviewers mailing list
> >>>>>>>>> theme-reviewers at lists.wordpress.org <javascript:;>
> >>>>>>>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >>>>>>>>
> >>>>>>>> _______________________________________________
> >>>>>>>> theme-reviewers mailing list
> >>>>>>>> theme-reviewers at lists.wordpress.org <javascript:;>
> >>>>>>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >>>>>>>
> >>>>>>> _______________________________________________
> >>>>>>> theme-reviewers mailing list
> >>>>>>> theme-reviewers at lists.wordpress.org <javascript:;>
> >>>>>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> theme-reviewers mailing list
> >>>>>> theme-reviewers at lists.wordpress.org <javascript:;>
> >>>>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >>>>> _______________________________________________
> >>>>> theme-reviewers mailing list
> >>>>> theme-reviewers at lists.wordpress.org <javascript:;>
> >>>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >>>>
> >>>> _______________________________________________
> >>>> theme-reviewers mailing list
> >>>> theme-reviewers at lists.wordpress.org <javascript:;>
> >>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >>>
> >>> _______________________________________________
> >>> theme-reviewers mailing list
> >>> theme-reviewers at lists.wordpress.org <javascript:;>
> >>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >>
> >> _______________________________________________
> >> theme-reviewers mailing list
> >> theme-reviewers at lists.wordpress.org <javascript:;>
> >> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> > -------------- next part --------------
> > An HTML attachment was scrubbed...
> > URL: <
> http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20140626/fbc586d5/attachment.html
> >
> >
> > ------------------------------
> >
> > Subject: Digest Footer
> >
> > _______________________________________________
> > theme-reviewers mailing list
> > theme-reviewers at lists.wordpress.org <javascript:;>
> > http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >
> >
> > ------------------------------
> >
> > End of theme-reviewers Digest, Vol 49, Issue 139
> > ************************************************
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org <javascript:;>
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20140626/186a5c38/attachment-0001.html>