Regarding Gitlab: I love gitlab and for organizations it's one of if not the best tools in its space. But it falls down for projects like Django, and I don't think moving migrating the code from GitHub is a good idea.
The labels would need automating, which would require a GitHub bot of some kind. The workflow could be as simple as "new tickets are assigned the awaiting review tag" and "only members of the Django org can modify tags"? On Tue, 11 Dec 2018, 19:38 Josh Smeaton <josh.smea...@gmail.com wrote: > For what it's worth, I agree. I think we should consider using GitHub > issues. I don't think there's anything in Trac, from a user perspective, > that we couldn't really do with Issues. The main issue, I think, would be > allowing non-committers (organisational members) to triage tickets and > change the ticket status. > > But I don't have the time to plan or champion a change like that through > these days, so while I'd like to see it happen, I'm not the person to push > for it to happen. > > Jamesie: please see "Why not Gitlab?" [0]. While it might be better from a > technical standpoint, it would not be better than GH Issues from an > onboarding perspective. > > [0]https://www.python.org/dev/peps/pep-0581/#why-not-gitlab > > On Tuesday, 11 December 2018 23:20:21 UTC+11, Tom Forbes wrote: >> >> > The only reason Github issues would be a consideration is if the group >> thought the onboarding experience (being where users already are with a >> tool they're already familiar with) would have more value than sticking >> with with the status quo which is strictly better from a feature >> perspective than GH Issues >> >> I really think it's worth considering - I'm not convinced Trac is >> strictly better from a feature perspective. Things like the dashboards are >> interesting, sure, but what does it do that Github issues don't? And by >> this I don't mean features that exist but we don't use, I mean our general >> ticket workflow that 99% of contributors are exposed to. There are far >> larger projects than Django currently using Github issues successfully and >> they have a far more complex workflow including CLA's, high-granularity >> tags, automatic reviewer selection, automatic closing, etc etc. >> >> The cost of a migration would not be cheap, but is it worth doing a >> formal evaluation and consider it? The "why Github section" ( >> https://www.python.org/dev/peps/pep-0581/#why-github) in that PEP lists >> some good reasons that apply to us as well. The key one for me is lowering >> the barrier to entry which I think we should be aiming towards. If we are >> looking to expand the development group and get more people onboard we may >> need to shake things up, as the status quo is problematic in that area. >> >> On 11 December 2018 at 12:04:32, Josh Smeaton (josh.s...@gmail.com) >> wrote: >> >> I don't think something like Jira would even be a consideration. >> >> The only reason Github issues would be a consideration is if the group >> thought the onboarding experience (being where users already are with a >> tool they're already familiar with) would have more value than sticking >> with with the status quo which is strictly better from a feature >> perspective than GH Issues. Incrementally improving Trac can improve the >> value prop for not changing, but I don't think anyone that actually uses >> Trac would say it's worse from a feature perspective. Even if that value >> judgement did land on GH issues side, there would still be a large >> operational undertaking to make that transition. >> >> Again, the PEP for doing this for CPython would be very similar for >> Django, so please refer to https://www.python.org/dev/peps/pep-0581/ for >> some examples of why and what operational concerns there can be (migration, >> permissions, etc). >> >> On Tuesday, 11 December 2018 07:26:58 UTC+11, Ira Abbott wrote: >>> >>> Apologies for the double post - my last one was not clear. "just that" >>> means that the payment is intended to indicate that it is worth a JIRA >>> license to me to not use JIRA. >>> >>> This group does great things. I am sure that the group can come up with >>> some interesting ways to scale that will ultimately benefit the framework >>> as a whole. >>> >>> On Monday, December 10, 2018 at 3:21:53 PM UTC-5, Ira Abbott wrote: >>>> >>>> FWIW: Please consider my contribution of $84 (one bulk JIRA license for >>>> one year) to be just that. >>>> >>>> On Monday, December 10, 2018 at 2:14:07 PM UTC-5, Zachary Garwood wrote: >>>>> >>>>> I'd pay money to NOT use Jira. >>>>> >>>>> On Mon, Dec 10, 2018, 11:09 AM Dan Davis <dans...@gmail.com wrote: >>>>> >>>>>> Tom, you are right about the UX issues, but full-text and inverted >>>>>> indexing would help with the responsiveness as well. Technically, I was >>>>>> talking about djangoproject's TracSearch >>>>>> <https://code.djangoproject.com/search>. That's closer to good UX >>>>>> as well, because you can get there by progressive enhancement rather than >>>>>> taking stuff away. >>>>>> >>>>>> You are also right that switching to another system such as github >>>>>> issues could be a better fix than customizing Trac. But I find it >>>>>> difficult to believe that Github issues grows up to cover as much >>>>>> workflow >>>>>> management as Trac issues or JIRA. Maybe we need money to get JIRA. >>>>>> >>>>>> >>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "Django developers (Contributions to Django itself)" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>> send an email to django-develop...@googlegroups.com. >>>>>> To post to this group, send email to django-d...@googlegroups.com. >>>>>> Visit this group at https://groups.google.com/group/django-developers >>>>>> . >>>>>> To view this discussion on the web visit >>>>>> https://groups.google.com/d/msgid/django-developers/CAFzonYZ%3DwRCX3HpfYCj0G2i3UrcQmVCDj%3Da%2BOb7zeqtvQm-pxg%40mail.gmail.com >>>>>> <https://groups.google.com/d/msgid/django-developers/CAFzonYZ%3DwRCX3HpfYCj0G2i3UrcQmVCDj%3Da%2BOb7zeqtvQm-pxg%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>>>> . >>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>> >>>>> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers (Contributions to Django itself)" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-develop...@googlegroups.com. >> To post to this group, send email to django-d...@googlegroups.com. >> Visit this group at https://groups.google.com/group/django-developers. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/127550d4-b2dd-4ad7-8e6e-b56a66080194%40googlegroups.com >> <https://groups.google.com/d/msgid/django-developers/127550d4-b2dd-4ad7-8e6e-b56a66080194%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> >> -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/393625cf-3edb-41f3-b208-2b3f22cabd49%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/393625cf-3edb-41f3-b208-2b3f22cabd49%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAFNZOJMPPyCOzNQvZVi%3DDRy%2B6fri3VYNOdQ%2Bi6chc-%2BMNNouSA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
