Migration to Jira - for those who contributed in GitHub Issues

[Stephen Mallette]

Hello All, 

This message is for all who contributed to the GitHub Issues in the TinkerPop3 repository:

https://github.com/tinkerpop/tinkerpop3/issues

by creating new issues or adding comments to issues. We are in the process of migrating from GitHub Issues to Jira hosted on Apache infrastructure:

https://issues.apache.org/jira/secure/Dashboard.jspa

Please keep reading if you intend to contribute to issues in the future in Jira and if you want to preserve your history of contribution from GitHub.

IF you have an existing Apache Jira account and a public GitHub email address and those two are the same, then the migration should link your account perfectly.  You have nothing to do.

IF you have an existing Apache Jira account and a public GitHub email address and those two are different, then you can either (1) make them the same OR (2) email me your GitHub username and Apache Jira email address so that we can make the proper link during migration.  If you do not do this, you will end up with two accounts in Apache Jira and Apache infrastructure will likely not want to take the time to handle the merge.  

IF you have an existing Apache Jira account and a private GitHub email address, please email me your GitHub username and email address used by your Apache Jira account so that we can make the proper link during migration.  

IF you do not yet have an Apache Jira account, the migration will create one for you automatically, provided that you have a public email address in GitHub (i.e. the new Jira Account will be tied to that email address).  If you do not have a public email address, please send me the email address you'd like to see used in Jira along with your GitHub account name and we will make sure it gets setup properly.  Note that in this case, your username from GitHub will become the username in Apache Jira.  If that username is already taken, your Jira username will become your GitHub username with a "-tinkerpop" suffix.  If the possibility of such a naming scheme bothers you, I suggest that you create your own Apache Jira account and then consider the above three IFs.

I think that covers all the scenarios we've considered.  Please post back if you don't fit in somewhere.  For those sending github usernames/jira emails to me, please submit them by 3/13/2015 to ensure that you get into the migration.  

Thanks,

Stephen

[Stephen Mallette]

Just a quick reminder to those who intended to take some action regarding the GitHub/Jira migration and haven't.  I still intend to keep the deadline for such actions as 3/13/2015.  After that time, we may execute the migration at any time so you may not get another chance to make adjustments.  Thanks.

[Dmill]

Hey Stephen.

Just to make sure I'm all clear on how this works. I've created an account on Jira. I then set my github email to be the same one as the jira account. Is this sufficient ? (my github email is public)

[Stephen Mallette]

yes, if your github email is public and it matches the one you use in jira, we shouldn't have any problem migrating your account.

--
You received this message because you are subscribed to the Google Groups "Gremlin-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gremlin-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gremlin-users/c7765ffa-2112-4d5b-8ef1-4e129030c012%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Dylan Millikin]

Ok great, thanks!

--
You received this message because you are subscribed to a topic in the Google Groups "Gremlin-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/gremlin-users/gQHEVcJ-fZM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to gremlin-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gremlin-users/CAA-H43-VN9xnFinHLJjnrGp_2CrA29NyVCSEZQKTVnKZSiiKEA%40mail.gmail.com.