Moving to github ?

[Brice Dutheil]

Hi everyone,

The Mockito team is interested to move the source code repository to Github, and we would like to hear your feedback on the matter.

For now, everything else (issues, wiki, documentation, etc.) should stay on Google Code.

-- Brice

[Eric Lefevre-Ardant]

I'd love it. When doing the Hackergarten the other day, there didn't seem to be a smooth way to push my changes to you. That was frustrating.

I'm missing the Pull Requests!

-- Brice

--
You received this message because you are subscribed to the Google Groups "mockito" group.
To post to this group, send email to moc...@googlegroups.com.
To unsubscribe from this group, send email to mockito+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/mockito?hl=en.

[welk]

I am only a user, browser, and I appreciate the one-stop shopping.
What are the "power-users" missing on googlecode, and could you talk
to Google about adding support for those features? You know you can
migrate to Git on Googlecode if you want. My googlecode project is in
Git.

[James Carr]

Well, for the most part github is more of a reason in itself to use
github rather than git. Bitbucket offered git support last year at
prices cheaper than what we pay github for but we stuck with github
for a lot of the features, such as code reviews, comments, painless
forking, etc.

You can contribute to a F/OSS project on github without even knowing
git. The barrier to entry is pretty low.

Thanks,
James

[leif hanack]

I thought that github is free of charge for open source projects: https://github.com/plans

Regards, Leif

[James Carr]

It is... I was talking about my business use within a company. Just
saying the collaborative tools it offers are way better than google
code and that we felt it was well worth paying for. ;)

[Geoffrey Wiseman]

On 2012-08-02, at 4:58 PM, James Carr <james....@gmail.com> wrote:

> It is... I was talking about my business use within a company. Just
> saying the collaborative tools it offers are way better than google
> code and that we felt it was well worth paying for. ;)

I just wish their pricing wasn't so repo-based since I tend to have lots of small repos.

GitHub is great -- although as a Mockito user, it won't affect me much.

- Geoffrey

[welk]

Hey James, good to see you.

Again, I have never tried to fork Mockito, or offer patches, etc. So
I don't know that pain, nor can I compare that to Github, but I have
done Googlecode code reviews and I find them very intuitive and
doable. I also *much* prefer the documentation/wiki and Issues
features on Googlecode (as Brice has suggested they keep those things
here). Frankly, whenever, I have to navigate thru Github as a casual
user, I am much more frustrated -- especially code browsig. GC AJAX
tree view is much easier to use.

But, I again I confess that my use of Mockito has been essentially
confined to source/issue/release/documentation browsing, and not
really anything on team development efforts. My own googlecode
development project has only had 2 users, no forks, and I have done
95% of the development. So my pain points are more limited than
perhaps those who are impacted most by the decision to move or stay.
I really would like to understand more for my own benefit.

[Brice Dutheil]

Hi,

Thanks for the feedback.

@wel Actually as I said that other resources such as documentation, wiki, etc will stay *for now*, which means that we don't want to move them but if the move is relevant and offers more advantages it might happen.

Now what I have to say :

Github offer actually many more feature than we have on Google Code. And Google Code doesn't really show any sign of improvements or new features, while Github is actually doing pretty well in that regard. Bitbucket is also quite good.

Some advantages we can see in Github that Google Code don't have :

- Pull request

- Code Review : https://github.com/features/projects/codereview

- SSH support

- better branch comparison : https://github.com/AxonFramework/AxonFramework/compare/master...axon-1.4.x

Plus some interesting gadgets :

- Also there is nice tutorials : https://github.com/blog/1183-try-git-in-your-browser

- Graphs on the repository : https://github.com/AxonFramework/AxonFramework/graphs

- The network graph : https://github.com/blog/39-say-hello-to-the-network-graph-visualizer

Things on github we are not yet ready to use, that doesn't mean these features are not great (on github) :

- Issues, Wiki, Downloads

The bad :

- Everyone will need to get accustomed to git

- We need to migrate the repository, while it mostly works, there is some adjustments to do regarding tags name

- Everyone who had a googlecode account will need a new one on Github

----------

Beyond the scope of that repository change, moving the issue tracker is bothering us, which is why we don't want to switch right now. Here's what's bothering us *if* we switch to a new issue management system :

  - What happens of the old issues? Shall we keep them, as they are most likely indexed by Google & co ? If yes shall we close them, and redirect the issues to the new system ?

  - What about the people that followed the issues ?

  - Changesets are different between git and mercurial, so automatic links might become incorrect ("revision 441930b6659a"). Note that we already have this issue (still un resolved) when the team switched from subversion to mercurial.

  - For the transfer, there is no real import stuff to help the switch. Youtrack though offer this support.

Anyway we are not there yet. 

Cheers,

-- Brice

[Eric Lefevre-Ardant]

Regarding old issues: I'd bet that 80% of them will remain unsolved.

I suggest that you migrate only the ones that have had any activity in the last 6 months.

Then close of them and put a message in the ones > 6 months explaining that, if it is still relevant, then the person should recreate the issue in Github.

Eric

[James Carr]

"Everyone will need to get accustomed to git"

You say that like it's a bad thing. ;)


Thanks,
James

[Brice Dutheil]

@James Well, from my point of view, git is not as user friendly as mercurial, even if there have been much progress in this area.

Some commands do not express the intent from the user perspective, I know it's possible to create aliases, still the user has to create them. I recognise myself the power of git, but I still like the friendliness of mercurial.

@Eric I'm not sure about that, I personally would like to have a centralised space, to avoid duplicate issues across trackers. I don't know how the rest of the team feels about that. Anyway the tracker is not a priority for now.

-- Brice

[Eric Lefevre-Ardant]

"avoid duplicate issues across trackers"

If they are all closed (which is what I was suggesting), then they are not duplicated, right?

[Brice Dutheil]

@Eric What I had in mind is more to avoid the creation of a duplicate issue on the new tracker, because some user didn't actually take a look at the older tracker. If all issues are in the same tracker then it's easy to look up for duplicate issues, even for us.

-- Brice

[Geoffrey Wiseman]

I like Git, and particularly GitHub quite a bit, although I do have some sympathy for the Mercurial's commands make more sense perspective. Some food for thought:

https://steveko.wordpress.com/2012/02/24/10-things-i-hate-about-git/

Incidentally, this doesn't change anything for me -- I still like GitHub more than I like any other hosting service that offer Mercurial. It's also true that GitHub's popularity means that many people, particularly in specific subsets of the software development community, are already very familiar with it.

  - Geoffrey

-- 
Geoffrey Wiseman
http://www.geoffreywiseman.ca/

[Thomas Sundberg]

+1

On 2 August 2012 15:23, Brice Dutheil <brice....@gmail.com> wrote:

> --
> You received this message because you are subscribed to the Google Groups
> "mockito" group.
> To post to this group, send email to moc...@googlegroups.com.
> To unsubscribe from this group, send email to
> mockito+u...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/mockito?hl=en.



--

Thomas Sundberg
M. Sc. in Computer Science

Mobile: +46 70 767 33 15
Blog: http://thomassundberg.wordpress.com/
Twitter: @thomassundberg

Better software through faster feedback