search

onlywei / explain-git-with-d3

Use D3 to visualize simple git branching operations.
MIT License
1.71k stars 390 forks source link

Improvements to the style & to the text content #24

Open drewrwilson opened 10 years ago

drewrwilson commented 10 years ago

@maya did some very cool work on the style of the page: https://github.com/maya/explain-git-with-d3

I changed some text to make it more accessible to a git novice.

If you're open to it, I'd suggest renaming the repo from "explain-git-with-d3" -> "understanding-git-visually". The difference being that it shifts the subject of the project from the creators and the tools that you used to the person learning git and what value this tool brings them.

PS Very cool project! Hope this helps!

JakeGinnivan commented 9 years ago

Hey @drewrwilson

I am also keen to see this become a bit more as it is a great tool. If @onlywei is up for it maybe lets create an org and I would be up for helping out maintaining this tool (I use it for presentations a lot).

It makes sense having the domain name and updating the styles etc. I noticed Zen Mode is broken on your fork.

@onlywei what do you think are you up for creating an org and adding a few more people to help maintain this. I think it will get more traction under it's own repo and we can help merge pull requests and such to keep it active.

It is a better solution than having forks (I have http://jake.ginnivan.net/explain-git-with-d3 as well because I need to publish my changes a while back).

onlywei commented 9 years ago

@JakeGinnivan I'm not sure I'm ready to create an org just yet. I have some work in mind that I wanted to do in this project before I open it up that much. I also don't fully understand what it means to create an org for this, as I've never done that before. Perhaps you could explain a little bit more to convince me?

JakeGinnivan commented 9 years ago

An org is really lightweight. For instance I have a library called shouldly and it lives in an org called shoudly.

The org isn't necessary, but i am happy to help you out with maintain this project. I'd prefer to try and keep all people working on the same project rather than forking.

If you want to get my thoughts on your ideas then feel free to email me as well. Jake at Ginnivan dot net

Sent from my Windows Phone

From: Wei Wangmailto:notifications@github.com Sent: ý15/ý02/ý2015 19:28 To: onlywei/explain-git-with-d3mailto:explain-git-with-d3@noreply.github.com Cc: Jake Ginnivanmailto:jake@ginnivan.net Subject: Re: [explain-git-with-d3] Improvements to the style & to the text content (#24)

@JakeGinnivanhttps://github.com/JakeGinnivan I'm not sure I'm ready to create an org just yet. I have some work in mind that I wanted to do in this project before I open it up that much. I also don't fully understand what it means to create an org for this, as I've never done that before. Perhaps you could explain a little bit more to convince me?

— Reply to this email directly or view it on GitHubhttps://github.com/onlywei/explain-git-with-d3/issues/24#issuecomment-74432364.

JakeGinnivan commented 9 years ago

@onlywei did you want to send me an email or have a quick chat on skype/something else.

Keen to know where you would like to take this.

Just to expand on the org thing, here are some I am part of:

https://github.com/TestStack, https://github.com/DbUp, https://github.com/funnelweblog, https://github.com/shouldly and https://github.com/Code52

As you can see, an organisation is just a collection of projects which is not your personal account. I have found that projects belonging to an org end up with more community involvement than ones on peoples personal account. It also makes it very easy to tell which repository is the 'main' one.

The great thing about open source is that people are willing to help you out and help you maintain a project, but the project will stay yours. Anyways, I am happy to answer any questions you have.