Issue 354 in 400plus: Migrating to GitHub

[400...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Enhancement Priority-High

New issue 354 by tiboun...@gmail.com: Migrating to GitHub
https://code.google.com/p/400plus/issues/detail?id=354

Hi !

Google Code will be closing its doors soon (by august 2015, our repository
will be read-only). I suggest using GitHub instead, which is a nice
replacement to Google Code. We can even integrate it with some CI software
such as Travis.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[400...@googlecode.com]

Comment #1 on issue 354 by tiboun...@gmail.com: Migrating to GitHub
https://code.google.com/p/400plus/issues/detail?id=354

(I've created the 400plus organisation on GitHub, just to prevent someone
from stealing the name)

[400...@googlecode.com]

Updates:
Status: Started

Comment #2 on issue 354 by eduardo....@gmail.com: Migrating to GitHub
https://code.google.com/p/400plus/issues/detail?id=354

Well, that was fast, many thanks... I had just read the announcement, when
your message arrived!

I have joined GitHub, and my username is "eduperez" (I am completely new to
GitHub, so please forgive me if I say something stupid). I see there are a
couple of "400plus" projects there; one seems to be yours, it contains all
the source code and releases, but no issues; the other one was uploaded
by "kautsu" a few hours before, and it only contains open issues. There is
also the "400plus" organization that you created, and it is still empty.

So, I guess the next step is to add the current developers to the
organization (you already have my username), and then upload a repository
there (shall we create a new one? shall we use yours?), the wiki pages
(does GitHub support that?), released files, issues, ...

[400...@googlecode.com]

Comment #3 on issue 354 by eduardo....@gmail.com: Migrating to GitHub
https://code.google.com/p/400plus/issues/detail?id=354

I see (https://code.google.com/p/support-tools/wiki/GitHubExporterFAQ and
https://help.github.com/articles/transferring-a-repository/) that the
correct procedure is to create a "user repository" and then migrate it to
the organization.

I will create now a repository, and do the migration there; seems like I
have some work ahead...

[Jean THOMAS]

I did the migration from Google Code using GitHub's tool on my 400plus repository (http://github.com/tibounise/400plus). It took quite a while, the code is here, but the issues were not imported ...

I don't have your GitHub username, can you give it to me so that I can add you as an admin to the 400plus organisation ?

--

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

--

Jean THOMAS
@tibounise sur Twitter
Mail : cliquez ici pour m'envoyer un message

[Jean THOMAS]

Oops, I read your message too fast :)

[Jean THOMAS]

It seems that the Google Code Exporter tool is currently busy. We might have to re-import the repository to GitHub later, in order to get both the issues and the code.

[Eduardo Pérez]

I have just accepted your invitation to the "400plus organization", many
thanks. Now I will experiment a bit with the migration process, using a
testing repo under my username, and we will later do it with the real
repo.

Edu.

[400...@googlecode.com]

Comment #4 on issue 354 by fired...@gmail.com: Migrating to GitHub
https://code.google.com/p/400plus/issues/detail?id=354

Yeah, I've read the message few hours ago...
Edu, the best would be (IMO) to create a repo in your user in GH, this
should be the master, since you're the maintainer. Anyone could then just
fork from you.
I haven't read the FAQs provided by google, but it should be easy to
migrate.
I have few repos in GH and I will fork 400plus from your user, once you put
the code in your repo.
I'm not sure if I can be of any help, since I haven't touched a camera for
2 years already. I even sold my 400D (gifted actually), but I still hold my
IDA files, so for some stuff I could be of some help, I guess...
Anyway, I'm still emotionally and morally connected to this camera and this
project for sure...

[Jean THOMAS]

I think we'd better use an organisation for 400plus. This would allow us to separate 400plus sub-projects (like lang_tool.pl) into a different repository.

I did new migration of the 400plus repository, this time the issues were correctly imported. I added the migrated repository to the 400plus organisation, I'm currently migrating the wiki's markdown files to GitHub's wiki.

> --
>
> ---You received this message because you are subscribed to the Google Groups "400plus" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to 400plus+u...@googlegroups.com.

[Eduardo Pérez Esteban]

As I wrote before, I am new to GH; but it looks like the owners of "personal repositories" can "donate" them to organizations, and then they become "organization repositories". Thus (unless there is something else I am missing), both paths lead to the same final result. I like the idea of having an organization, and Jean Thomas seems to be doing a very good job with the migration; I vote to adopt his repository as the official repository for 400plus.

I have been browsing the 400plus repository at GH, and things look fantastic there; many thanks! I think we should start planning the "we are moving" phase; my idea is to add warnings and links on the pages at GC, as soon as each section on GH is completed. Let's review where we are now:

* Code: the repository seems fine; can we move the development there yet?

* Issues: those look good, too; I will close all the issues at GC as "migrated" later, and add a link to the GH equivalent of each one.

* Wiki: all pages I browsed look fine, too. Links to other pages are working, but links to anchors inside the same pages do not work (for example, "https://github.com/400plus/400plus/wiki/User%20guide#Settings_Page.md"). Can this be fixed easily?

* Downloads: there are still no downloads, do you need help with that?

* Anything else?

Many thanks!

Edu.

--

---

[Jean THOMAS]

For the archor links, hover a title, and you'll see on the left a link icon.

[Jean THOMAS]

For the downloads, it is quite tricky. We can use GitHub's releases (https://github.com/400plus/400plus/releases), on which you can attach binairies (it'll take a long time to upload all the binairies). I'll work on that tonight, I'll keep you informed ;)

[Eduardo Pérez Esteban]

Looks like the format for the anchors has changed, and the conversion did not take this change into account. I'll have a look tonight, and see if there is a quick method to fix them all.

[Eduardo Pérez Esteban]

I think I have all the binaries at home, perhaps it will be easier if I do that part myself.

[Eduardo Pérez]

Ok, I have "forked" the repository from the organization into my own
repository, and then "cloned" my repository to my computer (did I do it
right?). Now I am struggling to "pull" that into a nice "project" I can
use from eclipse; but I am still new to GIT, and will have to read the
documentation before I know what I am doing...

Edu.

[Eduardo Pérez Esteban]

Hi!

I see there is already some activity at the GitHub repo; I will add a comment now to the wiki at Google Code, so people can go directly to GitHub and see the latest version there.

I have also noticed that Jean Thomas is working on new features in a branch ("screenshots") on the main repo at the 400plus organization. Is this the "usual practice" at GitHub? I understood that each developer would fork the main repo, and work on his own repo until changes where ready to be pushed to the main repo. Or should I delete my own fork, clone from the main repo, and work there? (As I said before, I am new to GitHub, thanks for your patience).

Edu.

[Jean THOMAS]

Using forks is needed when you don't have write access to a repo. You fork it, you modify the forked repo, and then you do a pull request.

Otherwise, I think that using branches is better when you're implementing something new. When the thing you're implementing is stable, you can merge the "beta" branch into the master branch. Thus we can work easily on the multiple features at the same time.

--

---

You received this message because you are subscribed to the Google Groups "400plus" group.

To unsubscribe from this group and stop receiving emails from it, send an email to 400plus+u...@googlegroups.com.

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

[Jean THOMAS]

Using fork can be a good idea if you're not familiar enough with Git. If you mess up something by error, only your repository will be affected.

[Jean THOMAS]

Maybe this link can help you : https://confluence.atlassian.com/display/BITBUCKET/Branch+or+fork+your+repository

2015-03-23 19:58 GMT+01:00 Jean THOMAS <tibo...@gmail.com>:

Using fork can be a good idea if you're not familiar enough with Git. If you mess up something by error, only your repository will be affected.

[400...@googlecode.com]

Comment #5 on issue 354 by eduardo....@gmail.com: Migrating to GitHub
https://code.google.com/p/400plus/issues/detail?id=354

I have uploaded all binaries to their respective releases at GitHUB, and I
have also adapted all the wiki entries; as far as I know, everything is
ready at GitHUB now.

Is everything ready for the final move? Or did I miss anything? I think we
can definitively close the project at Google Code, and leave here just a
pointer to GitHUB.

We should also try to update those external links (the CHDK forum, for
example) that point here; at least those that we can update.

[Jean THOMAS]

Yeah, I think we are good to go !

> --
>
> ---You received this message because you are subscribed to the Google Groups "400plus" group.