github repo

[Nathan Naze]

To gauge interest, how useful would a github mirror (or migration as
primary repo) be to folks using the library?

Nathan

[Daniel Steigerwald]

I was maintaining a clone on github, because google code does not support git protocol. Recently I found that Bower supports git+https so personally I don't need it.

  "dependencies": {

    "closure-compiler": "http://dl.google.com/closure-compiler/compiler-latest.zip",

    "closure-library": "git+https://code.google.com/p/closure-library/"

  }

Mirror itself does not make sense. Moving to GitHub entirely does .-)

[Nathan Naze]

> Mirror itself does not make sense. Moving to GitHub entirely does .-)

Using MOE [1], it's easy enough to for us to point our pushes at any
repo, and it's just a script, so we can update it to push to
either/or/both when we push.

I mostly would like to know, in general, would it be a sufficient
benefit to justify the work to either mirror or migrate.

Nathan

[1] https://code.google.com/p/make-open-easy/

> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Closure Library Discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to closure-library-d...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Nick Santos]

I think it would be worthwhile.

github does a better job that code.google.com at integrating the
documentation, patch submissions, and bug tracker with the main repo.

The time you'll save on accepting small documentation fixes will, I
think, make up for the small marginal cost of adding a second MOE
mirror.

[Tom Payne]

What's the plan for the bug tracker? Will existing issues at

  https://code.google.com/p/closure-library/issues/list

be moved to GitHub as well?

[Andre Tannus]

I also think it would be worthwhile.

André Tannús | Epungo | +55 11 2389-4360 

[thanpolas]

A mirror would be useless, a migration on the other hand... all my $$$$$$$

[Nathan Naze]

>What's the plan for the bug tracker? Will existing issues at
https://code.google.com/p/closure-library/issues/list
be moved to GitHub as well?

Yes, we'd write a small script to migrate existing issues.

[Lukáš Vlček]

+1 from me on migrating to github including issues.

Though I use maven artifacts I think community would benefit from this.

Regards,

Lukas

[Si Robertson]

Migrating to GitHub would be good. Mass project migration would be better :-)

I actually asked a related question today regarding the compiler (closure-compiler-discuss/huB-TnYcIdc) before being directed to this discussion.

[Daniel Steigerwald]

Switch to GitHub would be nice, but switch to CommonJS would be even more super-awesome.

On Sunday, April 13, 2014 8:08:55 PM UTC+2, Nathan Naze wrote:

[Yesudeep Mangalapilly]

That would be brilliant. Would love to see the entire closure stack on github.

[John Lenz]

CommonJS is a different topic.

--

[Nathan Naze]

Thanks for the feedback, all. We have decided to proceed with this.

We are moving the canonicals for the repos to github and will be turning down the previous locations shortly.

https://github.com/google/closure-library

Compiler, Templates, and Stylesheets will also be migrating.

Nathan

[Timo Lindemann]

That is great news! Thanks for this.

-T.

On Tue, 29 Apr 2014 16:04:25 -0400
"'Nathan Naze' via Closure Library Discuss"

[Nathan Wright]

This is great! 

Would it be possible to port closure-linter too? It's still running on SVN. I maintain a fork with a few patches and it'd be great if I could stop using git-svn, if at all possible.

[Andre Tannus]

Awesome!

[Lukáš Vlček]

Are you also going to use github issues for library as well? And if yes, are there any changes going into contributing process [1,2]?

Regards,

Lukas

[1] https://code.google.com/p/closure-library/wiki/Contributors

[2] https://github.com/google/closure-library/blob/master/CONTRIBUTING

[Nathan Naze]

Yes. We will be updating the documentation in the next few days.