Gnus development mailing list
 help / color / mirror / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: emacs-devel@gnu.org
Cc: ding@gnus.org
Subject: Re: debbugs.el
Date: Thu, 24 Feb 2011 12:33:12 +0100	[thread overview]
Message-ID: <87vd093bwn.fsf@gmx.de> (raw)
In-Reply-To: <87mxllambw.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Thu, 24 Feb 2011 09:06:11 +0100")

Reiner Steib <reinersteib+gmane@imap.cc> writes:

[Cc to ding@gnus.org]

> On Wed, Feb 23 2011, Chong Yidong wrote:
>
>> Michael Albinus <michael.albinus@gmx.de> writes:
>>
>>> I propose to add a small package to the trunk I have written last weeks:
>>>
>>> ;;; debbugs.el --- SOAP library to access debbugs servers
> [...]
>>> Those functions could be used to implement a UI towards debbugs,
>>> widget-based or via gnus/nnir.
>>>
>>> For installation, the package needs also a WSDL file (Debbugs.wsdl). I
>>> have no idea where to install this file, maybe at etc/ ?
>>>
>>> Comments?
>>
>> This sounds more suitable for elpa.gnu.org than the trunk.
>
> I think we need a better interface to our bug tracker[1].  It would be
> better to have it in Emacs so that Gnus (nnir, message mode, ...) can
> build upon it.
>
> [1] handling bugs as described in admin/notes/bugtracker: closing,
>     merging, tagging, setting severity, ...

That was my motivation writing debbugs.el. I've also started an nnir
integration, but I failed badly due to missing gnus knowledge.

OTOH, the debbugs SOAP interface is poor, there are only very basic
information one could retrieve, and there is no "activiation" function
(changing whatever for a bug). So it might be better, we first make a
prototype implementation integrating it with nnir etc, before adding it
to Emacs core. For this purpose, it might be sufficient to bring it to
elpa (or gnus) for a while.

I would volunteer to participate in this integration work. I have
learned, I'm not able to do it alone.

> Bye, Reiner.

Best regards, Michael.



       reply	other threads:[~2011-02-24 11:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8762sa9770.fsf@gmx.de>
     [not found] ` <87pqqibr30.fsf@stupidchicken.com>
     [not found]   ` <87mxllambw.fsf@marauder.physik.uni-ulm.de>
2011-02-24 11:33     ` Michael Albinus [this message]
2011-02-24 23:44       ` debbugs.el Evgeny M. Zubok
2011-02-25 10:55         ` debbugs.el Michael Albinus
2011-02-25 16:51           ` debbugs.el Evgeny M. Zubok
2011-03-01 10:15             ` debbugs.el Michael Albinus
2011-03-02 15:56               ` debbugs.el Evgeny M. Zubok
2011-02-25  3:37       ` debbugs.el Lars Ingebrigtsen
2011-02-25  8:17         ` debbugs.el Eli Zaretskii
2011-02-25  8:33           ` debbugs.el Michael Albinus
2011-02-25  8:54             ` debbugs.el Eli Zaretskii
2011-02-25  9:29               ` debbugs.el Miles Bader
2011-02-25  9:55                 ` debbugs.el Eli Zaretskii
2011-02-25 15:43                   ` debbugs.el Stefan Monnier
2011-02-25 15:52                     ` debbugs.el Eli Zaretskii
2011-02-25  9:59           ` debbugs.el Lars Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vd093bwn.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).