I agree with Sitaram on this,

"The tortoise type stuff can only do the mundane actions like commit
and diff.  The feature set of git is so different that if you contort
it into those tools commonly known interface, you'll be limiting
yourself. "

I do agree with you though Nazgulled on the Google Code point you
made. Lots more people have Google Accounts. People who have GitHub
accounts are generally not your regular users, they are developer
whereas many of your users might have Google Accounts. Of course, when
you think about it, the sign up process itself is easy and is not the
issue you should be concerned with. What you should really consider
is, is it easier for regular users to enter issues on GitHub or on
Google Code? I'm not saying which is easier or which is better, but
that's what I think you should be concerned with. The extra step of
creating a GitHub account is well worth it if your users can enter the
issues more easily.

http://twitter.com/deceth

On May 1, 2:20 am, Icebreaker <[email protected]> wrote:
> > 2) Now days, most people as a Google Account but not a GitHub account
> > and that will not change.
>
> I wouldn't be so sure about this one, GitHub it's the "Facebook" of source
> code hosting  :))
>
>
>
> On Fri, May 1, 2009 at 3:44 AM, Nazgulled <[email protected]> wrote:
>
> > Hi,
>
> > I've always used SVN and TortoiseSVN as I mostly develop for Windows
> > and that's not going to change any time soon...
>
> > Overall, I like the concept of Git and the whole GitHub website, it
> > also looks much better than Google Code. But there's a few things
> > that's keeping me from GitHub...
>
> > 1) Is TortoiseGit good enough to be used in production systems? A
> > friend of mine didn't inspired me much about using TortoiseGit (not
> > Git itself), but without a TortoiseSVN alike for Git, I don't have any
> > intentions of using GitHub or any other Git based revision control
> > system for that matter. The opinions on this group may be a little
> > biased, but I still want to hear them...
>
> > 2) Now days, most people as a Google Account but not a GitHub account
> > and that will not change. Google provides a lot of different
> > services... The problem with this for me is that I also wanted to use
> > GitHub to control issues with my applications, using your integrated
> > issue system. But people need to be registered for that...
>
> > Are there any possibilities to have people posting issues without
> > signing up on Git? They might not be developers at all and just post
> > some issues about my software... Maybe not all features can possibly
> > be enable, but create issues and comment on that, would be nice to
> > have without signing up. And maybe make it an option per repository...
> > Another and probably better idea, would be to implement OpenID on
> > GitHub, this way, every one with a Google Account (and many other
> > providers) would be able to use the website. Maybe you could limit
> > what this OpenID account type could on the site...
>
> > Wat do you think?
>
> --
>
> George Bernard 
> Shaw<http://www.brainyquote.com/quotes/authors/g/george_bernard_shaw.html>
> - "We learn from experience that men never learn anything from
> experience."

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"GitHub" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/github?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to