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