Hi Ian and Jean-Paul Thanks for the feedback.
On Thu, 11 Nov 2021 at 13:26, Jean-Paul Calderone <[email protected]> wrote: > > On Thu, Nov 11, 2021 at 4:34 AM Adi Roiban <[email protected]> wrote: >> [snip] >> With the migration the original author of a ticket/comment is lost. >> This is a security feature in GitHub. >> Also, it's not trivial to get all the Trac accounts mapped to GitHub >> accounts. > > > Maybe rather than losing this (and any other metadata) it can be preserved as > non-canonical metadata. For example, maybe each issue description and > comment can end with an easily machine-identifiable block that encodes the > information from trac. > > The information may not be especially interesting in the day-to-day > development of Twisted but it could potentially be interesting for certain > investigations - for example, I have often been interested in finding out who > made some change or comment that I could not understand so I could find them > and talk to them about it. Great feedback. The current code migrated all possible metadata to GitHub Issue dedicated fields like labels , asigneed, milestone ... and add a human readable info for the metadata that couldn't be migrated to GitHub metadata. But I think that keeping all metadata in the description will help. The current tool migrate a ticket something like this https://github.com/chevah/compat/issues/133 Without any machine readable metadata in the comment. And with GitHub resolution closed:fixed converted into a label. > Maybe this kind of thing is already done by the migration tool anyway and you > were only talking about canonical GitHub metadata, though? I've seen > projects migrated to, eg, GitLab where the migration tool leaves a text blurb > with original author information at the bottom, for example. > I need feedback regarding the ticket ID mapping. We have 2 options. Option A - Create a new repo Pros: All trac ID can be preserved to GitHub IDs Cons: All existing twisted/twisted PR will be hosted in a separate repo (twisted/twisted-archive) Option B - Migrate over the existing repo Pros: You still have all the 1670 PR in the same repo Cons: Trac tickets up to 1670 will not have a direct mapping to GitHub issue IDs >> We can keep the existing Trac in read-only mode for some time. >> And it can (and will be) linked from Github Issues > > > If all of the trac metadata gets encoded into GitHub *somehow* then maybe > this Trac deployment doesn't have to be maintained for very long. > > I know this may mean extra work for the migration. However, I'd ask that you > strongly weigh that cost against what's being lost if this isn't done. > Twisted has decades of history at this point. That represents a massive > investment from many people. Apart from the practical value that is lost if > metadata about those contributions is thrown away, it also seems > disrespectful to the people who put in that investment and sends a certain > signal about how current and new contributions are likely to be valued by > future project maintainers. Thanks again for the feedback. My plan is to not lose any metadata or attachments. I have created an issue to make sure this is not forgotten https://github.com/chevah/trac-to-github/issues/17 I will wait over the weekend to receive more feedback about Option A or Option B :) The plan is then to do a testing migration over a testing repo, get a round of feedback and then the actual migration only after that. Regards -- Adi Roiban _______________________________________________ Twisted mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/twisted.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/2AGY7OZEQBOCU35TLFCEPLMHDHPADCAB/ Code of Conduct: https://twisted.org/conduct
