[admin] Turning on Issues tab on Github for Boost libraries

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

[admin] Turning on Issues tab on Github for Boost libraries

Boost - Dev mailing list
Can we not have some resolution from an administrator about turning on
the Issues tab in Github for Boost libraries ? There are two 'admin'
issues regarding this and, since it should be a quick job for an
administrator to implement this, I would really prefer not to wait for a
long time for this to get done. Just now I had a "bogus" PR for
iostreams, which I rejected, and the explanation from the person who
created the PR was that the PR was "created" because there was no Issue
tab for the library and he was only trying to create an Issue to be
looked at. There is absolutely no logical reason that I can think of why
the Issue tab on Github cannot be turned on for Boost libraries, to
benefit end-users.


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [admin] Turning on Issues tab on Github for Boost libraries

Boost - Dev mailing list
On Thu, Sep 28, 2017 at 8:36 AM, Edward Diener via Boost <
[hidden email]> wrote:

> Can we not have some resolution from an administrator about turning on the
> Issues tab in Github for Boost libraries ? There are two 'admin' issues
> regarding this and, since it should be a quick job for an administrator to
> implement this, I would really prefer not to wait for a long time for this
> to get done. Just now I had a "bogus" PR for iostreams, which I rejected,
> and the explanation from the person who created the PR was that the PR was
> "created" because there was no Issue tab for the library and he was only
> trying to create an Issue to be looked at. There is absolutely no logical
> reason that I can think of why the Issue tab on Github cannot be turned on
> for Boost libraries, to benefit end-users.
>

The usual solution on this has up to now been that the admin of the
particular library repo turns issues on. If you are a library maintainer
and aren't the admin for the library repo.. File an admin issue to get the
admin access to your repo.

Note, I'm just pointing out what the procedure has been so far :-)

--
-- Rene Rivera
-- Grafik - Don't Assume Anything
-- Robot Dreams - http://robot-dreams.net
-- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [admin] Turning on Issues tab on Github for Boost libraries

Boost - Dev mailing list
In reply to this post by Boost - Dev mailing list
On Thu, Sep 28, 2017 at 8:37 AM Edward Diener via Boost <
[hidden email]> wrote:

> Can we not have some resolution from an administrator about turning on
> the Issues tab in Github for Boost libraries


Beast has Issues turned on, and it is my preferred means of receiving
reports. It is also the method I prefer for reporting issues. I don't look
at Trac.

> --
Follow me on GitHub: https://github.com/vinniefalco

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [admin] Turning on Issues tab on Github for Boost libraries

Boost - Dev mailing list
In reply to this post by Boost - Dev mailing list
On 9/28/2017 11:46 AM, Rene Rivera via Boost wrote:

> On Thu, Sep 28, 2017 at 8:36 AM, Edward Diener via Boost <
> [hidden email]> wrote:
>
>> Can we not have some resolution from an administrator about turning on the
>> Issues tab in Github for Boost libraries ? There are two 'admin' issues
>> regarding this and, since it should be a quick job for an administrator to
>> implement this, I would really prefer not to wait for a long time for this
>> to get done. Just now I had a "bogus" PR for iostreams, which I rejected,
>> and the explanation from the person who created the PR was that the PR was
>> "created" because there was no Issue tab for the library and he was only
>> trying to create an Issue to be looked at. There is absolutely no logical
>> reason that I can think of why the Issue tab on Github cannot be turned on
>> for Boost libraries, to benefit end-users.
>>
>
> The usual solution on this has up to now been that the admin of the
> particular library repo turns issues on. If you are a library maintainer
> and aren't the admin for the library repo.. File an admin issue to get the
> admin access to your repo.
>
> Note, I'm just pointing out what the procedure has been so far :-)

I have added an Admin request for Admin access to the libraries for
which I have write access in order to turn on the Issues tab, with
https://github.com/boostorg/admin/issues/136. I am glad you pointed out
the procedure to me.


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost