Re: [Twisted-Python] Migrating Trac Tickets to GitHub issues

2017-10-01 Thread Glyph
> On Sep 30, 2017, at 2:15 PM, Adi Roiban wrote: > > Hi, > > I would like to re-start the conversation about migrating Trac tickets > to GitHub issues. > > My main reason for doing this is to make it easier for people to > contribute to Twisted. > > In CONTRIBUTING there is this info > > `G

Re: [Twisted-Python] Migrating Trac Tickets to GitHub issues

2017-10-01 Thread Glyph
> On Sep 30, 2017, at 5:30 PM, Craig Rodrigues wrote: > > I think migrating Twisted issues from Trac to GitHub is a good idea, > and will make it easier for people to interact with the project. To be clear, because I am grumpy about a lot of specifics with respect to GH issues: I agree with thi

Re: [Twisted-Python] Migrating Trac Tickets to GitHub issues

2017-10-01 Thread Glyph
> On Oct 1, 2017, at 9:31 AM, Craig Rodrigues wrote: > > > > On Sun, Oct 1, 2017 at 3:30 AM, Amber Brown > wrote: > > > Currently, GitHub Issues don't allow for non-committers to make modifications > to categories, milestones, edit the original ticket des

Re: [Twisted-Python] Migrating Trac Tickets to GitHub issues

2017-10-01 Thread Craig Rodrigues
On Sun, Oct 1, 2017 at 3:30 AM, Amber Brown wrote: > > > Currently, GitHub Issues don't allow for non-committers to make > modifications to categories, milestones, edit the original ticket > description, or close tickets. This kinda sucks, because it makes the pool > of triagers smaller, and also

Re: [Twisted-Python] Migrating Trac Tickets to GitHub issues

2017-10-01 Thread Amber Brown
> On 1 Oct 2017, at 8:15 am, Adi Roiban wrote: > > Hi, > > I would like to re-start the conversation about migrating Trac tickets > to GitHub issues. > > My main reason for doing this is to make it easier for people to > contribute to Twisted. > > In CONTRIBUTING there is this info > > `GitH

Re: [Twisted-Python] Migrating Trac Tickets to GitHub issues

2017-09-30 Thread Craig Rodrigues
On Sat, Sep 30, 2017 at 2:15 PM, Adi Roiban wrote: > Hi, > > I would like to re-start the conversation about migrating Trac tickets > to GitHub issues. > > My main reason for doing this is to make it easier for people to > contribute to Twisted. > I think migrating Twisted issues from Trac to G

Re: [Twisted-Python] Migrating Trac Tickets to GitHub issues

2017-09-30 Thread Adi Roiban
On 30 September 2017 at 22:15, Adi Roiban wrote: [snip] > > > Below are the things that I things we will lose when migrating to > GitHub Issues and which will require extra work. > [snip] 6. We will no longer get the tickets pending review reported on IRC. Beside reimplementing this

[Twisted-Python] Migrating Trac Tickets to GitHub issues

2017-09-30 Thread Adi Roiban
Hi, I would like to re-start the conversation about migrating Trac tickets to GitHub issues. My main reason for doing this is to make it easier for people to contribute to Twisted. In CONTRIBUTING there is this info `GitHub doesn't provide adequate tooling for its community.` I don't know what