Whenever I've had to move from one issue-system to another, the main pain point has always been issue/comment ownership[*]. This is because many systems want a login-capable, verified user for every single person that have ever made an issue or comment. If there is no 1-to-1 mapping, the issue/comment is often owned by the importing user, and the username/email of the original contributor is mangled into the issue/comment-text itself.
This looks so nice for an issue with 50+ different contributors when wind up being owned by the same user. Robert explains to Robert that Robert's patch won't work with Roberts latest PR because Robert pulled the wrong commit that Robert made to update the dependencies that Robert discovered needed to be updated because Robert found a security flaw, with apologies to Robert. There's usually no way to search for the actual contributors either. It is as if importing to such issue-systems are an after thought. Starting out with a design where user and contributor are two different but potentially linked objects would have solved the problem *correctly*. </rant> [*] There are no doubt problems other than this, it's just the one that bugs me the most. Especially since the solution so often is "Drop all history, start from scratch." -- 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/CACQ%3DrreeXWcVCjxZGG18GDeeh98P_OxresAm9w_JrN0HSOQNhg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
