Opened 17 years ago
Closed 17 years ago
#3676 closed (worksforme)
Non English content in the Django Website community feed aggregator
| Reported by: | Fred | Owned by: | Jacob |
|---|---|---|---|
| Component: | *.djangoproject.com | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Not to be offensive against any foreign language or it's speakers, but could we please exclude user blogs from the community feed on http://www.djangoproject.com/community/ if the blog contains non english entries? I think it's safe to assume that any language other than english will be only understandable by a small minority of the Django user community, especially for potential users browsing around the Django website to get a feel for the framework.
Seeing three top posts in Russian (as an example for March 7th. 2007 ) will unfortunately not give a positive first impression, though the content could be very useful and of high quality for a native speaker.
Change History (2)
comment:1 by , 17 years ago
comment:2 by , 17 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
(and closing worksforme, since that seems the best status)
I like the idea that anybody who's writing about Django can get listed there; English/non-English doesn't really bother me (and I'd wager that there are more non-native-English-speakers using Django than one would first suspect).