Re: Ticket spam

Ville Säävuori wrote: >> I miss the "Week In Review" blog posts from Adrian but surely he's not >> writting those to have more time for coding :) > > Yeah, me too! It's very nice to read something "digested" about ongoing > deveploment (from an insider) because following all trac changes and >

Re: Ticket spam

> I miss the "Week In Review" blog posts from Adrian but surely he's not > writting those to have more time for coding :) Yeah, me too! It's very nice to read something "digested" about ongoing deveploment (from an insider) because following all trac changes and dev-list is sometimes not very eas

Re: Dev policy, was Re: Ticket spam

Michael Radziej wrote: > I like Django, perhaps I rather contribute > more tiny stuff of which I feel that it will get integrated, and I have > my own patchset for Django. So what? It works fine for me. Why should I > turn to a different framework when I like the concept and code (and the > docs!)

Re: Dev policy, was Re: Ticket spam

Hi, let me add my own view, and this is not a direct answer to Ian but more to the whole thread. I personally got frustrated about the way tickets are handled. And sure, Adrian is currently a very scarce and important resource. There's written enough about that and I don't want to deepen it agai

Re: Dev policy, was Re: Ticket spam

On 11/4/06, iain duncan <[EMAIL PROTECTED]> wrote: > > I have to say that I think you're confusing arrogance with a desire to > > do things *RIGHT*, and a lack of time on the part of the core devs. > > This however is part of the issue. With rapid growth comes that lack of > time for the founders.

Re: Dev policy, was Re: Ticket spam

> I'd just like to point out a counter-example to those arguing that the > core developers don't listen to criticism. There was a post recently > to django-users called "Why I'm giving up on Django" : Agreed. I would like to point out that I am not saying the core doesn't listen. I'm not trying

Re: Dev policy, was Re: Ticket spam

Hi all, I'd just like to point out a counter-example to those arguing that the core developers don't listen to criticism. There was a post recently to django-users called "Why I'm giving up on Django" : http://groups.google.com/group/django-users/browse_thread/thread/394701c83497e405/f85b5013b6

Re: Re: Dev policy, was Re: Ticket spam

> What I've said here, repeatedly, is that if there's this problem, I > want to see examples of it, because I haven't so far, and if I'm going > to understand that there is a problem and understand where it comes > from, I *need* to see examples. There's a big, big difference between > that and "n

Re: Re: Dev policy, was Re: Ticket spam

> well, then I do. I´m scared away. why? exactly because of what james > is writing here. > it seems that noone except the "core developers" are allowed to > criticize django - whenever something like this comes up on the list, > there´s someone who fights the arguments tooth and nail. there´s no

Re: Re: Re: Re: Ticket spam

I miss the "Week In Review" blog posts from Adrian but surely he's not writting those to have more time for coding :) On 11/4/06, James Bennett <[EMAIL PROTECTED]> wrote: > > And to clarify regarding Trac in particular: that's not really a > Django issue, it's a server maintenance issue. "We're w

Re: Dev policy, was Re: Ticket spam

> So far as I can tell, our biggest long-term management problem right > now is not one of scaring developers away, it's one of keeping track > of all the people who want to get involved and all the things they > want to do. You haven't yet provided an example to the contrary. well, then I do. I´

Re: Re: Dev policy, was Re: Ticket spam

On 11/4/06, iain duncan <[EMAIL PROTECTED]> wrote: > Every single comparison of Gears to Django I have read say something to > the effect of "Gears is more community based". I think that's pretty > clear if you read between the lines. And part of what I'm going on about > is addressed in your blog

Re: Dev policy, was Re: Ticket spam

> I would like to see examples of this; I have a pretty comprehensive > set of ego searches and tag subscriptions for Django-related postings, > and I don't get the "Django is closed, don't bother trying to get > involved" vibe as much as you apparently do. So I'd really be > interested to see exa

Re: Dev policy, was Re: Ticket spam

On 11/4/06, iain duncan <[EMAIL PROTECTED]> wrote: > Ok, this is where you are IMHO wrong. You don't get to choose which > misconceptions you throw out. The perceptions are there, obviously, or > there wouldn't be blog postings about it, and you saying they are wrong > accomplishes nothing. I was

Dev policy, was Re: Ticket spam

Before I reply to various points, let me preface by saying my interest is only in seeing Django succeed, because as a long time Csound user, I have watched less than ideal open source management push away really talented developers and result in unproductive fork wars. So it is not personal. > If

Re: Re: Re: Re: Ticket spam

And to clarify regarding Trac in particular: that's not really a Django issue, it's a server maintenance issue. "We're working on it" means "the guys whose desks are within shouting distance of the server are working on it", not "the Django team is working on it". -- "May the forces of evil bec

Re: Re: Re: Ticket spam

On 11/3/06, iain duncan <[EMAIL PROTECTED]> wrote: > Therefore, we public readers > can only assume there must be a fair bit of dev related communication > going on *off* list. This is totally understandable given that the core > developers are all at the same company. I can see the point, certai

Re: Re: Ticket spam

On Fri, 2006-03-11 at 21:01 -0600, James Bennett wrote: > On 11/3/06, Ilia Kantor <[EMAIL PROTECTED]> wrote: > > I can't write anything too. Akismet is a great tool against developers. > > Thanks. > > It's being worked on. Patience is appreciated. This seems a good time to make a point related t

Re: Re: Ticket spam

On 11/3/06, Ilia Kantor <[EMAIL PROTECTED]> wrote: > I can't write anything too. Akismet is a great tool against developers. > Thanks. It's being worked on. Patience is appreciated. -- "May the forces of evil become confused on the way to your house." -- George Carlin --~--~-~--~

Re: Ticket spam

I can't write anything too. Akismet is a great tool against developers. Thanks. > Akismet is bugging me again... that's the third time that week I can't > submit a comment to a ticket due to akismet not liking me could > you whitelist telenieko at telenieko dot com so I can press the submit

Re: Ticket spam

Akismet is bugging me again... that's the third time that week I can't submit a comment to a ticket due to akismet not liking me could you whitelist telenieko at telenieko dot com so I can press the submit button again? Thanks in advance! And the akismet thing should be really looked at it re

Re: Ticket spam

On 11/3/06, Jeremy Dunck <[EMAIL PROTECTED]> wrote: > > On 11/3/06, Robin Munn <[EMAIL PROTECTED]> wrote: > > > > http://code.djangoproject.com/ticket/107 just got comment spammed. > > And, ironically, akismet is rejecting my attempts to clean it up. :-) > > > > I fixed the fields on it, though I

Re: Ticket spam

On 11/2/06, Christopher Lenz <[EMAIL PROTECTED]> wrote: ... > Continuing the monologue... See: > > I, for one, am happy to see your efforts. --~--~-~--~~~---~--~~ You received this message because you a

Re: Ticket spam

On 11/3/06, Robin Munn <[EMAIL PROTECTED]> wrote: > > http://code.djangoproject.com/ticket/107 just got comment spammed. > And, ironically, akismet is rejecting my attempts to clean it up. :-) > I fixed the fields on it, though I can't remove the spammy comment itself. --~--~-~--~~--

Re: Ticket spam

http://code.djangoproject.com/ticket/107 just got comment spammed. And, ironically, akismet is rejecting my attempts to clean it up. :-) Here's what got changed: #107: Pouroilontroubledwaters -+-- Reporter: Manuzhai <[EMAI

Re: Ticket spam

Am 27.10.2006 um 00:35 schrieb Christopher Lenz: > FYI: Akismet has been having a really high rate of false positive > lately, we've seen the same problems with it at trac.edgewall.org. > I've filed a support request but haven't heard back. > > Anyway, this whole issue has provoked me to completel

Re: Ticket spam

Am 25.10.2006 um 17:22 schrieb Christopher Lenz: > Am 25.10.2006 um 11:24 schrieb Michael Radziej: >> Adrian Holovaty schrieb: Also, I've been mulling over the idea of requiring an account signup >>> in order to post tickets and comments. Would that be worth the pain? >> >> I wouldn't

Re: Ticket spam

On 10/24/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > Also, I've been mulling over the idea of requiring an account signup > in order to post tickets and comments. Would that be worth the pain? I'm +1 on requiring an account signup; it's irritating to make wiki edits and append to tickets on

Re: Ticket spam

let me add the Akismet is not a solution, it looks like it has become part of the problem. It doesn't keep the spam out to a degree that could be ignored, but now it keeps me from opening tickets (yes, I sent the mail to Tom after digging through my email archive for his address--the whitelist

Re: Ticket spam

Matthew Flanagan wrote: > In one project I know of that uses trac they just have a single login > for users to create tickets and submit patches rather than requiring > every user to register. This eliminated 99% of their trac spam. They > just documented the login/password in their 'contributing

Re: Ticket spam

Am 25.10.2006 um 11:24 schrieb Michael Radziej: > Adrian Holovaty schrieb: >>> Also, I've been mulling over the idea of requiring an account signup >> in order to post tickets and comments. Would that be worth the pain? > > I wouldn't mind to have to sign up before I could submit a > ticket, but i

Re: Ticket spam

Adrian Holovaty schrieb: >> Also, I've been mulling over the idea of requiring an account signup > in order to post tickets and comments. Would that be worth the pain? I wouldn't mind to have to sign up before I could submit a ticket, but it seems there's no automatic sign-up in trac. That woul

Re: Re: Ticket spam

Hi Adrian, On 25/10/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > > On 10/24/06, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: > > It appears that some little inbred turd has decided that the ticket > > submission page is a great place to drop their little nuggets of > > spammy goodness, and

Re: Ticket spam

On 10/25/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > > On 10/24/06, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: > I've been going through and mercilessly deleting all spam tickets and > comments, using a script I wrote that reverts changes. (I submitted it > to Trac's Trac here: http://tra

Re: Ticket spam

On 10/24/06, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: > It appears that some little inbred turd has decided that the ticket > submission page is a great place to drop their little nuggets of > spammy goodness, and as far as I can make out Askimet isn't blocking > them. > > Is there anything