On Tue, Mar 23, 2021 at 9:16 PM J. Lewis Muir <[email protected]> wrote:
> On 03/23, Jeremy Evans wrote: > > Here's an example of an import from Google Groups to GitHub Discussions > > using one of my smaller projects (AutoForme): > > https://github.com/jeremyevans/test-autoforme-discussions/discussions > > > > This is to give people an idea for how such an import would like like, > and > > see if anyone wants such an import to work differently. > > I like it that you've got a nice clear Google Group "header" at the > beginning of each message with a link to the original post, the date, > and the sender. > > I didn't anticipate the problem of what to do when the sender does not > have a GitHub account which is presumably the case in > > https://github.com/jeremyevans/test-autoforme-discussions/discussions/32 > > That's unfortunate. It's awkward and confusing because it looks like > you wrote the question since it's your avatar and your name in the > title, but you did not. This, then, also makes it hard to tell what > messages are actually from you. I see that it's got the Google Group > Sender field to indicate who really wrote it, but the presentation is > unfortunately confusing. I understand that it may be the best that can > be done in this case. Sad, though. > > Much better would be if there were some way to use a generic avatar and > use the email address that appears in the Google Group Sender field as > the name in the title. But I suppose it's not possible. > > If the above is not possible, another idea that comes to mind is > creating a GitHub account under your control specifically for > representing all Google Group senders that cannot be mapped to a GitHub > account. Then, it could be a generic avatar and a generic name like > "Google Group Sender" or whatever. > This isn't about email addresses that don't have a GitHub account. This is about all posts, regardless of whether they have a GitHub account. GitHub doesn't support creating discussion posts or comments as another user, I'm sure for security reasons: https://docs.github.com/en/graphql/guides/using-the-graphql-api-for-discussions#creatediscussion I agree with you that it is confusing, but I don't think there is any way to fix it. It's just something we would have to accept it we wanted to switch to GitHub Discussions and import from Google Groups. I don't want to create a separate GitHub account for the import, so any import will have me as the author for all discussions and comments. Note that there is historical precedence in Sequel for this, as the same is true for issues imported from Google Code to GitHub Issues (example: https://github.com/jeremyevans/sequel/issues/100). One other thing: I noticed in the above discussion that one of the > comments includes an automatically added signature like: > > You received this message because you are subscribed to the Google Groups > "Forme" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > ... > > It would be nice if that kind of signature could be removed as part of > the import process. But, just a thought. Maybe it's not worth the > effort. Hopefully that won't be too difficult to implement in the simple case. I'm guessing it's nontrivial to handle in complex cases, such as when the signature is quoted, but those can probably be ignored. Thanks, Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/sequel-talk/CADGZSSdGuuCRnn%2Ba9tMP68a1%2BJt%3Dhsq6%3D4SSut9mARHocb74dQ%40mail.gmail.com.
