Hi all: I am refactoring a django app to make it reusable and share it open sourced to the world. There is a lot code which I think it is optional and maybe not everybody will want to use, like some model fields, url patterns of view functions. so my initial approach is to release only the minimal version and let them add whatever they need.
But then a question arises, regarding maintenance and update of the application in the projects where the app is gonna live. When I will release further versions with bufixes or new features, then should these people download the app, and maybe do a merge with their modified versions? That would be against the philosophy of a django app for me, that is, to be de-coupled from other parts of the project. Also conflicts may appear, if my next app versions differ a lot from previous ones. The opposite approach I have seen in other apps is to include everything the developer considers suitable. But doing this means forcing people to include useless stuff for their projects, like model fields they won't never use in their database schema, for example. So how do u guys think I should target it? Minimalistic or full- batteries included? Thanks! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
