hey marty, i agree. see: http://code.djangoproject.com/wiki/SchemaEvolutionDocumentation
maybe another day or two for the stand-alone version... derek Marty Alchin wrote: > I won't get into the discussion on features or implementation yet, but > I do have to agree that working code speaks volumes compared to > descriptions. I'll have need for schema evolution in a future project, > so I've been following these discussions, and I've completely lost > track of who's working on what, and how each offering is expected to > work. > > Personally, what I'd like to see is this: > > * Each view is presented with working code. It doesn't have to be > feature complete, but does some basic jobs, to illustrate how it would > work > * Along with the code, give a list of features it provides. Again, it > doesn't have to be all the features it will ever provide, just those > that are currently implemented. > * A brief (yes, brief) description of why you chose a particular > approach. This way, if two people come up with different approaches to > the same problem, it's easier to compare the reasoning behind them. > * If possible, some sort of feature matrix comparing the states of the > various implementations. So if it looks like one group is tackling > half of the problems, while another group is tackling the other half, > maybe merging them could be easy. > > It'd probably be easiest to do the descriptions on the Wiki, with each > proposal having its own article. The current SchemaEvolution article > tries to cover everybody at once, and it does a poor job of organizing > information. I would suggest that article be used for descriptions of > the problems that need to be solved by schema migration, the feature > matrix comparing the implementations, and links to individual articles > that provide more detail for each implementation. > > Each article would then describe the implementation's motivations and > tactics, example usage code, and links to relevant supporting > articles, previous discussions, and working code. There's merit in > documenting future plans in each individual article, but I would like > to see the main SchemaEvolution only cover those features that are > actually finished. > > I'd be willing to set this up if there's support for it, but if you > guys don't want to maintain it, I won't bother. It's just one > suggestion, but I think it would help. > > -Gul > > > > --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
