Maybe django-developers is really confusing ("I am developer using django" is not "I am developer of the django" ), have you been guys thinking about moving to another name? django-internals?
On Sun, Apr 13, 2008 at 9:28 PM, Mike Scott <mic...@gmail.com> wrote: > This mailing list is for the development of django itself. Your issue is > with mod_python and is probably better answered at > http://mailman.modpython.org/mailman/listinfo/mod_python
> It has nothing to do with django itself.
> If you have any issues with django, then the first port of call (and often > the only port of call) is the django-users list.
> Cheers.
> On Mon, Apr 14, 2008 at 6:24 AM, jurian <jurianbo...@gmail.com> wrote:
> > I've been battling with this issue for half a day now.
> > This is the error I'm getting when starting-up apache:
> > [Sun Apr 13 20:13:29 2008] [error] make_obcallback: could not import > > mod_python.apache.\n > > Traceback (most recent call last): > > File "/home/django/active/Python-2.5.2/lib/python2.5/site-packages/ > > mod_python/apache.py", line 23, in <module> > > import time > > ImportError: No module named time > > [Sun Apr 13 20:13:29 2008] [error] make_obcallback: Python path being > > used "['/home/django/active/Python-2.5.2/lib/python25.zip', '/home/ > > django/active/Python-2.5.2/lib/python2.5', '/home/django/active/ > > Python-2.5.2/lib/python2.5/plat-linux2', '/home/django/active/ > > Python-2.5.2/lib/python2.5/lib-tk', '/usr/lib/python2.5/lib-dynload', > > '/home/django/active/Python-2.5.2/lib/python2.5/site-packages', '/usr/ > > lib/python2.5/site-packages']".
On Sun, Apr 13, 2008 at 2:10 PM, Robert Šmol <smol.rob...@gmail.com> wrote: > Maybe django-developers is really confusing ("I am developer using django" > is not "I am developer of the django" ), have you been guys thinking about > moving to another name? django-internals?
""" Discussion group for Django developers. This group is used for discussion of developing Django itself, not user questions; Please use django-users for issues regarding using the framework, questions for the Django user community outreach, etc. """
Changing the name would just give folks another thing to ignore.
Ok, so you mean people post here even the read the description? I was more thinking that they read only the group-name, not the description of the group name and this is what is causing their confusion. Anyway, I guess not a big deal.
On Sun, Apr 13, 2008 at 10:54 PM, Jacob Kaplan-Moss <
> On Sun, Apr 13, 2008 at 2:10 PM, Robert Šmol <smol.rob...@gmail.com> > wrote: > > Maybe django-developers is really confusing ("I am developer using > django" > > is not "I am developer of the django" ), have you been guys thinking > about > > moving to another name? django-internals?
> """ > Discussion group for Django developers. This group is used for > discussion of developing Django itself, not user questions; Please use > django-users for issues regarding using the framework, questions for > the Django user community outreach, etc. > """
> Changing the name would just give folks another thing to ignore.
> Changing the name would just give folks another thing to ignore.
If the name of the list were changed to, say, "django-internal", you
would have to ignore the name of the list to accidentally mis-post;
this is very unlikely, and hardly "another thing to ignore". Right
now, all that you'd have to ignore to mistakenly post user questions
to this list is the end of the description of the list (the first
sentence doesn't suggest either interpretation).
> On Sun, Apr 13, 2008 at 2:10 PM, Robert Šmol <smol.rob...@gmail.com> > wrote: > > Maybe django-developers is really confusing ("I am developer using > django" > > is not "I am developer of the django" ), have you been guys thinking > about > > moving to another name? django-internals?
> """ > Discussion group for Django developers. This group is used for > discussion of developing Django itself, not user questions; Please use > django-users for issues regarding using the framework, questions for > the Django user community outreach, etc. > """
> Changing the name would just give folks another thing to ignore.
My initial reaction to the suggestion of changing the group name was an immediate NO, that's a bad idea. However after looking into it a little (and seeing yet another mis-directed message appear), I've changed my mind. The main thing I found when looking into it is that changing the "Group name" (which appears in the upper left in a large font on all the group pages) wouldn't affect the group email address, so email subscribers would not have to update filters, etc. Email subscribers who never even look at the Google groups pages might never even notice a change in "Group name".
However, I can see it might be inconsistent/confusing to have a group named "Django internals" with an email address of django-developers@googlegroups.com, so I can understand if you still don't want to mess with it. However I did notice something else that might help: a welcome message for the group. A welcome message, if it existed, would show up on the main group page ( http://groups.google.com/group/django-developers) in between the "Home" and "Discussion" banners. If you put a welcome message there that said:
NOTE: This group is used for discussion of developing Django itself, not user questions; Please use django-users for issues regarding using the framework, questions for the Django user community outreach, etc.
new users might actually notice it. It would at least (likely) be on the first page they come to when they find the group versus having to hope they think to click on the "About" link before deciding to post. It might still be missed by some, but I expect it would cut down on the number of misdirected posts, and it has no downside that I can see.
When using the google interface to make a new post I have seen
instructions as part of the 'new message' form for other groups. The
groups I am thinking of are all 'google' help/developer/etc groups so
it might not be something a general group can configure. I think
having instructions right in your face when you are typing up a new
post with a link to django-users would go a long way to alleviate the
problem. Replies will not be effected, and most people making a new
post who know what they are doing will quickly get used to ignoring
that text. Some people will still send posts in via the e-mail address
but I believe those to be few and far between.
-Doug
On Apr 13, 6:16 pm, "Karen Tracey" <kmtra...@gmail.com> wrote:
> > On Sun, Apr 13, 2008 at 2:10 PM, Robert Šmol <smol.rob...@gmail.com>
> > wrote:
> > > Maybe django-developers is really confusing ("I am developer using
> > django"
> > > is not "I am developer of the django" ), have you been guys thinking
> > about
> > > moving to another name? django-internals?
> > """
> > Discussion group for Django developers. This group is used for
> > discussion of developing Django itself, not user questions; Please use
> > django-users for issues regarding using the framework, questions for
> > the Django user community outreach, etc.
> > """
> > Changing the name would just give folks another thing to ignore.
> My initial reaction to the suggestion of changing the group name was an
> immediate NO, that's a bad idea. However after looking into it a little
> (and seeing yet another mis-directed message appear), I've changed my mind.
> The main thing I found when looking into it is that changing the "Group
> name" (which appears in the upper left in a large font on all the group
> pages) wouldn't affect the group email address, so email subscribers would
> not have to update filters, etc. Email subscribers who never even look at
> the Google groups pages might never even notice a change in "Group name".
> However, I can see it might be inconsistent/confusing to have a group named
> "Django internals" with an email address of
> django-developers@googlegroups.com, so I can understand if you still don't
> want to mess with it. However I did notice something else that might help:
> a welcome message for the group. A welcome message, if it existed, would
> show up on the main group page (http://groups.google.com/group/django-developers) in between the "Home" and
> "Discussion" banners. If you put a welcome message there that said:
> NOTE: This group is used for discussion of developing Django itself, not
> user questions; Please use django-users for issues regarding using the
> framework, questions for the Django user community outreach, etc.
> new users might actually notice it. It would at least (likely) be on the
> first page they come to when they find the group versus having to hope they
> think to click on the "About" link before deciding to post. It might still
> be missed by some, but I expect it would cut down on the number of
> misdirected posts, and it has no downside that I can see.
