In this case, I think it should be DISCUSS tag. When the developer believe the requirements are all in, then resend with a PROPOSAL tag.
I updated the Mailing list Guidelines assuming there's no objections. But please raise if there are. --Alex > -----Original Message----- > From: Min Chen [mailto:[email protected]] > Sent: Monday, January 07, 2013 12:13 PM > To: [email protected] > Subject: Re: [DISCUSS] Using Proposal tag for FS > > What tag should be used if developers sent out a requirement discussion > email together with a FS link? I saw that there were several discussion > threads like that the past week. > > Thanks > -min > > On 1/7/13 11:45 AM, "Chip Childers" <[email protected]> wrote: > > >On Mon, Jan 7, 2013 at 2:43 PM, Alex Huang <[email protected]> > wrote: > >> I propose that when developers actually send out a FS, then switch over > >>to using the tag PROPOSAL to mark it differently from requirement > >>gathering which currently uses DISCUSS tag. What does the community > >>think? > >> > >> --Alex > >> > >> > >> > > > >I was against this at first, but I'm now in agreement. > > > >If nobody disagrees, we should update the email conventions wiki page too > >;-)
