Hello Inkscape Developers,
I was able to convert the bzr repo into a git repository yesterday using https://github.com/git/git/blob/master/contrib/remote-helpers/git-remote-bzr
What I'm suggesting we do is to create an "Inkscape" orgranisation e.g. (https://github.com/wikimedia) on Github and put up a read-only git-mirror of Inkscape's sources (which will be updated periodically, say once a week).
I think this will surely increase the "visibility" of Inkscape's sources and the Inkscape organisation, in general, and we may be able to get new contributors. A lot of other projects seem to do this, even though actual development happens elsewhere.
IIRC, cloning a git repository is a lot faster, so, this might help people submit patches quicker.
Regular development can continue in Launchpad, as usual.
Is this a reasonable idea?
Samuel
On Fri, May 24, 2013 at 1:15 PM, Samuel Chase wrote:
Hello Inkscape Developers,
I was able to convert the bzr repo into a git repository yesterday using https://github.com/git/git/blob/master/contrib/remote-helpers/git-remote-bzr
What I'm suggesting we do is to create an "Inkscape" orgranisation e.g. (https://github.com/wikimedia) on Github and put up a read-only git-mirror of Inkscape's sources (which will be updated periodically, say once a week).
I think this will surely increase the "visibility" of Inkscape's sources and the Inkscape organisation, in general.
How?
Alexandre Prokoudine http://libregraphicsworld.org
You have to take that Python script and put it in your path (I put it in ~/bin) and then:
git clone bzr::/path/to/inkscape-bzr-repo inkscape-git-repo
It took about 8 minutes.
Using similar methods I was able to convert some hg repositories of mine as well.
On Fri, May 24, 2013 at 3:20 PM, Alexandre Prokoudine <alexandre.prokoudine@...400...> wrote:
On Fri, May 24, 2013 at 1:15 PM, Samuel Chase wrote:
Hello Inkscape Developers,
I was able to convert the bzr repo into a git repository yesterday using https://github.com/git/git/blob/master/contrib/remote-helpers/git-remote-bzr
What I'm suggesting we do is to create an "Inkscape" orgranisation e.g. (https://github.com/wikimedia) on Github and put up a read-only git-mirror of Inkscape's sources (which will be updated periodically, say once a week).
I think this will surely increase the "visibility" of Inkscape's sources and the Inkscape organisation, in general.
How?
Alexandre Prokoudine http://libregraphicsworld.org
Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Fri, May 24, 2013 at 2:52 PM, Samuel Chase wrote:
You have to take that Python script and put it in your path (I put it in ~/bin) and then:
git clone bzr::/path/to/inkscape-bzr-repo inkscape-git-repo
It took about 8 minutes.
Using similar methods I was able to convert some hg repositories of mine as well.
Not what I meant. See again:
I think this will surely increase the "visibility" of Inkscape's sources and the Inkscape organisation, in general.
How?
Alexandre Prokoudine http://libregraphicsworld.org
On Fri, May 24, 2013 at 4:25 PM, Alexandre Prokoudine <alexandre.prokoudine@...400...> wrote:
On Fri, May 24, 2013 at 2:52 PM, Samuel Chase wrote:
You have to take that Python script and put it in your path (I put it in ~/bin) and then:
git clone bzr::/path/to/inkscape-bzr-repo inkscape-git-repo
It took about 8 minutes.
Using similar methods I was able to convert some hg repositories of mine as well.
Not what I meant. See again:
I think this will surely increase the "visibility" of Inkscape's sources and the Inkscape organisation, in general.
How?
Inkscape is quite easy to find for those that need it. Typing "free svg editor" on a search engine should be enough.
However, there probably are developers who have not heard of it, who may serendipitiously come across it on GitHub and maybe one day even contribute. (assuming Inkscape manages to get rated highly enough i.e. stars over there)
In terms of open-source project hosting websites, GitHub has a considerable number of users. Taking advantage of the free hosting provided for open-source organisations on GH, seems to me like an opportunity for greater publicity.
Alexandre Prokoudine http://libregraphicsworld.org
Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Fri, May 24, 2013 at 3:24 PM, Samuel Chase wrote:
However, there probably are developers who have not heard of it, who may serendipitiously come across it on GitHub and maybe one day even contribute. (assuming Inkscape manages to get rated highly enough i.e. stars over there)
In terms of open-source project hosting websites, GitHub has a considerable number of users. Taking advantage of the free hosting provided for open-source organisations on GH, seems to me like an opportunity for greater publicity.
My point is that your proposal boils down to:
- updating the repo _all the time_ - tracking pull requests _all the time_ - reviewing pull requests and merging them _all the time_
Which basically means a dedicated team for Github.
Do we have the human resources for that?
Don't get me wrong: I love Git and personally prefer it to Bzr. I also use Github for personal projects. But I don't expect scattering of the codebase across two repositories to help us a lot. Just my 0.02 euro.
Alexandre Prokoudine http://libregraphicsworld.org
On Fri, May 24, 2013 at 5:44 PM, Alexandre Prokoudine <alexandre.prokoudine@...400...> wrote:
On Fri, May 24, 2013 at 3:24 PM, Samuel Chase wrote:
My point is that your proposal boils down to:
- updating the repo _all the time_
- tracking pull requests _all the time_
- reviewing pull requests and merging them _all the time_
Do we have the human resources for that?
Surely we don't. Yes. We will not allow GH Issues or Pull Requests. I repositories on GH that clearly have "Read-Only: Do not make pull requests here."
A purely read-only repository, with a link to the actual bzr repository for people who are interested.
Think of it as Inkscape's "presence" on GitHub, but all development will take place on Launchpad as usual.
Updating the trunk git-mirror twice/thrice a month should be enough, I guess...
Samuel
On Fri, 2013-05-24 at 16:14 +0400, Alexandre Prokoudine wrote:
Don't get me wrong: I love Git and personally prefer it to Bzr. I also use Github for personal projects. But I don't expect scattering of the codebase across two repositories to help us a lot. Just my 0.02 euro.
I like git, but I don't like github. It's become a sort of proprietary monopoly and doesn't seem to get the deserved criticism for having poor project management, branding, merge management and bug tracking. And well, for being proprietary.
I'm happy with our repositories and we should encourage git users to try the git-bzr plugin if it helps them.
I'm more concerned with compile time being a barrier to development atm.
Martin,
On 05/24/2013 02:43 PM, Martin Owens wrote:
On Fri, 2013-05-24 at 16:14 +0400, Alexandre Prokoudine wrote:
Don't get me wrong: I love Git and personally prefer it to Bzr. I also use Github for personal projects. But I don't expect scattering of the codebase across two repositories to help us a lot. Just my 0.02 euro.
I like git, but I don't like github. It's become a sort of proprietary monopoly and doesn't seem to get the deserved criticism for having poor project management, branding, merge management and bug tracking. And well, for being proprietary.
+1
I think it would still be a good idea to have a read-only repository as a mirror on github. For example, git does that [1]. They do not use any of github's features except git hosting. All development still happens on the mailing list. I think such a mirror would increase visibility. Also, it's free, the only cost is a cron job regularily updating it (which I'd be happy to provide).
Regards, Sebastian
On Fri, May 24, 2013 at 4:23 PM, Samuel Chase wrote:
Do we have the human resources for that?
Surely we don't. Yes. We will not allow GH Issues or Pull Requests. I repositories on GH that clearly have "Read-Only: Do not make pull requests here."
A purely read-only repository, with a link to the actual bzr repository for people who are interested.
It kinda defeats the point of having a Github repo, no? :) Because the point of Github as social development.
Sorry, if I sound like a pessimistic ass :)
Alexandre Prokoudine http://libregraphicsworld.org
participants (4)
-
Alexandre Prokoudine -
Martin Owens -
Samuel Chase -
Sebastian Götte