migrate hbs module to expressjs org about discussions HOT 17 CLOSED

@dougwilson hbs has been moved to pillarjs. added you as admin as well.

from discussions.

@defunctzombie who should I add to the org to move the hbs module?

from discussions.

@dougwilson I think only @donpark can move the repo due to admin limitations on user repos (one of the reasons to move it)

from discussions.

hi @dougwilson, thx for accepting hbs module into expressjs.

let me know when I should execute the move and feel free to remove me from the expressjs org once dust settles.

from discussions.

Thanks, everyone! Sorry for the delay. @donpark I just invited you to be an Owner of the pillarjs organization on GitHub to move the hbs project into.

from discussions.

@defunctzombie can you think of anything we need to do before moving?

from discussions.

No but once moved we will need to update the readme badges, CI links,
package file, other webhooks.

I believe github will redirect the old page to the new but if not we will
need a dummy repo directing users to the new location.

On Tuesday, September 13, 2016, Don Park [email protected] wrote:

@defunctzombie https://github.com/defunctzombie can you think of
anything we need to do before moving?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#36 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFLON44eIH7fcZp91SiFli0u1-o5mUgks5qpv1ygaJpZM4J3dY1
.

from discussions.

ok. transfer is in progress.
and it landed https://github.com/pillarjs/hbs

from discussions.

Will the project remain there or migrate to the expressjs org? Once it is in the final place let me know and I will update the readme and other links.

from discussions.

We have never really had this type of module before. With the current structure, pillarjs org should be the final resting place unless any other TC members have an opinion otherwise :)

from discussions.

Main motivation for moving hbs to express.js was to give it the attention it needs given that @defunctzombie no longer can.

Is it your understanding that this move fulfills that need @dougwilson? Do you have someone in the TC or supporters in mind who can take things over and address future needs as they arise? If so, I don't particularly care if it's under express.js or pillarjs.org. If not and pillarjs is some sort of open graveyard for expressjs related projects then we'll have to back out because that wouldn't be in the best interest of hbs users.

from discussions.

Both orgs are Express.js and have the same members, is under the current TC, etc. The different github orgs are simply a way to organize the dozens of modules 😊 I will be subscribing to the repo and making sure it gets the attention it needs. We had a brief discussion of even making it the default template engine for the express generator, which would also help ensure that

from discussions.

oops. you replied while I was editing my two-cents worth. What you wrote sounds good although I would rather see hbs included in a 'best combo meal' pack of sort for expressjs instead since TJ went to so much trouble to pull things out of it.

from discussions.

If not and pillarjs is some sort of open graveyard for expressjs related projects

It is absolutely in no way this. The expressjs org is really only to host express and middleware. Since this module is neither, it is organized into pillarjs, which are the modules that are the building blocks of express, for example the router, the file sending, etc. We have a third org jshttp,but that is for the low level http utilities, which this is not.

I understand if you want to "back out" simply because you expected it to be in the expressjs org, but if that were the case, that org would end up just being a disaster.

although I would rather see hbs included in a 'best combo meal' pack of sort for expressjs instead

Can you elaborate on this point :) ? I'm not sure what it meant, and I would love to understand your vision so we are all on the same page. Until we figure this out, you will definitely retain full control of your repo, so I hope you don't feel trapped in ant way... I am very much willing it has a good home and it is heading into some sort of grave yard.

from discussions.

The expressjs org is really only to host express and middleware. Since this module is neither, it is organized into pillarjs

Now I understand why pillarjs exists and it does make good sense. Description BYO Framework Framework confused me.

Express.js combo meal pack

The idea is to publish one or more express-xxx modules containing expressjs and a reasonable collection of middlewares and add-ons like hbs that developers typically install with expressjs. body-parser for example is commonly installed yet each new comer has to discover and integrate. These 'combo packs' are not boilerplates but more 'deluxe' version of expressjs. Closest example is Eclipse offering Eclipse Classic, Eclipse for J2EE, etc.

I hope that helps.

from discussions.

👍 Thanks for handling the migration. I'll update the links and webhooks. I believe this issue can be closed.

from discussions.

Awesome everyone! Let me know if there is anything you need :)

from discussions.