On Mar 29, 10:01 pm, radisb <[email protected]> wrote: > To be honest i'd love to contribute, but since I ve never participated > in an open source project, I maybe dont know how thinks are supposed > to work in such a context of collaboration. For example, suppose I > change the code in action.lisp in a copy of the source tree i ve > downloaded. How will I know how to proceed?
Either get familar with Mercurial, our versioning control system, or create a traditional patch. How to do the latter is covered extensively on the net, just search for "create diff" or "linux create patch", this should give you a start. > Are there tests that should pass before i proceed to send the patch? > Am I required to provide my own test for the issue? Weblocks has a test suite, but it's deprecated. So you don't need to write tests. > More importantly, I dont feel I > know the code well enough to be able to create a suitable context to > verify the correctness of the fix. In a summary I don't know what > typical procedure or steps to follow when I want to contribute. Is > sending a patch sufficient? (To tell you the truth I ve never even > created a patch but that shouldnt be that difficult :) ) And to whom > should I send patches to? Please send patch files as attachments to the list and explain what the patch does. People will review it and if everything is well it will enter the main tree. Leslie -- You received this message because you are subscribed to the Google Groups "weblocks" 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/weblocks?hl=en.
