fenics team mailing list archive

[Anders Logg <logg@xxxxxxxxx>]

Dear all,

A couple of developers told me last week they were waiting for the
dust to settle before jumping in and working actively with the new
code repositories. I think the dust has now settled (with yet another
rewrite of the FFC repository yesterday) and it's safe to jump in.

As before, please read up on

   http://git-scm.com/book
   https://www.kernel.org/pub/software/scm/git/docs/gitworkflows.html
   https://bitbucket.org/petsc/petsc/wiki/developer-instructions-git

One thing I would suggest now is that core developers publish branches
they intend to merge as part of the main repositories (as opposed to
storing them in personal repositories). It makes it easier for others
to follow the development. Note e.g. that PETSc has 66 branches at the
moment. Examples would be the UFL repository which could have the
following branches:

  master
  next
  martinal/subdomains
  martinal/signatureopt
  logg/tuplenotation ;-)

Issues we still need to discuss (please jump in) are:

- Moving questions to stackexchange (comment on previously suggested
  instructions)

- Updating the information on the web pages (please help out)

--
Anders