migration to github

classic Classic list List threaded Threaded
22 messages Options
12
Reply | Threaded
Open this post in threaded view
|

migration to github

Kallin Nagelberg
It's great to see ongoing development of Spock happening in github! Is the plan to move everything over there? It would be nice to have a master branch there; the lack of one now is a little confusing. I'd also love to see all the documentation and issues moved in there as I think it would help improve adoption of spock. Currently things seem a little scattered across this google group, the google code docs/wiki, github, and http://docs.spockframework.org/. 

At first I thought the project might be dead based on what I saw on the google code site (which is the first place you go when you search for Spock). I'm curious about what the future plans of Spock are. It's so easy to create a gradle project using spock now with the init task, so hopefully users can find everything they need to know in one place!

Cheers,
-Kal

--
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/spockframework.
For more options, visit https://groups.google.com/groups/opt_out.
Reply | Threaded
Open this post in threaded view
|

Re: migration to github

Peter Niederwieser
Administrator
We moved to GitHub years ago. Couldn’t find a way to delete the Google Code repo, but I’ll revisit that at some point. I recently wanted to move issues to GitHub, but it’s impossible because GitHub doesn’t offer any sensible way to import issues. We’ll probably move them somewhere else. As for the new docs, I haven’t yet decided where they’ll end up. In any case, you’ll find them via http://docs.spockframework.org.

Immediate plans are to get 1.0 out of the door, hopefully around the new year.

Cheers,
Peter

On 04 Dec 2013, at 03:44, Kallin Nagelberg <[hidden email]> wrote:

It's great to see ongoing development of Spock happening in github! Is the plan to move everything over there? It would be nice to have a master branch there; the lack of one now is a little confusing. I'd also love to see all the documentation and issues moved in there as I think it would help improve adoption of spock. Currently things seem a little scattered across this google group, the google code docs/wiki, github, and http://docs.spockframework.org/

At first I thought the project might be dead based on what I saw on the google code site (which is the first place you go when you search for Spock). I'm curious about what the future plans of Spock are. It's so easy to create a gradle project using spock now with the init task, so hopefully users can find everything they need to know in one place!

Cheers,
-Kal

--
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/spockframework.
For more options, visit https://groups.google.com/groups/opt_out.


signature.asc (817 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: migration to github

Guillaume Laforge
Even if you can't delete the Google Code project, can you at least update the website to remove all the documentation and details and replace that with a link to the GitHub project?

When someone searches for the Spock framework, she will find the Google Code project.
She will notice there's no news since 2012.
Nonetheless, she clicks on getting started, and notices examples using the very old Groovy 1.8.6 and Spock 0.6, also mentions of Gradle 1.0-milestone-9, etc...

So... remove all the wiki pages and point directly at the GitHub home!
Or better if you find a way, delete the Google Code project.

And icing on the cake... finish Spock 1.0 ;-)
Even what we have now could be 1.0 if you wanted!
Ideally, with the reporting features included.

Guillaume


On Wed, Dec 4, 2013 at 3:42 PM, [hidden email] <[hidden email]> wrote:
We moved to GitHub years ago. Couldn’t find a way to delete the Google Code repo, but I’ll revisit that at some point. I recently wanted to move issues to GitHub, but it’s impossible because GitHub doesn’t offer any sensible way to import issues. We’ll probably move them somewhere else. As for the new docs, I haven’t yet decided where they’ll end up. In any case, you’ll find them via http://docs.spockframework.org.

Immediate plans are to get 1.0 out of the door, hopefully around the new year.

Cheers,
Peter

On 04 Dec 2013, at 03:44, Kallin Nagelberg <[hidden email]> wrote:

It's great to see ongoing development of Spock happening in github! Is the plan to move everything over there? It would be nice to have a master branch there; the lack of one now is a little confusing. I'd also love to see all the documentation and issues moved in there as I think it would help improve adoption of spock. Currently things seem a little scattered across this google group, the google code docs/wiki, github, and http://docs.spockframework.org/

At first I thought the project might be dead based on what I saw on the google code site (which is the first place you go when you search for Spock). I'm curious about what the future plans of Spock are. It's so easy to create a gradle project using spock now with the init task, so hopefully users can find everything they need to know in one place!

Cheers,
-Kal

--
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/spockframework.
For more options, visit https://groups.google.com/groups/opt_out.




--
Guillaume Laforge
Groovy Project Manager
Pivotal, Inc.

--
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/spockframework.
For more options, visit https://groups.google.com/groups/opt_out.
Reply | Threaded
Open this post in threaded view
|

Re: migration to github

Kallin Nagelberg
Good advice Guillaume! To put this in context, I am starting a new project and decided to try out Spock, but didn't even find the github repo until I was a few days into it. I was very hesitant to even start learning Spock since it seemed dead based on what I was seeing on the google code site. I'm glad to hear that 1.0 is coming soon though! I am still curious though; is there plans for a master branch on github? It's a little confusing currently without one. 

Cheers,
-Kal

On Wednesday, December 4, 2013 6:51:19 AM UTC-8, Guillaume Laforge wrote:
Even if you can't delete the Google Code project, can you at least update the website to remove all the documentation and details and replace that with a link to the GitHub project?

When someone searches for the Spock framework, she will find the Google Code project.
She will notice there's no news since 2012.
Nonetheless, she clicks on getting started, and notices examples using the very old Groovy 1.8.6 and Spock 0.6, also mentions of Gradle 1.0-milestone-9, etc...

So... remove all the wiki pages and point directly at the GitHub home!
Or better if you find a way, delete the Google Code project.

And icing on the cake... finish Spock 1.0 ;-)
Even what we have now could be 1.0 if you wanted!
Ideally, with the reporting features included.

Guillaume


On Wed, Dec 4, 2013 at 3:42 PM, <a href="javascript:" target="_blank" gdf-obfuscated-mailto="7YYFy4CdgBkJ" onmousedown="this.href='javascript:';return true;" onclick="this.href='javascript:';return true;">pnie...@... <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="7YYFy4CdgBkJ" onmousedown="this.href='javascript:';return true;" onclick="this.href='javascript:';return true;">pnie...@...> wrote:
We moved to GitHub years ago. Couldn’t find a way to delete the Google Code repo, but I’ll revisit that at some point. I recently wanted to move issues to GitHub, but it’s impossible because GitHub doesn’t offer any sensible way to import issues. We’ll probably move them somewhere else. As for the new docs, I haven’t yet decided where they’ll end up. In any case, you’ll find them via <a href="http://docs.spockframework.org" target="_blank" onmousedown="this.href='http://www.google.com/url?q\75http%3A%2F%2Fdocs.spockframework.org\46sa\75D\46sntz\0751\46usg\75AFQjCNFRJxZJjFmZwyOpmG9I_CIWbHWOVw';return true;" onclick="this.href='http://www.google.com/url?q\75http%3A%2F%2Fdocs.spockframework.org\46sa\75D\46sntz\0751\46usg\75AFQjCNFRJxZJjFmZwyOpmG9I_CIWbHWOVw';return true;">http://docs.spockframework.org.

Immediate plans are to get 1.0 out of the door, hopefully around the new year.

Cheers,
Peter

On 04 Dec 2013, at 03:44, Kallin Nagelberg <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="7YYFy4CdgBkJ" onmousedown="this.href='javascript:';return true;" onclick="this.href='javascript:';return true;">kallin.n...@...> wrote:

It's great to see ongoing development of Spock happening in github! Is the plan to move everything over there? It would be nice to have a master branch there; the lack of one now is a little confusing. I'd also love to see all the documentation and issues moved in there as I think it would help improve adoption of spock. Currently things seem a little scattered across this google group, the google code docs/wiki, github, and <a href="http://docs.spockframework.org/" target="_blank" onmousedown="this.href='http://www.google.com/url?q\75http%3A%2F%2Fdocs.spockframework.org%2F\46sa\75D\46sntz\0751\46usg\75AFQjCNGu6SIxpSortkNstW8Lxc4rtZ7NGg';return true;" onclick="this.href='http://www.google.com/url?q\75http%3A%2F%2Fdocs.spockframework.org%2F\46sa\75D\46sntz\0751\46usg\75AFQjCNGu6SIxpSortkNstW8Lxc4rtZ7NGg';return true;">http://docs.spockframework.org/. 

At first I thought the project might be dead based on what I saw on the google code site (which is the first place you go when you search for Spock). I'm curious about what the future plans of Spock are. It's so easy to create a gradle project using spock now with the init task, so hopefully users can find everything they need to know in one place!

Cheers,
-Kal

--
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="7YYFy4CdgBkJ" onmousedown="this.href='javascript:';return true;" onclick="this.href='javascript:';return true;">spockframewor...@googlegroups.com.
To post to this group, send email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="7YYFy4CdgBkJ" onmousedown="this.href='javascript:';return true;" onclick="this.href='javascript:';return true;">spockfr...@googlegroups.com.
Visit this group at <a href="http://groups.google.com/group/spockframework" target="_blank" onmousedown="this.href='http://groups.google.com/group/spockframework';return true;" onclick="this.href='http://groups.google.com/group/spockframework';return true;">http://groups.google.com/group/spockframework.
For more options, visit <a href="https://groups.google.com/groups/opt_out" target="_blank" onmousedown="this.href='https://groups.google.com/groups/opt_out';return true;" onclick="this.href='https://groups.google.com/groups/opt_out';return true;">https://groups.google.com/groups/opt_out.




--
Guillaume Laforge
Groovy Project Manager
Pivotal, Inc.

Blog: <a href="http://glaforge.appspot.com/" target="_blank" onmousedown="this.href='http://glaforge.appspot.com/';return true;" onclick="this.href='http://glaforge.appspot.com/';return true;">http://glaforge.appspot.com/
Social: <a href="http://twitter.com/glaforge" target="_blank" onmousedown="this.href='http://www.google.com/url?q\75http%3A%2F%2Ftwitter.com%2Fglaforge\46sa\75D\46sntz\0751\46usg\75AFQjCNGCEf6mUIX8sOaMYOs7GBUoKkZLHA';return true;" onclick="this.href='http://www.google.com/url?q\75http%3A%2F%2Ftwitter.com%2Fglaforge\46sa\75D\46sntz\0751\46usg\75AFQjCNGCEf6mUIX8sOaMYOs7GBUoKkZLHA';return true;">@glaforge / <a href="https://plus.google.com/u/0/114130972232398734985/posts" target="_blank" onmousedown="this.href='https://plus.google.com/u/0/114130972232398734985/posts';return true;" onclick="this.href='https://plus.google.com/u/0/114130972232398734985/posts';return true;">Google+

--
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/spockframework.
For more options, visit https://groups.google.com/groups/opt_out.
Reply | Threaded
Open this post in threaded view
|

Re: migration to github

Kallin Nagelberg
In reply to this post by Peter Niederwieser
Re: importing issues;

I haven't tried it but others have seemingly faced the same problem and have devised some solutions though I cannot comment on their quality:

https://github.com/arthur-debert/google-code-issues-migrator
https://github.com/jeremyevans/gcit2ghi

and a simple CSV generator listed here:

http://stackoverflow.com/questions/17824401/how-do-i-export-issues-from-a-google-code-project-to-github

P.S.
Was great seeing you @ gradle summit this year Peter, hope to do it again in 2014!

On Wednesday, December 4, 2013 6:42:59 AM UTC-8, Peter Niederwieser wrote:
We moved to GitHub years ago. Couldn’t find a way to delete the Google Code repo, but I’ll revisit that at some point. I recently wanted to move issues to GitHub, but it’s impossible because GitHub doesn’t offer any sensible way to import issues. We’ll probably move them somewhere else. As for the new docs, I haven’t yet decided where they’ll end up. In any case, you’ll find them via <a href="http://docs.spockframework.org" target="_blank" onmousedown="this.href='http://www.google.com/url?q\75http%3A%2F%2Fdocs.spockframework.org\46sa\75D\46sntz\0751\46usg\75AFQjCNFRJxZJjFmZwyOpmG9I_CIWbHWOVw';return true;" onclick="this.href='http://www.google.com/url?q\75http%3A%2F%2Fdocs.spockframework.org\46sa\75D\46sntz\0751\46usg\75AFQjCNFRJxZJjFmZwyOpmG9I_CIWbHWOVw';return true;">http://docs.spockframework.org.

Immediate plans are to get 1.0 out of the door, hopefully around the new year.

Cheers,
Peter

On 04 Dec 2013, at 03:44, Kallin Nagelberg <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="s5remH0J3H4J" onmousedown="this.href='javascript:';return true;" onclick="this.href='javascript:';return true;">kallin.n...@...> wrote:

It's great to see ongoing development of Spock happening in github! Is the plan to move everything over there? It would be nice to have a master branch there; the lack of one now is a little confusing. I'd also love to see all the documentation and issues moved in there as I think it would help improve adoption of spock. Currently things seem a little scattered across this google group, the google code docs/wiki, github, and <a href="http://docs.spockframework.org/" target="_blank" onmousedown="this.href='http://www.google.com/url?q\75http%3A%2F%2Fdocs.spockframework.org%2F\46sa\75D\46sntz\0751\46usg\75AFQjCNGu6SIxpSortkNstW8Lxc4rtZ7NGg';return true;" onclick="this.href='http://www.google.com/url?q\75http%3A%2F%2Fdocs.spockframework.org%2F\46sa\75D\46sntz\0751\46usg\75AFQjCNGu6SIxpSortkNstW8Lxc4rtZ7NGg';return true;">http://docs.spockframework.org/. 

At first I thought the project might be dead based on what I saw on the google code site (which is the first place you go when you search for Spock). I'm curious about what the future plans of Spock are. It's so easy to create a gradle project using spock now with the init task, so hopefully users can find everything they need to know in one place!

Cheers,
-Kal

--
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="s5remH0J3H4J" onmousedown="this.href='javascript:';return true;" onclick="this.href='javascript:';return true;">spockframewor...@googlegroups.com.
To post to this group, send email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="s5remH0J3H4J" onmousedown="this.href='javascript:';return true;" onclick="this.href='javascript:';return true;">spockfr...@googlegroups.com.
Visit this group at <a href="http://groups.google.com/group/spockframework" target="_blank" onmousedown="this.href='http://groups.google.com/group/spockframework';return true;" onclick="this.href='http://groups.google.com/group/spockframework';return true;">http://groups.google.com/group/spockframework.
For more options, visit <a href="https://groups.google.com/groups/opt_out" target="_blank" onmousedown="this.href='https://groups.google.com/groups/opt_out';return true;" onclick="this.href='https://groups.google.com/groups/opt_out';return true;">https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/spockframework.
For more options, visit https://groups.google.com/groups/opt_out.
Reply | Threaded
Open this post in threaded view
|

Re: migration to github

Peter Niederwieser
Administrator
In reply to this post by Kallin Nagelberg
The fact that there is no `master` branch is by design. We maintain one branch per supported Groovy version, and cut separate release artifacts for each branch. As such there is no single `master`, and our branching model simply reflects this reality.

Cheers,
Peter

On 04 Dec 2013, at 18:48, Kallin Nagelberg <[hidden email]> wrote:

Good advice Guillaume! To put this in context, I am starting a new project and decided to try out Spock, but didn't even find the github repo until I was a few days into it. I was very hesitant to even start learning Spock since it seemed dead based on what I was seeing on the google code site. I'm glad to hear that 1.0 is coming soon though! I am still curious though; is there plans for a master branch on github? It's a little confusing currently without one. 

Cheers,
-Kal

On Wednesday, December 4, 2013 6:51:19 AM UTC-8, Guillaume Laforge wrote:
Even if you can't delete the Google Code project, can you at least update the website to remove all the documentation and details and replace that with a link to the GitHub project?

When someone searches for the Spock framework, she will find the Google Code project.
She will notice there's no news since 2012.
Nonetheless, she clicks on getting started, and notices examples using the very old Groovy 1.8.6 and Spock 0.6, also mentions of Gradle 1.0-milestone-9, etc...

So... remove all the wiki pages and point directly at the GitHub home!
Or better if you find a way, delete the Google Code project.

And icing on the cake... finish Spock 1.0 ;-)
Even what we have now could be 1.0 if you wanted!
Ideally, with the reporting features included.

Guillaume


On Wed, Dec 4, 2013 at 3:42 PM, pnie...@gmail.com <pnie...@gmail.com> wrote:
We moved to GitHub years ago. Couldn’t find a way to delete the Google Code repo, but I’ll revisit that at some point. I recently wanted to move issues to GitHub, but it’s impossible because GitHub doesn’t offer any sensible way to import issues. We’ll probably move them somewhere else. As for the new docs, I haven’t yet decided where they’ll end up. In any case, you’ll find them viahttp://docs.spockframework.org.

Immediate plans are to get 1.0 out of the door, hopefully around the new year.

Cheers,
Peter

On 04 Dec 2013, at 03:44, Kallin Nagelberg <kallin.n...@gmail.com> wrote:

It's great to see ongoing development of Spock happening in github! Is the plan to move everything over there? It would be nice to have a master branch there; the lack of one now is a little confusing. I'd also love to see all the documentation and issues moved in there as I think it would help improve adoption of spock. Currently things seem a little scattered across this google group, the google code docs/wiki, github, and http://docs.spockframework.org/

At first I thought the project might be dead based on what I saw on the google code site (which is the first place you go when you search for Spock). I'm curious about what the future plans of Spock are. It's so easy to create a gradle project using spock now with the init task, so hopefully users can find everything they need to know in one place!

Cheers,
-Kal

-- 
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to spockframewor...@googlegroups.com.
To post to this group, send email to spockfr...@googlegroups.com.
Visit this group at http://groups.google.com/group/spockframework.
For more options, visit https://groups.google.com/groups/opt_out.




-- 
Guillaume Laforge
Groovy Project Manager
Pivotal, Inc.


-- 
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/spockframework.
For more options, visit https://groups.google.com/groups/opt_out.


signature.asc (817 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: migration to github

Peter Niederwieser
Administrator
In reply to this post by Kallin Nagelberg
I researched these options, and either they weren’t functional (the Google Code REST API was shut down some time ago), or they weren’t adequate. I’ve meanwhile written my own (Geb-based) exporter, so that part is solved. However, there is no sensible way to import into GitHub these days, so we’ll have to move somewhere else.

Cheers,
Peter

On 04 Dec 2013, at 19:43, Kallin Nagelberg <[hidden email]> wrote:

> Re: importing issues;
>
> I haven't tried it but others have seemingly faced the same problem and have devised some solutions though I cannot comment on their quality:
>
> https://github.com/arthur-debert/google-code-issues-migrator
> https://github.com/jeremyevans/gcit2ghi
>
> and a simple CSV generator listed here:
>
> http://stackoverflow.com/questions/17824401/how-do-i-export-issues-from-a-google-code-project-to-github


signature.asc (817 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: migration to github

Rick Jensen
I believe Github has a rather robust API that includes managing issues. Since you have the export portion done, the import should be much easier.

Barring that, I'm sure there would be volunteers to manually port the issues over if that would help move things along and make the Spock world a better place. If this is something we (the community) should pursue, simply ask :)

- Rick

On Wednesday, December 4, 2013 7:19:17 PM UTC-6, Peter Niederwieser wrote:
I researched these options, and either they weren’t functional (the Google Code REST API was shut down some time ago), or they weren’t adequate. I’ve meanwhile written my own (Geb-based) exporter, so that part is solved. However, there is no sensible way to import into GitHub these days, so we’ll have to move somewhere else.

Cheers,
Peter

On 04 Dec 2013, at 19:43, Kallin Nagelberg <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="_43A5b8E5qcJ" onmousedown="this.href='javascript:';return true;" onclick="this.href='javascript:';return true;">kallin.n...@...> wrote:

> Re: importing issues;
>
> I haven't tried it but others have seemingly faced the same problem and have devised some solutions though I cannot comment on their quality:
>
> <a href="https://github.com/arthur-debert/google-code-issues-migrator" target="_blank" onmousedown="this.href='https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Farthur-debert%2Fgoogle-code-issues-migrator\46sa\75D\46sntz\0751\46usg\75AFQjCNGVsBpjIZAFrLN9SLanUHpXEo7CtQ';return true;" onclick="this.href='https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Farthur-debert%2Fgoogle-code-issues-migrator\46sa\75D\46sntz\0751\46usg\75AFQjCNGVsBpjIZAFrLN9SLanUHpXEo7CtQ';return true;">https://github.com/arthur-debert/google-code-issues-migrator
> <a href="https://github.com/jeremyevans/gcit2ghi" target="_blank" onmousedown="this.href='https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Fjeremyevans%2Fgcit2ghi\46sa\75D\46sntz\0751\46usg\75AFQjCNEg3hzQPZsQKu2deF1GV7KS5eev2w';return true;" onclick="this.href='https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Fjeremyevans%2Fgcit2ghi\46sa\75D\46sntz\0751\46usg\75AFQjCNEg3hzQPZsQKu2deF1GV7KS5eev2w';return true;">https://github.com/jeremyevans/gcit2ghi
>
> and a simple CSV generator listed here:
>
> <a href="http://stackoverflow.com/questions/17824401/how-do-i-export-issues-from-a-google-code-project-to-github" target="_blank" onmousedown="this.href='http://www.google.com/url?q\75http%3A%2F%2Fstackoverflow.com%2Fquestions%2F17824401%2Fhow-do-i-export-issues-from-a-google-code-project-to-github\46sa\75D\46sntz\0751\46usg\75AFQjCNHlawyHq3ATWTyt1aYvMK3qcNUxkQ';return true;" onclick="this.href='http://www.google.com/url?q\75http%3A%2F%2Fstackoverflow.com%2Fquestions%2F17824401%2Fhow-do-i-export-issues-from-a-google-code-project-to-github\46sa\75D\46sntz\0751\46usg\75AFQjCNHlawyHq3ATWTyt1aYvMK3qcNUxkQ';return true;">http://stackoverflow.com/questions/17824401/how-do-i-export-issues-from-a-google-code-project-to-github

--
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/spockframework.
For more options, visit https://groups.google.com/groups/opt_out.
Reply | Threaded
Open this post in threaded view
|

Re: migration to github

Peter Niederwieser
Administrator
As I said, GitHub doesn’t have an issue import API. They have an issue creation API, but using that means losing all sorts of information (e.g. association with issue reporter). They’ve also stopped doing manual imports, so unless you happen to have some connections there (mine didn’t help), GitHub is not an option.

Cheers,
Peter

On 05 Dec 2013, at 11:38, Rick Jensen <[hidden email]> wrote:

> I believe Github has a rather robust API that includes managing issues. Since you have the export portion done, the import should be much easier.
>
> Barring that, I'm sure there would be volunteers to manually port the issues over if that would help move things along and make the Spock world a better place. If this is something we (the community) should pursue, simply ask :)
>
> - Rick


signature.asc (817 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: migration to github

Russel Winder-2
In reply to this post by Guillaume Laforge
On Wed, 2013-12-04 at 15:51 +0100, Guillaume Laforge wrote:
> Even if you can't delete the Google Code project, can you at least update
> the website to remove all the documentation and details and replace that
> with a link to the GitHub project?

I did a short intro to Spock for Java folk at the LJC unconference a
couple of weeks back, and this was the biggest hurdle:

> When someone searches for the Spock framework, she will find the Google
> Code project.
> She will notice there's no news since 2012.

Dead project!

> Nonetheless, she clicks on getting started, and notices examples using the
> very old Groovy 1.8.6 and Spock 0.6, also mentions of Gradle
> 1.0-milestone-9, etc...
>
> So... remove all the wiki pages and point directly at the GitHub home!
> Or better if you find a way, delete the Google Code project.
>
> And icing on the cake... finish Spock 1.0 ;-)
> Even what we have now could be 1.0 if you wanted!
> Ideally, with the reporting features included.

I was pushing the data driven testing line and use of @Unroll, which is
a "huge win" for computational folk. Sadly many in the audience thought
JUnit4 handled this well with "theories". :-(
--
Russel.
=============================================================================
Dr Russel Winder      t: +44 20 7585 2200   voip: sip:[hidden email]
41 Buckmaster Road    m: +44 7770 465 077   xmpp: [hidden email]
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

--
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/spockframework.
For more options, visit https://groups.google.com/groups/opt_out.
Reply | Threaded
Open this post in threaded view
|

Re: migration to github

Russel Winder-2
In reply to this post by Peter Niederwieser
On Wed, 2013-12-04 at 20:03 -0500, [hidden email] wrote:
> The fact that there is no `master` branch is by design. We maintain one branch per supported Groovy version, and cut separate release artifacts for each branch. As such there is no single `master`, and our branching model simply reflects this reality.

Isn't this going to put off people trying to contribute on the grounds it is not idiomatic use of Git?

--
Russel.
=============================================================================
Dr Russel Winder      t: +44 20 7585 2200   voip: sip:[hidden email]
41 Buckmaster Road    m: +44 7770 465 077   xmpp: [hidden email]
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

--
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/spockframework.
For more options, visit https://groups.google.com/groups/opt_out.
Reply | Threaded
Open this post in threaded view
|

Re: migration to github

Russel Winder-2
In reply to this post by Peter Niederwieser
On Thu, 2013-12-05 at 11:54 -0500, [hidden email] wrote:
> As I said, GitHub doesn’t have an issue import API. They have an issue creation API, but using that means losing all sorts of information (e.g. association with issue reporter). They’ve also stopped doing manual imports, so unless you happen to have some connections there (mine didn’t help), GitHub is not an option.

Is BitBucket any better? If it is then ship everything there?

--
Russel.
=============================================================================
Dr Russel Winder      t: +44 20 7585 2200   voip: sip:[hidden email]
41 Buckmaster Road    m: +44 7770 465 077   xmpp: [hidden email]
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

--
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/spockframework.
For more options, visit https://groups.google.com/groups/opt_out.
Reply | Threaded
Open this post in threaded view
|

Re: migration to github

Peter Niederwieser
Administrator
In reply to this post by Russel Winder-2
Having a `master` branch isn’t the right fit for every project, and that’s why Git and GitHub allow for other designs. Our model is easy enough to explain and understand, but I’ll add something to the readme.

Cheers,
Peter

On 07 Dec 2013, at 13:41, Russel Winder <[hidden email]> wrote:

> On Wed, 2013-12-04 at 20:03 -0500, [hidden email] wrote:
>> The fact that there is no `master` branch is by design. We maintain one branch per supported Groovy version, and cut separate release artifacts for each branch. As such there is no single `master`, and our branching model simply reflects this reality.
>
> Isn't this going to put off people trying to contribute on the grounds it is not idiomatic use of Git?
>
> --
> Russel.
> =============================================================================
> Dr Russel Winder      t: +44 20 7585 2200   voip: sip:[hidden email]
> 41 Buckmaster Road    m: +44 7770 465 077   xmpp: [hidden email]
> London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder
>
> --
> You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
> To post to this group, send email to [hidden email].
> Visit this group at http://groups.google.com/group/spockframework.
> For more options, visit https://groups.google.com/groups/opt_out.


signature.asc (817 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: migration to github

Alex Anderson
Just wanted to comment that I've been happily using spock for 3 years,
but I didn't realise it was hosted on github - I thought it was on
googlecode.  And I'm fairly sure I've cloned the repository there a
couple of times for a poke around.

On 7 December 2013 21:54, [hidden email] <[hidden email]> wrote:

> Having a `master` branch isn’t the right fit for every project, and that’s why Git and GitHub allow for other designs. Our model is easy enough to explain and understand, but I’ll add something to the readme.
>
> Cheers,
> Peter
>
> On 07 Dec 2013, at 13:41, Russel Winder <[hidden email]> wrote:
>
>> On Wed, 2013-12-04 at 20:03 -0500, [hidden email] wrote:
>>> The fact that there is no `master` branch is by design. We maintain one branch per supported Groovy version, and cut separate release artifacts for each branch. As such there is no single `master`, and our branching model simply reflects this reality.
>>
>> Isn't this going to put off people trying to contribute on the grounds it is not idiomatic use of Git?
>>
>> --
>> Russel.
>> =============================================================================
>> Dr Russel Winder      t: +44 20 7585 2200   voip: sip:[hidden email]
>> 41 Buckmaster Road    m: +44 7770 465 077   xmpp: [hidden email]
>> London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder
>>
>> --
>> You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
>> To post to this group, send email to [hidden email].
>> Visit this group at http://groups.google.com/group/spockframework.
>> For more options, visit https://groups.google.com/groups/opt_out.
>

--
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/spockframework.
For more options, visit https://groups.google.com/groups/opt_out.
Reply | Threaded
Open this post in threaded view
|

Re: migration to github

Guillaume Laforge
Just like the wiki pages should be removed from Google Code, the code itself on Google Code should also be completely removed, just leaving a README file saying the code migrated to GitHub!

Guillaume


On Mon, Dec 9, 2013 at 2:26 PM, Alex Anderson <[hidden email]> wrote:
Just wanted to comment that I've been happily using spock for 3 years,
but I didn't realise it was hosted on github - I thought it was on
googlecode.  And I'm fairly sure I've cloned the repository there a
couple of times for a poke around.

On 7 December 2013 21:54, [hidden email] <[hidden email]> wrote:
> Having a `master` branch isn’t the right fit for every project, and that’s why Git and GitHub allow for other designs. Our model is easy enough to explain and understand, but I’ll add something to the readme.
>
> Cheers,
> Peter
>
> On 07 Dec 2013, at 13:41, Russel Winder <[hidden email]> wrote:
>
>> On Wed, 2013-12-04 at 20:03 -0500, [hidden email] wrote:
>>> The fact that there is no `master` branch is by design. We maintain one branch per supported Groovy version, and cut separate release artifacts for each branch. As such there is no single `master`, and our branching model simply reflects this reality.
>>
>> Isn't this going to put off people trying to contribute on the grounds it is not idiomatic use of Git?
>>
>> --
>> Russel.
>> =============================================================================
>> Dr Russel Winder      t: <a href="tel:%2B44%2020%207585%202200" value="+442075852200">+44 20 7585 2200   voip: [hidden email]
>> 41 Buckmaster Road    m: <a href="tel:%2B44%207770%20465%20077" value="+447770465077">+44 7770 465 077   xmpp: [hidden email]
>> London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder
>>
>> --
>> You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
>> To post to this group, send email to [hidden email].
>> Visit this group at http://groups.google.com/group/spockframework.
>> For more options, visit https://groups.google.com/groups/opt_out.
>

--
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/spockframework.
For more options, visit https://groups.google.com/groups/opt_out.



--
Guillaume Laforge
Groovy Project Manager
Pivotal, Inc.

--
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/spockframework.
For more options, visit https://groups.google.com/groups/opt_out.
Reply | Threaded
Open this post in threaded view
|

Re: migration to github

Peter Niederwieser
Administrator
The Wiki pages will be removed once the reference documentation is complete. Until then, they are still needed.

I couldn't find a way to remove all code from the Google Code repo, in particular without losing the Wiki. However, trunk now just contains a MOVED_TO_GITHUB.txt file.

Once Spock has its own website, we'll be able to retire the Google Code project completely, or just keep the issue tracker for historical reference.

Cheers,
Peter

Am Montag, 9. Dezember 2013 14:32:26 UTC+1 schrieb Guillaume Laforge:
Just like the wiki pages should be removed from Google Code, the code itself on Google Code should also be completely removed, just leaving a README file saying the code migrated to GitHub!

Guillaume

--
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/spockframework.
For more options, visit https://groups.google.com/groups/opt_out.
Reply | Threaded
Open this post in threaded view
|

Re: migration to github

Marcin Zajączkowski
In reply to this post by Peter Niederwieser
On 2013-12-04 15:42, [hidden email] wrote:
(...)
> I recently wanted to move issues to GitHub, but it’s impossible
> because GitHub doesn’t offer any sensible way to import issues. We’ll
> probably move them somewhere else.

I'm bringing back this old thread just in case you would like to move
the issues to GitHub one day.

Recently PIT (Mutation Testing Tool) migrated all the issues from Google
Code [1] to GitHub [2]. They used google-code-issues-migrator [3] and
the issues look quite good and the process seems to be quite automatic [4].

[1] - https://code.google.com/p/pitestrunner/issues/list
[2] - https://github.com/szpak/gradle-pitest-plugin/issues
[3] - https://github.com/arthur-debert/google-code-issues-migrator/
[4] - https://groups.google.com/forum/#!topic/pitusers/mQCsijREdSQ

Marcin



>
> Immediate plans are to get 1.0 out of the door, hopefully around the new year.
>
> Cheers,
> Peter
>
> On 04 Dec 2013, at 03:44, Kallin Nagelberg <[hidden email]> wrote:
>
>> It's great to see ongoing development of Spock happening in github! Is the plan to move everything over there? It would be nice to have a master branch there; the lack of one now is a little confusing. I'd also love to see all the documentation and issues moved in there as I think it would help improve adoption of spock. Currently things seem a little scattered across this google group, the google code docs/wiki, github, and http://docs.spockframework.org/.
>>
>> At first I thought the project might be dead based on what I saw on the google code site (which is the first place you go when you search for Spock). I'm curious about what the future plans of Spock are. It's so easy to create a gradle project using spock now with the init task, so hopefully users can find everything they need to know in one place!
>>
>> Cheers,
>> -Kal
>>


--
http://blog.solidsoft.info/ - Working code is not enough

--
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/spockframework.
For more options, visit https://groups.google.com/groups/opt_out.
Reply | Threaded
Open this post in threaded view
|

Re: migration to github

Peter Niederwieser
Administrator
Thanks for the pointer. That script has all the problems I mentioned (see their README). I’m not sure if I can cope with this, but we’ll see. It’s not an urgent matter. 

It’s unbelievable that GitHub doesn’t offer a way to import issues. The only explanation I have is that it’s not relevant anymore business-wise. Unfortunately, there is a lot to be said for having everything in one place.

Cheers,
Peter

On 09 Jan 2014, at 22:19, Marcin Zajączkowski <[hidden email]> wrote:

On 2013-12-04 15:42, [hidden email] wrote:
(...)
I recently wanted to move issues to GitHub, but it’s impossible
because GitHub doesn’t offer any sensible way to import issues. We’ll
probably move them somewhere else.

I'm bringing back this old thread just in case you would like to move
the issues to GitHub one day.

Recently PIT (Mutation Testing Tool) migrated all the issues from Google
Code [1] to GitHub [2]. They used google-code-issues-migrator [3] and
the issues look quite good and the process seems to be quite automatic [4].

[1] - https://code.google.com/p/pitestrunner/issues/list
[2] - https://github.com/szpak/gradle-pitest-plugin/issues
[3] - https://github.com/arthur-debert/google-code-issues-migrator/
[4] - https://groups.google.com/forum/#!topic/pitusers/mQCsijREdSQ

Marcin




Immediate plans are to get 1.0 out of the door, hopefully around the new year.

Cheers,
Peter

On 04 Dec 2013, at 03:44, Kallin Nagelberg <[hidden email]> wrote:

It's great to see ongoing development of Spock happening in github! Is the plan to move everything over there? It would be nice to have a master branch there; the lack of one now is a little confusing. I'd also love to see all the documentation and issues moved in there as I think it would help improve adoption of spock. Currently things seem a little scattered across this google group, the google code docs/wiki, github, and http://docs.spockframework.org/. 

At first I thought the project might be dead based on what I saw on the google code site (which is the first place you go when you search for Spock). I'm curious about what the future plans of Spock are. It's so easy to create a gradle project using spock now with the init task, so hopefully users can find everything they need to know in one place!

Cheers,
-Kal



-- 
http://blog.solidsoft.info/ - Working code is not enough

-- 
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/spockframework.
For more options, visit https://groups.google.com/groups/opt_out.


signature.asc (817 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: migration to github

Mike Wilkes
Have you considered moving to the Atlassian stack? Bitbucket supports Git (and Mercurial). Free for open source (actually one can collaborate on private repos with up to 5 others).

I wouldn't recommend the issue tracker in BitBucket. It's too basic. But, JIRA (and the other Atlassian tools) is free for open source projects. You'd have to apply for a license.

JIRA and Bitbucket integrate well (as one would hope).

JIRA could be customized to your liking, and odds are their are people on here familiar with it, and able to aid in any customizations.

I know Github is the 'cool' place to be, but if their tools aren't supporting you, maybe Bitbucket will be better (and just leave a readme on the github repo that points there). I know, lots of indirection.

I'm not associated with Atlassian, but generally like and use their tools.

Bitbucket also allows one to login using their Github, google, facebook, twitter or a Bitbucket specific account.

--
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/spockframework.
For more options, visit https://groups.google.com/groups/opt_out.
Reply | Threaded
Open this post in threaded view
|

Re: migration to github

Peter Niederwieser
Administrator
GitHub and YouTrack are the only options I’m considering (besides keeping issues on Google Code). A full migration is difficult/problematic though, and a partial migration has the big downside that the Google Code issue tracker can’t be switched into read-only mode. Either you keep it, or you delete it. Gladly, it’s not a pressing problem. It’s much more important to have a logo, website, better documentation, etc.

Cheers,
Peter

On 10 Jan 2014, at 14:03, Mike Wilkes <[hidden email]> wrote:

Have you considered moving to the Atlassian stack? Bitbucket supports Git (and Mercurial). Free for open source (actually one can collaborate on private repos with up to 5 others).

I wouldn't recommend the issue tracker in BitBucket. It's too basic. But, JIRA (and the other Atlassian tools) is free for open source projects. You'd have to apply for a license.

JIRA and Bitbucket integrate well (as one would hope).

JIRA could be customized to your liking, and odds are their are people on here familiar with it, and able to aid in any customizations.

I know Github is the 'cool' place to be, but if their tools aren't supporting you, maybe Bitbucket will be better (and just leave a readme on the github repo that points there). I know, lots of indirection.

I'm not associated with Atlassian, but generally like and use their tools.

Bitbucket also allows one to login using their Github, google, facebook, twitter or a Bitbucket specific account.

--
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/spockframework.
For more options, visit https://groups.google.com/groups/opt_out.


signature.asc (817 bytes) Download Attachment
12