I agree that we should distill it down, but maybe not to one page? At least not if that page get too long. The page on pull request would be nice to keep, and maybe expand with more (and dolfin specific) use examples?
Johan On 05/27/2013 06:20 PM, Anders Logg wrote: > Good start. I think we should distill this down to one page, minimize > the amount of text (we can read the Git book or the PETSc pages for > that) and present a concise list of use cases with copy-paste cookbook > instructions. > > -- > Anders > > > On Mon, May 27, 2013 at 09:34:40AM +0200, Johan Hake wrote: >> I have now cloned petsc wiki and adjusted it to dolfin. Have a look at: >> >> https://bitbucket.org/fenics-project/dolfin/wiki/Home >> >> Please have a look. For core developers adjust the wiki at will, for >> others I bet an email (preferably with a patch) to this list would be >> sufficient. >> >> I have added a courtesy to the petsc community for our blatant rip of >> their wiki: >> >> https://bitbucket.org/fenics-project/dolfin/wiki/about-wiki >> >> Most of the discussion we recently had on handling pull-requests are >> already covered in: >> >> >> https://bitbucket.org/fenics-project/dolfin/wiki/pull-request-instructions-git >> >> I will later add some of the more esoteric topics we stumbled over in >> our discussion. >> >> Regards, >> >> Johan >> _______________________________________________ >> fenics mailing list >> fenics@fenicsproject.org >> http://fenicsproject.org/mailman/listinfo/fenics _______________________________________________ fenics mailing list fenics@fenicsproject.org http://fenicsproject.org/mailman/listinfo/fenics
