On Sun, Feb 8, 2015 at 8:18 PM, Barry Smith <[email protected]> wrote:
> > > On Feb 8, 2015, at 8:08 PM, Jed Brown <[email protected]> wrote: > > > > Mark Adams <[email protected]> writes: > >> Bitbucket should have some sort of graphical representation of the PETSc > >> code base and color code who "controls" which code so that we can track > of > >> this. Like a war room sort of thing. > > > > No, we should use a uniform style everywhere. I used a typedef to > > reduce code and to normalize the documentation. Barry decided we should > > do it a different way, but didn't update everything. > > Yeah, lazyness and fear of Jed's wraith stopped me from "cleaning up" > the TS public API so far :-) > > > I don't think it's > > urgent, but we should be consistent in new code. > I still think its a good idea to know who is on the hook for each part since it is getting big enough that no one practically patrols all the code anymore. Matt -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener
