A quick tip (which might be obvious, but might help a few people): I
use the RSS feed for specific tickets to keep track of their progress.
That way, if comments are added, or new patches are supplied, it
automatically pops up in "Django tickets" in my RSS reader.
-Phil
On 14/01/07, Adrian Holo
I think this should be really high on the priority list of the core
django team because, as many have said, everybody here is a volunteer,
and personally many times I would be thinking of investing some time to
implement a feature in django thinking that it might be useful for
other people (inste
Russell Keith-Magee wrote:
On 1/14/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> Trac's non-feature of not automatically sending changes to the reporter
> (which follows from not requiring a valid reporter email) doesn't help
> here, either.
I'd always wondered about this.. er... featur
On 1/14/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
Trac's non-feature of not automatically sending changes to the reporter
(which follows from not requiring a valid reporter email) doesn't help
here, either.
I'd always wondered about this.. er... feature. Is it possible to
filter the s
[EMAIL PROTECTED] schrieb:
I'm willing to put some time into triage, if we get some guidelines
sorted.
I'd join in. Especially sorting out all the old stuff.
Michael
--
noris network AG - Deutschherrnstraße 15-19 - D-90429 Nürnberg -
Tel +49-911-9352-0 - Fax +49-911-9352-100
http://www.nor
I'm willing to put some time into triage, if we get some guidelines
sorted.
--Simon
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Django
developers" group.
To post to this group, send email to django-developers
On 1/14/07, Michael Radziej <[EMAIL PROTECTED]> wrote:
after thinking about drproject: I'd rather switch to something
full-fledged like Bugzilla (http://www.bugzilla.org/). But I guess that
is out of question. The integration of tickets with svn and all this is
really too cool, and while bugzill
Hi,
after thinking about drproject: I'd rather switch to something
full-fledged like Bugzilla (http://www.bugzilla.org/). But I guess that
is out of question. The integration of tickets with svn and all this is
really too cool, and while bugzilla provides a much better ticketing
system than trac
Hi Tim,
Tim schrieb:
I wonder if any of you have seen "Dr. Project". It's basically some
additional functionality built on top of Trac (includes a tag cloud and
multi-project support).
https://www.drproject.org/
Hmm, browsing through the docs the only stuff that tries to explain the
differe
Granted, Jan, but a human still had to sign up their spam bot.
In the case of the web site, all the email addresses publicly
accessible to any and every spam-spider. It's just not good etiquette.
--~--~-~--~~~---~--~~
You received this message because you are su
Op zondag 14-01-2007 om 12:40 uur [tijdzone -0800], schreef SmileyChris:
It has always frustrated me that email addresses are just given away
to spammers. Is there anything that can be done to hide or obscure
commenter/submitter emails and "CC" emails?
By mailing this list, you have just sent
FYI, this is being talked about too:
http://trac.edgewall.org/ticket/153
http://trac.edgewall.org/ticket/1459
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Django
developers" group.
To post to this group, send e
I wonder if any of you have seen "Dr. Project". It's basically some
additional functionality built on top of Trac (includes a tag cloud and
multi-project support).
https://www.drproject.org/
This may be a source of inspiration or even a solution.
--~--~-~--~~~---~-
It has always frustrated me that email addresses are just given away to
spammers. Is there anything that can be done to hide or obscure
commenter/submitter emails and "CC" emails?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the G
Hi,
Michael Radziej wrote:
First, Malcolm has brought up the idea about using Trac's keywords. I've
looked up the URL from his email, and I'd like these keywords:
Oops: it wasn't brought up by Malcolm but by Gary. Sorry about that!
Michael
--~--~-~--~~~---~--~--
Hi,
here are a few further suggestions for the ticket workflow.
First, Malcolm has brought up the idea about using Trac's keywords. I've
looked up the URL from his email, and I'd like these keywords:
From adrian:
- design-q (or rather: "needs-design-decision")
- ok-needs-patch (or rather: n
Adrian Holovaty wrote:
Hello all,
I'd really like to streamline the way we interact with our ticket system, Trac.
We've fallen behind on managing tickets, which is not only frustrating
to contributors but a hindrance to Django's growth, as solid
contributions are made but eventually get lost i
On 1/14/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
Hello all,
I'd really like to streamline the way we interact with our ticket system, Trac.
We've fallen behind on managing tickets, which is not only frustrating
to contributors but a hindrance to Django's growth, as solid
contributions ar
On Sat, 2007-01-13 at 21:09 -0600, Adrian Holovaty wrote:
Hello all,
I'd really like to streamline the way we interact with our ticket system, Trac.
We've fallen behind on managing tickets, which is not only frustrating
to contributors but a hindrance to Django's growth, as solid
contributions
Hello all,
I'd really like to streamline the way we interact with our ticket system, Trac.
We've fallen behind on managing tickets, which is not only frustrating
to contributors but a hindrance to Django's growth, as solid
contributions are made but eventually get lost in the sea of
half-baked
20 matches
Mail list logo
