You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
keyword_sprintresolution_fixedtype_enhancement | by loa@pi.nu
Today a wg groups have procedures that is followed before the actual poll for working group adoption is started, for example we let working group review teams do reviews to help the chairs to see if a document is ready, and we do IPR polls. "Candidate for wg Adoption" were created for this purpose, however to today when working groups starts working on a document it is forced into "Call for adoption by working issued", which in many cases are not true and since it causes traffic to the wg mailing list and the authors, we also spread misinformation that we need to correct with further mails.
When we press the "Adopt in WG" button we should have the opportunity to decided which state document should go into - e.g. "Candidate for working group adoption" if that is what we want to do.
Issue migrated from trac:1406 at 2022-03-04 03:44:29 +0000
The text was updated successfully, but these errors were encountered:
keyword_sprint
resolution_fixed
type_enhancement
| by loa@pi.nuToday a wg groups have procedures that is followed before the actual poll for working group adoption is started, for example we let working group review teams do reviews to help the chairs to see if a document is ready, and we do IPR polls. "Candidate for wg Adoption" were created for this purpose, however to today when working groups starts working on a document it is forced into "Call for adoption by working issued", which in many cases are not true and since it causes traffic to the wg mailing list and the authors, we also spread misinformation that we need to correct with further mails.
When we press the "Adopt in WG" button we should have the opportunity to decided which state document should go into - e.g. "Candidate for working group adoption" if that is what we want to do.
Issue migrated from trac:1406 at 2022-03-04 03:44:29 +0000
The text was updated successfully, but these errors were encountered: