Move awestruct projects to a github organization such as https://github.com/organizations/awestruct/ about awestruct HOT 4 CLOSED

What sort of issues are you talking about, tickets? I think they'll just move over. If not I'm sure could ask github support to move them.

Sent from my iPhone

On Mar 3, 2012, at 15:44, Lance [email protected] wrote:

I think it's time we move awestruct to a github organization that, for starters contains https://github.com/bobmcwhirter/awestruct https://github.com/bobmcwhirter/awestruct.org and maybe a third repository for contributed extensions. In the long run, it will be easier to manage things like pull requests, releases, and issue management if we can broaden the scope of the project just a little bit.

I'd be thrilled to make this happen, and Bob and I have talked a little about it. I haven't done it yet, because I don't know how to best handle current and historical issues. Any ideas?

---

Reply to this email directly or view it on GitHub:
https://github.com/bobmcwhirter/awestruct/issues/84

from awestruct.

+1

The extensions repositories is the compelling reason we were looking for to make this move. I also think it's going to give the project more visibility in general.

from awestruct.

I think having a mailinglist, issue #74, is an important part of this maturation as well.

from awestruct.

Just thought of this one, would nabble's embeddable mailing list backed forum make for a good extension to add to the site?

Sent from my iPhone

On Mar 4, 2012, at 2:56, Dan [email protected] wrote:

I think having a mailinglist, issue #74, is an important part of this maturation as well.

---

Reply to this email directly or view it on GitHub:
https://github.com/bobmcwhirter/awestruct/issues/84#issuecomment-4308716

from awestruct.