Were any alternatives proposed?

In T146307#2676260, @Legoktm wrote:

Were any alternatives proposed?

The viable options I'm aware of:

1. wikitech-l
2. Some other mailing list (e.g. wikitech-ambassadors, some announcement mailing list)
3. Some on-wiki notification on mediawiki.org
4. Some combination of the above (e.g. multiple mailing lists)

One note for myself: as part of completing this task, I'd like to move https://www.mediawiki.org/wiki/User:RobLa-WMF/Wikitech-l to https://www.mediawiki.org/wiki/Wikitech-l , since I believe that wikitech-l is important enough to MediaWiki that it should have page on MediaWiki.org describing this list and its role as "paper of record" for last call announcements (assuming we keep this on wikitech-l)

I think wikitech-l should always receive last call announcements. wikitech-ambassadors maybe if it is relevant.

I think we could add a |status=lastcall parameter to {{rfc}} plus the category to generate a "RfCs in Last call" listing on https://www.mediawiki.org/wiki/Requests_for_comment for example.

In T146307#2696140, @Legoktm wrote:

I think wikitech-l should always receive last call announcements. wikitech-ambassadors maybe if it is relevant.

I think we could add a |status=lastcall parameter to {{rfc}} plus the category to generate a "RfCs in Last call" listing on https://www.mediawiki.org/wiki/Requests_for_comment for example.

Hmmm....short of doing a lot of bot programming to pull this information out of Phab, I'd prefer to refer people back to Phab rather than manually syncing two different sources (DRY principle).

Ultimately, I hope Phab upstream can improve their API to make it so that it's easier to pull workboard column IDs. That would make it so that it possible for us to have tighter coupling of Phab and MediaWiki. As I recall from the last time I worked extensively with the Phab API, workboard column was difficult information to extract (IIRC, I needed to use BeautifulSoup to scrape the information off the web view). Phab has been going through rapid evolution since I last looked, so there may be sensible, stable web APIs for this information now.