Re: EuroPython Sprints
I'm scheduled to give a talk there and if I can definitely make it then I'll be going to the sprints as well. Rob On May 19, 8:40 am, Sergio Oliveira wrote: > Is there someone going to EuroPython (Birmingham - UK)? > I've just saw that Django is in the top of the proposed sprints > list:http://wiki.europython.eu/Sprints > > Cheers, > > -- > Sergio Oliveira > > If builders built buildings the way programmers wrote programs, then the > first woodpecker that came along would destroy civilization. --~--~-~--~~~---~--~~ 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: interest in extending {% blocktrans %}
Hi all,
I've read that kind of answer to feature proposals quite often during
the last weeks. Maybe we should create an informal trac-wiki page
collecting all those good ideas and explaining why this is currently
necessary. That way the devs won't have to search through the old
mailings after 1.1 to find the proposals.
By the way, an answer to a mail of that kind could be a simple link to
that wiki page, where the situation is explained.
What do the devs think about it? If I get an OK, I'd create the page and
use Russels mail text as a starting point.
Marc
Russell Keith-Magee schrieb:
> On Wed, May 20, 2009 at 9:11 AM, Andy Smith wrote:
>
>> Hey y'all, I'd like to propose that {% blocktrans %} support resolving of
>> simple variables.
>>
>
> I don't want to dampen your enthusiasm, but I'd like to propose that
> we hold off discussions like this until we are in the v1.2 feature
> discussion phase.
>
> Right now, we are (desperately) trying to get v1.1 out the door. We
> need the community to be focussing on finding (and preferably fixing)
> the bugs in v1.1. Discussions of new features distract from this goal.
> You definitely won't have the full attention of the core developers,
> and ultimately, this is what any proposal will require.
>
> Once v1.1 is finished (hopefully not long now!), we will move into a
> feature discussion period as we decide what we want to put into v1.2.
>
> Yours,
> Russ Magee %-)
>
> >
>
--~--~-~--~~~---~--~~
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: Oracle savepoints
On May 18, 5:12 pm, Ian Kelly wrote: > Yes, it was reason a). Transactions aren't automatically invalidated > after an IntegrityError, as far as I was able to determine. Thanks Ian. Ticket #11156 records the current inefficiency on Oracle. Cheers, Richard. --~--~-~--~~~---~--~~ 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: interest in extending {% blocktrans %}
On Wed, May 20, 2009 at 6:22 PM, Marc Remolt wrote: > > Hi all, > > I've read that kind of answer to feature proposals quite often during > the last weeks. Maybe we should create an informal trac-wiki page > collecting all those good ideas and explaining why this is currently > necessary. That way the devs won't have to search through the old > mailings after 1.1 to find the proposals. > > By the way, an answer to a mail of that kind could be a simple link to > that wiki page, where the situation is explained. > > What do the devs think about it? If I get an OK, I'd create the page and > use Russels mail text as a starting point. Meh. Personally, I'm not a big fan of wikis. They aren't an automatic win for every documentation problem. They require a lot of gardening effort if they are going to be useful resources. My experience has been that in most cases, this effort would be more effectively spent on other tasks. On top of that, by using the wiki to provide a place where we are documenting new ideas, we are effectively providing an off-list forum that is doing exactly the thing we are trying to avoid - discussion of new features. The "searching old mailings" problem isn't really as big as you make it out to be. If any new idea is to make it to trunk, it will need an individual to guide it through the commit process. If an idea can't survive a couple of weeks without community attention, then it probably isn't going to make it to trunk. Consider it a 'trial by fire' for new ideas. :-) However, if you are particularly enthused about this idea, then go right ahead. The wiki is open for all to contribute - maybe you can prove me wrong on the value of wikis. Yours, Russ Magee %-) --~--~-~--~~~---~--~~ 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: interest in extending {% blocktrans %}
It was just an idea. I'm not the person repeatedly writing the "not now but soon"-mails. You and the other devs have to decide, which way you save the most of your (currently very precious and limited) time. It would really make no sense to create additional documentation structure, that is not used by the devs. Would a special keyword or milestone for those ideas help in trac? In my company we use a dedicated priority (but you could use a milestone or special keyword) as a collection for new and maybe stupid ideas. Everyone, including the users of our apps, is invited to add new tickets containing feature requests, usability enhancements or whatever else, as long as they use the "just an idea"-priority (nah, not really called that way). When another development iteration begins, we can skim through those tickets and look for things we hadn't thought of till now. If we think the idea is crap, we mark the ticket as wontfix, otherwise we give it a real priority, assign a milestone and edit the text to make it developer friendly. You have something similar with the triage system, but I'm not sure how you extract those kind of new ideas out of the ticket flood, as all new tickets are marked unreviewed. Maybe the system I propose is already working here or better. But as it is with all new ideas at the moment, I guess it is better to postpone the discussion about it to after 1.1. So consider this mail just as an archiving of the idea on the mailing list. I'll see, if you are going to remember and find it again in a few weeks. ;-) Marc Russell Keith-Magee schrieb: > Meh. Personally, I'm not a big fan of wikis. They aren't an automatic > win for every documentation problem. They require a lot of gardening > effort if they are going to be useful resources. My experience has > been that in most cases, this effort would be more effectively spent > on other tasks. On top of that, by using the wiki to provide a place > where we are documenting new ideas, we are effectively providing an > off-list forum that is doing exactly the thing we are trying to avoid > - discussion of new features. > > The "searching old mailings" problem isn't really as big as you make > it out to be. If any new idea is to make it to trunk, it will need an > individual to guide it through the commit process. If an idea can't > survive a couple of weeks without community attention, then it > probably isn't going to make it to trunk. Consider it a 'trial by > fire' for new ideas. :-) > > However, if you are particularly enthused about this idea, then go > right ahead. The wiki is open for all to contribute - maybe you can > prove me wrong on the value of wikis. > > Yours, > Russ Magee %-) > > --~--~-~--~~~---~--~~ 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: EuroPython Sprints
Same here. If I can make it to EuroPython I'll try really hard to be there for the sprints. -- Horst On Wed, May 20, 2009 at 11:59 AM, Robert Lofthouse wrote: > > I'm scheduled to give a talk there and if I can definitely make it > then I'll be going to the sprints as well. > > Rob > > On May 19, 8:40 am, Sergio Oliveira wrote: >> Is there someone going to EuroPython (Birmingham - UK)? >> I've just saw that Django is in the top of the proposed sprints >> list:http://wiki.europython.eu/Sprints >> >> Cheers, >> >> -- >> Sergio Oliveira >> >> If builders built buildings the way programmers wrote programs, then the >> first woodpecker that came along would destroy civilization. > > > --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
DjangoAdmin - Permission in custom modules
Hello Guys! Firstly, sorry for the English errors than came in. English is not my home language. I have a simple problem here: On my custom AdminModules, there's permissions at level-group to view the my admin modules on the home of the admin? Currently, only the superuser(s) can view them, and I not achieve to find these permissions. I hope you could understand me. Thanks. Julio --~--~-~--~~~---~--~~ 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: DjangoAdmin - Permission in custom modules
On Wed, May 20, 2009 at 9:40 AM, Júlio Cesar wrote: > > Hello Guys! > Firstly, sorry for the English errors than came in. English is not my > home language. > > I have a simple problem here: On my custom AdminModules, there's > permissions at level-group to view the my admin modules on the home of > the admin? > > Currently, only the superuser(s) can view them, and I not achieve to > find these permissions. > > I hope you could understand me. > Thanks. > Julio > > > > > Take a look at this: http://www.b-list.org/weblog/2008/dec/24/admin/ blog post, it explains how to overide a number of the defaults (including authorization) on the Admin. Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." --Voltaire "The people's good is the highest law."--Cicero --~--~-~--~~~---~--~~ 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: Application developed using Django
Thank you very much for your answer and congratulations to you all for developing such a great project. Kind regards, Marc 2009/5/20 Jacob Kaplan-Moss > > Hi Marc -- > > In general this isn't exactly the right place for these questions -- > some would be better put to django-users since they're questions about > *using* Django, not developing it, and others would more appropriately > be directed to the DSF (http://www.djangoproject.com/foundation/). > > However, since this stuff comes up often it's worth answering > publicly, and since I've got a "DSF President" hat around here > somewhere... let me look... ah, here we go: > > On Wed, May 20, 2009 at 10:27 AM, M C wrote: > >> - what license type (if any) you recommend ? > > This one's a huge can of worms, actually. Free software licenses are > one of those "emacs vs. vi" or "Python vs Perl" holy wars that us > free/open software geeks like to argue about. > > I'm not going to get in the middle of this particular fight, but I > will point out that Django's licensed under the very permissive BSD > license. This means that Django can be used essentially anywhere, > including in distributed commercial software, as long as its properly > attributed. This means that if you release code under a more > restrictive license, some of the places that use Django might not also > be able to use your code. It's up to you to decide if this is a good > thing or not. > > >> - under what circumstances and in what form can I use the Django name > >> ? > > You can find official logos, colors, and usage policy at > http://www.djangoproject.com/community/logos/. > > In general, you're free to use the Django name and logo as long as you > stay within the bounds of fair use. That means using the logo to refer > to Django (and not something else). If you have specific questions > about your usage you should get in touch with the Django Software > Foundation and ask. > > >> Can I use the Django name in my technical and functional documentation > ? > >> > >> Can I use the Django name in my slides / presentation ? > > You sure can -- please do! > > Thanks, > > 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: Application developed using Django
Hi Marc -- In general this isn't exactly the right place for these questions -- some would be better put to django-users since they're questions about *using* Django, not developing it, and others would more appropriately be directed to the DSF (http://www.djangoproject.com/foundation/). However, since this stuff comes up often it's worth answering publicly, and since I've got a "DSF President" hat around here somewhere... let me look... ah, here we go: On Wed, May 20, 2009 at 10:27 AM, M C wrote: >> - what license type (if any) you recommend ? This one's a huge can of worms, actually. Free software licenses are one of those "emacs vs. vi" or "Python vs Perl" holy wars that us free/open software geeks like to argue about. I'm not going to get in the middle of this particular fight, but I will point out that Django's licensed under the very permissive BSD license. This means that Django can be used essentially anywhere, including in distributed commercial software, as long as its properly attributed. This means that if you release code under a more restrictive license, some of the places that use Django might not also be able to use your code. It's up to you to decide if this is a good thing or not. >> - under what circumstances and in what form can I use the Django name >> ? You can find official logos, colors, and usage policy at http://www.djangoproject.com/community/logos/. In general, you're free to use the Django name and logo as long as you stay within the bounds of fair use. That means using the logo to refer to Django (and not something else). If you have specific questions about your usage you should get in touch with the Django Software Foundation and ask. >> Can I use the Django name in my technical and functional documentation ? >> >> Can I use the Django name in my slides / presentation ? You sure can -- please do! Thanks, 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: Application developed using Django
> > > Hello, > > > I've developed an application using django, mysql and graphviz (please find > the list of functionalities below). > > I plan to release the code and the documentation and this brings me to ask > you the following : > * - what license type (if any) you recommend ? * >I intend this to be completely free software > > *- under what circumstances and in what form can I use the Django name ?* > > I plan to also submit the application's code to OSSIM (Open Source > Security Information Management), as they are interested in integrating the > Asset classification/valuation and Risk assessment functionality. > > They are currently using python but not the django framework. > > * Can I use the Django name in my technical and functional documentation > ?* > > *Can I use the Django name in my slides / presentation ?* > > > > Thanks and kind regards, > Marc Chisinevski > > > > > > *List of functionalities* > *==* > License management > Server management > Party (Clients, Providers) management > Contract management > Asset classification and valuation > Risk assessment > Graphs (using graphviz) > Reports > Email alerts (Contract expiration alerts, License expiration alerts) > --~--~-~--~~~---~--~~ 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: DjangoAdmin - Permission in custom modules
Hello all! I work with Julio Cesar, and I comes to transpose this question more transparently. The question is about apps that shows when we as super users, and not appear with all others users... I put all permissions of a app (add, change and delete), registered in the admin with a ModelAdmin, and nothing... I think it about a problem with permissions, but no have a idea about the problem :( Thanks! On 20 maio, 11:45, Alex Gaynor wrote: > On Wed, May 20, 2009 at 9:40 AM, Júlio Cesar wrote: > > > Hello Guys! > > Firstly, sorry for the English errors than came in. English is not my > > home language. > > > I have a simple problem here: On my custom AdminModules, there's > > permissions at level-group to view the my admin modules on the home of > > the admin? > > > Currently, only the superuser(s) can view them, and I not achieve to > > find these permissions. > > > I hope you could understand me. > > Thanks. > > Julio > > Take a look at this:http://www.b-list.org/weblog/2008/dec/24/admin/blog > post, it explains how to overide a number of the defaults (including > authorization) on the Admin. > > Alex > > -- > "I disapprove of what you say, but I will defend to the death your right to > say it." --Voltaire > "The people's good is the highest law."--Cicero --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Belated Update - GSOC [ Testing ]
A belated update (e-mail trouble): Nothing too exciting this last week, got feedback on my sample patch and updated accordingly. I'm pretty bad on PEP8 compliance, so we found some good resources on that, and have been working on making sure I write PEP8-safe code. Otherwise, a slow last week. Again, I'm very sorry for the last update! -- Kevin Kubasik http://kubasik.net/blog --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
