On Fri, Jun 12, 2015 at 5:34 AM, 'Martin Albrecht' via sage-devel <
sage-devel@googlegroups.com> wrote:

> Hi,
>
> so, the Singular team *wants* to keep PolyBoRi alive, but it's currently
> not
> clear if and when they *can* devote resources to it. This will be clarified
> over the next few months it seems.
>


What about this:

Now: We work on making polybori an optional package in sage.
  * At least going by this thread, the number of people who use polybori in
Sage is small enough for it to make sense to have polybori as an optional
package.
  * (I looked into this before I did the autotoolization) It shouldn't take
too much work to optionalize polybori -- the main effort will be its uses
in the crypto code.
  * Polybori is the sole dependency of Sage that doesn't at least build
against python 3 -- getting past this last major hurdle will make it much
easier to work on porting the actual sage library to python 3.

Future: The Singular team or whoever dedicates the time to maintain a
sequel to polybori.
  * This will be required once we stop supporting python 2 in the very
distant future (at least after 2020, which is the EOL for python 2).


>
> Cheers,
> Martin
>
> On Friday 12 Jun 2015 10:14:53 Martin Albrecht wrote:
> > I started talking to some people from the symbolic computation community
> to
> > discuss options (e.g. if someone wants to take over maintenance). Hence,
> > don't rush to a conclusion please, I'd really like to keep PolyBoRi
> around
> > somehow but don't want to be (sole) maintainer.
> >
> > Cheers,
> > Martin
> >
> > On Thursday 11 Jun 2015 20:45:41 William Stein wrote:
> > > On Thursday, June 11, 2015, Ralf Stephan <gtrw...@gmail.com> wrote:
> > > > So folks, be careful when you fork---you might end up as maintainer.
> > >
> > > Good point.  I think we should either
> > >
> > > 1. Remove polybori or
> > >
> > > 2. Have a specific person (or persons) step up to be maintainer.
> > >
> > > I'm fine with either option.
> > >
> > > > --
> > > > 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 <javascript:;>.
> > > > To post to this group, send email to sage-devel@googlegroups.com
> > > > <javascript:;>.
> > > > Visit this group at http://groups.google.com/group/sage-devel.
> > > > For more options, visit https://groups.google.com/d/optout.
> --
> .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.

Reply via email to