On Jul 12, 12:59 pm, William Stein <wst...@gmail.com> wrote: > On Monday, July 12, 2010, kcrisman <kcris...@gmail.com> wrote: > > >> This would be a good reason for us to setup a separate trac server for > >> the notebook. It's tempting. There's probably also a way to make it > >> so > > >> http://trac.sagemath.org/sage_notebook > > >> is a trac just for the notebook. > > > However, at the very least one would want to have intense integration > > between this and Sage's trac. What if something at this new Trac > > needed to include a Sage library patch that affected someone who > > doesn't develop on the notebook? Also, I see the potential for even > > more balkanization when it comes to the notebook. > > Separating the notebook from sage is by far the best chance we have to > reduce the number of different competing notebook projects. The less > tight the integration with sage the better for this.... >
True, but that doesn't address the problem of how to deal with sagenb patches that require complementary sage library patches, especially for non-notebook developers who would find it difficult to wait several months for a new spkg if there was something they needed (don't ask me for a specific example, I'm just raising a hypothetical here). - kcrisman -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
