Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

which repository should be in Metadata? #11

Closed
jtravs opened this issue Feb 1, 2014 · 10 comments
Closed

which repository should be in Metadata? #11

jtravs opened this issue Feb 1, 2014 · 10 comments

Comments

@jtravs
Copy link
Contributor

jtravs commented Feb 1, 2014

Currently metadata points to jverzani/Roots.jl

We should resolve which repository is the official one. I suggest we use this one, and give @jverzani commit access?

@StefanKarpinski see also discussion here: 7246e1ac37635041bf49bbe75651be5d0e9d5a65

@jverzani
Copy link
Member

jverzani commented Feb 1, 2014

Agreed, I thought it was like that already outside of the commit access.

@johnmyleswhite
Copy link

Yes, let's give @jverzani access. I'll look into doing that now.

@johnmyleswhite
Copy link

I didn't have high enough privileges to give @jverzani access.

@StefanKarpinski
Copy link

What needs to happen here?

@jverzani
Copy link
Member

I thought the decision was to keep this under JuliaLang. If that is the
case then:

  • change METADATA to point there and not my repository
  • merge a pull request, if suitable

If someone wants to give my push access that would be helpful going
forward, but isn't such a big deal.

On Mon, Feb 10, 2014 at 11:27 AM, Stefan Karpinski <notifications@github.com

wrote:

What needs to happen here?

Reply to this email directly or view it on GitHubhttps://github.com//issues/11#issuecomment-34650821
.

John Verzani
Chair, Department of Mathematics
College of Staten Island, CUNY
verzani@math.csi.cuny.edu

@StefanKarpinski
Copy link

Sorry about that – I could have sworn I'd already added you. You've got push access now.

@jverzani
Copy link
Member

Hope I'm not missing something obvious, but I don't seem to be able to merge #12, which I was hoping to do before updating METADATA with the correct url.

@jwmerrill
Copy link
Contributor

Bump.

Would be nice to have the official version of this package settled.

@johnmyleswhite
Copy link

Bump.

@jverzani
Copy link
Member

Hopefully fixed with 9416279 (manual edits seems to be correct)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants