Wrong group type in scheduling request email response

[ietf-svn-bot]

keyword_sprint type_defect | by [email protected]

---

"Working Group" should be replaced by group type everywhere. "Area Name" is also confusing, since the IRTF isn't an area.

A new meeting session request has just been submitted by Lars Eggert, a Chair of the irtfopen working group.


---------------------------------------------------------
Working Group Name: IRTF Open Meeting
Area Name: IRTF
Session Requester: Lars Eggert

Number of Sessions: 1
Length of Session(s):  1.5 Hours
Number of Attendees: 200
Conflicts to Avoid: 
First Priority: maprg gaia cfrg hrpc iccrg icnrg nfvrg  nmrg nwcrg sdnrg t2trg quic




Special Requests:
 Ideally, schedule early in the week but after the IAB plenary. Avoid overlapping with all IRTF sessions and IETF area meetings, and ideally BoFs.

---

Issue migrated from trac:2120 at 2022-03-04 05:38:01 +0000

[ietf-svn-bot]

@[email protected] changed priority from n/a to medium

[ietf-svn-bot]

@[email protected] changed component from doc/ to meeting/

[ietf-svn-bot]

@[email protected] commented

---

This isn't quite as easy as it looks, but we can make some improvements.

First - it's good you used irtfopen as an example. It's currently configured as an Area Group (or 'AG') not a Research Group. It's probably right that it's something analogous to an Area Group, but we probably want a new group type to indicate what it really is.

When this is implemented: the string you're hoping to use lives in GroupTypeName.verbose_name

[ietf-svn-bot]

@[email protected] changed keywords from `` to sprint

[ietf-svn-bot]

@[email protected] changed status from new to under_review

[ietf-svn-bot]

@[email protected] commented

---

Several things have changed since this was last discussed. We need to look at the group type settings and see if this is still an issue. If so, it should be easier to fix than it was at the time of the original report.