Re: GitHub migration done!

[Aymeric Augustin]

On 28 avr. 2012, at 05:08, Adrian Holovaty wrote:

> * We're going to keep using Trac for tickets, but pull requests on
> GitHub are also welcome.

Hi everyone,

For extra safety, I recommend you still create Trac tickets for each suggested 
change, until we work out how pull requests integrate into the triage workflow.

Thanks,

-- 
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!

[Dana Woodman]

Congrats Adrian, this is very exciting news! I'm excited to see Django 
taking the next leap forward, exciting times ahead! Cheers!

-- 
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/-/2Y5IENlucmQJ.
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.

Redesign of djangoproject.com?

[Dana Woodman]

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.

Re: Redesign of djangoproject.com?

[Russell Keith-Magee]

Hi Dana,

I completely agree. I've been trying to get a redesign of djangoproject.com 
going for quite some time under the auspices of the Django Foundation. As you 
can see from the lack of changes, you can see that I haven't been particularly 
successful :-(

The fundamental problem is that we have plenty of coding talent at our 
disposal, but not as much design talent. That's not to say that there aren't 
many talented designers in our community -- there are -- it's just that they're 
all very busy. We've approached several people in the Django design community 
asking them to help out, and some have even made done some initial work. 
However, redesign of a high-profile site like djangoproject.com is a big job, 
and nobody has been able to spare the time to bring the job to completion.

So - at this point I'm open to any offers. I want to avoid design by committee 
-- ideally, I would like to pass this off to a single person (or a small group) 
and give them complete control over design process. I'm not completely sure how 
to organise who gets this role -- suggestions are welcome.

If you (or anyone else) is interested, drop me a line and I can give you the 
design brief we've been working with.

Yours,
Russ Magee %-)



On Saturday, 28 April 2012 at 3:22 PM, Dana Woodman wrote:

> 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 (http://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 (http://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 
> (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: Redesign of djangoproject.com?

[Dana Woodman]

Great to know they're is some interest in it and agreement that it is in need :)

I'm very interested in the prospect of redesigning the site and would love to 
chat more about it. I feel like I owe the Django community something for all 
that it has given me (including the job I currently have!). I'd love to talk 
scope and other factors so I have a clear idea of what would be involved. 

Is this a good forum for this type of discussion or should we get in touch 
elsewhere to talk? You can get in touch with me here: http://danawoodman.com/ 

--
Dana Woodman
d...@danawoodman.com (mailto:d...@danawoodman.com)
http://www.danawoodman.com


On Saturday, April 28, 2012 at 1:05 AM, Russell Keith-Magee wrote:

> Hi Dana,
> 
> I completely agree. I've been trying to get a redesign of djangoproject.com 
> (http://djangoproject.com) going for quite some time under the auspices of 
> the Django Foundation. As you can see from the lack of changes, you can see 
> that I haven't been particularly successful :-(
> 
> The fundamental problem is that we have plenty of coding talent at our 
> disposal, but not as much design talent. That's not to say that there aren't 
> many talented designers in our community -- there are -- it's just that 
> they're all very busy. We've approached several people in the Django design 
> community asking them to help out, and some have even made done some initial 
> work. However, redesign of a high-profile site like djangoproject.com 
> (http://djangoproject.com) is a big job, and nobody has been able to spare 
> the time to bring the job to completion.
> 
> So - at this point I'm open to any offers. I want to avoid design by 
> committee -- ideally, I would like to pass this off to a single person (or a 
> small group) and give them complete control over design process. I'm not 
> completely sure how to organise who gets this role -- suggestions are welcome.
> 
> If you (or anyone else) is interested, drop me a line and I can give you the 
> design brief we've been working with.
> 
> Yours,
> Russ Magee %-)
> 
> 
> 
> On Saturday, 28 April 2012 at 3:22 PM, Dana Woodman wrote:
> 
> > 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 (http://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 (http://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 
> > (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 
> (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!

[Camilo Nova]

Great Job. This will make easier for a lot of people to be involved on the 
project.

On Friday, April 27, 2012 10:08:09 PM UTC-5, 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 
>
> A few quick points (though this definitely deserves a more in-depth 
> writeup): 
>
> * I renamed the old (mirror) repository to 
> https://github.com/django/django-old. We had talked about deleting it 
> outright to avoid confusion, but I realized at the last minute that 
> doing so would have deleted all the pull requests. I didn't want to 
> throw all of that out, and I think we can figure out a way to use 
> those pull requests in the new repository. 
>
> * I only migrated trunk (now called "master"), rather than including 
> all of the branches. This was the result of a bunch of discussion on 
> IRC with Brian R., et al. The thinking is that it kept the migration a 
> lot cleaner/simpler, and we can always add branches later. Of course, 
> we'll need to create the latest release branches. Otherwise, we can 
> consider the SVN branches on an individual basis. 
>
> * As expected, all forks of the old repository are now broken. Can 
> somebody volunteer to write some documentation on how to upgrade your 
> old fork to use the new upstream repo (rebase? simple patch?)? 
>
> * We're going to keep the Subversion repository around indefinitely, 
> but it'll no longer be updated. 
>
> * We're going to keep using Trac for tickets, but pull requests on 
> GitHub are also welcome. 
>
> * Clearly there are lots of bits of process that need to be updated 
> now, from the django-updates mailing list to our "contributing" 
> documentation, etc. We'll take care of all of that in the coming days, 
> and we should all expect some degree of confusion and unsettlement in 
> the community. That's totally fine, and we'll get through it. :-) 
>
> * Finally, big thanks to the folks on IRC today who helped me through 
> the process and contributed good ideas. 
>
> I'm planning to write up a blog post on how the process went, for the 
> benefit of the five open-source projects still using Subversion. 
>
> Adrian 
>

-- 
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/-/3AYxf2T_uFgJ.
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!

[Vitaly Babiy]

Awesome job guys!

Vitaly Babiy



On Sat, Apr 28, 2012 at 9:07 AM, Camilo Nova  wrote:

> Great Job. This will make easier for a lot of people to be involved on the
> project.
>
>
> On Friday, April 27, 2012 10:08:09 PM UTC-5, 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 
>>
>> A few quick points (though this definitely deserves a more in-depth
>> writeup):
>>
>> * I renamed the old (mirror) repository to
>> https://github.com/django/**django-old.
>> We had talked about deleting it
>> outright to avoid confusion, but I realized at the last minute that
>> doing so would have deleted all the pull requests. I didn't want to
>> throw all of that out, and I think we can figure out a way to use
>> those pull requests in the new repository.
>>
>> * I only migrated trunk (now called "master"), rather than including
>> all of the branches. This was the result of a bunch of discussion on
>> IRC with Brian R., et al. The thinking is that it kept the migration a
>> lot cleaner/simpler, and we can always add branches later. Of course,
>> we'll need to create the latest release branches. Otherwise, we can
>> consider the SVN branches on an individual basis.
>>
>> * As expected, all forks of the old repository are now broken. Can
>> somebody volunteer to write some documentation on how to upgrade your
>> old fork to use the new upstream repo (rebase? simple patch?)?
>>
>> * We're going to keep the Subversion repository around indefinitely,
>> but it'll no longer be updated.
>>
>> * We're going to keep using Trac for tickets, but pull requests on
>> GitHub are also welcome.
>>
>> * Clearly there are lots of bits of process that need to be updated
>> now, from the django-updates mailing list to our "contributing"
>> documentation, etc. We'll take care of all of that in the coming days,
>> and we should all expect some degree of confusion and unsettlement in
>> the community. That's totally fine, and we'll get through it. :-)
>>
>> * Finally, big thanks to the folks on IRC today who helped me through
>> the process and contributed good ideas.
>>
>> I'm planning to write up a blog post on how the process went, for the
>> benefit of the five open-source projects still using Subversion.
>>
>> Adrian
>>
>  --
> 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/-/3AYxf2T_uFgJ.
>
> 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?

[Ned Batchelder]

Will there be any specific discussion about what's wrong with the 
current site?  You two seem to agree something needs to be done, but 
haven't mentioned anything specific.


--Ned.

On 4/28/2012 4:13 AM, Dana Woodman wrote:
Great to know they're is some interest in it and agreement that it is 
in need :)


I'm very interested in the prospect of redesigning the site and would 
love to chat more about it. I feel like I owe the Django community 
something for all that it has given me (including the job I currently 
have!). I'd love to talk scope and other factors so I have a clear 
idea of what would be involved.


Is this a good forum for this type of discussion or should we get in 
touch elsewhere to talk? You can get in touch with me here: 
http://danawoodman.com/


--
Dana Woodman
d...@danawoodman.com 
http://www.danawoodman.com

On Saturday, April 28, 2012 at 1:05 AM, Russell Keith-Magee wrote:


Hi Dana,

I completely agree. I've been trying to get a redesign of 
djangoproject.com  going for quite some 
time under the auspices of the Django Foundation. As you can see from 
the lack of changes, you can see that I haven't been particularly 
successful :-(


The fundamental problem is that we have plenty of coding talent at 
our disposal, but not as much design talent. That's not to say that 
there aren't many talented designers in our community -- there are -- 
it's just that they're all very busy. We've approached several people 
in the Django design community asking them to help out, and some have 
even made done some initial work. However, redesign of a high-profile 
site like djangoproject.com  is a big job, 
and nobody has been able to spare the time to bring the job to 
completion.


So - at this point I'm open to any offers. I want to avoid design by 
committee -- ideally, I would like to pass this off to a single 
person (or a small group) and give them complete control over design 
process. I'm not completely sure how to organise who gets this role 
-- suggestions are welcome.


If you (or anyone else) is interested, drop me a line and I can give 
you the design brief we've been working with.


Yours,
Russ Magee %-)



On Saturday, 28 April 2012 at 3:22 PM, Dana Woodman wrote:

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 (http://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 
(http://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 
(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.


--
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?

[Alec Taylor]

I can throw in some UX designing if you want

On Sat, Apr 28, 2012 at 11:53 PM, Ned Batchelder  wrote:
> Will there be any specific discussion about what's wrong with the current
> site?  You two seem to agree something needs to be done, but haven't
> mentioned anything specific.
>
> --Ned.
>
>
> On 4/28/2012 4:13 AM, Dana Woodman wrote:
>
> Great to know they're is some interest in it and agreement that it is in
> need :)
>
> I'm very interested in the prospect of redesigning the site and would love
> to chat more about it. I feel like I owe the Django community something for
> all that it has given me (including the job I currently have!). I'd love to
> talk scope and other factors so I have a clear idea of what would be
> involved.
>
> Is this a good forum for this type of discussion or should we get in touch
> elsewhere to talk? You can get in touch with me
> here: http://danawoodman.com/
>
> --
> Dana Woodman
> d...@danawoodman.com
> http://www.danawoodman.com
>
> On Saturday, April 28, 2012 at 1:05 AM, Russell Keith-Magee wrote:
>
> Hi Dana,
>
> I completely agree. I've been trying to get a redesign of djangoproject.com
> going for quite some time under the auspices of the Django Foundation. As
> you can see from the lack of changes, you can see that I haven't been
> particularly successful :-(
>
> The fundamental problem is that we have plenty of coding talent at our
> disposal, but not as much design talent. That's not to say that there aren't
> many talented designers in our community -- there are -- it's just that
> they're all very busy. We've approached several people in the Django design
> community asking them to help out, and some have even made done some initial
> work. However, redesign of a high-profile site like djangoproject.com is a
> big job, and nobody has been able to spare the time to bring the job to
> completion.
>
> So - at this point I'm open to any offers. I want to avoid design by
> committee -- ideally, I would like to pass this off to a single person (or a
> small group) and give them complete control over design process. I'm not
> completely sure how to organise who gets this role -- suggestions are
> welcome.
>
> If you (or anyone else) is interested, drop me a line and I can give you the
> design brief we've been working with.
>
> Yours,
> Russ Magee %-)
>
>
>
> On Saturday, 28 April 2012 at 3:22 PM, Dana Woodman wrote:
>
> 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 (http://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 (http://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
> (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.
>
>
> --
> 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.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" 

Re: GitHub migration done!

[slav0nic]

what about "Browse Source", trac links to changset, CommitTicketUpdater ?
Maybe this will be possible only if you syncing github to local copy via 
pulling.

-- 
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/-/Iw7p_8dmgvAJ.
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?

[Chris Pickett]

It seems to me that this might be one of those opportunities to just jump 
right in and get your hands dirty. I many ways I don't know if a redesign 
is going to happen without someone taking the initiative and getting it 
done, so it might as well be you! :)

On Saturday, April 28, 2012 2:22:59 AM UTC-5, Dana Woodman wrote:
>
> 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/-/sWZOWG-NqmgJ.
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!

[Sean Lee]

Great job!

在 2012年4月28日星期六UTC+8上午11时08分09秒，Adrian Holovaty写道：
>
> 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 
>
> A few quick points (though this definitely deserves a more in-depth 
> writeup): 
>
> * I renamed the old (mirror) repository to 
> https://github.com/django/django-old. We had talked about deleting it 
> outright to avoid confusion, but I realized at the last minute that 
> doing so would have deleted all the pull requests. I didn't want to 
> throw all of that out, and I think we can figure out a way to use 
> those pull requests in the new repository. 
>
> * I only migrated trunk (now called "master"), rather than including 
> all of the branches. This was the result of a bunch of discussion on 
> IRC with Brian R., et al. The thinking is that it kept the migration a 
> lot cleaner/simpler, and we can always add branches later. Of course, 
> we'll need to create the latest release branches. Otherwise, we can 
> consider the SVN branches on an individual basis. 
>
> * As expected, all forks of the old repository are now broken. Can 
> somebody volunteer to write some documentation on how to upgrade your 
> old fork to use the new upstream repo (rebase? simple patch?)? 
>
> * We're going to keep the Subversion repository around indefinitely, 
> but it'll no longer be updated. 
>
> * We're going to keep using Trac for tickets, but pull requests on 
> GitHub are also welcome. 
>
> * Clearly there are lots of bits of process that need to be updated 
> now, from the django-updates mailing list to our "contributing" 
> documentation, etc. We'll take care of all of that in the coming days, 
> and we should all expect some degree of confusion and unsettlement in 
> the community. That's totally fine, and we'll get through it. :-) 
>
> * Finally, big thanks to the folks on IRC today who helped me through 
> the process and contributed good ideas. 
>
> I'm planning to write up a blog post on how the process went, for the 
> benefit of the five open-source projects still using Subversion. 
>
> Adrian 
>

-- 
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/-/9CyF3ab4Ya4J.
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!

[Mateusz Harasymczuk]

On Saturday, April 28, 2012 5:08:09 AM UTC+2, Adrian Holovaty wrote:
>
> OK, it's live! 
> https://github.com/django/django 
>

Great news!

Therefore probably you should update this site:
https://www.djangoproject.com/download/ 

-- 
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/-/VbYNgiYgClwJ.
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: More on Customizable Serialization

[Tom Christie]

> If you've got the time and enthusiasm, I'd certainly appreciate you 
hanging around in a "co-mentor"-like capacity.

Sure, I'd be more than happy to help out wherever possible.
Piotr, if you need to get in touch with me off-list for any reason please 
feel free to do so - t...@tomchristie.com

  - Tom

On Saturday, 28 April 2012 04:05:17 UTC+1, Russell Keith-Magee wrote:
>
> Hi Tom, 
>
> On Friday, 27 April 2012 at 12:44 PM, Tom Christie wrote: 
> > Seeing another proposal for Customizable Serialization for the GSoC this 
> year 
> > prompted me to dust off the bits of work I've done along similar lines. 
> > I'd really like to see this get properly addressed in core and I thought 
> it 
> > was about time I helped to make it happen. 
> > 
> > I've made a fairly comprehensive start, and pushed the results of what I 
> have 
> > to date as the `django-serializers` project. It's available on PyPI, and 
> the 
> > source is here: 
> > http://github.com/tomchristie/django-serializers 
> > 
> > There are some docs up on the GitHub site, but in brief it gives you: 
> > 
> > * A Declarative Serializer/Field API that mirrors the Form/Field API. 
> > * A Serializer class which can deal with arbitrary python objects. 
> > * A ModelSerializer class which can handle model instances and query 
> sets. 
> > * A DumpDataSerializer class which mimics the existing dumpdata 
> behaviour. 
> > * Supports flat or nested ouput, and deals with recursive structures. 
> > * Handles FK, M2M, OneToOne, and reverse relationships, model fields, 
> and non-database attributes/properties. 
> > * Serialization structure decoupled from output encoding concerns. 
> > * Currently supports JSON, YAML, and XML. 
> > * Decent test suite of the above. 
> > 
> > It's not yet at the point where it could be a proposal for core - Right 
> now the 
> > API isn't backwards compatible with the existing serializers, the dump 
> > data serializer is still missing some tweaks such as dealing with 
> natural keys, 
> > and there's some work to do on the XML output. It is a pretty 
> comprehensive 
> > start though, and I'm really happy with the shape of the API. 
>
> Thanks for letting us know about the prior art -- I know we discussed 
> serialisation at DjangoCon last year, and I'm kicking myself that I didn't 
> provide more feedback at the time. Hopefully having this as a GSoC project 
> will be enough to kick me into action and bring this project to completion. 
> > 
> > Given that Piotr's GSoC proposal has now been accepted, I'm wondering 
> what the 
> > right way forward is? I'd like to continue to push forward with this, 
> but I'm 
> > also aware that it might be a bit of an issue if there's already an 
> ongoing 
> > GSoC project along the same lines? 
> > 
> > Having taken a good look through the GSoC proposal, it looks good, and 
> there 
> > seems to be a fair bit of overlap, so hopefully he'll find what I've 
> done 
> > useful, and I'm sure I'll have plenty of comments on his project as it 
> > progresses. 
> > 
> > I'd consider suggesting a collaborative approach, but the rules of the 
> GSoC 
> > wouldn't allow that right? 
>
> Unfortunately, the GSoC rules don't allow for collaboration - the work 
> that is submitted needs to be that of the student alone. However, they do 
> allow for others to contribute by providing code reviews, design feedback, 
> and so on. Given that we're building a user-facing API, there's also plenty 
> of room to provide assistance by testing -- i.e., hunting down obscure 
> serialisation use cases, and making sure that the API we've got can cover 
> them. 
>
> If you've got the time and enthusiasm, I'd certainly appreciate you 
> hanging around in a "co-mentor"-like capacity. You've clearly spent a lot 
> of time thinking about on this problem, and I'm sure your input would be 
> extremely valuable. You're also in a slightly more helpful timezone for 
> Piotr, so if he needs some feedback when I'm not available, it would be 
> nice to have someone he can call on that is familiar with the problem and 
> his progress. 
>
> Yours, 
> Russ Magee %-) 
>
>   
>
>
>

-- 
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/-/kiJQ2dvvhlUJ.
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!

[Jacob Kaplan-Moss]

On Saturday, April 28, 2012 at 5:17 AM, slav0nic wrote:
> what about "Browse Source", trac links to changset, CommitTicketUpdater ?
> Maybe this will be possible only if you syncing github to local copy via 
> pulling.
Yup, I'm working on that. I didn't get it done yesterday, but didn't want to 
block the move. I'll get it done this weekend.

Jacob

-- 
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?

[Dana Woodman]

Very true Chris. I'd love to see the documents that were put together when this 
was discussed last time, if they're still around.

In regards to what  needs improvement, there are some core issues as I see it. 

1) the home page does a poor job of conveying what someone should do if they 
want to try out Django. It also could do a much better job of making Django a 
bit more "sexy". 
2) the documentation itself, while thorough, is a bit difficult to navigate, 
especially for new users. I think this could be partially remedied by some 
modifications to headers and color choices. 
3) the project could do a better job of selling itself, especially in regards 
to showcasing why it is so great: automatic admin, large active community and 
plugins, large sites and organizations using it, active development, lots of 
built in security, etc...
4) it just looks old and outdated, which is a problem in its own right. 

Should I just fork the project on Github and hack away or do I need to work on 
subversion?

In regards to organization of the documentation, I assume that is generated via 
the docs within Django, correct? Would I have freedom to do content 
organization/copy changes or would it just be a design change? I don't mean 
changing the documentation, but more how other pages and sections are laid out. 

I assume I'd also need to work on the code.djangoproject.org site as well? Are 
there other things that would need to change? I'd really need the scope down so 
I know how and where to start. 

This is no simple task so any direction or help would be greatly appreciated!

Cheers

On Apr 28, 2012, at 5:11 AM, Chris Pickett  wrote:

> It seems to me that this might be one of those opportunities to just jump 
> right in and get your hands dirty. I many ways I don't know if a redesign is 
> going to happen without someone taking the initiative and getting it done, so 
> it might as well be you! :)
> 
> On Saturday, April 28, 2012 2:22:59 AM UTC-5, Dana Woodman wrote:
> 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/-/sWZOWG-NqmgJ.
> 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: GitHub migration done!

[Mateusz Harasymczuk]

Could you make tags out of stable releases. It would help a lot :}

-- 
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/-/NzF2b8Xl9wUJ.
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!

[Cal Leeming [Simplicity Media Ltd]]

Amazing news!! Great job, Adrian.

Cal

On Sat, Apr 28, 2012 at 4:08 AM, 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
>
> A few quick points (though this definitely deserves a more in-depth
> writeup):
>
> * I renamed the old (mirror) repository to
> https://github.com/django/django-old. We had talked about deleting it
> outright to avoid confusion, but I realized at the last minute that
> doing so would have deleted all the pull requests. I didn't want to
> throw all of that out, and I think we can figure out a way to use
> those pull requests in the new repository.
>
> * I only migrated trunk (now called "master"), rather than including
> all of the branches. This was the result of a bunch of discussion on
> IRC with Brian R., et al. The thinking is that it kept the migration a
> lot cleaner/simpler, and we can always add branches later. Of course,
> we'll need to create the latest release branches. Otherwise, we can
> consider the SVN branches on an individual basis.
>
> * As expected, all forks of the old repository are now broken. Can
> somebody volunteer to write some documentation on how to upgrade your
> old fork to use the new upstream repo (rebase? simple patch?)?
>
> * We're going to keep the Subversion repository around indefinitely,
> but it'll no longer be updated.
>
> * We're going to keep using Trac for tickets, but pull requests on
> GitHub are also welcome.
>
> * Clearly there are lots of bits of process that need to be updated
> now, from the django-updates mailing list to our "contributing"
> documentation, etc. We'll take care of all of that in the coming days,
> and we should all expect some degree of confusion and unsettlement in
> the community. That's totally fine, and we'll get through it. :-)
>
> * Finally, big thanks to the folks on IRC today who helped me through
> the process and contributed good ideas.
>
> I'm planning to write up a blog post on how the process went, for the
> benefit of the five open-source projects still using Subversion.
>
> Adrian
>
> --
> 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.

Inconsistent humanize naturaltime (#18202)

[rikuthero...@gmail.com]

Hi folks,

I was about to start fixing ticket
#18202,
and I have a little doubt of how to focus that ticket. The workaround
proposed by "oradoe" seems good and works fine, but that will allow to show
only one level, like "10 minutes ago", "2 hours ago" or "4 months ago". As
it's propose on the ticket, maybe add some extra parameter to the filter to
allow that the user can specify how many deep levels he wants.

The problem there is that the filter uses
django.utils.timesince,
that actually only returns 2 levels as maximum. Should I change thoset
functions too? I think it won't be difficult to change it and maintain the
current behavior as the default one, but I would like to check it with you
before.

Cheers,

-- 
Pablo Recio Quijano

-- 
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!

[Yuval Adam]

I think this issue should be dealt with sooner rather than later.

Django will start getting lots of orphan pull requests with no
matching trac ticket, and a policy of how community members should
contribute via github should be in place.

As a side note, it is kind of a hassle to submit a pull request and
then go fill a new trac ticket.
For me, as a kind-of-involved user of Django, I simply won't go into
that burden.

On Apr 28, 10:03 am, Aymeric Augustin
 wrote:
> On 28 avr. 2012, at 05:08, Adrian Holovaty wrote:
>
> > * We're going to keep using Trac for tickets, but pull requests on
> > GitHub are also welcome.
>
> Hi everyone,
>
> For extra safety, I recommend you still create Trac tickets for each 
> suggested change, until we work out how pull requests integrate into the 
> triage workflow.
>
> Thanks,
>
> --
> 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: Django Admin Revamp - Any updates?

[Idan Gazit]

As I wrote, I'd like to have a clear idea of what a new admin will accomplish 
before starting to bolt on enhancements, even great enhancements like grappelli.

The admin was an impressively future-proof design, given that it is still so 
useful years after it was designed. We should aim to make an admin that will be 
relevant and useful five years from now; we can't design for that without a 
couple of clear, simple goals. Grappelli may or may not align with those goals.

-I 

On Saturday, April 28, 2012 at 12:55 AM, Daniel Sokolowski wrote:

> On that note, why can't the fruits of Grappelli be used as a starting point?
> 
> -Original Message- 
> From: h3
> Sent: Friday, April 27, 2012 4:01 PM
> To: Django developers
> Subject: Re: Django Admin Revamp - Any updates?
> 
> I don't know the status of this project, but my guess is that you
> shouldn't hold your breath for it.
> 
> Fortunately, there is Grappelli: 
> https://github.com/sehmaschine/django-grappelli
> 
> We are currently working on making it compatible with django 1.4 (see
> the "grappelli_2_4" branch)
> 
> Alternatively the branch on my fork works pretty well with 1.4:
> https://github.com/h3/django-grappelli/tree/grappelli_2_4
> 
> Cheers
> 
> On Apr 26, 7:06 pm, Victor Hooi http://gmail.com)> 
> wrote:
> > Hi,
> > 
> > Is there any news on the Django Admin rewrite front?
> > 
> > I remember around a year ago, there was quite a bit of talk on revamping
> > the Django admin UI - I think Idan Gazit was heading that, right?
> > 
> > Is that still on the Django roadmap? Any idea of whether it'll be in 1.5,
> > 1.6, 1.7 etc?
> > 
> > Cheers,
> > Victor
> > 
> 
> 
> 
> -- 
> 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.
> 
> 
> 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 
> (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!

[Aymeric Augustin]

On 28 avr. 2012, at 21:46, Yuval Adam wrote:

> I think this issue should be dealt with sooner rather than later.
> 
> Django will start getting lots of orphan pull requests with no
> matching trac ticket, and a policy of how community members should
> contribute via github should be in place.
> 
> As a side note, it is kind of a hassle to submit a pull request and
> then go fill a new trac ticket.
> For me, as a kind-of-involved user of Django, I simply won't go into
> that burden.

Hi Yuval,

The core team is actively discussing this question.

My previous recommendation isn't a final decision.

I hope we'll release more information soon.

Thanks for your patience,

-- 
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!

[Yuval Adam]

Hey Aymeric,

Just throwing in my 2 cents.
If there's a public thread I can follow re: this issue, I'd appreciate
a link, since I haven't been able to find it.
Waiting patiently :)

- Yuval

On Apr 29, 12:36 am, Aymeric Augustin
 wrote:
> On 28 avr. 2012, at 21:46, Yuval Adam wrote:
>
> > I think this issue should be dealt with sooner rather than later.
>
> > Django will start getting lots of orphan pull requests with no
> > matching trac ticket, and a policy of how community members should
> > contribute via github should be in place.
>
> > As a side note, it is kind of a hassle to submit a pull request and
> > then go fill a new trac ticket.
> > For me, as a kind-of-involved user of Django, I simply won't go into
> > that burden.
>
> Hi Yuval,
>
> The core team is actively discussing this question.
>
> My previous recommendation isn't a final decision.
>
> I hope we'll release more information soon.
>
> Thanks for your patience,
>
> --
> 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: Redesign of djangoproject.com?

[Russell Keith-Magee]

Hi Ned,

It occurs to me that the design brief we've been using actually does a pretty 
good job of answering your questions, and there aren't any big secrets in those 
plans, so I figure I might as well share it for all to see. 


djangoproject.com design brief: 

We're not looking for anything too radical. It's really just about bringing the 
site up to current industry best practice, and exposing some information that 
is hidden on the current site.

* We need a visual refresh, keeping the same basic Django green-based color 
scheme. The web design world has moved on a bit since 2005; Django's site 
should reflect those changes. We say we're a state-of-the-art framework, so our 
design should reflect that. This means good uses of font faces, adaptive 
layouts, and so on -- all the things that have emerged in the best of web 
design over the last couple of years.

* It has to maintain a professional image -- no ponies or anything like that.

* Provide better pathways for people visiting the site. The site now has 
multiple audiences, who will each be looking for different information:
 - First time technical users, looking for technical overviews and tutorials
 - Long term users looking for documentation,
 - Users wanting to get involved with contributing code/patches/documentation
 - Business users considering Django that need a non-technical case

The current site doesn't reflect this diverse audience very well, and doesn't 
provide a clear call to action/next step for most of these visitors

* Increase the visibility of the DSF -- which is to say, make the DSF visible 
at all. The biggest subtask in this is making our sponsors visible. We're not 
looking to splash advertising over the homepage, but we do need to provide a 
clear way to say thank you to our sponsors, and invite others to join them.

* Ability to keep a consistent design across code.djangoproject.com 
(http://code.djangoproject.com), docs.djangoproject.com 
(http://docs.djangoproject.com) and any other sites that we pull into the mix.

* Flexibility to add links out to other community resources as we add them -- 
for example, if we resurrect djangopeople.net (http://djangopeople.net), we 
would like to be able to link to them somewhere on the site. The current site 
design doesn't really provide an appropriate place to put this sort of linkage.



Yours,
Russ Magee %-)


On Saturday, 28 April 2012 at 9:53 PM, Ned Batchelder wrote:

> Will there be any specific discussion about what's wrong with the current 
> site? You two seem to agree something needs to be done, but haven't mentioned 
> anything specific. 
> 
> --Ned.
> 
> On 4/28/2012 4:13 AM, Dana Woodman wrote: 
> > Great to know they're is some interest in it and agreement that it is in 
> > need :) 
> > 
> > I'm very interested in the prospect of redesigning the site and would love 
> > to chat more about it. I feel like I owe the Django community something for 
> > all that it has given me (including the job I currently have!). I'd love to 
> > talk scope and other factors so I have a clear idea of what would be 
> > involved. 
> > 
> > Is this a good forum for this type of discussion or should we get in touch 
> > elsewhere to talk? You can get in touch with me here: 
> > http://danawoodman.com/ 
> > 
> > -- 
> > Dana Woodman
> > d...@danawoodman.com (mailto:d...@danawoodman.com)
> > http://www.danawoodman.com
> > 
> > 
> > On Saturday, April 28, 2012 at 1:05 AM, Russell Keith-Magee wrote:
> > 
> > > Hi Dana,
> > > 
> > > I completely agree. I've been trying to get a redesign of 
> > > djangoproject.com (http://djangoproject.com) going for quite some time 
> > > under the auspices of the Django Foundation. As you can see from the lack 
> > > of changes, you can see that I haven't been particularly successful :-( 
> > > 
> > > The fundamental problem is that we have plenty of coding talent at our 
> > > disposal, but not as much design talent. That's not to say that there 
> > > aren't many talented designers in our community -- there are -- it's just 
> > > that they're all very busy. We've approached several people in the Django 
> > > design community asking them to help out, and some have even made done 
> > > some initial work. However, redesign of a high-profile site like 
> > > djangoproject.com (http://djangoproject.com) is a big job, and nobody has 
> > > been able to spare the time to bring the job to completion. 
> > > 
> > > So - at this point I'm open to any offers. I want to avoid design by 
> > > committee -- ideally, I would like to pass this off to a single person 
> > > (or a small group) and give them complete control over design process. 
> > > I'm not completely sure how to organise who gets this role -- suggestions 
> > > are welcome. 
> > > 
> > > If you (or anyone else) is interested, drop me a line and I can give you 
> > > the design brief we've been working with. 
> > > 
> > > Yours, 
> > > Russ Magee %-)
> > > 
> > > 
> > > 
> > > On Saturday,

Re: Redesign of djangoproject.com?

[Russell Keith-Magee]

Hi Dana


On Sunday, 29 April 2012 at 1:45 AM, Dana Woodman wrote:

> Very true Chris. I'd love to see the documents that were put together when 
> this was discussed last time, if they're still around.
> 
I've included the design brief in my response to Ned. If you're looking for 
something else in particular, let me know and I'll see if I can find (or 
produce) something that is suitable.
> 
> In regards to what needs improvement, there are some core issues as I see it. 
> 
> 1) the home page does a poor job of conveying what someone should do if they 
> want to try out Django. It also could do a much better job of making Django a 
> bit more "sexy". 
> 2) the documentation itself, while thorough, is a bit difficult to navigate, 
> especially for new users. I think this could be partially remedied by some 
> modifications to headers and color choices. 
> 3) the project could do a better job of selling itself, especially in regards 
> to showcasing why it is so great: automatic admin, large active community and 
> plugins, large sites and organizations using it, active development, lots of 
> built in security, etc...
> 4) it just looks old and outdated, which is a problem in its own right. 
> 
> Should I just fork the project on Github and hack away or do I need to work 
> on subversion?
> 
As of yesterday, we are a SVN-free organisation -- everything is on GitHub. 
However, djangoproject.com has been on GitHub for a while:

https://github.com/django/djangoproject.com
 
If you want to work on code directly, that's the place to start.
> 
> In regards to organization of the documentation, I assume that is generated 
> via the docs within Django, correct? Would I have freedom to do content 
> organization/copy changes or would it just be a design change? I don't mean 
> changing the documentation, but more how other pages and sections are laid 
> out.

Correct - the documentation is the contents of the /docs directory, as rendered 
by Sphinx. This means that the style of any individual page (e.g., fonts for 
headings, etc) is part of the Sphinx stylesheet, but the gross structure is 
determined by the file layout in the /docs directory (i.e., one page per file).

There's really two tasks contained in what you have described here:

 1) Restyling the docs to make them easier to read

 2) Reorganizing the docs to make information easier to find.

1) is definitely the remit of this design project. (2) is a much bigger 
project. Unless you're going to keep it simple - e.g., a proposing better home 
page layout for the docs - it may be better to leave the structure of the docs 
as a separate issue.
> I assume I'd also need to work on the code.djangoproject.org 
> (http://code.djangoproject.org) site as well? Are there other things that 
> would need to change? I'd really need the scope down so I know how and where 
> to start.

There's also pages for the foundation; these aren't currently linked to from 
the homepage, so they're really well hidden. Right now, they're currently 
implemented as flat pages. 

However, as the brief indicates, we'd like to have a bunch of broader design 
guidelines so if we want to improve any existing section of the site, or if any 
other project comes along and we want to integrate them into djangoproject.com 
(e.g., Django People or Django Packages), we can give that project a style 
guide to work with.

More importantly, one of my goals with this project is to broaden the base of 
"active design experts" that we have as a project. The core coding team has a 
relatively low bus factor -- if one of us stops committing, there are plenty of 
others who know the code and can maintain the project in our absence. However, 
our design bus factor is somewhere between 1 and 0 -- we've got Idan as our 
Benevolent Designer for Life, but he's a busy man; we really need to surround 
him with a bunch of talented designers, in the same way that we've got Jacob 
and Adrian, plus a bunch of talented developers. 

Yours,
Russ Magee %-)
> 
> This is no simple task so any direction or help would be greatly appreciated!
> 
> Cheers
> 
> On Apr 28, 2012, at 5:11 AM, Chris Pickett  (mailto:chris.pick...@gmail.com)> wrote:
> 
> > It seems to me that this might be one of those opportunities to just jump 
> > right in and get your hands dirty. I many ways I don't know if a redesign 
> > is going to happen without someone taking the initiative and getting it 
> > done, so it might as well be you! :)
> > 
> > On Saturday, April 28, 2012 2:22:59 AM UTC-5, Dana Woodman wrote:
> > > 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 (http://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 (http://djangoproj

Re: GitHub migration done!

[Adrian Holovaty]

On Fri, Apr 27, 2012 at 10:08 PM, Adrian Holovaty  wrote:
> OK, it's live!
>
> https://github.com/django/django

Hi all,

I've written a post-mortem here, for anybody interested in how the process went:

http://www.holovaty.com/writing/django-github/

Adrian

-- 
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?

[Dana Woodman]

Great info Russ, thanks!

My thoughts at this point would be to focus on the main content sections, 
including the home page and documentation overview pages. 

For the home page I'd see something like this working well:

-Logo and brief project description (fork on Github as well?) - Answers the 
"What is Django?" and "Why should I care?" questions. (for example, Twitter 
Bootstraps's home page: http://cl.ly/3R0d1X300S0S0f0A0j0S)
Link to download and docs - Answers the "How can I start?" question
"Who uses Django?" section - Answers, well... the "Who uses Django?" question. 
BTW, is there a reason that there isn't more of the larger users of Django on 
here?  Eg Disqus, Instagram, Pinterest, Google, Mahalo, addons.mozilla.org 
(http://addons.mozilla.org), etc... This alone would get people excited to use 
Django and would convince a lot of the business types that Django can scale and 
is worth the investment.
A graphical site navigation area, eg: http://cl.ly/3B1N2h3E2x3x0f3V091K - Give 
people a an easy way to get around to the core content on the site.



Thinking a layout along the lines of Node.js (http://nodejs.org/) homepage 
would be effective. Node does a good job of keeping things minimal and easy to 
navigate.

Some sort of "blogroll" type feature would satisfy the need to update the 
community of interesting or useful links. This could work in concert with the 
documentation as well. Not sure what the exact needs for this are, what would 
be an ideal process for this?

How would the style guide be presented? Would it be a page on 
djangoproject.org, Github Wiki, a PDF, or...?

I assume it would be fairly straightforward to give Spinx a new skin?

Do you feel an incremental approach would be best or should it be a complete 
overhaul in one go? 

--
Dana Woodman
d...@danawoodman.com (mailto:d...@danawoodman.com)
http://www.danawoodman.com


On Saturday, April 28, 2012 at 4:49 PM, Russell Keith-Magee wrote:

> Hi Dana
> 
> 
> On Sunday, 29 April 2012 at 1:45 AM, Dana Woodman wrote:
> 
> > Very true Chris. I'd love to see the documents that were put together when 
> > this was discussed last time, if they're still around.
> I've included the design brief in my response to Ned. If you're looking for 
> something else in particular, let me know and I'll see if I can find (or 
> produce) something that is suitable.
> > 
> > In regards to what needs improvement, there are some core issues as I see 
> > it. 
> > 
> > 1) the home page does a poor job of conveying what someone should do if 
> > they want to try out Django. It also could do a much better job of making 
> > Django a bit more "sexy". 
> > 2) the documentation itself, while thorough, is a bit difficult to 
> > navigate, especially for new users. I think this could be partially 
> > remedied by some modifications to headers and color choices. 
> > 3) the project could do a better job of selling itself, especially in 
> > regards to showcasing why it is so great: automatic admin, large active 
> > community and plugins, large sites and organizations using it, active 
> > development, lots of built in security, etc...
> > 4) it just looks old and outdated, which is a problem in its own right. 
> > 
> > Should I just fork the project on Github and hack away or do I need to work 
> > on subversion?
> As of yesterday, we are a SVN-free organisation -- everything is on GitHub. 
> However, djangoproject.com (http://djangoproject.com) has been on GitHub for 
> a while:
> 
> https://github.com/django/djangoproject.com
> 
> If you want to work on code directly, that's the place to start.
> > 
> > In regards to organization of the documentation, I assume that is generated 
> > via the docs within Django, correct? Would I have freedom to do content 
> > organization/copy changes or would it just be a design change? I don't mean 
> > changing the documentation, but more how other pages and sections are laid 
> > out.
> 
> Correct - the documentation is the contents of the /docs directory, as 
> rendered by Sphinx. This means that the style of any individual page (e.g., 
> fonts for headings, etc) is part of the Sphinx stylesheet, but the gross 
> structure is determined by the file layout in the /docs directory (i.e., one 
> page per file).
> 
> There's really two tasks contained in what you have described here:
> 
> 1) Restyling the docs to make them easier to read
> 
> 2) Reorganizing the docs to make information easier to find.
> 
> 1) is definitely the remit of this design project. (2) is a much bigger 
> project. Unless you're going to keep it simple - e.g., a proposing better 
> home page layout for the docs - it may be better to leave the structure of 
> the docs as a separate issue.
> > I assume I'd also need to work on the code.djangoproject.org 
> > (http://code.djangoproject.org) (http://code.djangoproject.org) site as 
> > well? Are there other things that would need to change? I'd really need the 
> > scope down so I know how and where to star

Re: GitHub migration done!

[charettes]

I wrote a little userscript that linkifies ticket numbers in github pull 
request to the correct trac ticket.

It can be found here .

Le vendredi 27 avril 2012 23:08:09 UTC-4, Adrian Holovaty a écrit :
>
> 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 
>
> A few quick points (though this definitely deserves a more in-depth 
> writeup): 
>
> * I renamed the old (mirror) repository to 
> https://github.com/django/django-old. We had talked about deleting it 
> outright to avoid confusion, but I realized at the last minute that 
> doing so would have deleted all the pull requests. I didn't want to 
> throw all of that out, and I think we can figure out a way to use 
> those pull requests in the new repository. 
>
> * I only migrated trunk (now called "master"), rather than including 
> all of the branches. This was the result of a bunch of discussion on 
> IRC with Brian R., et al. The thinking is that it kept the migration a 
> lot cleaner/simpler, and we can always add branches later. Of course, 
> we'll need to create the latest release branches. Otherwise, we can 
> consider the SVN branches on an individual basis. 
>
> * As expected, all forks of the old repository are now broken. Can 
> somebody volunteer to write some documentation on how to upgrade your 
> old fork to use the new upstream repo (rebase? simple patch?)? 
>
> * We're going to keep the Subversion repository around indefinitely, 
> but it'll no longer be updated. 
>
> * We're going to keep using Trac for tickets, but pull requests on 
> GitHub are also welcome. 
>
> * Clearly there are lots of bits of process that need to be updated 
> now, from the django-updates mailing list to our "contributing" 
> documentation, etc. We'll take care of all of that in the coming days, 
> and we should all expect some degree of confusion and unsettlement in 
> the community. That's totally fine, and we'll get through it. :-) 
>
> * Finally, big thanks to the folks on IRC today who helped me through 
> the process and contributed good ideas. 
>
> I'm planning to write up a blog post on how the process went, for the 
> benefit of the five open-source projects still using Subversion. 
>
> Adrian 
>

-- 
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/-/cPx2omZVWmIJ.
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!

[ptone]

On Saturday, April 28, 2012 12:46:53 PM UTC-7, Yuval Adam wrote:
>
> I think this issue should be dealt with sooner rather than later. 
>
> Django will start getting lots of orphan pull requests with no 
> matching trac ticket, and a policy of how community members should 
> contribute via github should be in place. 
>
> As a side note, it is kind of a hassle to submit a pull request and 
> then go fill a new trac ticket. 
> For me, as a kind-of-involved user of Django, I simply won't go into 
> that burden. 


It is a small hassle, but I've done it several times (creating a pull and 
ticket with cross referencing links).  Writing tests can sometimes feel 
like a hassle.

Hopefully we will see some solutions and improvements in the trac-github 
space, but in the meantime - it shouldn't be a barrier to contributing - a 
few more clicks is all.

 -P


> On Apr 28, 10:03 am, Aymeric Augustin 
>  wrote: 
> > On 28 avr. 2012, at 05:08, Adrian Holovaty wrote: 
> > 
> > > * We're going to keep using Trac for tickets, but pull requests on 
> > > GitHub are also welcome. 
> > 
> > Hi everyone, 
> > 
> > For extra safety, I recommend you still create Trac tickets for each 
> suggested change, until we work out how pull requests integrate into the 
> triage workflow. 
> > 
> > Thanks, 
> > 
> > -- 
> > Aymeric.

-- 
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/-/d9oL2HA1IXIJ.
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.