Base my new app on kickstarter

[crussi]

I am not as familiar with Github as I should be, I apologize. If I base my new app on this kickstarter; what is the best way to sync new changes that happen to this repository? As I build up my app and I start adding new custom files; what is the best way to stay in sync with the architecture of this starter project? Is there an easy way to find out what changed from the time I cloned this repository? Or is there a way to merge the changes to my app?

Best regards,
Chris

[natecox]

That's a good question. Because this isn't a true framework, but rather a specification, keeping up to date with changes may not be straightforward.

@arunoda We should probably make an effort to maintain a change log at the very least.

[arunoda]

@natecox Yes. We'll make a one.
I'll do it.

[natecox]

@crussi I imagine that at some point we'll start seeing tooling and scaffolding being built around the Mantra spec, which may or may not help to alleviate the issue of keeping up to date with the spec.

[crussi]

Thank you all for your answers. I know timing is everything and I wish I had time to wait until things settled. But, @arunoda has such an amazing track record that I'm migrating over to using this approach right away. I guess my concern is founded on the unanswered question of whether there is large, medium or small changes to the overall approach in the foreseeable future. There has been a lot of debate about the structure of the app, for one thing, and I was concerned, that's all.

[natecox]

At this point if I had to guess I'd err on the side of caution and say 'expect large changes in the near future'. Still seeing structure changes, particularly in terms of modules, on a daily basis.

[makstr]

@crussi I plan to post some guidelines on how to track a repo and work on your code without breaking things. For now take a look I just updated https://github.com/mantrajs/meteor-mantra-kickstarter/.

[crussi]

@makstr ... that's good news. I've already hit the ground running with this kickstarter. Yes, that is awesome! I've been studying the code and trying to figure out the concepts. Reminds me of other frameworks with which I've worked in the past. Right now, as with many on the forums and crater.io, I am torn between the previous way of doing Meteor and the new way with Meteor 1.3. This morning I made a decision to move forward with this new approach. I hope I can learn enough about Github to contribute back to this kickstarter. I have done some advanced work with React sidebar navigation that stays in sync with the router, despite browser back/forward clicks and random routing changes in the url navigation bar and with FlowRouter.go() commands. It would be neat to have it evaluated and contribute back to the community.

[crussi]

Although I'm an experienced developer I have to ask a newb question. I really want to contribute back to this project. What are the basic steps I can take to 1) get a working branch of this project 2) make changes 3) request review for contribution. Can someone point me in the right direction? Even documentation would be helpful. I'm more used to other source control repositories, like TFS.

[lhaig]

I'm just commenting to say I like the idea around the kickstarter. Thanks guys