Django-values has had a long and rocky road thus far, with its name not being the least of its problems. I finally put it to the masses in a recent blog post, and I got back the simplest word I'm amazed I didn't think of: policy. Organizations are very familiar with the idea of policies and procedures, and I think this encapsulates that fairly well. Procedures are what would be done in various situations (Python code), while policies are the rules that define when and how those procedures should be carried out.
In short, I vote that it be changed to django-policy. I can't change the URL in Google Code without starting a whole new project (and since I already have issues in place, I'd rather not do that), but I can change all the documentation and add a note explaining the discrepancy. For the most part, I just wanted to put that to the general population here to see if policy would be a useful enough name to use for this app. Unless there are other objections, I figure the rest of the names can remain the same, using policy.Options and policy.*Value for the API. I don't have a new version of it checked in yet, but I've been doing a lot of work on it, and it should be very near completion later this week. This next update will also include documentation, which is another reason I'd like to make sure the name will stick before I go too far with all of it. Thoughts? -Gul --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
