From: Nick H. <nic...@ho...> - 2013-10-29 17:52:12
|
There have been a couple of threads suggesting that we move from subversion to git. What are your views? The options are: 1. Continue to use subversion. 2. Convert to using git. 3. Convert to using git, and move the hosting from SourceForge. 4. Don't mind. Please keep your answers short and include your SourceForge login, if you have one. Regards, Nick. |
From: Nick H. <nic...@ho...> - 2013-10-29 17:58:23
|
I would prefer git, hosted either on SourceForge or elsewhere. So either option 2 or 3. Nick (nick-h). |
From: Brian M. <br...@gr...> - 2013-10-30 00:57:47
|
I don't have a preference either way about what we use. All the tools work fine for me. However, if we want to change, I would prefer to not be the one to make the conversion. I helped with the original conversion from CVS to SVN and it was a fair amount of work with a few nervous moments while our precious data was in limbo. I do think that GIT has a slightly higher barrier to entry for new (especially non-technical) contributors. Also, I would rather not have to maintain (and coordinate) the project resoures across multiple backends. We already have to coordinate the sourceforge site with our godaddy hosted web site. Adding one more is just that many more passwords and admin panels to remember. In my opinion, nothing beats the github interface - with the ability to edit and commit from a web page and to send and apply pull requests from the web. ~Brian On Tuesday, October 29, 2013 12:58 PM, Nick Hall <nic...@ho...> wrote: I would prefer git, hosted either on SourceForge or elsewhere. So either option 2 or 3. Nick (nick-h). ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ Gramps-devel mailing list Gra...@li... https://lists.sourceforge.net/lists/listinfo/gramps-devel |
From: Adam S. <ad...@cs...> - 2013-10-29 18:06:12
|
If I had a choice, I would choose git, so either choice 2 or 3 (doesn't matter where it's hosted to me). Adam (adamstein) On Tue, 2013-10-29 at 17:52 +0000, Nick Hall wrote: > There have been a couple of threads suggesting that we move from > subversion to git. > > What are your views? > > The options are: > > 1. Continue to use subversion. > 2. Convert to using git. > 3. Convert to using git, and move the hosting from SourceForge. > 4. Don't mind. > > Please keep your answers short and include your SourceForge login, if > you have one. > > Regards, > > Nick. > > > ------------------------------------------------------------------------------ > Android is increasing in popularity, but the open development platform that > developers love is also attractive to malware creators. Download this white > paper to learn more about secure code signing practices that can help keep > Android apps secure. > http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel -- Adam (ad...@cs...) |
From: Enno B. <enn...@gm...> - 2013-10-29 18:06:51
|
On 10/29/2013 06:52 PM, Nick Hall wrote: > 4. Don't mind. No login. |
From: Muhammad B. Al-N. <mb...@gm...> - 2013-10-29 20:47:43
|
Git with hosting at http://gitorious.org/ or http://github.com/ P.S. I always prefer gitorious because it's open source portal :) On Tue, Oct 29, 2013 at 7:52 PM, Nick Hall <nic...@ho...> wrote: > There have been a couple of threads suggesting that we move from > subversion to git. > > What are your views? > > The options are: > > 1. Continue to use subversion. > 2. Convert to using git. > 3. Convert to using git, and move the hosting from SourceForge. > 4. Don't mind. > > Please keep your answers short and include your SourceForge login, if > you have one. > > Regards, > > Nick. > > > ------------------------------------------------------------------------------ > Android is increasing in popularity, but the open development platform that > developers love is also attractive to malware creators. Download this white > paper to learn more about secure code signing practices that can help keep > Android apps secure. > http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel -- Best Regards Muhammad Bashir Al-Noimi |
From: Muhammad B. Al-N. <mb...@gm...> - 2013-10-29 20:48:03
|
I forgot to tell you something important; Keep away from Bzr because it has ton of memory bugs (specially under Windows) and developing process stopped since more than year. BTW, I used Bzr for 5 years under heavy developing process and I can tell you briefly it's very flexible but unfortunately the community preferred Git more. On Tue, Oct 29, 2013 at 10:46 PM, Muhammad Bashir Al-Noimi <mb...@gm...> wrote: > Git with hosting at http://gitorious.org/ or http://github.com/ > > P.S. I always prefer gitorious because it's open source portal :) > > On Tue, Oct 29, 2013 at 7:52 PM, Nick Hall <nic...@ho...> wrote: >> There have been a couple of threads suggesting that we move from >> subversion to git. >> >> What are your views? >> >> The options are: >> >> 1. Continue to use subversion. >> 2. Convert to using git. >> 3. Convert to using git, and move the hosting from SourceForge. >> 4. Don't mind. >> >> Please keep your answers short and include your SourceForge login, if >> you have one. >> >> Regards, >> >> Nick. >> >> >> ------------------------------------------------------------------------------ >> Android is increasing in popularity, but the open development platform that >> developers love is also attractive to malware creators. Download this white >> paper to learn more about secure code signing practices that can help keep >> Android apps secure. >> http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk >> _______________________________________________ >> Gramps-devel mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > > -- > Best Regards > Muhammad Bashir Al-Noimi -- Best Regards Muhammad Bashir Al-Noimi |
From: John R. <jr...@ce...> - 2013-10-29 21:28:45
|
On Oct 29, 2013, at 10:52 AM, Nick Hall <nic...@ho...> wrote: > There have been a couple of threads suggesting that we move from > subversion to git. > > What are your views? > > The options are: > > 1. Continue to use subversion. > 2. Convert to using git. > 3. Convert to using git, and move the hosting from SourceForge. > 4. Don't mind. > > Please keep your answers short and include your SourceForge login, if > you have one. > I think everyone here knows I prefer git. I’m not wild about SF’s git browser, but it’s no worse than the SVN browser. Moving to a git-oriented host like Github or Gitorious encourages but doesn’t require a slightly different approach to non-committer contributions: In general it’s much easier. Regards, John Ralls (SF: jralls) |
From: Vassilii K. <vas...@ta...> - 2013-10-29 21:36:50
|
On 29.10.2013 19:52, Nick Hall wrote: > There have been a couple of threads suggesting that we move from > subversion to git. > > What are your views? > > The options are: > > 1. Continue to use subversion. > 2. Convert to using git. > 3. Convert to using git, and move the hosting from SourceForge. > 4. Don't mind. > > Please keep your answers short and include your SourceForge login, if > you have one. > 2 or 3, no particular feelings about sourceforge vassilii@sf |
From: Doug B. <dou...@gm...> - 2013-10-30 01:04:49
|
On Tue, Oct 29, 2013 at 1:52 PM, Nick Hall <nic...@ho...> wrote: > There have been a couple of threads suggesting that we move from > subversion to git. > > What are your views? > > The options are: > > 1. Continue to use subversion. > 2. Convert to using git. > 3. Convert to using git, and move the hosting from SourceForge. > 4. Don't mind. > > Please keep your answers short and include your SourceForge login, if > you have one. I did not want to have to switch from svn (I haven't been using svn for that long, having learned on cvs), but colleagues on another project convinced me that it would be worthwhile. It took a couple of weeks to adjust, but now I prefer git and a good associated website. I think git and a good website (we are using bitbucket.org) are better than svn because: * I can easily switch (git stash) between projects I am working on; that can really speed up development * I like commenting on the commits * I like commenting on lines of code in the commit * It has an integrated issue tracker (automatically refers to commits and issues, and can close it for you) * makes it easy to get patches (pull request) from other users * can edit a file on the website But the biggest motivation for me is that it makes development much more of a interactive, community process. Making forking a good thing was a brilliant idea, and with good management tools, makes it easy to see and merge what others are doing. It is a much more compelling move if one gets a good website with the switch. So, I vote for #3. -Doug > Regards, > > Nick. > > > ------------------------------------------------------------------------------ > Android is increasing in popularity, but the open development platform that > developers love is also attractive to malware creators. Download this white > paper to learn more about secure code signing practices that can help keep > Android apps secure. > http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel |
From: Jiri K. <cz1...@gm...> - 2013-10-30 07:33:34
|
git: +1 there is also new code review gui for github projects - gerrithub.io j. |
From: Jerome <rom...@ya...> - 2013-10-30 08:43:17
|
Some months ago, we listed some limitations[1] before using GitHub[2]/gitorious! [1] http://sourceforge.net/mailarchive/message.php?msg_id=30518256 [2] https://help.github.com/articles/github-terms-of-service Le mar. 29 oct. 2013 at 18:52,Nick Hall <nic...@ho...> a écrit : > There have been a couple of threads suggesting that we move from > subversion to git. > > What are your views? > > The options are: > > 1. Continue to use subversion. > 2. Convert to using git. > 3. Convert to using git, and move the hosting from SourceForge. > 4. Don't mind. > > Please keep your answers short and include your SourceForge login, if > you have one. > > Regards, > > Nick. > > > ------------------------------------------------------------------------------ > Android is increasing in popularity, but the open development > platform that > developers love is also attractive to malware creators. Download this > white > paper to learn more about secure code signing practices that can help > keep > Android apps secure. > http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Paul F. <pf....@gm...> - 2013-10-30 17:02:19
|
> The options are: > > 1. Continue to use subversion. I vote we continue to use subversion. (paul-franklin) |
From: Gary B. <bur...@ya...> - 2013-10-30 21:36:03
|
I don't know git so don't have any feel for it's merits and benefits with respect to svn. Are the benefits enough to overcome the inertia of learning and moving the project to git? I find svn functional and doesn't give me reasons to look at the alternatives, so I vote 1. gburto01 Gary >________________________________ > From: Nick Hall <nic...@ho...> >To: Gramps Development List <gra...@li...> >Sent: Tuesday, 29 October 2013, 17:52 >Subject: [Gramps-devel] POLL: What revision control software should we use for Gramps development? > > >There have been a couple of threads suggesting that we move from >subversion to git. > >What are your views? > >The options are: > >1. Continue to use subversion. >2. Convert to using git. >3. Convert to using git, and move the hosting from SourceForge. >4. Don't mind. > >Please keep your answers short and include your SourceForge login, if >you have one. > >Regards, > >Nick. > > >------------------------------------------------------------------------------ >Android is increasing in popularity, but the open development platform that >developers love is also attractive to malware creators. Download this white >paper to learn more about secure code signing practices that can help keep >Android apps secure. >http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk >_______________________________________________ >Gramps-devel mailing list >Gra...@li... >https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > |
From: Jerome <rom...@ya...> - 2013-10-31 06:53:57
|
I only have used git clone command for installing pygobject, gtkspell, osm-gps-map, etc ... About Gramps project, I don't mind! So, I vote for (4.) [or (1.) and (2.)] ... Note, we also need to find an alternative to svn2cl for generating Changelog files: $ svn2cl --reparagraph --include-rev --authors=data/authors.xml $ cd po $ svn2cl --reparagraph --include-rev --authors=../data/authors.xml $ cd .. http://www.gramps-project.org/wiki/index.php?title=What_to_do_for_a_release#Changelog_and_NEWS_file Should we also try to move 'gramps-addons'? Jérôme Le mar. 29 oct. 2013 at 18:52,Nick Hall <nic...@ho...> a écrit : > There have been a couple of threads suggesting that we move from > subversion to git. > > What are your views? > > The options are: > > 1. Continue to use subversion. > 2. Convert to using git. > 3. Convert to using git, and move the hosting from SourceForge. > 4. Don't mind. > > Please keep your answers short and include your SourceForge login, if > you have one. > > Regards, > > Nick. > > > ------------------------------------------------------------------------------ > Android is increasing in popularity, but the open development > platform that > developers love is also attractive to malware creators. Download this > white > paper to learn more about secure code signing practices that can help > keep > Android apps secure. > http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Benny M. <ben...@gm...> - 2013-10-31 14:32:57
|
I vote 2 As to 2 or 3. Many projects use SF only for hosting files it seems. So, even if we move to github/gitorious/bitbucket (I use all 3 for different projects already actually), SF for file hosting is still interesting, because SF never made problems about our data use (specifically gramps-addons downloads !!). The web interface of SF is shit, but truth be told, I don't use the one of github/gitorious/bitbucket, only need git gui locally for my needs. Perhaps we can ask SF if they plan online edit in the near future if people think that is a killer feature for casual development? For developers, once used to git, they will not look back. For simple tasks, only knowing the very basics ( https://git.wiki.kernel.org/index.php/GitSvnCrashCourse ) seems to work, though I see some of my students messing up enormously with branches, so some handholding (good doc for translators, eg branch per translation) will be needed. As Brian indicated, if the result is git, we need a conversion manager, and it will not be me. Benny 2013/10/31 Jerome <rom...@ya...> > > I only have used git clone command for installing pygobject, gtkspell, > osm-gps-map, etc ... About Gramps project, I don't mind! > > So, I vote for (4.) [or (1.) and (2.)] ... > > Note, we also need to find an alternative to svn2cl for generating > Changelog files: > > $ svn2cl --reparagraph --include-rev --authors=data/authors.xml > $ cd po > $ svn2cl --reparagraph --include-rev --authors=../data/authors.xml > $ cd .. > > > http://www.gramps-project.org/wiki/index.php?title=What_to_do_for_a_release#Changelog_and_NEWS_file > > Should we also try to move 'gramps-addons'? > > > Jérôme > > > Le mar. 29 oct. 2013 at 18:52,Nick Hall <nic...@ho...> a > écrit : > > There have been a couple of threads suggesting that we move from > > subversion to git. > > > > What are your views? > > > > The options are: > > > > 1. Continue to use subversion. > > 2. Convert to using git. > > 3. Convert to using git, and move the hosting from SourceForge. > > 4. Don't mind. > > > > Please keep your answers short and include your SourceForge login, if > > you have one. > > > > Regards, > > > > Nick. > > > > > > > ------------------------------------------------------------------------------ > > Android is increasing in popularity, but the open development > > platform that > > developers love is also attractive to malware creators. Download this > > white > > paper to learn more about secure code signing practices that can help > > keep > > Android apps secure. > > > http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk > > _______________________________________________ > > Gramps-devel mailing list > > Gra...@li... > > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > > > > ------------------------------------------------------------------------------ > Android is increasing in popularity, but the open development platform that > developers love is also attractive to malware creators. Download this white > paper to learn more about secure code signing practices that can help keep > Android apps secure. > http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Adam S. <ad...@cs...> - 2013-10-31 15:02:19
|
If git is picked, we might want to follow the branching model at: http://nvie.com/posts/a-successful-git-branching-model/ I've used it before and it works really well and is easy to do. As for a git GUI, never really used one. Do everything command line. On Thu, 2013-10-31 at 15:32 +0100, Benny Malengier wrote: > I vote 2 > > > As to 2 or 3. Many projects use SF only for hosting files it seems. > So, even if we move to github/gitorious/bitbucket (I use all 3 for > different projects already actually), SF for file hosting is still > interesting, because SF never made problems about our data use > (specifically gramps-addons downloads !!). > > The web interface of SF is shit, but truth be told, I don't use the > one of github/gitorious/bitbucket, only need git gui locally for my > needs. Perhaps we can ask SF if they plan online edit in the near > future if people think that is a killer feature for casual > development? > > > > For developers, once used to git, they will not look back. For simple > tasks, only knowing the very basics > ( https://git.wiki.kernel.org/index.php/GitSvnCrashCourse ) seems to > work, though I see some of my students messing up enormously with > branches, so some handholding (good doc for translators, eg branch per > translation) will be needed. As Brian indicated, if the result is git, > we need a conversion manager, and it will not be me. > > > Benny > > > > 2013/10/31 Jerome <rom...@ya...> > > I only have used git clone command for installing pygobject, > gtkspell, > osm-gps-map, etc ... About Gramps project, I don't mind! > > So, I vote for (4.) [or (1.) and (2.)] ... > > Note, we also need to find an alternative to svn2cl for > generating > Changelog files: > > $ svn2cl --reparagraph --include-rev > --authors=data/authors.xml > $ cd po > $ svn2cl --reparagraph --include-rev > --authors=../data/authors.xml > $ cd .. > > http://www.gramps-project.org/wiki/index.php?title=What_to_do_for_a_release#Changelog_and_NEWS_file > > Should we also try to move 'gramps-addons'? > > > Jérôme > > > Le mar. 29 oct. 2013 at 18:52,Nick Hall > <nic...@ho...> a > écrit : > > > There have been a couple of threads suggesting that we move > from > > subversion to git. > > > > What are your views? > > > > The options are: > > > > 1. Continue to use subversion. > > 2. Convert to using git. > > 3. Convert to using git, and move the hosting from > SourceForge. > > 4. Don't mind. > > > > Please keep your answers short and include your SourceForge > login, if > > you have one. > > > > Regards, > > > > Nick. > > > > > > > ------------------------------------------------------------------------------ > > Android is increasing in popularity, but the open > development > > platform that > > developers love is also attractive to malware creators. > Download this > > white > > paper to learn more about secure code signing practices that > can help > > keep > > Android apps secure. > > > http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk > > _______________________________________________ > > Gramps-devel mailing list > > Gra...@li... > > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > > > ------------------------------------------------------------------------------ > Android is increasing in popularity, but the open development > platform that > developers love is also attractive to malware creators. > Download this white > paper to learn more about secure code signing practices that > can help keep > Android apps secure. > http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > > ------------------------------------------------------------------------------ > Android is increasing in popularity, but the open development platform that > developers love is also attractive to malware creators. Download this white > paper to learn more about secure code signing practices that can help keep > Android apps secure. > http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel -- Adam (ad...@cs...) |
From: Doug B. <dou...@gm...> - 2013-10-31 18:43:22
|
On Thu, Oct 31, 2013 at 7:32 AM, Benny Malengier <ben...@gm...> wrote: > I vote 2 > > As to 2 or 3. Many projects use SF only for hosting files it seems. So, even > if we move to github/gitorious/bitbucket (I use all 3 for different projects > already actually), SF for file hosting is still interesting, because SF > never made problems about our data use (specifically gramps-addons downloads > !!). I agree that it has been nice that SourceForge has been fairly reliable from the command line, and they have never given us issue with the somewhat alternative way that we use the SVN to serve our addon listings and downloads. As we think about some changes, it might be nice to move the serving of the listings to a little server-side script. Where could that go? Currently the listing.LANG is generated by touching all addons. It would be better if the listings for a particular language could be gathered on the fly, or at periodic times (every 10 minutes), or when a commit triggers it. If we have each addon have its own listing in various languages, then a dynamic script could look something like: LANG = HTTP.get("lang") for addon in contrib: if exists(addon + "/listing.txt): for line in open(addon + "/listing.txt"): if line.startswith(LANG): yield line... So, it would need to have access to either an updated repository directly, or to an interface over the internet. The downloads could then also be served independently of the repository. (We could even put the URL in listing so that each one could come from anywhere). We would need a server-side URL that we control. Would this server-side script architecture be worthwhile? Or just keep using a repository as a file server? > The web interface of SF is shit, but truth be told, I don't use the one of > github/gitorious/bitbucket, only need git gui locally for my needs. Perhaps > we can ask SF if they plan online edit in the near future if people think > that is a killer feature for casual development? If SourceForge had definite plans to better support git, that sounds like a fine path. > For developers, once used to git, they will not look back. For simple tasks, > only knowing the very basics ( > https://git.wiki.kernel.org/index.php/GitSvnCrashCourse ) seems to work, > though I see some of my students messing up enormously with branches, so > some handholding (good doc for translators, eg branch per translation) will > be needed. As Brian indicated, if the result is git, we need a conversion > manager, and it will not be me. I would certainly help with any transitions. -Doug > Benny > > > 2013/10/31 Jerome <rom...@ya...> >> >> >> I only have used git clone command for installing pygobject, gtkspell, >> osm-gps-map, etc ... About Gramps project, I don't mind! >> >> So, I vote for (4.) [or (1.) and (2.)] ... >> >> Note, we also need to find an alternative to svn2cl for generating >> Changelog files: >> >> $ svn2cl --reparagraph --include-rev --authors=data/authors.xml >> $ cd po >> $ svn2cl --reparagraph --include-rev --authors=../data/authors.xml >> $ cd .. >> >> >> http://www.gramps-project.org/wiki/index.php?title=What_to_do_for_a_release#Changelog_and_NEWS_file >> >> Should we also try to move 'gramps-addons'? >> >> >> Jérôme >> >> >> Le mar. 29 oct. 2013 at 18:52,Nick Hall <nic...@ho...> a >> écrit : >> > There have been a couple of threads suggesting that we move from >> > subversion to git. >> > >> > What are your views? >> > >> > The options are: >> > >> > 1. Continue to use subversion. >> > 2. Convert to using git. >> > 3. Convert to using git, and move the hosting from SourceForge. >> > 4. Don't mind. >> > >> > Please keep your answers short and include your SourceForge login, if >> > you have one. >> > >> > Regards, >> > >> > Nick. >> > >> > >> > >> > ------------------------------------------------------------------------------ >> > Android is increasing in popularity, but the open development >> > platform that >> > developers love is also attractive to malware creators. Download this >> > white >> > paper to learn more about secure code signing practices that can help >> > keep >> > Android apps secure. >> > >> > http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk >> > _______________________________________________ >> > Gramps-devel mailing list >> > Gra...@li... >> > https://lists.sourceforge.net/lists/listinfo/gramps-devel >> > >> >> >> >> ------------------------------------------------------------------------------ >> Android is increasing in popularity, but the open development platform >> that >> developers love is also attractive to malware creators. Download this >> white >> paper to learn more about secure code signing practices that can help keep >> Android apps secure. >> >> http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk >> _______________________________________________ >> Gramps-devel mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > > ------------------------------------------------------------------------------ > Android is increasing in popularity, but the open development platform that > developers love is also attractive to malware creators. Download this white > paper to learn more about secure code signing practices that can help keep > Android apps secure. > http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Nick H. <nic...@ho...> - 2013-11-01 10:17:23
|
On 31/10/13 18:43, Doug Blank wrote: >> As Brian indicated, if the result is git, we need a conversion >> >manager, and it will not be me. > I would certainly help with any transitions. I'm also willing to help. Nick. |
From: John R. <jr...@ce...> - 2013-11-01 14:45:55
|
On Nov 1, 2013, at 3:17 AM, Nick Hall <nic...@ho...> wrote: > On 31/10/13 18:43, Doug Blank wrote: >>> As Brian indicated, if the result is git, we need a conversion >>>> manager, and it will not be me. >> I would certainly help with any transitions. > > I'm also willing to help. > I can easily push my already-existing git repository to wherever we choose for hosting. Of course, so can anyone else with the necessary privs. If that wherever is SF, then all that's needed is for someone with admin privs to enable Git and disable SVN in the admin control panel. Are we also going to convert gramps-addons? If so it will take somewhere between a couple of hours and a couple of days to convert it to git (probably closer to a couple of hours; IIRC there are only a few thousand commits), after which I can easily push it wherever we decide. I already have everything in place to do it, so I'll volunteer for that. One other little niggle: Git doesn't do file attributes the way SVN does. All of the $Id$ lines should go away. No time requirement, they're harmless comments, but the $Id$ won't get expanded. Line ending conversion is handled repository-wide with .gitconfig, with exceptions in .gitattributes. See https://help.github.com/articles/dealing-with-line-endings#platform-all and http://git-scm.com/book/ch7-2.html. We could use .gitattributes to set a custom 'mime-type' attribute, but what would use it? For that matter, what uses it in SVN? BTW, http://git-scm.com/book is a free web edition of Scott Chacon's Pro Git, which is an excellent guide to learning and using git. It's also available as a free ebook on that site, or in paper for about $25 in the US, probably more in Europe and the UK. You'll also find the Git man pages on that web site; I find it more convenient than running man in a terminal window. The git wiki page at http://www.gramps-project.org/wiki/index.php?title=Git will need some updating, and we'll need to announce the switch here. What else needs to be done? Regards, John Ralls |
From: Vassilii K. <vas...@ta...> - 2013-11-01 16:15:39
|
On 01.11.2013 16:45, John Ralls wrote: [SNIP] > One other little niggle: Git doesn't do file attributes the way SVN does. All of the $Id$ lines should go away. No time requirement, they're harmless comments, but the $Id$ won't get expanded. Good riddance... > BTW, http://git-scm.com/book is a free web edition of Scott Chacon's Pro Git, which is an excellent guide to learning and using git. It's also available as a free ebook on that site, or in paper for about $25 in the US, probably more in Europe and the UK. You'll also find the Git man pages on that web site; I find it more convenient than running man in a terminal window. This is indeed a great book which helped me understand git as well. Also, there is another great book, "git from the bottom up" by J.Wiegley, which I liked, too, although it is probably less appealing to non-programmers. After reading even one of these books, man pages are more than enough to remind of anything I forget. V. |
From: Nick H. <nic...@ho...> - 2013-11-01 17:08:30
|
On 01/11/13 14:45, John Ralls wrote: > Are we also going to convert gramps-addons? If so it will take somewhere between a couple of hours and a couple of days to convert it to git (probably closer to a couple of hours; IIRC there are only a few thousand commits), after which I can easily push it wherever we decide. I already have everything in place to do it, so I'll volunteer for that. Yes, I suggest we convert gramps-addons. There are only 2272 commits. > The git wiki page athttp://www.gramps-project.org/wiki/index.php?title=Git will need some updating, and we'll need to announce the switch here. What else needs to be done? There are quite a few wiki pages that will need updating. They are mainly development pages, such as: Brief introduction to SVN Getting started with Gramps development Committing policies Development using Eclipse and Pydev Addons development We will also need to update the release instructions. I assume that there is a git2cl script to replace svn2cl. There are a few places that make reference to svn in the code. Most of these are in docstrings. The get_svn_revision function will need updating. A couple of files include code to ignore .svn directories, which will no longer be necessary. Nick. |
From: John R. <jr...@ce...> - 2013-11-01 21:55:53
|
On Nov 1, 2013, at 10:08 AM, Nick Hall <nic...@ho...> wrote: > On 01/11/13 14:45, John Ralls wrote: >> Are we also going to convert gramps-addons? If so it will take somewhere between a couple of hours and a couple of days to convert it to git (probably closer to a couple of hours; IIRC there are only a few thousand commits), after which I can easily push it wherever we decide. I already have everything in place to do it, so I'll volunteer for that. > > Yes, I suggest we convert gramps-addons. There are only 2272 commits. > > >> The git wiki page athttp://www.gramps-project.org/wiki/index.php?title=Git will need some updating, and we'll need to announce the switch here. What else needs to be done? > > There are quite a few wiki pages that will need updating. They are > mainly development pages, such as: > > Brief introduction to SVN > Getting started with Gramps development > Committing policies > Development using Eclipse and Pydev > Addons development > > We will also need to update the release instructions. I assume that > there is a git2cl script to replace svn2cl. Several. This one: http://savannah.nongnu.org/projects/git2cl/ is in Debian as git2cl. > > There are a few places that make reference to svn in the code. Most of > these are in docstrings. The get_svn_revision function will need > updating. A couple of files include code to ignore .svn directories, > which will no longer be necessary. > Get_svn_revision (or a copy) should be fixed up before we make the switch. ISTM the other code changes can happen afterwards. Regards, John Ralls |
From: Tim L. <guy...@gm...> - 2013-11-04 00:22:28
|
Sorry to reply late, but I have been away on holiday. I would prefer to stay with svn, simply because I am familiar with it. The disadvantages of git are: - I would have to learn it. - it is apparently more complicated than svn. - there will inevitably be glitches in making the change. - it is important to retain the project history, would we be able to do that. - is there a git command line client for Mac OS PPC? - is there a suitable git plug-in for Eclipse (again on Mac OS PPC - though architecture probably doesn't matter for eclipse)? - web-ui views of the repository are very important to me, preferably like SF offered before they mucked everything up. It would be nice to check out all these points before making a switch. If a change is made I hope that there will be plenty of support from more experienced developers, and updates to the wiki. I feel no loyalty to SF - they have now apparently become purely commercial, and I am very frustrated at the way they had removed most of the facilities of the web-ui. They have since improved things a bit (e.g. history now gives the history of whatever page you are on, not just the history of the branch, etc.). As I said at the time, the web GUI tool that they were using seemed just fine, so I would ideally like to go back to that (can't remember the name of the tool). (Sorry, Benny, but no amount of you telling me that you find one of the GUI svn browsers works well for you can make it work well for me - I probably have a slower internet connection) (I note that when I looked at one of the git UIs, there was no next to go on to the next page of history. As JR says [1] "For those dissatisfied with the new SF code browser, I find Github's to be a bit less annoying" - not good, just a bit less annoying) Regards, Tim. [1] http://gramps.1791082.n4.nabble.com/Git-Mirror-tp4657588.html Nick Hall-6 wrote > There have been a couple of threads suggesting that we move from > subversion to git. > > What are your views? > > The options are: > > 1. Continue to use subversion. > 2. Convert to using git. > 3. Convert to using git, and move the hosting from SourceForge. > 4. Don't mind. > > Please keep your answers short and include your SourceForge login, if > you have one. > > Regards, > > Nick. > > > ------------------------------------------------------------------------------ > Android is increasing in popularity, but the open development platform > that > developers love is also attractive to malware creators. Download this > white > paper to learn more about secure code signing practices that can help keep > Android apps secure. > http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk > _______________________________________________ > Gramps-devel mailing list > Gramps-devel@.sourceforge > https://lists.sourceforge.net/lists/listinfo/gramps-devel -- View this message in context: http://gramps.1791082.n4.nabble.com/POLL-What-revision-control-software-should-we-use-for-Gramps-development-tp4663255p4663316.html Sent from the GRAMPS - Dev mailing list archive at Nabble.com. |
From: John R. <jr...@ce...> - 2013-11-04 00:41:51
|
On Nov 3, 2013, at 4:21 PM, Tim Lyons <guy...@gm...> wrote: > Sorry to reply late, but I have been away on holiday. > > I would prefer to stay with svn, simply because I am familiar with it. The > disadvantages of git are: > - I would have to learn it. Wah. ;-) > - it is apparently more complicated than svn. No, it’s simpler than svn, has more features, and logs that are actually useful. > - there will inevitably be glitches in making the change. Maybe, but you’re not likely to notice them. > - it is important to retain the project history, would we be able to do > that. Yes, of course. > - is there a git command line client for Mac OS PPC? Yes. > - is there a suitable git plug-in for Eclipse (again on Mac OS PPC - though > architecture probably doesn't matter for eclipse)? http://www.eclipse.org/egit/ > - web-ui views of the repository are very important to me, preferably like > SF offered before they mucked everything up. Take a look at https://github.com/jralls/Gramps/tree/trunk > > It would be nice to check out all these points before making a switch. > > If a change is made I hope that there will be plenty of support from more > experienced developers, and updates to the wiki. > > > I feel no loyalty to SF - they have now apparently become purely commercial, > and I am very frustrated at the way they had removed most of the facilities > of the web-ui. They have since improved things a bit (e.g. history now gives > the history of whatever page you are on, not just the history of the branch, > etc.). As I said at the time, the web GUI tool that they were using seemed > just fine, so I would ideally like to go back to that (can't remember the > name of the tool). Actually the web-gui that they were using, ViewVC, was old, creaky, and doesn’t support git or hg. They (SF) do provide a project web server in which we can install anything we like. I rather like Trac (http://trac.edgewall.org/). > > (Sorry, Benny, but no amount of you telling me that you find one of the GUI > svn browsers works well for you can make it work well for me - I probably > have a slower internet connection) With git, the repository is replicated on your machine, and you can use one of the several git GUIs > > (I note that when I looked at one of the git UIs, there was no next to go on > to the next page of history. As JR says [1] "For those dissatisfied with the > new SF code browser, I find Github's to be a bit less annoying" - not good, > just a bit less annoying) On github, it’s at the bottom-left of the page, labelled “older”. It would be nice if there was one at the top of the page as well along with a way to jump to a particular date. There isn’t, unfortunately. Regards, John Ralls |