Move Reagent to reagent-project about reagent

[Whoops]

As far as I can see that's probably the best way. I'd also add a link in this description of your fork to the one in the org, since initially at least yours will have higher Google power than the org, so people are likely to find it first.

I'll go ahead and destroy the existing repo in the reagent-project, since I don't think it serves a purpose anymore, and we can do the move whenever your comfortable, unless @yogthos or @seancorfield have something to add.

[holmsand]

Yes, a prominent link in README.md to the reagent-project repo should do the trick, I think. Anyway, Github will say "forked from reagent-project/reagent", if I'm not mistaken.

[seancorfield]

Yes, that's what I've done when I've moved projects under new organizations. Also turn off the wiki and issues in the forked-back repo so that folks don't read outdated docs or mistakenly open issues on the fork instead of the new, main repo.

[yogthos]

@holmsand @Whoops @seancorfield just wanted to touch base with you guys to see if we're ready to move the project over. It sounds like the plan is to transfer it over to reagent-project and then we should probably make a release from there with the updates for React 0.12. Any chance we could get that going this week or the next?

[holmsand]

@yogthos Sure, if it's ok with everyone, I can move the project over tomorrow. I'll also merge the 0.12 branch into master, so that people can do some testing with that before release (perhaps we should have some kind of half-formal release procedure?).

I think I'll start of with keeping the doc site where it is for the time being (until the future of the org's site is clearer), except that I'll change the links to the project to its new location. I (not surprisingly, perhaps) think that the current site is quite good, except that it obviously needs more documentation (and perhaps some links to users, related projects etc.).

The advantages of the current site are (in my head):

• it's easy to add live examples, since everything is built with Reagent already
• it's quite fast, both on first load (since every page is pre-rendered using node.js), and subsequently (since it is all Reagent)
• it exists :)

The main disadvantage is probably that it seems to be hard for other people to modify :)

If you guys agree, I could start on improving the site by adding some docs for reagent.core, and write a little guide on how it all works.

[seancorfield]

👍

[yogthos]

@holmsand sounds excellent. I can help testing against 0.12 once you've got it moved over then. Having some sort of a release process would probably be a good idea, @seancorfield might have the most experience in that department? :)

I definitely agree that the current docs page is excellent. It's very clear and easy to follow, while describing all the major aspects of Reagent. It does a great job of communicating what makes Reagent so fantastic to work with. :)

One thing we could probably do is add instructions how to create a new project from the template, so people can easily follow along.

Aside from that, I my vote would be to keep the existing page as is and then have a separate site for detailed documentation, tutorials, etc.

[seancorfield]

I'd just recommend publishing an 0.4.4-beta for testing (since we already had an 0.4.4-alpha from @Whoops repo) and leave that out there for a while (a month?), and then do a full 0.4.4 release.

[yogthos]

that sounds like a solid plan :)

[holmsand]

Ok, so now the project is reagent-project/reagent!

Welcome everyone to the brand new world of org-based reagent-ing!

[seancorfield]

Woohoo!!! Thank you @holmsand !

[yogthos]

exciting times ahead :)

[Whoops]

👏 exciting indeed!

[seancorfield]

Looks like this can be closed out as completed?

[yogthos]

Looks that way :)