Is it only me or does the ideas page is really showing HTML code instead of
parsed markdown output.

On Tue, Feb 16, 2021 at 7:41 PM Naman Nimmo <[email protected]> wrote:

> Hi everyone.
>
> I have also updated the GSoC ideas page by adding another physics-related
> idea on Control theory.
>
> https://github.com/sympy/sympy/wiki/GSoC-Ideas#symbolic-control-systems-sympyphysicscontrol
>
> Since the Control module
> <https://docs.sympy.org/dev/modules/physics/control/index.html> was added
> to SymPy last summer, it would be great to attract some users as it can
> turn out to be quite useful to them.
> Other fixes/features are also appreciated because of its early stages. :-)
>
> Have an amazing week!
>
> Regards,
>
> --
>
>
>
>
> On Tue, Feb 16, 2021 at 1:52 PM Gagandeep Singh (B17CS021) <
> [email protected]> wrote:
>
>> Hi,
>>
>> Ideas for Probability and Statistics are updated. Please visit,
>> https://github.com/sympy/sympy/wiki/GSoC-Ideas#probability
>>
>> Thanks.
>>
>> On Sat, Feb 13, 2021 at 3:40 AM Psycho-Pirate <[email protected]>
>> wrote:
>>
>>> Hey Aaron,
>>> I would like to help clean up the ideas page. Please let me know how you
>>> want me to proceed. Should I just search the tags related to ideas and see
>>> how much work has been done and how much can be done in the given coding
>>> period?
>>>
>>> Prakhar Saxena
>>>
>>> On Saturday, February 13, 2021 at 3:09:00 AM UTC+5:30 [email protected]
>>> wrote:
>>>
>>>> Reminder that our deadline to submit our application to Google is Feb
>>>> 19 (a week from today). I plan on working on the application next
>>>> week, but if anyone can volunteer to go through and clean up the ideas
>>>> page, that would be really helpful. Also reminder that if you are
>>>> potentially interested in mentoring to please add your name to list
>>>> https://github.com/sympy/sympy/wiki/GSoC-Ideas#potential-mentors
>>>>
>>>> Aaron Meurer
>>>>
>>>>
>>>> On Fri, Jan 29, 2021 at 5:55 PM Oscar Benjamin
>>>> <[email protected]> wrote:
>>>> >
>>>> > On Fri, 29 Jan 2021 at 23:32, Aaron Meurer <[email protected]>
>>>> wrote:
>>>> > >
>>>> > > On Fri, Jan 29, 2021 at 4:20 PM Oscar Benjamin
>>>> > > <[email protected]> wrote:
>>>> > > >
>>>> > > > Thanks Aaron for sorting this.
>>>> > > >
>>>> > > > I've removed the ODE systems idea from the ideas page as it has
>>>> been
>>>> > > > mostly sorted out by Milan Jolly last year. There is still work
>>>> to do
>>>> > > > but it is not such a high priority after Milan's work.
>>>> > > >
>>>> > > > The change to 175hrs which is basically 5 actual weeks which
>>>> places
>>>> > > > quite significant limits on what could be achieved. We should
>>>> think
>>>> > > > about how to break up a lot of these ideas and make them more
>>>> > > > manageable. For example the highest priority ideas are probably
>>>> things
>>>> > > > like the Risch algorithm, Cylindrical Algebraic Decomposition,
>>>> Karr
>>>> > > > etc. Each of those is way beyond 5 weeks though - we shouldn't
>>>> bother
>>>> > > > listing them there unless we can distil the idea down to more
>>>> > > > carefully described steps that are actually achievable.
>>>> > >
>>>> > > Yes, although I would argue that that has already been a problem.
>>>> We
>>>> > > haven't had much interest in these problems because they are too
>>>> > > unapproachable. I don't know if they can be split into smaller
>>>> > > problems, and if doing so would make them more approachable
>>>> (there's
>>>> > > also the issue that they are mathematically hard).
>>>> >
>>>> > I think that these problems would be more approachable if there was
>>>> > clear documentation explaining:
>>>> >
>>>> > 1. What is already implemented
>>>> > 2. What should ideally be implemented
>>>> > 3. What the next steps should be
>>>> > 4. Where to find more information
>>>> >
>>>> > The problem is when we have something like the Risch algorithm that
>>>> is
>>>> > partially implemented but it is difficult for any newcomer to
>>>> > understand what should actually be done to take it further. Listing
>>>> > the idea of "implementing the algorithm" in the GSOC page isn't very
>>>> > helpful if it doesn't represent any manageable piece of work.
>>>> >
>>>> > > > I think that it would be good to move all of these ideas to a
>>>> page
>>>> > > > like "old ideas" and say that if anyone wants to rejuvenate the
>>>> idea
>>>> > > > then it should be updated and reframed in a way that is suitable
>>>> to
>>>> > > > the new GSOC arrangement before being moved to the new ideas
>>>> page.
>>>> > > > Bigger goals like the Risch algorithm should be moved to
>>>> something
>>>> > > > like a "big ideas" page. Any ideas listed for GSOC need to be
>>>> specific
>>>> > > > and achievable. Open ended ideas should go somewhere else I
>>>> think.
>>>> > >
>>>> > > Feel free to refactor the page however you see fit. I deleted the
>>>> old
>>>> > > years pages because they were only confusing.
>>>> >
>>>> > Thanks for doing that.
>>>> >
>>>> > I guess what I'm saying is that we shouldn't allow any ideas to "roll
>>>> > over" from one year to another. I think that the ideas page should
>>>> > always be a page of up to date fresh proposals presented by currently
>>>> > available mentors.
>>>> >
>>>> > Or perhaps there should be a separation where there is a page of
>>>> > general "ideas" and then another page of off the shelf "projects"
>>>> that
>>>> > are suitable for the GSOC timeline.
>>>> >
>>>> > Either way if we want to make the most of GSOC then I think we could
>>>> > do better by giving better guidance to students.
>>>> >
>>>> > Oscar
>>>> >
>>>> > --
>>>> > 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 [email protected].
>>>> > To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/sympy/CAHVvXxSDX1r%2BR7zyU3uz2aa7X%2BRLy_hsXAyQagKrJCeQdkS3_A%40mail.gmail.com.
>>>>
>>>>
>>> --
>>> 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 [email protected].
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/sympy/2662f687-f5c2-4530-ab79-b2d8944b2db9n%40googlegroups.com
>>> <https://groups.google.com/d/msgid/sympy/2662f687-f5c2-4530-ab79-b2d8944b2db9n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>
>>
>> --
>> With regards,
>> Gagandeep Singh
>> Github - https://github.com/czgdp1807/
>> Linkedin - https://www.linkedin.com/in/czgdp1807/
>>
>> --
>> 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 [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/sympy/CAAvS0gWTiHW9s0Sab49%3DbHS3LqSECH9nkEmKHXUjvcByF%3DafAg%40mail.gmail.com
>> <https://groups.google.com/d/msgid/sympy/CAAvS0gWTiHW9s0Sab49%3DbHS3LqSECH9nkEmKHXUjvcByF%3DafAg%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
> --
> 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 [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sympy/CALkUZD%3Dg_KW9ZOZRsL%3DbheL15Ne%2Br-NFQUosVjR7d6mix8rxhQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/sympy/CALkUZD%3Dg_KW9ZOZRsL%3DbheL15Ne%2Br-NFQUosVjR7d6mix8rxhQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>


-- 
With regards,
Gagandeep Singh
Github - https://github.com/czgdp1807/
Linkedin - https://www.linkedin.com/in/czgdp1807/

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/CAAvS0gWQW76c50k%2B1853o1S%3D6XMxeYabwiq9yhDR6rQtAWjH3A%40mail.gmail.com.

Reply via email to