+1 Though I am a newbie. On Tuesday, September 26, 2017 at 7:50:59 AM UTC+2, David Roe wrote: > > Hi everyone, > Sorry for the delay! > > I've created scheduling polls. If you have a conflict with part of a time > slot, feel free to use the "maybe" option by clicking twice. The polls are > for a specific week (October 7-13) but I'm hoping that we can use the same > time slot to meet more than once if it's productive. So feel free to fill > out the poll even if you have a conflict with this week in particular, and > just make a comment. Also, put your trac username in parentheses after > your name! > > * Python 3 - https://doodle.com/poll/xyituk2k3iwu7taf > * Infrastructure - https://doodle.com/poll/zduyvyshxcfv3wz6 > * Packaging - https://doodle.com/poll/2xrezk86vpaa9x2p > * Category cleanup - https://doodle.com/poll/tpyqzh8pska8wzu6 > > David > > On Sun, Sep 10, 2017 at 12:13 PM, Vincent Delecroix <20100.d...@gmail.com > <javascript:>> wrote: > >> +1 >> >> Would make sense to come up with topics (we are discussing it right now >> in this thread). And then, we could set up a date poll for each of them. >> (Might be what you were suggesting) >> >> For the themtaics, I will be up for >> >> * Python 3 >> >> * (Random) testing / speed regression >> >> 1) the test suite should not be that long (e.g. there are some places >> with duplicated and long doctest). I would like >> - the short testsuite to run fast (e.g. "sage -tp --all" running in >> less than 5 minutes) >> - have the long testsuite one reasonably fast (i.e. no "long >> doctest" warning in any circumstance) >> - introduce a new flag for very long doctest that can not be avoided >> (e.g. they carefully check a bug that appear only in huge dimensions). >> These will be run by patchbots only in the rc release cycle. >> >> 2) Specify and test the random generators (random_element is now >> unpredictible). >> >> 3) In the flint testsuite they also have specific random generators >> to test examples (e.g. on polynomials such random generator is likely to >> return 0 or 1 or x or x^100 + 1). It would make sense to adapt this >> strategy in Sage. I would actually get rid of the methods `some_elements` >> and just have a hidden `_random_test_elements()`. I do not see the point of >> having this method public >> >> * Clean and finish the categorification. That is all the mess that >> appear in tab completion as soon as you inherit from sage.structure.Element >> (like base_ring). Also get rid of the last old parent classes. >> >> * And for more mathematical things I am more likely to develop/debug the >> parts that are related to my research at the time I need them. So I would >> be happy with some review sessions where people post and review tickets. >> But nothing dedicated to a specific area. >> >> Vincent >> >> >> >> On 09/09/2017 05:04, David Roe wrote: >> >>> Hi everyone, >>> I'd like to organize some online Sage Days, where people gather on >>> zulip.sagemath.org and work on Sage together. The two things to be >>> decided >>> are >>> 1. What topics should we focus on? >>> 2. What days/times work for the most people? >>> Some of these may transition into in-person working groups (the IMA has >>> funding for small groups to meet there over this coming year to work on >>> projects) >>> >>> I'll send out a survey for the scheduling part, but I wanted to solicit >>> suggestions for topics first. Some ideas: >>> >>> * Python 3 Compatibility >>> * Work on documentation tickets, discuss overall documentation structure, >>> make docbuilding more robust >>> * Sage Infrastructure (improving the patchbot; common login for trac, >>> github, google, zulip using OAuth; investigate options for in-line code >>> review....) >>> * Sage's packaging and build system >>> * Infrastructure for more random testing, speed regression testing >>> * Interacts and interactive mathematics >>> * Comparing Magma and Sage >>> * Additional interfaces (Macaulay2....) >>> >>> And on the mathematical side: >>> * p-adics >>> * function fields >>> * linear algebra >>> * modular forms >>> * representation theory >>> * polyhedral geometry >>> * Coxeter group/root systems and braid groups >>> * Schubert polynomials >>> >>> If you'd like me to include other topics in the survey, chime in! >>> David >>> >>> >> -- >> 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+...@googlegroups.com <javascript:>. >> To post to this group, send email to sage-...@googlegroups.com >> <javascript:>. >> Visit this group at https://groups.google.com/group/sage-devel. >> For more options, visit https://groups.google.com/d/optout. >> > >
-- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
