From: Torbjorn T. <to...@to...> - 2009-02-12 13:08:22
|
Hi folks, I've been using github for a while now and it has been pure joy. I think Yaws would benefit greatly if it moved to github. It is so easy to follow the development and to contribute. Just a thought, Tobbe |
From: Davide M. <ne...@gm...> - 2009-02-12 13:50:39
|
Hi! I second that thought! :) My experience with git/github has also been very positive (thumbs up for the network graphs: http://github.com/blog/39-say-hello-to-the-network-graph-visualizer). Cheers, Davide On Thu, Feb 12, 2009 at 11:56 AM, Torbjorn Tornkvist <to...@to...>wrote: > > Hi folks, > > I've been using github for a while now and it has been pure joy. > I think Yaws would benefit greatly if it moved to github. > It is so easy to follow the development and to contribute. > > Just a thought, Tobbe > > > > > ------------------------------------------------------------------------------ > Create and Deploy Rich Internet Apps outside the browser with > Adobe(R)AIR(TM) > software. With Adobe AIR, Ajax developers can use existing skills and code > to > build responsive, highly engaging applications that combine the power of > local > resources and data with the reach of the web. Download the Adobe AIR SDK > and > Ajax docs to start building applications today- > http://p.sf.net/sfu/adobe-com > _______________________________________________ > Erlyaws-list mailing list > Erl...@li... > https://lists.sourceforge.net/lists/listinfo/erlyaws-list > |
From: Claes W. <kl...@ta...> - 2009-02-12 16:40:46
|
Davide Marquês wrote: > Hi! > > I second that thought! :) > My experience with git/github has also been very positive (thumbs up for > the network graphs: > http://github.com/blog/39-say-hello-to-the-network-graph-visualizer). > Hmmmm, I feel kinda reluctant. What would be the purpose? It's mostly Steve Vinoski and me using the repo anyway and i sure don't need no graph visualizers. Besides, svn works excellent for our purposes - thus I believe the "if it works don't fix it" theorem applies here. /klacke |
From: Davide M. <ne...@gm...> - 2009-02-12 18:59:01
|
Hi again! My comments below. On Thu, Feb 12, 2009 at 4:40 PM, Claes Wikström <kl...@ta...> wrote: > Davide Marquês wrote: > >> Hi! >> >> I second that thought! :) >> My experience with git/github has also been very positive (thumbs up for >> the network graphs: >> http://github.com/blog/39-say-hello-to-the-network-graph-visualizer). >> >> > Hmmmm, I feel kinda reluctant. What would be the purpose? I'd say: growth! :) Github would provide a simply way for others to fork the official codebase and play around with new features having them visible by the community at large (which would help finding collaborators). Using git helps speed up the collaboration process in that a small group of people can hack away, pulling/pushing changes as they go along without having to depend on the "official repository". As for developments on the "official" Yaws repository, since you'd be using the same scm tool you could pull patches directly from other people's repositories without having to email patches around. I really like github in that it get's people's contributions out in the open. Even if their changes aren't accepted back into the "official" codebase they're still there (who knows if someone won't find them useful!). That might be enough to get more people contributing to Yaws and even if it doesn't it will enable Yaws to reach a more wider audience. It's mostly Steve Vinoski and me using the repo anyway > and i sure don't need no graph visualizers. The visualizer is actually quite useful for seeing code changes across branches and user's repositories. > Besides, svn works excellent for our purposes - thus I believe the > "if it works don't fix it" theorem applies here. I am tempted to suggest a Yaws github mirror ( http://github.com/guides/import-from-subversion) but since that would create a new channel for receiving contributions I think it's your call. ;) > > > > /klacke > > Davide |
From: Torbjorn T. <to...@to...> - 2009-02-12 20:06:34
|
Claes Wikström <kl...@ta...> writes: > Davide Marquês wrote: >> Hi! >> >> I second that thought! :) >> My experience with git/github has also been very positive (thumbs up for >> the network graphs: >> http://github.com/blog/39-say-hello-to-the-network-graph-visualizer). >> > > Hmmmm, I feel kinda reluctant. What would be the purpose? > > It's mostly Steve Vinoski and me using the repo anyway Exactly! --Tobbe > and i sure don't need no graph visualizers. > > Besides, svn works excellent for our purposes - thus I believe the > "if it works don't fix it" theorem applies here. > > > /klacke > > > ------------------------------------------------------------------------------ -- KREDITOR EUROPE AB S:t Eriksgatan 117 SE-113 43 Stockholm, Sweden Tel: +46(0)8-120 120 00 Fax: +46(0)8-120 120 99 Email: tor...@kr... Web: www.kreditor.se |
From: Claes W. <kl...@ta...> - 2009-02-12 22:44:37
|
Torbjorn Tornkvist wrote: Yaeh yeah ... all praise to the git. So, well, maybe then. Need to find some time as well. Quite a few release scripts and whatnot to rewrite. /klacke |
From: Hans U. N. <hu...@n-...> - 2009-02-13 12:53:42
|
Claes Wikstrom wrote: > Yaeh yeah ... all praise to the git. > > So, well, maybe then. Need to find some time as well. Quite a few > release scripts and whatnot to rewrite. In case it helps, I have been tracking yaws SVN using a git-svn repo created with the following command line (requires git 1.6.0 or 1.6.1 for the wildcards in the branches and tags): git svn clone \ https://erlyaws.svn.sourceforge.net/svnroot/erlyaws/ yaws \ --trunk='trunk/yaws' \ --branches='branches/*/yaws' \ --tags='tags/*/yaws' \ --authors-file='erlyaws-users' This needs a file named erlyaws-users consisting of username=Full Name <em...@ex... lines for the following user names: brucefitzsimons cschultz etnt jbevemyr jockeg juliannoble klacke lpsmith lukeg mbj mikaelka mikl seanhinde sstrollo uid50986 vinoski yarivvv The "klacke" and "vinoski" parts I could easily fill in, but not so the others. The changes to the release scripts should mostly be taken care of by the attached 0001-make-release-Adapt-for-git-repo-instead-of-svn.patch. The win32 patches came up while I was hacking on scripts/make-release. -- Hans Ulrich Niedermann |
From: Hans U. N. <hu...@n-...> - 2009-02-13 13:25:26
|
Hans Ulrich Niedermann wrote: > The changes to the release scripts should mostly be taken care of by the > attached 0001-make-release-Adapt-for-git-repo-instead-of-svn.patch. I have changed the make-release script a little. Now I have split it into two patches (disregard my former patch to make-release): 0001-make-release-make-more-robust-easy-to-read.patch make-release: make more robust, easy to read No changes should be visible from the outside. Inside, we changed this: - do not set obsolete CVS_RSH - define tag and tarball names in single place - more robust regarding directory to be called from 0002-make-release-Adapt-for-git-repo-instead-of-svn.patch make-release: Adapt for git repo instead of svn Functionally equivalent to the old script except: - use git repository instead of SVN - do not push the local git changes to any public repo (unlike "svn tag" does) Note: The workflow regarding tagging, pushing the tag, building the sources, and uploading the source tarball and windows installer might need rethinking. Note2: The "release resides" output probably was not accurate before regarding the location of the Win32 installer, and now is probably using a different directory. I hope any of that stuff can be helpful. -- Hans Ulrich Niedermann |
From: Torbjorn T. <to...@to...> - 2009-02-13 14:25:06
|
Do you also have some clever way to keep it in sync? I'm using the following naive method: $ crontab -l # m h dom mon dow command @daily /home/tobbe/bin/sync_git_repos.sh $ cat /home/tobbe/bin/sync_git_repos.sh #!/bin/sh cd /home/tobbe/git/yaws git-svn fetch git merge git-svn But for many repos and branches, a better way must exist, or? --Tobbe Hans Ulrich Niedermann <hu...@n-...> writes: > Hans Ulrich Niedermann wrote: > >> The changes to the release scripts should mostly be taken care of by the >> attached 0001-make-release-Adapt-for-git-repo-instead-of-svn.patch. > > I have changed the make-release script a little. Now I have split it > into two patches (disregard my former patch to make-release): > > > > 0001-make-release-make-more-robust-easy-to-read.patch > > make-release: make more robust, easy to read > > No changes should be visible from the outside. > > Inside, we changed this: > - do not set obsolete CVS_RSH > - define tag and tarball names in single place > - more robust regarding directory to be called from > > > > 0002-make-release-Adapt-for-git-repo-instead-of-svn.patch > > make-release: Adapt for git repo instead of svn > > Functionally equivalent to the old script except: > - use git repository instead of SVN > - do not push the local git changes to any public repo > (unlike "svn tag" does) > > Note: The workflow regarding tagging, pushing the tag, > building the sources, and uploading the source > tarball and windows installer might need rethinking. > > Note2: The "release resides" output probably was not > accurate before regarding the location of the > Win32 installer, and now is probably using a > different directory. > > > I hope any of that stuff can be helpful. > > -- > Hans Ulrich Niedermann > > > ------------------------------------------------------------------------------ > Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA > -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise > -Strategies to boost innovation and cut costs with open source participation > -Receive a $600 discount off the registration fee with the source code: SFAD > http://p.sf.net/sfu/XcvMzF8H_______________________________________________ > Erlyaws-list mailing list > Erl...@li... > https://lists.sourceforge.net/lists/listinfo/erlyaws-list -- KREDITOR EUROPE AB S:t Eriksgatan 117 SE-113 43 Stockholm, Sweden Tel: +46(0)8-120 120 00 Fax: +46(0)8-120 120 99 Email: tor...@kr... Web: www.kreditor.se |
From: Hans U. N. <hu...@n-...> - 2009-02-13 18:21:12
Attachments:
signature.asc
|
Torbjorn Tornkvist wrote: > Do you also have some clever way to keep it in sync? No. Every time I start working on something yaws-related, I (manually) run a "git svn rebase" to get updated to SVN HEAD. > But for many repos and branches, a better way must exist, or? Migrate to git and let SVN rot, and that's where we are trying to get to here, right? :) For your specific case (and this is not really yaws-related), I'd create a directory /path/to/dir where all subdirs are git-svn working trees, and regularly run a naive (untested) script like #!/bin/sh cd /path/to/dir for dir in * do (cd "$dir" && git svn rebase) done and then start debugging why it does not quite work. -- Hans Ulrich Niedermann |
From: Torbjorn T. <to...@to...> - 2009-02-12 23:02:38
|
Torbjorn Tornkvist <to...@to...> writes: > Claes Wikström <kl...@ta...> writes: > >> Davide Marquês wrote: >>> Hi! >>> >>> I second that thought! :) >>> My experience with git/github has also been very positive (thumbs up for >>> the network graphs: >>> http://github.com/blog/39-say-hello-to-the-network-graph-visualizer). >>> >> >> Hmmmm, I feel kinda reluctant. What would be the purpose? >> >> It's mostly Steve Vinoski and me using the repo anyway > > Exactly! Sorry if I was a bit brief; I had to run for the bus. I truly believe that you would see an increased activity among Yaws contributors if you choose to put Yaws at Github. Why? Simply because Github makes everything so visible. For example, that 'network visualizer' that you dismissed so quickly. It is actually extremely useful. With it, you can see exactly what other people are doing in their branches. You can pin-point a certain commit with just a click, scrutinize the code and even give feedback comments. And if you want to bring in some new functionality from a branch, well then you have the immense merging power of git in your hands. Perhaps you just want to cherry-pick a certain commit? That is just fine too with git. Github also have support for a wiki where the community can contribute, and a way to publish your apps. HTML docs. So what else can I say? Github just bring the fun into the collaborative development effort. And what about if Github would go bankrupt? Well, then you still would have a *complete* repository, wherever you have a clone checked out, and so would every other developer. In the worst case scenario, development could continue using the built-in mail-patch support that Linus is using for the Linux kernel. Phui...that was a long rant, Tobbe > > --Tobbe > >> and i sure don't need no graph visualizers. >> >> Besides, svn works excellent for our purposes - thus I believe the >> "if it works don't fix it" theorem applies here. >> >> >> /klacke >> >> >> ------------------------------------------------------------------------------ > > -- > KREDITOR EUROPE AB > S:t Eriksgatan 117 > SE-113 43 Stockholm, Sweden > Tel: +46(0)8-120 120 00 > Fax: +46(0)8-120 120 99 > Email: tor...@kr... > Web: www.kreditor.se > > > ------------------------------------------------------------------------------ -- KREDITOR EUROPE AB S:t Eriksgatan 117 SE-113 43 Stockholm, Sweden Tel: +46(0)8-120 120 00 Fax: +46(0)8-120 120 99 Email: tor...@kr... Web: www.kreditor.se |
From: Torbjorn T. <to...@to...> - 2009-02-13 13:19:54
|
Nice! I've also been tracking the Yaws repos for quite some time: http://www.tornkvist.org/gitweb?p=yaws.git;a=summary I haven't used an authors-file though... --Tobbe Hans Ulrich Niedermann <hu...@n-...> writes: > Claes Wikstrom wrote: > >> Yaeh yeah ... all praise to the git. >> >> So, well, maybe then. Need to find some time as well. Quite a few >> release scripts and whatnot to rewrite. > > In case it helps, I have been tracking yaws SVN using a git-svn repo > created with the following command line (requires git 1.6.0 or 1.6.1 for > the wildcards in the branches and tags): > > git svn clone \ > https://erlyaws.svn.sourceforge.net/svnroot/erlyaws/ yaws \ > --trunk='trunk/yaws' \ > --branches='branches/*/yaws' \ > --tags='tags/*/yaws' \ > --authors-file='erlyaws-users' > > This needs a file named erlyaws-users consisting of > > username=Full Name <em...@ex... > > lines for the following user names: > > brucefitzsimons > cschultz > etnt > jbevemyr > jockeg > juliannoble > klacke > lpsmith > lukeg > mbj > mikaelka > mikl > seanhinde > sstrollo > uid50986 > vinoski > yarivvv > > The "klacke" and "vinoski" parts I could easily fill in, but not so the > others. > > The changes to the release scripts should mostly be taken care of by the > attached 0001-make-release-Adapt-for-git-repo-instead-of-svn.patch. > > The win32 patches came up while I was hacking on scripts/make-release. > > -- > Hans Ulrich Niedermann > > > > ------------------------------------------------------------------------------ > Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA > -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise > -Strategies to boost innovation and cut costs with open source participation > -Receive a $600 discount off the registration fee with the source code: SFAD > http://p.sf.net/sfu/XcvMzF8H_______________________________________________ > Erlyaws-list mailing list > Erl...@li... > https://lists.sourceforge.net/lists/listinfo/erlyaws-list -- KREDITOR EUROPE AB S:t Eriksgatan 117 SE-113 43 Stockholm, Sweden Tel: +46(0)8-120 120 00 Fax: +46(0)8-120 120 99 Email: tor...@kr... Web: www.kreditor.se |
From: Claes W. <kl...@ta...> - 2009-02-18 12:46:13
|
Torbjorn Tornkvist wrote: > Hi folks, > > I've been using github for a while now and it has been pure joy. > I think Yaws would benefit greatly if it moved to github. > It is so easy to follow the development and to contribute. > > Just a thought, Tobbe I had a look at this yesterday, and I must say that it sure looks good. I'll let you all know what happens soon. /klacke |