On Sat, Apr 24, 2010 at 2:34 AM, Jeremy Dunck wrote:
> On Fri, Apr 23, 2010 at 11:32 AM, Russell Keith-Magee
> wrote:
> Frequent contributors are not the only audience for this tool -- I'm
> trying to help answer the question -- where is help most needed right
> now?
>
> With that perspective, d
On Fri, Apr 23, 2010 at 11:32 AM, Russell Keith-Magee
wrote:
>> Can a DB dump be shared?
>
> I don't have any problem sharing the raw ticket data. However, I'm not
> sure if there's anything else in the database (like emails and
> passwords/hashes) that we would want to strip out before sharing.
>
On Fri, Apr 23, 2010 at 11:32 AM, Russell Keith-Magee
wrote:
...
> 2: Would be useful as a work list for people looking for. It would
> also be useful if tickets could be auto-disowned; i.e., if there's no
> activity from the owner after a month, post a comment asking for a
> status update; if no
On Fri, Apr 23, 2010 at 3:04 PM, Jeremy Dunck wrote:
> Commiters and triagers,
> I've gone through the contributing doc and tried to identify places
> that tickets might get stuck (or other places that automation might
> smooth the process).
> If you could take a few minutes to give feedback on
Kevin Howerton wrote:
> The widget and admin media system needs to be re-evaluated IMO
> none of these solutions are going to address the flaws you are
> referring to.
>
"Flaws", sounds a bit harsh :P Let's alias that as "room for improvement".
I'd agree that wrangling hashes and compressin
Hi Jeremy,
And what about information on the page if the patch commits cleanly,
and if all tests pass after applying patch?
Not just sending email to the patch author, but making it visible to everyone.
On Fri, Apr 23, 2010 at 10:04 AM, Jeremy Dunck wrote:
> Commiters and triagers,
> I've gone
The thing is, quoted get variables will get unquoted, quoted url
parameters won't be unquoted automatically. That's up to the developer
to handle.
Ran into the same issue today, and for me it made sense to do the
quoting before passing it to the reverse function, but for me it was
an URL which was
On Fri, Apr 23, 2010 at 8:38 AM, JohnHenry wrote:
> Hi, all
> As I know, Django Templates got all variables through views
> function with Context dict; But I read some source, There is some
> variables like {{SITE_ROOT}} {{MEDIA_URL}} {{MEDIA_SERIAL}}
> {{request}} {{ user }} {{siteconfig}} ;
django-developers is for the discussion of the development of Django
itself, not development with Django.
As such this mailing list is not appropriate for this message,
django-users would be more appropriate.
However you should take a look at template context processor[1]
[1]: http://docs.djangop
Hi, all
As I know, Django Templates got all variables through views
function with Context dict; But I read some source, There is some
variables like {{SITE_ROOT}} {{MEDIA_URL}} {{MEDIA_SERIAL}}
{{request}} {{ user }} {{siteconfig}} ; Such variables seems globlly
usable; But I can't find any C
Commiters and triagers,
I've gone through the contributing doc and tried to identify places
that tickets might get stuck (or other places that automation might
smooth the process).
If you could take a few minutes to give feedback on the list,
hopefully prioritizing in your named column with +/-
11 matches
Mail list logo
