-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reinstate go-ontology and go-annotation summary emails #1530
Comments
Operationally: go-annotation
go-ontology
|
@kltm Can you assign someone to do this ? It would be nice to have this for the GOC meeting in Oct. |
@pgaudet @kltm I got pretty far with using a github action for this in this repo: https://github.com/dustine32/daily-tracker-email I'll move the repo over to https://github.com/geneontology soon. |
Thanks ! |
Talking to @dustine32, we'll be needing to move on to some testing to try working with an SMTP server (either GH or LBL, depending). |
Thank you @dustine32 . @vanaukenk Here is some example output from the "new" iteration of the script:
Summary for tickets from 2020-10-20 to 2020-10-21New TicketsThere are 42 new tickets.
Updated TicketsThere are 7 updated tickets.
I believe that this is a straight port of the old script. Also note that it is sending in HTML (which I think is weird, but I so don't want to rock the boat on this one--I guess everybody else allows that in their incoming email and that's apparently what we had before). If this looks okay, we can start playing around with getting this sent out. |
Looks good ! Although I thought people were mostly interested in the go-ontology repo. In any case, can you change the header so that it states which repo is the report from ? ie Summary for tickets from 2020-10-20 to 2020-10-21 (& likewise for go-ontology). Thanks, Pascale |
Thanks @dustine32 and @kltm This looks good. Let's start with go-annotation and go-ontology and take it from there. |
Summary to date: What is missing from the ticket are some discussions that I had with @dustine32 on the side. Essentially, what we had been hoping to do was take advantage of GitHub Actions (now that Travis is going away) to send the email periodically and easily. While Dustin was able to make it mostly work, creating the scripts and using the GH API, the actual email sending part turned out to be a difficult prospect using GHA. After a few tries, we decided it might, in fact, be better handled by the pipeline, as the email environment was a little better understood at the BBOP site. The core issue that has been run into here is that most outgoing email servers tend to be locked to individual identities and fixed or paid services, so getting the email out with parts-off-the-shelf approach did work out as we had hoped; related to that is that sending sorta-anonymous email to mailing lists gets flagged as spam. With these issues, the ball was in my court to try and get this done through the mail servers that BBOP has access to, or find another way forward. Unfortunately, I have been otherwise occupied with various issues and have not been able to commit enough time to make progress. That said, we've had a little more experience as a group with GHA now, so I've just asked internally if there is anybody who could help out with this. |
I think there are three ways forward here. I would propose the following path:
@dustine32 Would you be willing and available to take another crack at this? Ping me and we can chat. |
Status update on this. |
Pinging @dustine32 for any further news for the GHA effort. |
Thanks @kltm! For the GHA route, I just need to finish coding the OAuth2 login step for accessing the USC mail server in order to send out the email from GitHub's servers. |
Will we be ready to mention this at the GOC meeting next week? @suzialeksander this could go in the 'Communication' presentation. |
@pgaudet @suzialeksander You should be able to mention it in some capacity; I'm not sure it will be finalized by then, but things are quicker now that we're putting a temp hold on the GHA route. We still need to cycle owner @vanaukenk , who may be a little busy at this point :) |
@pgaudet Is the full
Or we can get surgical if we don't want the "geneontology/" part. |
I have a slight personal preference for just |
…eader Change str formatting for compatibility and update header for #1530
@suzialeksander No prob! Just dropped the org part. This change should be safe. |
…eader GH issue search now full 24hr, for #1530
From @pgaudet: Filter out pull requests in email. |
Easy to do, actually. Thanks GH API! |
…eader Filter for only issues (not PRs) for #1530
We are going to reinstate the go-ontology and go-annotation summary emails, which had been left behind when the old pipeline system finally went offline. The jobs were: go-github-annotation-tracker-summary-email and go-github-ontology-requests-summary-email.
For this, we'd like to keep it out of the main pipeline, as they are solely a function of GitHub, and are looking to implement them with GH actions. As well, we'd like to take this chance to migrate from the crufty old JS to standard and no-frills python.
Originally geneontology/helpdesk#259
Tagging @dustine32 @dougli1sqrd
The text was updated successfully, but these errors were encountered: