Can we combine our boilerplates?

[matteodem]

I also created one, the features currently are:

• Comprehensible folder structure
• TDD / BDD with laika
• Multi page apps with iron-router
• A way to load fixtures (as of now no external packages used for that)
• meteor-boilerplate console tool, which helps on creating views, routes and so on

More info here: http://matteodem.github.io/meteor-boilerplate/

I'd love to team up or anything like that.

[ryw]

Hi — looks like we're pretty close to compatible.

• We haven't started doing TDD/BDD yet — but we need to start. We should probably have specs for sign-in, sign-up, sign-out out of the box, that the user can then build upon.
• We love iron-router
• We're big into fixture usage, and are doing it pretty similar to how you do it, so compatible there
• We were just talking last week about doing a console tool — so that's definitely a match
• We've built an accounts-ui replacement (https://github.com/BeDifferential/accounts-entry) that we think is a better standard vs. accounts-ui — curious to get your feedback on that. You can see it in action @ http://supporter.io and http://makeuphaulic.com/sign-up and have implemented signup code too http://new.differential.io/sign-up

So we'd need to communicate a bit to ensure we all agree on best practices, but that sounds fun to me :)

/cc other Differential peeps @dapearce @queso @hellogerard @schnie @cfly15

[queso]

Yeah, I could see us working together for sure, but I think accounts-entry is a must for us, we find styling and usage to be too hard with accounts-ui, so we built our own.

[matteodem]

Oh I love this accounts-entry, just tried it out. So how shall we integrate all of this? Also folder structure wise. Is there any better place to discuss than here?

Thanks for the rapid answers :+1:

[ryw]

Also - there's the coffescript thing :) We're pretty into it — how strongly do you feel about keeping your code in regular JS?

[matteodem]

I tried out coffeescript some time ago and I don't dislike it, but the thing is: to have everyone be able to use the boilerplate we should create it as general as possible (if that makes any sense).

You may have seen that there's a blank branch on my boilerplate (https://github.com/matteodem/meteor-boilerplate/tree/blank)

Could be an option to have a seperate coffeescript branch?

[matteodem]

push.

[ryw]

Hi Matteo —

Sacha Grief just released his boilerplate – https://github.com/SachaG/Void

I'm thinking a boilerplate app will likely be a fairly personalized, opinionated decision for each development team, so rather than trying to merge into one codebase, we should keep an eye on each other's repos, steal ideas from each other, and link to each other in our docs...

/cc @SachaG

[SachaG]

I'm not opposed to merging the projects down the road (after all, no need to duplicate work), but there's probably a lot of things on which we'll have a different opinion, and I'm not sure how we'd decide?

So at least for now, I'd like to keep mine separate to get some feedback on the structure, organization, etc. @matteodem I really like the CLI tool though, I was thinking about doing something similar :)

[matteodem]

I'd also like to merge our boilerplate's if possible. There are a lot of topics like using coffeescript, folder structure and so on but it'd be awome if we could decide on something.

Otherwise if there's no way to merge it then it's fine for me too, just saying it would be nice to be working on one boilerplate.

[SachaG]

Did you post your own boilerplate to the Google group? Did you get any feedback on it? Personally I really like most of what you did, except that the code is a bit too fragmented for my taste, I think you could get rid of some of these directories.

[matteodem]

No, I didn't. Here's the post: https://groups.google.com/forum/#!topic/meteor-talk/O31447OeLyg

[matteodem]

Sorry to bug you guys but do we now want to actively try to combine our boilerplates (maybe by sharing a list of the things we absolutely need to have / things that are optional) or not?

I think it's possible, since there are already some awesome boilerplates (https://github.com/ngbp/ng-boilerplate) out there. Which do it right, in terms of:

• They have the right sense of what they & most people need and what not
• They provide an easy way to set it up
• Most of the development is at one place, repository

What do you think?

[SachaG]

Again, I'm ok with the idea of combining them down the road, but I just came out with mine and I don't even know if anybody's used it yet or what people like/dislike. So it seems a bit premature to merge the projects since we wouldn't know what to pick from each one, imho.

[matteodem]

okay, then let's stop the idea for now and we'll see how it goes later