search

kbase / project_guides

This repo contains documents and guides that describe project principles, how-to docs, etc.
MIT License
7 stars 33 forks source link

Propose managing all issues via JIRA in the future, and disable gh-issues. #56

Closed fperez closed 9 years ago

fperez commented 9 years ago

Hopefully simpler workflow in the long run.

kkellerlbl commented 9 years ago

We will need to open up our public JIRA instance before we can post a link to it. Perhaps that should be a priority for the next maintenance week?

As a stopgap measure we could post a link to the contact page or the report-an-issue page.

fperez commented 9 years ago

Do you have an estimate of how much work that is? I don't want to schedule your time unduly.

But yes, this is something we've been talking about for a while, and we put it on our slides to DOE at the RSV, so it's time to do it.

kkellerlbl commented 9 years ago

I think most of the work is done, really. What I'd really like is people's feedback on what I've already done, to try to find weaknesses or problems. After that I think it's just making the appropriate changes in production JIRA, submitting a web form to Atlassian, and waiting to hear back.

fperez commented 9 years ago

Ok, let us know how we can give you that feedback, what to look at, etc. It would be great to have it out and start playing with it.

On Fri, Sep 25, 2015, 20:04 kkellerlbl notifications@github.com wrote:

I think most of the work is done, really. What I'd really like is people's feedback on what I've already done, to try to find weaknesses or problems. After that I think it's just making the appropriate changes in production JIRA, submitting a web form to Atlassian, and waiting to hear back.

— Reply to this email directly or view it on GitHub https://github.com/kbase/project_guides/pull/56#issuecomment-143393619.

kkellerlbl commented 9 years ago

Here's a link to the ticket with all of my notes, and a link to the dev JIRA instance I've been using for testing.

https://atlassian.kbase.us/browse/KBASE-2122?focusedCommentId=22090&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-22090

(I don't want to post a link to the dev JIRA, just in case I missed something that allows it to be exploited. I don't think I did but I'd feel better if others could try to break it and confirm they can't.)

dangunter commented 9 years ago

I can't get to that instance. I'm at home. But I thought the point was to allow anyone from anywhere on the internet.

kkellerlbl commented 9 years ago

Yes, we will open our production instance to the world when it's ready.

I didn't want the dev instance too open since I don't know for sure how secure it is. If you have a static IP I can open up the dev instance to you (email me, don't post here), or you can forward ports from login1, or if you want to VPN in to LBL I can open up that address space.

fperez commented 9 years ago

But @kkellerlbl, do you basically agree with the gist of this PR? I really don't see us managing both JIRA and a ton of discombobulated github issues all over the place...

kkellerlbl commented 9 years ago

Hi Fernando, yes, I agree we should use just JIRA and not github issues. I apologize, I didn't mean for my comment to seem like an objection. :)

fperez commented 9 years ago

No worries, just clarifying :)

It seems that we're converging on agreement here.

I'll let it simmer for another day or two, and if there's no further dissent, we'll move forward. This seems fairly uncontroversial.

fperez commented 9 years ago

Merging this, no big dissent apparent...