Move gulp repo to gulpjs/gulp, and create gulpjs.github.io repo for site about gulp HOT 12 CLOSED

@gratimax I was planning to put it on GH pages already.

Moving the repo: I was planning on keeping all community material (demos, the website, artwork, etc.) on the gulpjs repo + any new code + gulp util. If there was a way to transfer the repo while keeping all of the info in tact (stars, wiki, forks, watchers, etc.) I would be open to moving the main repo.

Plugins by gulp authors: I don't like having "official" plugins either because it makes others less likely to create plugins that compete with ours. I would actually like to give ownership of those plugins away at some point so somebody else can maintain them.

Plugin search: I was thinking of making a client-side library that handles most of the work (npm calls, gh calls, caching, etc.) so other sites can use it. People have reinvented the wheel a lot here and it would be good to solve the problem once and for all. I've made the gulp-www repo so we can start throwing around ideas.

https://github.com/gulpjs/gulp-www

from gulp.

If there was a way to transfer the repo while keeping all of the info in tact (stars, wiki, forks, watchers, etc.) I would be open to moving the main repo.

There is: https://github.com/blog/1508-repository-redirects-are-here

from gulp.

@contra Cool. When you move a github repo, basically all that happens is the url changes(there's a redirect). I don't think you even need to update your remotes. All the information is kept, like wikis, pull requests, issues, etc.(fun fact: github wikis are actually their own mini-repos connected to the main repository). See here.

from gulp.

@gratimax @sindresorhus Nice! I'm up for it then. I'm in the process of breaking some more stuff out of gulp core/gulp-util into modules so I will transfer the repos when I'm done with that

from gulp.

So I've been tinkering with this for a while, and I haven't been able to find a way to get this to work on the client-side. There doesn't seem a way to access the npm apis cross domain from the client side without running into some kind of block. So it might have to be at least partially a server-side app.

from gulp.

@gratimax yes, there is: sindresorhus/old-gruntjs-site@e2523ea#diff-77ab163850ef0fa98d6a9ee9fb6bbcafR60 but not recommended as it doesn't scale and npm is so slow.

from gulp.

It may be true that it does not scale well, but I built a pretty good prototype already. For me, it takes about a second to load the plugins at first, and on subsequent loads it is essentially instant. This is because there are only 54 plugins, but when that starts to become an issue, it wouldn't take too long to just move some stuff to the backend.

from gulp.

@gratimax Super nice! I think we can keep a cache of the gh info + the npm results somewhere and update it hourly or something. DO sponsored us with some credit so we can run it there.

from gulp.

@contra

I think we can keep a cache of the gh info + the npm results somewhere and update it hourly or something.

Good idea to cache, because I was unable to implement keeping track of stars on a project, as github fails when the number of api requests is above 60 an hour.

DO sponsored us with some credit so we can run it there.

Sorry, what?

from gulp.

@gratimax DO = Digital Ocean

from gulp.

Site is at https://github.com/gulpjs/gulpjs.github.io

I'll move the repo over once I close out all of the current issues

from gulp.

done

from gulp.