queerviolet / bones

MIT License
36 stars 119 forks source link

Perhaps re-init Fullstack Bones as a standalone repo? #24

Closed glebec closed 7 years ago

glebec commented 7 years ago

Many of the issues on queerviolet/Bones are Fullstack-centric. This is because issues cannot be opened against forks (which Fullstack's Bones currently is). We could:

Thoughts?

omriAckley commented 7 years ago

I vote for bullet number 2, transferring ownership. Seems like the "root" skeleton should be under Fullstack.

glebec commented 7 years ago

@queerviolet — any thoughts?

queerviolet commented 7 years ago

Huh. I didn't realize there was any "root" repo--that's a concept foreign to git. Can we just open issues against the Fullstack fork?

If that doesn't work, there's no reason to "transfer ownership", per se. We could just clone bones and push a new repo.

glebec commented 7 years ago

Can we just open issues against the Fullstack fork?

Annoyingly, that doesn't seem to be possible. Blah.

We could just clone bones and push a new repo.

Yeah, that's my first suggestion in the top comment — I have no opinion between ownership vs standalone repo. I've used a standalone clone at least once before and it worked fine, just requires an extra step to manually transfer any existing issues. EDIT: though actually I don't know that "transferring ownership" also moves over the issues — I just assume so but haven't tested it.

glebec commented 7 years ago

Good news everyone! It turns out forks CAN have issues — but you have to turn them on manually. I just did so for Fullstack and I'm going to port many / most of the issues on https://github.com/queerviolet/bones over to https://github.com/fullstackacademy/bones.

glebec commented 7 years ago

This issue was moved to FullstackAcademy/bones#73