According to, https://woof.bzg.fr/howto, there must be a certain pattern
in the email subject to convert an email into a report. However, not all
the users follow this pattern. Often, bug reports are just ordinary
emails.
Would it be possible to mark reports right in the reply?
Hi Ihor,
Ihor Radchenko <yantar92@posteo.net> writes:
> According to, https://woof.bzg.fr/howto, there must be a certain pattern> in the email subject to convert an email into a report. However, not all> the users follow this pattern. Often, bug reports are just ordinary> emails.>> Would it be possible to mark reports right in the reply?
I added a section in the howto explaining how maintainers can create
or update reports by directly sending an email to the Woof! inbox.
If someone sends a bug with the wrong subject e.g. "this is a bug",
you can edit the email subject as "[BUG] this is a bug" then resend
this email to the Woof! inbox.
This works if:
- You are a maintainer
- Your email client allows you to edit emails
- Your resent email keeps the same Message-Id
Would this be usable for you?
Another possibility is simply to reply to all (including the mailing
list address) and to change the subject, it will create a report from
*your* reply and remind people about the convention used for reports.
--
Bastien
Bastien <bzg@gnu.org> writes:
> I added a section in the howto explaining how maintainers can create> or update reports by directly sending an email to the Woof! inbox.
Do you mean "Updating a report without replying to the mailing list"?
I can see how it can work for silently closing reports, but it is not
obvious how I can re-qualify the reports from that section.
BTW, what is that magic control email tracker.orgmode.org now uses?
Still orgmode@bzg.fr? We should probably document it at some point in
org-maintenance.
> If someone sends a bug with the wrong subject e.g. "this is a bug",> you can edit the email subject as "[BUG] this is a bug" then resend> this email to the Woof! inbox.> This works if: >> - You are a maintainer> - Your email client allows you to edit emails> - Your resent email keeps the same Message-Id>> Would this be usable for you?
Err. I am not sure if my Emacs client allows editing emails.
I am pretty sure that Emacs does allow it, but this sounds like too much
restrictions for people who want to be maintainer stewards. Especially
given that Woof! is positioned as generic tool not linked to Emacs and
surrounding software.
> Another possibility is simply to reply to all (including the mailing> list address) and to change the subject, it will create a report from> *your* reply and remind people about the convention used for reports.
And it prohibits confirming the report in the same email...
I guess we can find some inspiration from
https://debbugs.gnu.org/server-control.html that is solving a similar
set of problems.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
Ihor Radchenko <yantar92@posteo.net> writes:
> Bastien <bzg@gnu.org> writes:>>> I added a section in the howto explaining how maintainers can create>> or update reports by directly sending an email to the Woof! inbox.>> Do you mean "Updating a report without replying to the mailing> list"?
Yes.
> I can see how it can work for silently closing reports, but it is not> obvious how I can re-qualify the reports from that section.
I added this paragraph:
https://git.sr.ht/~bzg/woof/commit/0f3c81d> BTW, what is that magic control email tracker.orgmode.org now uses?> Still orgmode@bzg.fr? We should probably document it at some point in> org-maintenance.
Yes, it is orgmode@bzg.fr - for now, Woof! is still a bit unstable and
I prefer to wait until we advertize https://tracker.orgmode.org to all
users. I hope feedback from you and Tim will help enhance it enough
so that you like relying on it.
Once this is settled, no problem for advertizing it to Org users.
Also, the Woof! inbox should probably be advertized in the howto from
Woof! directly, I'm not just sure where.
>> If someone sends a bug with the wrong subject e.g. "this is a bug",>> you can edit the email subject as "[BUG] this is a bug" then resend>> this email to the Woof! inbox.>>> This works if: >>>> - You are a maintainer>> - Your email client allows you to edit emails>> - Your resent email keeps the same Message-Id>>>> Would this be usable for you?>> Err. I am not sure if my Emacs client allows editing emails.> I am pretty sure that Emacs does allow it, but this sounds like too much> restrictions for people who want to be maintainer stewards. Especially> given that Woof! is positioned as generic tool not linked to Emacs and> surrounding software.
Fair enough. Gnus allows it, but you're right, probably an exception,
and feels too hackish anyway.
Doing what you suggest would require Woof! to store *every* email sent
to a list, so that maintainers can act upon any stored email after it
has been sent.
I don't want Woof! to store every email sent, I'd rather stick to the
current way: if a user forget a prefix (e.g. [BUG]), they someone can
reply with a new subject (e.g. [BUG]) and quote the original message
so that the content of the bug report is not lost.
It is strict, but hopefully good enough.
>> Another possibility is simply to reply to all (including the mailing>> list address) and to change the subject, it will create a report from>> *your* reply and remind people about the convention used for reports.>> And it prohibits confirming the report in the same email...
... unless maintainers can add updates in the original reports.
> I guess we can find some inspiration from> https://debbugs.gnu.org/server-control.html that is solving a similar> set of problems.
I have debbugs well in mind. One direction I want to avoid: having
emails cluttered with formal instructions that don't feel natural at
all. But yes, all these "actions" can make sense in the context of
Woof.
--
Bastien
Bastien <bzg@gnu.org> writes:
>> I can see how it can work for silently closing reports, but it is not>> obvious how I can re-qualify the reports from that section.>> I added this paragraph: > https://git.sr.ht/~bzg/woof/commit/0f3c81d
This does not sound very clear.
I am not sure how to "edit" the subject other than by replying with
changed subject.
>> Err. I am not sure if my Emacs client allows editing emails.>> I am pretty sure that Emacs does allow it, but this sounds like too much>> restrictions for people who want to be maintainer stewards. Especially>> given that Woof! is positioned as generic tool not linked to Emacs and>> surrounding software.>> Fair enough. Gnus allows it, but you're right, probably an exception,> and feels too hackish anyway.>> Doing what you suggest would require Woof! to store *every* email sent> to a list, so that maintainers can act upon any stored email after it> has been sent.
May Woof! instead query and store email according to In-Reply-To?
>> I guess we can find some inspiration from>> https://debbugs.gnu.org/server-control.html that is solving a similar>> set of problems.>> I have debbugs well in mind. One direction I want to avoid: having> emails cluttered with formal instructions that don't feel natural at> all. But yes, all these "actions" can make sense in the context of> Woof.
What about "private" emails that are sent to Woof! directly?
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
Ihor Radchenko <yantar92@posteo.net> writes:
>> Doing what you suggest would require Woof! to store *every* email sent>> to a list, so that maintainers can act upon any stored email after it>> has been sent.>> May Woof! instead query and store email according to In-Reply-To?
I don't understand: either Woof! stores every email sent to a list or
it does not. If it does not, there is no way to get the data of emails
that Woof! has not seen.
But I feel I did not understand your suggestion.
>>> I guess we can find some inspiration from>>> https://debbugs.gnu.org/server-control.html that is solving a similar>>> set of problems.>>>> I have debbugs well in mind. One direction I want to avoid: having>> emails cluttered with formal instructions that don't feel natural at>> all. But yes, all these "actions" can make sense in the context of>> Woof.>> What about "private" emails that are sent to Woof! directly?
Yes, those emails can contain many Woof! triggers, e.g.
Confirmed.
Important.
Urgent.
It does not hurt. But I also want a consistent way of triggering Woof
updates, whether the email is sent privately or publicly, I think it's
easier to memorize and use.
--
Bastien
Bastien <bzg@gnu.org> writes:
>> May Woof! instead query and store email according to In-Reply-To?>> I don't understand: either Woof! stores every email sent to a list or> it does not. If it does not, there is no way to get the data of emails> that Woof! has not seen.>> But I feel I did not understand your suggestion.
What I mean is:
1. Maintainer sends a reply renaming subject to have [BUG] + saying
"Confirmed" in the body
2. Woof! sees this and looks into In-Reply-To. Then, it downloads the
email in In-Reply-To and marks it as confirmed bug, if the new
subject is [BUG] <in-reply-to email subject>.
>> What about "private" emails that are sent to Woof! directly?>> Yes, those emails can contain many Woof! triggers, e.g.>> Confirmed.> Important.> Urgent.>> It does not hurt. But I also want a consistent way of triggering Woof> updates, whether the email is sent privately or publicly, I think it's> easier to memorize and use.
Agree.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
Ihor Radchenko <yantar92@posteo.net> writes:
> 2. Woof! sees this and looks into In-Reply-To. Then, it downloads the> email in In-Reply-To and marks it as confirmed bug, if the new> subject is [BUG] <in-reply-to email subject>.
Got it. But "downloading the email in In-Reply-To" is not doable
consistently. You can do it with public-inbox, list.sr.ht, but I
don't think you can do it with handled by mailman (at least with
mailman < v3) or sympa.
That's the limitation I was mentioning: if Woof misses an email,
there is no consistent way to re-add it to the list of reports.
--
Bastien
Bastien <bzg@gnu.org> writes:
> Ihor Radchenko <yantar92@posteo.net> writes:>>> 2. Woof! sees this and looks into In-Reply-To. Then, it downloads the>> email in In-Reply-To and marks it as confirmed bug, if the new>> subject is [BUG] <in-reply-to email subject>.>> Got it. But "downloading the email in In-Reply-To" is not doable> consistently. You can do it with public-inbox, list.sr.ht, but I> don't think you can do it with handled by mailman (at least with> mailman < v3) or sympa.
But can't you query the required message from IMAP server? Via
`search-inbox'.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
Ihor Radchenko <yantar92@posteo.net> writes:
> But can't you query the required message from IMAP server? Via> `search-inbox'.
Indeed, good idea! In the meantime, I'm also testing the idea of
keeping track of *every* email, maybe the db size is acceptable.
--
Bastien
Bastien <bzg@gnu.org> writes:
> ... In the meantime, I'm also testing the idea of> keeping track of *every* email, maybe the db size is acceptable.
Then, wouldn't it be easier to deploy something like public-inbox to
store emails? Or use another existing mail db indexer, like notmuch.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>