Vinzent Steinberg wrote: >>> 1) Like Robert's Rules of Order, before beginning to make a solution >>> for an issue, seek a "second" for your motion. That affirmation >>> would indicate that someone thinks your proposal for a solution is >>> worth pursuing. >> >> This is a general rule, it correlates with "release early, release >> often".
I guess one could gauge the extent on the fix. The smaller the fix, the less important this step is since it's more likely to get in and you (may) spend less time finding the solution. >> >> If you want to avoid "wasting time" (if you want to call it like >> this) >> it makes sense to speak about your plans with the community. "Getting >> your code in" is relatively easy in SymPy, compared to projects like >> Linux though. Somewhere in the introductory material, sympy has put out a good invitation to get involved. I've appreciated that. ... >> Please note that pull request are already much nicer than patches to >> the mailinglist, because they won't be forgotten. yes >> >> I agree that it makes sense to create a wiki page on "how to get your >> code into SymPy", which would be essentially your 4 points. >> Somewhere this point is raised: build community support and be clear about why your patch is important. I'll see if I can find that. /c -- You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sympy?hl=en.
