That is a question that we have to address: if we allow this kind of external packages (or furthermore, move the devlopments of parts of sage to a different workflow)... what kind of control will we do about them? Will we make no promises about them at all? Have some kind of revision process before accepting them? If so, what exactly do we check?
The fact that all Sage code goes through a peer review process is an important point. So, if we split the development process in different modules... should we enforce such a review process in all the modules? El viernes, 15 de abril de 2016, 23:40:05 (UTC+2), Dima Pasechnik escribió: > > > > On Friday, April 15, 2016 at 10:13:22 PM UTC+1, Simon King wrote: >> >> On 2016-04-15, Vincent Delecroix <[email protected]> wrote: >> > +1. The need of modifying Sage source code to have an external package >> > is very bad. >> >> I miss old-style packages, too. > > > we didn't get to see an spkg with a virus or with `rm -rf /`, but surely > it was just a question of time... > > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
