[theme-reviewers] BuddyPress theme rejected?

[Kirk Wight]

Doug: http://themes.trac.wordpress.org/ticket/8589

On 10 September 2012 10:26, Doug Stewart <zamoose at gmail.com> wrote:

> Kirk:
> Ticket #?
>
> On Mon, Sep 10, 2012 at 10:20 AM, Kirk Wight <kwight at kwight.ca> wrote:
> > I've had GitHub rejected as a URL as having "no real value to the
> enduser".
> > I understand it may be intimidating to a lot of users, but the benefits
> of
> > collaboration, issue tracking, milestones etc far outweigh the
> discomfort of
> > less technical users.
> >
> >
> > On 10 September 2012 10:06, Chip Bennett <chip at chipbennett.net> wrote:
> >>
> >> 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.
> >>
> >> 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.)
> >>
> >> Thanks,
> >>
> >> Chip
> >>
> >> p.s. if we've been rejecting subdomains (e.g. themename.example.com) 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.
> >>
> >>
> >> On Mon, Sep 10, 2012 at 6:08 AM, Chandra Maharzan <maharzan at gmail.com>
> >> wrote:
> >>>
> >>> I think since we have been rejecting github or other subdomains /
> >>> folder whose root URL doesn't have to do anything with the theme, this
> >>> should also be rejected unless there is a different rule for
> >>> buddypress. If we approve this, people will argue why theirs were
> >>> rejected.
> >>>
> >>> It might be best if you could create a page about the theme in your
> >>> own buddypress.org URL and have all the information including github
> >>> link on that page.
> >>>
> >>>
> >>> On Mon, Sep 10, 2012 at 4:43 PM, Japheth Thomson <japh at envato.com>
> wrote:
> >>> > What's not appropriate about a GitHub link? What's not "a page
> >>> > specifically
> >>> > related to the Theme" about it?
> >>> >
> >>> > Cheers,
> >>> > Japh
> >>> >
> >>> >
> >>> > On 10 September 2012 20:50, Otto <otto at ottodestruct.com> wrote:
> >>> >>
> >>> >> Umm... I kinda actually agree with him. A github link isn't
> >>> >> appropriate for a theme URL. IMO, of course.
> >>> >>
> >>> >> -Otto
> >>> >>
> >>> >>
> >>> >> On Mon, Sep 10, 2012 at 5:48 AM, Emil Uzelac <emil at themeid.com>
> wrote:
> >>> >> > commented, please check the ticket :)
> >>> >> >
> >>> >> > Emil
> >>> >> >
> >>> >> > On Mon, Sep 10, 2012 at 5:37 AM, Japheth Thomson <japh at envato.com
> >
> >>> >> > wrote:
> >>> >> >>
> >>> >> >> Hey everyone,
> >>> >> >>
> >>> >> >> I assume someone else is already taking a look at this, but just
> in
> >>> >> >> case,
> >>> >> >> please check out this ticket:
> >>> >> >> http://themes.trac.wordpress.org/ticket/9057
> >>> >> >>
> >>> >> >> I'm not convinced this should've been a rejection.
> >>> >> >>
> >>> >> >> Cheers,
> >>> >> >> Japh
> >>> >> >>
> >>> >> >> --
> >>> >> >> Japh Thomson
> >>> >> >> WordPress Evangelist
> >>> >> >> japh at envato.com
> >>> >> >> http://envato.com
> >>> >> >> http://twitter.com/envato
> >>> >> >>
> >>> >> >>
> >>> >> >>
> >>> >> >> _______________________________________________
> >>> >> >> 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
> >>> >> >
> >>> >> _______________________________________________
> >>> >> theme-reviewers mailing list
> >>> >> theme-reviewers at lists.wordpress.org
> >>> >> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >>> >
> >>> >
> >>> >
> >>> >
> >>> > --
> >>> > Japh Thomson
> >>> > WordPress Evangelist
> >>> > japh at envato.com
> >>> > http://envato.com
> >>> > http://twitter.com/envato
> >>> >
> >>> >
> >>> >
> >>> > _______________________________________________
> >>> > theme-reviewers mailing list
> >>> > theme-reviewers at lists.wordpress.org
> >>> > http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >>> >
> >>>
> >>>
> >>>
> >>> --
> >>> cmans
> >>> _______________________________________________
> >>> 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
> >>
> >
> >
> > _______________________________________________
> > theme-reviewers mailing list
> > theme-reviewers at lists.wordpress.org
> > http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >
>
>
>
> --
> -Doug
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20120910/6c1b6a30/attachment-0001.htm>