These are chat archives for bespokejs/bespoke

27th
Sep 2015
Dan Allen
@mojavelinux
Sep 27 2015 07:26
bespoke-blackout is now available: https://www.npmjs.com/package/bespoke-blackout
What do you think about the proposal for help text infrastructure? markdalgleish/bespoke.js#64
I think it would be really nice to have a help overlay in bespoke.js, but we need the plugins to coordinate in order to achieve it (without hardcoding all the bindings into a single plugin)
Rahman Usta
@rahmanusta
Sep 27 2015 08:06
@mojavelinux I tried it, it is very nice. I think, publication of deck API is important for us.
Dan Allen
@mojavelinux
Sep 27 2015 08:43
Indeed. I'm going to get started on that this week because we also need it for deck2pdf export. Should be a fairly simple plugin to write.
Rahman Usta
@rahmanusta
Sep 27 2015 08:44
:+1:
Dan Allen
@mojavelinux
Sep 27 2015 09:01
I'll be sure to discuss it here once I dive into the design and implementation
I'm happy to say that thanks to encouragement by Mark, I've also been making sure that all my plugins have 100% (or as close to 100% as feasible) test coverage. It sure does make sleeping easier at night :) not to mention how confident I feel making changes to the plugins.
I think that the highly modular design is a great motivator for writing tests and documentation.
It's also pretty fun to watch the tests run for bespoke-overview (enable Firefox or Chrome).
Rahman Usta
@rahmanusta
Sep 27 2015 09:04
:+1: :clap:
Mark Dalgleish
@markdalgleish
Sep 27 2015 21:40
@mojavelinux just set up the bespokejs org and added you
I haven't moved any repos across yet, though
@mcollina would you be keen to be included, while I'm at it?
Dan Allen
@mojavelinux
Sep 27 2015 22:37
Joined!
Mark Dalgleish
@markdalgleish
Sep 27 2015 22:54
Worried that we'll lose this chat when I move the repo
Dan Allen
@mojavelinux
Sep 27 2015 23:02
I've moved a bunch of repositories, so I can shed some light on that.
When you move a repository, GitHub sets up a redirect so the old URL and the new URL are the same as far as any external service is concerned. It's almost like you've added an additional URL rather than remove an existing one.
You can then decide to fork the repository so that the old URL becomes your fork with a clear link to upstream. That still keeps that URL in place, but now it's a downstream instead of a redirect. It's up to you if you want to take that step, but I think the maintainers should use the same workflow as the contributors (pull requests from a fork)
Either way, the original URL never goes away
Bottom line, I'm confident this chat won't disappear. But, of course, you'll be able to setup a new chat at the new location.
Dan Allen
@mojavelinux
Sep 27 2015 23:08
I've also observed that Travis CI automatically updates itself to point to the new repository location. So it follows the redirect that GitHub sets up. It's smart like that.
Mark Dalgleish
@markdalgleish
Sep 27 2015 23:14
yep, I know that GitHub does the right thing :)
it's Gitter that I'm not sure about
Dan Allen
@mojavelinux
Sep 27 2015 23:16
I guess what I was saying is that all the services I've seen so far get this right. But actually, I'll try something just to verify.
Okay, it appears that Gitter never changes the URL. So it keeps using the old URL and the room name stays the same.
So, no change in the Gitter interface.
Dan Allen
@mojavelinux
Sep 27 2015 23:22
Actually, I see it just updated the room name. So after a few minutes, it just updates the room name to the new repo name transparently. So it behaves just like Travis CI.
(I tried this with a test repository, moving it around).
The chat content is never lost.
The chat follows the repository, in other words.
Only when I deleted the repository did the chat room disappear (after reload).
Matteo Collina
@mcollina
Sep 27 2015 23:32
I'm in for the bespokejs org. Also I can move my plugins over.
Dan Allen
@mojavelinux
Sep 27 2015 23:36
Cool!