In reply, I would say the first place to start becoming a contributer is much like in the Rails world. First you fork/modify someone else's code and submit a patch back to them (or continue the fork). A good place to learn about merb, that I realized was actually in creating a slice (merb-gen slice <name>) and contributing small little tweaks to other peoples code. The first project I worked on was submitting a patch to merb-auth-slice-activation. From there I surfed other addons (outside of merb's core app) and moved from there. If you really want to start contributing to the merb core and merb more packages, I would start with what I stated above. As time goes on, you will be more comfortable moving around merb that you can insert patches and then features...etc. If you want a good playground, maybe even work on merb- book or merbherd on github (yes, the latter is my own project for the community), but its a good starting place. Lastly, github guides make using git fairly easy, but if you want direct help, feel free to ask on IRC - jstad.
Hope this SOMEWHAT helps, Justin On Dec 19, 5:33 pm, Jon Hancock <[email protected]> wrote: > once again, you've written my thoughts exactly. I also want to > contribute but simply don't know how due to the same reasons you > give. I look forward to seeing any more clues you put together. > thanks, Jon > > On Dec 20, 1:30 am, cult hero <[email protected]> wrote: > > > The other night I made and submitted a patch following a guide I found > > through Google. My methods to get to that point were, to say the > > least, a hack job! The patch worked though and I'm using it locally. > > Trouble is, I went in and modified my installed gem which doesn't seem > > like the proper way of doing things. On top of that, I ran this > > command today to check further into my patch because of a comment on > > Lighthouse: > > > git clone git://github.com/wycats/merb-core.git > > > So I go looking into the file (builder.rb in forms) and couldn't find > > some code I was SURE was in there. Sure enough, it was removed. So, I > > wanted to see if the problem I fixed was fixed in some other way. This > > is where I got stuck. > > > (As a side note, why is the nightly gem 1.0.6.0.1 when the current gem > > is 1.0.6.1? Is the nightly gem being updated?) > > > The moral of the story is this: I liked patching Merb and I'm not > > nearly as bone-headed as I thought because I was able to follow a > > large portion of the code I was reading through. I'd like to > > contribute but I've never done it before (to any project). I don't > > know how to make a gem (although I'm sure there are guides 'a plenty), > > I don't know how to use git (again, I know there are guides) and on > > top of that there's rake, sake and thor! > > > Can someone give me a rundown of what I need to know or where to start > > and what tools I need and a general idea of where I should go? I'm not > > opposed to doing a lot of reading, but without some kind of direction > > I feel a bit overwhelmed AND Google, because of merb's current > > fluctuation, returns all kinds of useless and outdated information. > > > So... > > > I'd like the latest stable gem on my system concurrently with the > > development branch. In a perfect world, I could then merely change the > > gem version in my merb project to see how a project runs in stable > > versus my working version. Is this how testing is generally done or is > > there another method? > > > I wouldn't mind doing some kind of verbose write up after doing this > > too to get someone new familiar with git and a few of the other tools > > out there. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" 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/merb?hl=en -~----------~----~----~----~------~----~------~--~---
