On Sat, Jun 13, 2015 at 5:21 AM, 'Martin Albrecht' via sage-devel < sage-devel@googlegroups.com> wrote:
> Hi all, > > On Saturday 13 Jun 2015 10:41:15 Francois Bissey wrote: > > I think Andrew has already done quite a bit of the porting to autotools > and > > some python 3 fixes. But neither he or I want to be a maintainer - at > least > > for the long term. > > ah, sorry that I missed that. Great! How about this: > > 1. We create an organisation on GitHub PolyBoRi3 > 2. We move Andrew's current version over there > I can do this. I might also rebase a few of the commits while doing so (to ease the review process), and probably rename it to BRiAl as per Alexander's suggestion. > 3. I volunteer to be *a* maintainer, help would greatly be appreciated > I can add you to the github organization as an owner when I make it. > I envision that it would be good to split PolyBoRi up roughly as follows to > make maintenance simpler (please do tell me if this is silly). This way we > keep dependencies of Sage as external dependencies and don't have to suck > large parts into the Sage library proper: > > - polybori-core (libpolybori, Cudd, groebner (?)) > > the C++ stuff that doesn't involve python at all. This would be a standard > package in Sage (hopefully) and autotoolised. > The autotoolisation of this stuff is basically done. Mainly the testsuite needs to be included. > > - polybori-python-binding-boost (PyPolyBoRi) > > the C++ boost stuff which does the Python bindings. This is not used by > Sage - > I believe - so we don't care much. Autotoolised, but not a priority, > because > Sage has its own Cython bindings reimplementing this stuff. > I think the main reason why Sage has its own Cython bindings is mainly historical -- they existed before polybori added their own python bindings. It would probably be a better idea to use polybori's own bindings in Sage -- it makes no sense trying to maintain two sets of python bindings. > - polybori-python > > The Python stuff which can be managed by distutils or whatever the kids are > using now. This could in principle be an optional package, but I guess it > might as well be standard given that's pure python and relatively small. > > Cheers, > Martin > > -- > .www: https://martinralbrecht.wordpress.com > .pgp: 40BC 7F0D 724B 4AB1 CC98 4014 A040 043C 6532 AFB4 > .xmpp: martinralbre...@jabber.ccc.de > .twitter: https://twitter.com/martinralbrecht > .keybase: https://keybase.io/martinralbrecht > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-devel+unsubscr...@googlegroups.com. > To post to this group, send email to sage-devel@googlegroups.com. > Visit this group at http://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. > -- Andrew -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
