Thanks Aaron. We've been working on this application https://pydy.org/gsoc_2013_organization_application (which takes a lot of inspiration from SymPy's work). We'll give it a shot and hopefully we can round up several students to work on a couple projects in SymPy and maybe some outside.
Jason moorepants.info +01 530-601-9791 On Sun, Mar 10, 2013 at 3:14 PM, Aaron Meurer <asmeu...@gmail.com> wrote: > Python is now accepting applications for projects to work as mentoring > organizations for them. See > http://wiki.python.org/moin/SummerOfCode/2013. You can also fill out > this form > https://docs.google.com/forms/d/12t6trgG_X9ZWE6Rj1VgkTTeDqtMfL9gyhsLRUvOFdI8/viewform > . > If you think there's a pretty good chance that you might have some > projects that live mostly outside the scope of SymPy itself, you might > want to do this. > > Aaron Meurer > > On Tue, Feb 26, 2013 at 1:20 AM, Jason Moore <moorepa...@gmail.com> wrote: > > Cool, Luke has the ball rolling with the Github folks. They said they can > > give it to us if there is no activity for 6 months, so we may eventually > get > > it. > > > > Jason > > moorepants.info > > +01 530-601-9791 > > > > > > On Mon, Feb 25, 2013 at 9:44 PM, Aaron Meurer <asmeu...@gmail.com> > wrote: > >> > >> Great. According to > >> https://help.github.com/articles/name-squatting-policy, name squatting > is > >> prohibited, and it looks like that account has absolutely no activity. > The > >> github guys are pretty helpful, and they care about their users, so I'm > >> pretty confident you'll get it. > >> > >> Contrast that with twitter. I tried several times to get access to > @sympy, > >> until they eventually just told me that they don't release accounts, > even > >> unused ones. > >> > >> Aaron Meurer > >> > >> On Feb 25, 2013, at 10:32 PM, Jason Moore <moorepa...@gmail.com> wrote: > >> > >> We are already trying to get it. Someone seems to be squatting the name. > >> > >> Jason > >> moorepants.info > >> +01 530-601-9791 > >> > >> > >> On Mon, Feb 25, 2013 at 8:28 PM, Aaron Meurer <asmeu...@gmail.com> > wrote: > >>> > >>> Cool. I like where this is going. You might want to see if you can get > >>> access to https://github.com/pydy somehow (or is that already you > guys who > >>> own that?). > >>> > >>> Aaron Meurer > >>> > >>> On Feb 25, 2013, at 5:19 PM, Gilbert Gede <gilbertg...@gmail.com> > wrote: > >>> > >>> I added a few more points to our entry on the Ideas page, and my name > as > >>> a mentor. > >>> > >>> We came up with a rough roadmap for PyDy (http://pydy.org/roadmap), > and I > >>> actually think there is enough work for a student's GSoC project that > would > >>> be entirely within SymPy. That being said though, at this point it > would be > >>> more beneficial (for both groups) to do some work on things outside the > >>> SymPy codebase. There's quite a bit of work to go on bringing > >>> physics.mechanics from where it is now to where it is accessible by > "the > >>> masses", which would increase visibility for SymPy. We should probably > put > >>> "Powered by SymPy", or something like that, on the PyDy page, and try > and > >>> show of some of SymPy's non-mechanics abilities within the PyDy > examples. > >>> > >>> But for now (this year), I agree that work on PyDy could still be a > SymPy > >>> project. > >>> > >>> -Gilbert > >>> > >>> On Monday, 25 February 2013 12:31:54 UTC-8, Aaron Meurer wrote: > >>>> > >>>> On Feb 25, 2013, at 11:04 AM, Dale Lukas Peterson <hazel...@gmail.com > > > >>>> wrote: > >>>> > >>>> > On Sat, Feb 23, 2013 at 3:32 PM, Aaron Meurer <asme...@gmail.com> > >>>> > wrote: > >>>> >> pydy.org gives a 404. You might want to fix that. > >>>> > > >>>> > I'm not sure why pydy.org was 404'ing, it is fine now. It is > hosted > >>>> > on a AWS t1.micro instance, so maybe it just got briefly overloaded. > >>>> > > >>>> >> You should also contact the SymPy list, as they will probably be > the > >>>> >> mentoring organization that you will apply to (unless you guys have > >>>> >> some project that would live outside the SymPy code base, in which > >>>> >> case, it can possibly also go under the umbrella of another > project, > >>>> >> such as Python). > >>>> > > >>>> > With regards to the mentoring organization, we are interested in > >>>> > development of some things which are related to > >>>> > sympy.physics.mechanics but are not symbolic in nature and as such > >>>> > might not make sense to be part of sympy. Where the boundary is > >>>> > exactly I am not certain, but I think the line is probably somewhere > >>>> > near the point where sympy expressions get output as C code that is > >>>> > then compiled to do some sort of numerical study. We have some ideas > >>>> > of things we'd like to do be able to (in a generic sense) with this > >>>> > numerical code, and it doesn't seem like this belongs in sympy. So > we > >>>> > were considering creating a project that depends on sympy and > >>>> > specifcally sympy.physics.mechanics but isn't necessarily part of > it. > >>>> > This has code maintenance issues though, so we should verify that > this > >>>> > is absolutely necessary before we go this route. > >>>> > > >>>> > If people have thoughts on this, I would love to hear them. > >>>> > >>>> This is a great example of what Matthew suggested earlier on this list > >>>> about using GSoC to support external projects that use SymPy. So even > >>>> if most of the code doesn't directly go in SymPy, we could still > >>>> consider "hosting" such a project. If it really is completely separate > >>>> from SymPy (except for the inevitable bug fix patches to SymPy), you > >>>> might want to have the student also apply to Python. Then they will > >>>> have a better chance of being accepted regardless of how the slots > >>>> work out. If you do decide to go this route, you should decide soon, > >>>> as Python requires orgs that they umbrella to apply to them. > >>>> > >>>> Aaron Meurer > >>>> > >>>> > > >>>> >> You should also read > >>>> >> https://github.com/sympy/sympy/wiki/GSoC-2013-application-template > . > >>>> >> In > >>>> >> particular, we require at least one patch to SymPy to be accepted. > >>>> > > >>>> > Definitely. > >>>> > > >>>> >> By the way, can you guys make sure that > >>>> >> https://github.com/sympy/sympy/wiki/GSoC-2013-ideas is up-to-date > >>>> >> with > >>>> >> all the potential ideas for the mechanics module? > >>>> > > >>>> > I have added a few ideas related to the sympy.physics.mechancis to > the > >>>> > bottom of the GSoC-2013 ideas list. I have added my name to the list > >>>> > of potential mentors and would be interested in mentoring something > >>>> > related to common subexpression elimination or > >>>> > sympy.physics.mechanics. > >>>> > > >>>> > Luke > >>>> > > >>>> > -- > >>>> > 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. > >>>> > 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?hl=en. > >>> 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?hl=en. > >>> 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?hl=en. > >> 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?hl=en. > >> 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?hl=en. > > 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?hl=en. > 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
