Re: Redesign of djangoproject.com?

2012-05-01 Thread Buddy Lindsey, Jr. 
um, not sure what happened to part of my response, but to summarize a 
missing paragraph I would like the design to consider showing more of 
the community as well.


Buddy Lindsey, Jr. wrote:


Russell Keith-Magee wrote:



* One of my personal goals for this redesign is to give more
visibility to community resources. Over the last 6 years, we've had a
number of unofficial projects come and done great service for the
community -- django people, several packaging indices, and so on.
However, many of these projects have died on the vine. I suspect one
of the reasons that these projects has died is that they've never
really been considered first class members of the community, and so
it's mentally easy to abandon them rather than seeking to hand them
off to a new maintainer. The only place I can see in Giovanni's
design for this sort of community content would be to bury it in the
footer, or on a separate part of the community page.




I came to Django from the Rails community and while I prefer Django
over Rails one thing I was disappointed with on arrival was I didn't
know "where" the Django community was, still not sure I do. Maybe the
django community is quiter than the Rails community is, but if I
didn't actively scour the internet I would think the community is dead
which is one of my evaluations of using a technology.

my 2 cents on the community aspect.

--
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@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.


--
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@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Redesign of djangoproject.com?

2012-05-01 Thread Buddy Lindsey, Jr. 

Russell Keith-Magee wrote:


* One of my personal goals for this redesign is to give more 
visibility to community resources. Over the last 6 years, we've had a 
number of unofficial projects come and done great service for the 
community -- django people, several packaging indices, and so on. 
However, many of these projects have died on the vine. I suspect one 
of the reasons that these projects has died is that they've never 
really been considered first class members of the community, and so 
it's mentally easy to abandon them rather than seeking to hand them 
off to a new maintainer. The only place I can see in Giovanni's design 
for this sort of community content would be to bury it in the footer, 
or on a separate part of the community page.



I came to Django from the Rails community and while I prefer Django over 
Rails one thing I was disappointed with on arrival was I didn't know 
"where" the Django community was, still not sure I do. Maybe the django 
community is quiter than the Rails community is, but if I didn't 
actively scour the internet I would think the community is dead which is 
one of my evaluations of using a technology.


my 2 cents on the community aspect.

--
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@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Redesign of djangoproject.com?

2012-05-01 Thread Dana Woodman 
People weren't proposing finished designs Daniel, they're mockups/wireframes. 
The first focus here is getting the IA right and then making it "sexy". 

I for one think that canned designs are not the way to go for a project such as 
Django. One of the goals with the redesign of the site is to showcase how the 
Django community values design in addition to development and choosing a pre 
made design doesn't serve those ends IMO. 

On the flip side, there's nothin wrong with borrowing (read stealing) good 
ideas from other designs. That's what art is anyways ;)

Just my $.02. 

On May 1, 2012, at 5:14 PM, "Daniel Sokolowski" 
 wrote:

> Being realistic here we must acknowledge that likely the majority of us are 
> great programmers but not great designers – none of the design proposed did 
> it for me – they were not bad but they weren’t great, and I want epic, I want 
> sexy and I want eye candy. 
>  
> So I say this: it is no shame to use a pre-existing, pre-made  template.
>  
> I have used http://themeforest.net/?ref=danols successfully in the past - yes 
> it includes my referral link - an added benefit is we can get through the 
> mock up and conversion phases very quickly. Some designs that caught my eye 
> --- please note these are fluid designs hence table and smartphone ready, 
> resize your browser window to see what I mean.
>  
> http://themeforest.net/item/spectrum-responsive-business-site-template/full_screen_preview/2035034
> http://themeforest.net/item/doctype-claquette-responsive-video-html-template/full_screen_preview/2085780
> http://themeforest.net/item/valera-responsive-html-template/full_screen_preview/2194402
>  
>  
>  
> However
> From: Dana Woodman
> Sent: Saturday, April 28, 2012 3:22 AM
> To: django-developers@googlegroups.com
> Subject: Redesign of djangoproject.com?
>  
> So now that Django is being moved to Git/Github (which is awesome!), maybe it 
> would be a good time to think about a revamped home page for the project ala 
> djangoproject.com?
>  
> Obviously this is no small undertaking and would be potentially contentions 
> as to what would be the proper path, but I feel (and I don't think I'm alone) 
>  that djangoproject.com could use a bit of a facelift. 
>  
> I have some idea of my own as to how this could be accomplished and I'm sure 
> there are a ton of others out there with great ideas as well. Maybe we could 
> open up some discussion on this idea?
>  
> Forgive me if this has been proposed before as I'm new to the group!
>  
> Cheers,
> Dana
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django developers" group.
> To view this discussion on the web visit 
> https://groups.google.com/d/msg/django-developers/-/g8ngEnVG_EsJ.
> To post to this group, send email to django-developers@googlegroups.com.
> To unsubscribe from this group, send email to 
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/django-developers?hl=en.
> Daniel Sokolowski
> Web Engineer
> Danols Web Engineering
> http://webdesign.danols.com/
> -- 
> 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@googlegroups.com.
> To unsubscribe from this group, send email to 
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/django-developers?hl=en.

-- 
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@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: startproject template context

2012-05-01 Thread Ramiro Morales 
On Tue, May 1, 2012 at 11:04 AM, Sam Simmons  wrote:
> For app/project templates I found the docs a little misleading when they say
> 'Any option passed to the startapp command' will be added to the context.

You' ve understood the documentation correctly. This is a feature that is
currently (and AFAICT was DOA) not fully implemented because there is code to
process and add the custom command line switches to the context but the
validation that the management commands framework performs on the command line
options isn't allowing them to pass.

Please open a ticket in our issue tracker.

Thanks.

-- 
Ramiro Morales

-- 
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@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: timezone.override() doesn't play well with template response views, by default

2012-05-01 Thread Aymeric Augustin 
On 1 mai 2012, at 19:28, Yo-Yo Ma wrote:

>  This is because the context manager returns control after dispatch is called,
> but the lazy response isn't rendered to a string until later on

Hello,

This behavior isn't specific to `timezone.override`. It would also happen with 
other context managers such as `translation.override`.

It's a consequence of using `TemplateResponse`, whose goal is precisely to 
postpone rendering until the response middleware have run.

To set the timezone globally, the docs recommend using 
`timezone.activate/deactivate` in a middleware (as in `LocaleMiddleware`).

Best regards,

-- 
Aymeric.

-- 
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@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: GitHub migration done!

2012-05-01 Thread Donald Stufft 
Pretty sure this isn't going to make a compatible with the existing mirror 
mirror but http://hg-git.github.com/ should make it easy to go from git -> hg.


On Tuesday, May 1, 2012 at 12:39 PM, Carl Meyer wrote:

> On 05/01/2012 12:45 AM, Vinay Sajip wrote:
> > On May 1, 2:19 am, Carl Meyer wrote:
> > > Good point. I think which of those happens now depends on whether a
> > > motivated someone steps up to figure out how to convert the mirror to
> > > use hg-git and source from Git, and then maintain it as needed. I
> > > originally did the current mirror, and it really hasn't needed any
> > > maintenance over the past two years, but I no longer use Mercurial or
> > > the Mercurial Django mirror, so that "motivated someone" is not likely
> > > to be me this time around.
> > > 
> > 
> > 
> > I don't mind doing it, if it's sufficiently low-maintenance,
> 
> I can't speak for how it will be with hg-git (there is a bit more 
> potential complexity since the source repo is not simple and linear like 
> Subversion), but hgsubversion has required exactly zero maintenance 
> since I first set it up.
> 
> > and I do
> > use Mercurial as well as Git. Did you implement it using a local repo
> > and a cron job, or was there something else you used which was more
> > purpose-built?
> > 
> 
> 
> It's just a cron job and a local repo using hgsubversion; every five 
> minutes it pulls the latest from Subversion and pushes it to Bitbucket. 
> The repo and cron job are hosted on the djangoproject.com 
> (http://djangoproject.com) server. If you 
> are able to get the conversion from git working and repeatable on a 
> local repo, I think Jacob can probably get you hooked up to host it on 
> djangoproject.com (http://djangoproject.com) (which also has an ssh key with 
> permission to push to 
> bitbucket.org/django/django (http://bitbucket.org/django/django)).
> 
> The tricky bit will be making the switch to sourcing from git in a way 
> that doesn't change all the historical commit hashes, making the new 
> mirror repo merge-incompatible with the current mirror (and all clones 
> of it). It's possible there will be no way to do that, in which case I 
> guess a new incompatible mirror is still better than no mirror at all.
> 
> Carl
> 
> -- 
> 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@googlegroups.com 
> (mailto:django-developers@googlegroups.com).
> To unsubscribe from this group, send email to 
> django-developers+unsubscr...@googlegroups.com 
> (mailto:django-developers+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/django-developers?hl=en.
> 
> 


-- 
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@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: GitHub migration done!

2012-05-01 Thread Carl Meyer 

On 05/01/2012 12:45 AM, Vinay Sajip wrote:

On May 1, 2:19 am, Carl Meyer  wrote:

Good point. I think which of those happens now depends on whether a
motivated someone steps up to figure out how to convert the mirror to
use hg-git and source from Git, and then maintain it as needed. I
originally did the current mirror, and it really hasn't needed any
maintenance over the past two years, but I no longer use Mercurial or
the Mercurial Django mirror, so that "motivated someone" is not likely
to be me this time around.


I don't mind doing it, if it's sufficiently low-maintenance,


I can't speak for how it will be with hg-git (there is a bit more 
potential complexity since the source repo is not simple and linear like 
Subversion), but hgsubversion has required exactly zero maintenance 
since I first set it up.



and I do
use Mercurial as well as Git. Did you implement it using a local repo
and a cron job, or was there something else you used which was more
purpose-built?


It's just a cron job and a local repo using hgsubversion; every five 
minutes it pulls the latest from Subversion and pushes it to Bitbucket. 
The repo and cron job are hosted on the djangoproject.com server. If you 
are able to get the conversion from git working and repeatable on a 
local repo, I think Jacob can probably get you hooked up to host it on 
djangoproject.com (which also has an ssh key with permission to push to 
bitbucket.org/django/django).


The tricky bit will be making the switch to sourcing from git in a way 
that doesn't change all the historical commit hashes, making the new 
mirror repo merge-incompatible with the current mirror (and all clones 
of it). It's possible there will be no way to do that, in which case I 
guess a new incompatible mirror is still better than no mirror at all.


Carl

--
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@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: GitHub migration done!

2012-05-01 Thread Carsten Fuchs 
Hi all,

On Saturday, April 28, 2012 5:08:09 AM UTC+2, Adrian Holovaty wrote:
>
> On Fri, Apr 27, 2012 at 11:50 AM, Adrian Holovaty wrote: 
> > We're going to do the migration to GitHub today. This means we'll no 
> > longer be committing code to our Subversion repository. Committers, 
> > please hold off on making commits until the migration is done. 
>
> OK, it's live! 
> https://github.com/django/django 
>

Excellent job, thank you very much!

Please forgive me a side question though:
Why didn't you convert the feature branches when converting the repository 
from SVN to Git as well?
I'm asking this mainly because I'm relatively new to Git, and wonder how 
exactly do you plan to convert the branches (especially the long merged 
ones) at a later time? Wouldn't this unconditionally change the hashes of 
all commits subsequent to the merge (and thus be self-forbidding on a 
public repository? which in turn makes later adding of merged branches 
impossible?)

A thousand thanks to you all from a happy Django user!
Carsten

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-developers/-/FvyJOQOt5r8J.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Redesign of djangoproject.com?

2012-05-01 Thread Ivan Ivanov 
На Sun, 29 Apr 2012 14:33:33 -0700
Dana Woodman  написа:

> Giovanni and I have touched base about collaborating on the design.
> We'll update as we go. 

Hi all!

I have not enough time for participating on developement right now, but
I could be helpful with testing and (when needed) fixing issues, so when
you make a repo, please let us know, so I can follow the project.

Thanks for the grate job in advance!

Ivan

-- 
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@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: GitHub migration done!

2012-05-01 Thread Vinay Sajip 

On May 1, 2:19 am, Carl Meyer  wrote:
>
> Good point. I think which of those happens now depends on whether a
> motivated someone steps up to figure out how to convert the mirror to
> use hg-git and source from Git, and then maintain it as needed. I
> originally did the current mirror, and it really hasn't needed any
> maintenance over the past two years, but I no longer use Mercurial or
> the Mercurial Django mirror, so that "motivated someone" is not likely
> to be me this time around.

I don't mind doing it, if it's sufficiently low-maintenance, and I do
use Mercurial as well as Git. Did you implement it using a local repo
and a cron job, or was there something else you used which was more
purpose-built?

Regards,

Vinay Sajip

-- 
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@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.