SciPy is a bit over a week away.  I'd like to resurrect this thread.  Here
are some ideas for sprints that would interest me or that have come up
recently


   - Assumptions
   - Managing auto-evaluation
   - Generic, non-expr Add/Mul container classes
   - Solve?
   - Breaking apart giant methods (e.g. Mul.flatten) into more smaller
   methods (e.g. _eval_rewrite_foo)  (I think that this idea scales well for a
   sprint)
   - Step-by-step evaluation (I think this is feasible once we have the
   above, possibly requiring some meta-programming magic)
   - I'd also love to chat about rewrite rules and patterns - that might
   just be my own passion though :-)
   - Release 7.3 (should this happen before GSoC gets into full swing?)


Aaron, you seem to have an encyclopedic recall of the issue tracker.  What
have been the commonly recurring issues over the years?  Can you make a
list for us to look over?

Also, there is the possibility of having a low-latency high-level meeting
about some issues.  Not a sprint, more of the opposite.  Here are some
vague thoughts


   - Money: How should we use our money?   Should we get more money?  Apply
   for a grant?  What would we do if we got it?
   - Direction:  Does anyone have any big ideas about how SymPy should
   evolve in the future?  Lets write a new roadmap.
   - Publications:  I could work on SymPy a lot more if I could justify it
   from an academic point of view.  I think many of us are in similar
   positions.  How can the community support this?
   - What's the plan for SymPy Live? (I notice that David Li will be
   attending)



On Tue, Jun 4, 2013 at 5:58 AM, Mary Clark <mary.spritel...@gmail.com>wrote:

> If I have time at the end of my project, I will try to do so!
>
>
>
> On Sunday, 2 June 2013 02:08:27 UTC+1, Aaron Meurer wrote:
>
>> I agree we should do this, though I'm not sure if the sprints are the
>> best place for it since few of us who will be there are familiar with
>> that part of the code. How much work is there to do?  Maybe you could
>> incorporate it into your GSoC project.
>>
>> Aaron Meurer
>>
>> On Sat, Jun 1, 2013 at 3:10 PM, David Joyner <wdjo...@gmail.com> wrote:
>> > On Sat, Jun 1, 2013 at 4:00 PM, Mary Clark <mary.sp...@gmail.com>
>> wrote:
>> >> What about reorganising the combinatorics module so that group theory
>> has
>> >> its own space?  It doesn't belong in combinatorics, really.
>> >>
>> >
>> > I like this idea. In fact, I think It was already suggested by Aaron
>> but maybe
>> > I misunderstood him.
>> >
>> >
>> >>
>> >> On Saturday, 1 June 2013 15:38:45 UTC+1, Stefan Krastanov wrote:
>> >>>
>> >>> I am somewhat hesitant to suggest anything without actually being
>> there to
>> >>> help, but maybe redoing the return values from `solve` could be an
>> >>> appropriate task.
>> >>>
>> >>>
>> >>> On 30 May 2013 22:12, Aaron Meurer <asme...@gmail.com> wrote:
>> >>>>
>> >>>> There are going to be several of us at SciPy 2013, and we plan on
>> >>>> having a sprint for SymPy. Any suggestions on what you would like to
>> >>>> see the sprint be about?
>> >>>>
>> >>>> Aaron Meurer
>> >>>>
>> >>>> --
>> >>>> You received this message because you are subscribed to the Google
>> Groups
>> >>>> "sympy" group.
>> >>>> To unsubscribe from this group and stop receiving emails from it,
>> send an
>> >>>> email to sympy+un...@googlegroups.com.
>> >>>> To post to this group, send email to sy...@googlegroups.com.
>> >>>>
>> >>>> Visit this group at 
>> >>>> http://groups.google.com/**group/sympy?hl=en-US<http://groups.google.com/group/sympy?hl=en-US>.
>>
>> >>>> For more options, visit 
>> >>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out>.
>>
>> >>>>
>> >>>>
>> >>>
>> >> --
>> >> You received this message because you are subscribed to the Google
>> Groups
>> >> "sympy" group.
>> >> To unsubscribe from this group and stop receiving emails from it, send
>> an
>> >> email to sympy+un...@**googlegroups.com.
>> >> To post to this group, send email to sy...@googlegroups.com.
>> >> Visit this group at 
>> >> http://groups.google.com/**group/sympy?hl=en-US<http://groups.google.com/group/sympy?hl=en-US>.
>>
>> >> For more options, visit 
>> >> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out>.
>>
>> >>
>> >>
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> Groups "sympy" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> an email to sympy+un...@**googlegroups.com.
>> > To post to this group, send email to sy...@googlegroups.com.
>> > Visit this group at 
>> > http://groups.google.com/**group/sympy?hl=en-US<http://groups.google.com/group/sympy?hl=en-US>.
>>
>> > For more options, visit 
>> > https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out>.
>>
>> >
>> >
>>
>  --
> You received this message because you are subscribed to the Google Groups
> "sympy" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sympy+unsubscr...@googlegroups.com.
> To post to this group, send email to sympy@googlegroups.com.
> Visit this group at http://groups.google.com/group/sympy?hl=en-US.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sympy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sympy+unsubscr...@googlegroups.com.
To post to this group, send email to sympy@googlegroups.com.
Visit this group at http://groups.google.com/group/sympy.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to