Google Code hosting is shutting down; we migrate to...

[Alberto Mardegan]

Hi all!
Today Google announced [0] that it's going to shut down the Google
Code hosting, which is where we are currently hosting our projects.

We need to decide where to move our projects to. There are many options,
including:

- GitHub: everyone knows it, and Google Code has en export tool for
github, which will export code, issues and wikis. [1]

- Sourceforge: open source, offers an import tool. [2]

- GitLab: open source, nice UI, offers an import tool (but via GitHub) [3]

There are many more options, which you are feel free to suggest if you
think they offer some advantage over these three.

So, please just reply to this e-mail stating your favourite option, and
in a week (March 20th) we'll count the votes and try reaching a decision.

All options are fine with me, but my preference goes to gitlab.

Ciao,
Alberto


[0]
http://google-opensource.blogspot.ru/2015/03/farewell-to-google-code.html
[1] https://code.google.com/export-to-github/
[2] http://sourceforge.net/p/forge/documentation/Google%20Code%20Importer/
[3]
https://about.gitlab.com/2015/03/12/farewell-google-code-hello-gitlab-dot-com/

[Alexander Kanavin]

Hello,

no github (let alone SF!) please. They look and feel dated and messy.

My vote goes to Bitbucket. Much more cleaner, pleasant UI than github,
and has all the same stuff.
Gitlab seems nice too, but I haven't used it yet.

Alex

> --
> You received this message because you are subscribed to the Google Groups
> "Accounts & SSO framework developer group" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to accounts-sso-de...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Martin Klapetek]

Hey,

On Fri, Mar 13, 2015 at 7:33 AM, Alberto Mardegan <mardy...@gmail.com> wrote:

Hi all!
  Today Google announced [0] that it's going to shut down the Google Code hosting, which is where we are currently hosting our projects.

We need to decide where to move our projects to. There are many options, including:

- GitHub: everyone knows it, and Google Code has en export tool for github, which will export code, issues and wikis. [1]

- Sourceforge: open source, offers an import tool. [2]

- GitLab: open source, nice UI, offers an import tool (but via GitHub) [3]

There are many more options, which you are feel free to suggest if you think they offer some advantage over these three.

So, please just reply to this e-mail stating your favourite option, and in a week (March 20th) we'll count the votes and try reaching a decision.

All options are fine with me, but my preference goes to gitlab.

My only strong preference is "please oh please not SourceForge" :)

GitHub is where the cool kids seem to be, Bitbucket looks a bit confusing

to me (probably just a matter of getting used to though) and GitLab is

somewhere in between.

I'd probably even go for GitLab as it is free software (free as in freedom),

but they offer free hosting only to "private" projects, I'm not sure if Accounts SSO

falls into the "private" category however.

In the end I think all that matters is issue tracking and code reviewing.

I don't know either GitHub or Bitbucket enough to judge, but quickly

looking at some existing projects - the issues are moreless on par

except Bitbucket offers "priorty" and "votes".

As for code review tools, I think both are also comparable (though

judging Bitbucket just from screenshots).

What bothers me about Bitbucket, however, is the "FREE FOR 5 USERS"

where "user" means "Someone with read or write access to one of your

private repositories". That seems very very very limiting.

So, in the end, it looks like it would be GitHub vote from me.

Cheers

--

Martin Klapetek | KDE Developer

[Alberto Mardegan]

Hi again!
I was hoping to get some more feedback on this, that's why I've been
waiting longer than initially promised.

In the next few days I'll be migrating our projects to GitLab (looks
like I'll have to pass through GitHub, just for performing the
migration), which none here has criticized -- most likely because it
hasn't been used by anyone :-)

I'll keep you posted on how the conversion goes, but unless I hear
strong voices against it, GitLab is going to be our code host.

Ciao,
Alberto


--
http://blog.mardy.it <- geek in un lingua international!

[Alberto Mardegan]

On 04/07/2015 10:04 AM, Alberto Mardegan wrote:
> I'll keep you posted on how the conversion goes, but unless I hear
> strong voices against it, GitLab is going to be our code host.

And here they are:

https://gitlab.com/groups/accounts-sso

The conversion seems to have been successful. Please create an account
in gitlab.com and either tell me your ID, so that I'll add you to the
accounts-sso group. Feel free to use IRC for this.

We need to decide what to do with the umbrella project, which is where
all issues have been migrated to:
https://gitlab.com/accounts-sso/accounts-sso
Since gitlab has an issue tracker for each individual project, it makes
no sense to keep this umbrella project alive. I would propose to move
the valid issues to the affect projects, and delete this one.
Unfortunately there isn't a way to move the issues, other than the
manual one.

As for the docs, for the projects I maintain I plan to use
http://readthedocs.org, which can be setup to automatically generate the
documentation when a web hook is triggered, and in gitlab we can trigger
web hooks when a new tag is pushed.

Now let's learn how this thing works... :-)

[Alexander Kanavin]

2015-04-07 12:31 GMT+03:00 Alberto Mardegan <mardy...@gmail.com>:
> We need to decide what to do with the umbrella project, which is where
> all issues have been migrated to:
> https://gitlab.com/accounts-sso/accounts-sso
> Since gitlab has an issue tracker for each individual project, it makes
> no sense to keep this umbrella project alive. I would propose to move
> the valid issues to the affect projects, and delete this one.
> Unfortunately there isn't a way to move the issues, other than the
> manual one.

I have now moved or closed all the gsso-related issues. The ones that
remain are all about Qt stuff, so it's up to you to sort them :)

Alex