[mythtv] mythtv- code architecture

[David Asher]

I've been thinking of making some patches which are just comments for
the code to document what (little) I am able to figure out.  How large
would you want the patches?  I know generally smaller is better for
actual features, so that review is not too painful.  Would the same
thing be true for comments?  I suppose I could open a single ticket
and attach many small patches to be reviewed in bite-sized chunks as
time permitted.  My fear is that I'll be WRONG about the conclusions
I've come to, so I don't want them checked in without being read over
by someone with actual understanding of the code.

David.

On 6/13/07, Daniel Kristjansson <danielk at cuymedia.net> wrote:
> On Wed, 2007-06-13 at 15:20 -0400, hendrixski wrote:
> > Good documentation lowers the barrier to entry for new developers who
> > can make solid contributions.  Making that documentation easily
> > accessible wouldn't be a bad idea either.
>
> If you write any developer docs, doxygen or any other type,
> I'll be glad to commit these to the tree and mirror the
> results of 'cd mythtv/docs; make devdocs' at cuymedia.net.
>
> I think writing developer documentation for MythTV is a good
> way to learn the code.
>
> -- Daniel
>
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
>