I don't even understand why we're having this discussion. I don't understand why anyone would ever think that a GitHub project repository would *not* be appropriate as a ThemeURI. If we've been rejecting GitHub project repository URLs as invalid ThemeURIs (or GitHub user URLs as invalid AuthorURIs), then we need to stop doing that. A GitHub preject repository is absolutely acceptable as a ThemeURI. <div>
<br></div><div>Speaking personally and IMHO (i.e. my personal opinion, rather than as a WPTRT admin), GitHub project repository URLs would even be *recommended*. GitHub allows for project collaboration. It allows for version tagging. It has issue (bug/feature-request) and milestone tracking. It provides access to development versions (bleeding-edge, beta-testing, etc.)</div>
<div><br></div><div>Thanks,</div><div><br></div><div>Chip</div><div><br></div><div>p.s. if we've been rejecting subdomains (e.g. <a href="http://themename.example.com">themename.example.com</a>) as inherently inappropriate, we need to stop doing that, as well. When and why did we start this practice? There is nothing inherently wrong with using a subdomain URL.<br>
<div><br><div class="gmail_quote">On Mon, Sep 10, 2012 at 6:08 AM, Chandra Maharzan <span dir="ltr"><<a href="mailto:maharzan@gmail.com" target="_blank">maharzan@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I think since we have been rejecting github or other subdomains /<br>
folder whose root URL doesn't have to do anything with the theme, this<br>
should also be rejected unless there is a different rule for<br>
buddypress. If we approve this, people will argue why theirs were<br>
rejected.<br>
<br>
It might be best if you could create a page about the theme in your<br>
own <a href="http://buddypress.org" target="_blank">buddypress.org</a> URL and have all the information including github<br>
link on that page.<br>
<div><div class="h5"><br>
<br>
On Mon, Sep 10, 2012 at 4:43 PM, Japheth Thomson <<a href="mailto:japh@envato.com">japh@envato.com</a>> wrote:<br>
> What's not appropriate about a GitHub link? What's not "a page specifically<br>
> related to the Theme" about it?<br>
><br>
> Cheers,<br>
> Japh<br>
><br>
><br>
> On 10 September 2012 20:50, Otto <<a href="mailto:otto@ottodestruct.com">otto@ottodestruct.com</a>> wrote:<br>
>><br>
>> Umm... I kinda actually agree with him. A github link isn't<br>
>> appropriate for a theme URL. IMO, of course.<br>
>><br>
>> -Otto<br>
>><br>
>><br>
>> On Mon, Sep 10, 2012 at 5:48 AM, Emil Uzelac <<a href="mailto:emil@themeid.com">emil@themeid.com</a>> wrote:<br>
>> > commented, please check the ticket :)<br>
>> ><br>
>> > Emil<br>
>> ><br>
>> > On Mon, Sep 10, 2012 at 5:37 AM, Japheth Thomson <<a href="mailto:japh@envato.com">japh@envato.com</a>><br>
>> > wrote:<br>
>> >><br>
>> >> Hey everyone,<br>
>> >><br>
>> >> I assume someone else is already taking a look at this, but just in<br>
>> >> case,<br>
>> >> please check out this ticket:<br>
>> >> <a href="http://themes.trac.wordpress.org/ticket/9057" target="_blank">http://themes.trac.wordpress.org/ticket/9057</a><br>
>> >><br>
>> >> I'm not convinced this should've been a rejection.<br>
>> >><br>
>> >> Cheers,<br>
>> >> Japh<br>
>> >><br>
>> >> --<br>
>> >> Japh Thomson<br>
>> >> WordPress Evangelist<br>
>> >> <a href="mailto:japh@envato.com">japh@envato.com</a><br>
>> >> <a href="http://envato.com" target="_blank">http://envato.com</a><br>
>> >> <a href="http://twitter.com/envato" target="_blank">http://twitter.com/envato</a><br>
>> >><br>
>> >><br>
>> >><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>
>> ><br>
>> ><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>
>> _______________________________________________<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>
><br>
><br>
><br>
> --<br>
> Japh Thomson<br>
> WordPress Evangelist<br>
> <a href="mailto:japh@envato.com">japh@envato.com</a><br>
> <a href="http://envato.com" target="_blank">http://envato.com</a><br>
> <a href="http://twitter.com/envato" target="_blank">http://twitter.com/envato</a><br>
><br>
><br>
><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>
<br>
<br>
<br>
--<br>
</div></div>cmans<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<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>
</div></div></blockquote></div><br></div></div>