From: Michael Tremer <michael.tremer@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: [Documentation] new list in bugzilla
Date: Tue, 06 Mar 2012 15:43:03 +0100 [thread overview]
Message-ID: <1331044983.10879.0.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <4F561E7E.3020807@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1280 bytes --]
You didn't misunderstand anything. That was what I thought. I am totally
fine with the Documentation team using Bugzilla.
So go for it.
Michael
On Tue, 2012-03-06 at 15:26 +0100, Daniel Weismüller wrote:
> oh ok! Sorry I've misunderstood it!
>
> Did you have an alternative idea?
>
> - Daniel
>
> Am 06.03.2012 09:48, schrieb Michael Tremer:
> > Hello Daniel,
> >
> > I thought this was going to be just experimental for a while. Maybe the
> > overhead a bugtracker requires is too much for the simpler documentation
> > tasks.
> >
> > Anyway, I like the way to introduce a more strict way how to deal with
> > the issues. Good.
> >
> > Michael
> >
> > On Tue, 2012-03-06 at 08:05 +0100, Daniel Weismüller wrote:
> >> Hello!
> >> In bugziila we now have our own "buglist".
> >>
> >> https://bugzilla.ipfire.org/describecomponents.cgi
> >>
> >> The idea is that every one of us may write down what should be done and
> >> we are able to assign it to someone.
> >> Further we have quick overview of the work that must be done.
> >>
> >> What you think about it?
> >>
> >> - Daniel
> >>
> >>
> > _______________________________________________
> > Documentation mailing list
> > Documentation(a)lists.ipfire.org
> > http://lists.ipfire.org/mailman/listinfo/documentation
>
prev parent reply other threads:[~2012-03-06 14:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 7:05 Daniel Weismüller
2012-03-06 8:48 ` Michael Tremer
2012-03-06 14:26 ` Daniel Weismüller
2012-03-06 14:43 ` Michael Tremer [this message]
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=1331044983.10879.0.camel@rice-oxley.tremer.info \
--to=michael.tremer@ipfire.org \
--cc=documentation@lists.ipfire.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