Am I the only one getting very poor performance from FreeHG ? Quite often I get a 404 Not Found and right now it's hanging. Everyone confirms that Mercurial itself is really fast and I've seen other reports criticising FreeHG's performance. Perhaps we should think about moving host? It's not always easy to find time to devote to Dillo so it's rather aggravating when that time is wasted just waiting for a connection to the server. I'm committed enough to grit my teeth and wait but I can see it putting off would-be contributors. Just a thought, Jeremy Henty
On Fri, Jan 30, 2009 at 01:21:47PM +0000, Jeremy Henty wrote:
Am I the only one getting very poor performance from FreeHG ? Quite often I get a 404 Not Found and right now it's hanging. Everyone confirms that Mercurial itself is really fast and I've seen other reports criticising FreeHG's performance. Perhaps we should think about moving host? It's not always easy to find time to devote to Dillo so it's rather aggravating when that time is wasted just waiting for a connection to the server. I'm committed enough to grit my teeth and wait but I can see it putting off would-be contributors.
Just a thought,
Yes, I've also had trouble with it, and when normal it's slower than our Wearlab's CVS. A couple of days ago (while developoing/reviewing patches) I digged a bit on it and it seems that bitbucket is much faster. We can try bitbucket while we find a long term solution (e.g. FSF's savannah is offering Mercurial and Git repos, but the applying process may take some time). At some point in time we should move out from the Wearlab, as it may be closed soon. Currently we need webserver/CGI/python shell accounts and a DCVS (Hg or Git). CGI is quite useful, but we may use another bugtracker too. Suggestions? -- Cheers Jorge.- ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
On Fri, Jan 30, 2009 at 12:22:46PM -0300, Jorge Arellano Cid wrote:
[...] At some point in time we should move out from the Wearlab, as it may be closed soon. Currently we need webserver/CGI/python shell accounts and a DCVS (Hg or Git). CGI is quite useful, but we may use another bugtracker too.
Oh, I forgot email! (that's paramount :) -- Cheers Jorge.- ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
Hi Jorge, On Fri, 30 Jan 2009 12:22:46 -0300 Jorge Arellano Cid <jcid@dillo.org> wrote:
On Fri, Jan 30, 2009 at 01:21:47PM +0000, Jeremy Henty wrote:
Am I the only one getting very poor performance from FreeHG ? Quite often I get a 404 Not Found and right now it's hanging. Everyone confirms that Mercurial itself is really fast and I've seen other reports criticising FreeHG's performance. Perhaps we should think about moving host? It's not always easy to find time to devote to Dillo so it's rather aggravating when that time is wasted just waiting for a connection to the server. I'm committed enough to grit my teeth and wait but I can see it putting off would-be contributors.
Just a thought,
Yes, I've also had trouble with it, and when normal it's slower than our Wearlab's CVS.
A couple of days ago (while developoing/reviewing patches) I digged a bit on it and it seems that bitbucket is much faster. We can try bitbucket while we find a long term solution (e.g. FSF's savannah is offering Mercurial and Git repos, but the applying process may take some time).
At some point in time we should move out from the Wearlab, as it may be closed soon. Currently we need webserver/CGI/python shell accounts and a DCVS (Hg or Git). CGI is quite useful, but we may use another bugtracker too.
The server which actually hosts the dillo debian and openmoko packages should be an alternative. At least performance and bandwidth should be no problem. Maybe moving hg there is a starting point. Greetings Andreas Kemnade
Hi Andreas, On Fri, Jan 30, 2009 at 05:24:56PM +0100, Andreas Kemnade wrote:
Hi Jorge,
On Fri, 30 Jan 2009 12:22:46 -0300 Jorge Arellano Cid <jcid@dillo.org> wrote:
On Fri, Jan 30, 2009 at 01:21:47PM +0000, Jeremy Henty wrote:
Am I the only one getting very poor performance from FreeHG ? Quite often I get a 404 Not Found and right now it's hanging. Everyone confirms that Mercurial itself is really fast and I've seen other reports criticising FreeHG's performance. Perhaps we should think about moving host? It's not always easy to find time to devote to Dillo so it's rather aggravating when that time is wasted just waiting for a connection to the server. I'm committed enough to grit my teeth and wait but I can see it putting off would-be contributors.
Just a thought,
Yes, I've also had trouble with it, and when normal it's slower than our Wearlab's CVS.
A couple of days ago (while developoing/reviewing patches) I digged a bit on it and it seems that bitbucket is much faster. We can try bitbucket while we find a long term solution (e.g. FSF's savannah is offering Mercurial and Git repos, but the applying process may take some time).
At some point in time we should move out from the Wearlab, as it may be closed soon. Currently we need webserver/CGI/python shell accounts and a DCVS (Hg or Git). CGI is quite useful, but we may use another bugtracker too.
The server which actually hosts the dillo debian and openmoko packages should be an alternative. At least performance and bandwidth should be no problem. Maybe moving hg there is a starting point.
Does this server belong to the Wearlab? If not, what's its expected lifespan? Or are you suggesting it as an interim solution for mercurial hosting? -- Cheers Jorge.- ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
Hi, On Fri, 30 Jan 2009 17:24:56 +0100 Andreas Kemnade <akemnade@tzi.de> wrote:
Hi Jorge,
On Fri, 30 Jan 2009 12:22:46 -0300 Jorge Arellano Cid <jcid@dillo.org> wrote:
On Fri, Jan 30, 2009 at 01:21:47PM +0000, Jeremy Henty wrote:
Am I the only one getting very poor performance from FreeHG ? Quite often I get a 404 Not Found and right now it's hanging. Everyone confirms that Mercurial itself is really fast and I've seen other reports criticising FreeHG's performance. Perhaps we should think about moving host? It's not always easy to find time to devote to Dillo so it's rather aggravating when that time is wasted just waiting for a connection to the server. I'm committed enough to grit my teeth and wait but I can see it putting off would-be contributors.
Just a thought,
Yes, I've also had trouble with it, and when normal it's slower than our Wearlab's CVS.
A couple of days ago (while developoing/reviewing patches) I digged a bit on it and it seems that bitbucket is much faster. We can try bitbucket while we find a long term solution (e.g. FSF's savannah is offering Mercurial and Git repos, but the applying process may take some time).
At some point in time we should move out from the Wearlab, as it may be closed soon. Currently we need webserver/CGI/python shell accounts and a DCVS (Hg or Git). CGI is quite useful, but we may use another bugtracker too.
The server which actually hosts the dillo debian and openmoko packages should be an alternative. At least performance and bandwidth should be no problem. Maybe moving hg there is a starting point.
ok, try hg clone http://hg.dillo.org/dillo just add entries for hg.dillo.org in your /etc/hosts to point to that server. 85.214.105.140 hg.dillo.org or 2001:6f8:900:71b::2 hg.dillo.org push access (with ssl) is not set up yet. When it is done, of course the dns can be changed so that hg.dillo.org points to the right server. Greetings Andreas Kemnade
On Wed, Feb 04, 2009 at 08:31:06PM +0100, Andreas Kemnade wrote:
ok, try hg clone http://hg.dillo.org/dillo
Now *that* was nice and fast! Thanks! Jeremy Henty
On Wed, Feb 04, 2009 at 08:31:06PM +0100, Andreas Kemnade wrote:
Hi,
On Fri, 30 Jan 2009 17:24:56 +0100 Andreas Kemnade <akemnade@tzi.de> wrote:
Hi Jorge,
On Fri, 30 Jan 2009 12:22:46 -0300 Jorge Arellano Cid <jcid@dillo.org> wrote:
On Fri, Jan 30, 2009 at 01:21:47PM +0000, Jeremy Henty wrote:
Am I the only one getting very poor performance from FreeHG ? Quite often I get a 404 Not Found and right now it's hanging. Everyone confirms that Mercurial itself is really fast and I've seen other reports criticising FreeHG's performance. Perhaps we should think about moving host? It's not always easy to find time to devote to Dillo so it's rather aggravating when that time is wasted just waiting for a connection to the server. I'm committed enough to grit my teeth and wait but I can see it putting off would-be contributors.
Just a thought,
Yes, I've also had trouble with it, and when normal it's slower than our Wearlab's CVS.
A couple of days ago (while developoing/reviewing patches) I digged a bit on it and it seems that bitbucket is much faster. We can try bitbucket while we find a long term solution (e.g. FSF's savannah is offering Mercurial and Git repos, but the applying process may take some time).
At some point in time we should move out from the Wearlab, as it may be closed soon. Currently we need webserver/CGI/python shell accounts and a DCVS (Hg or Git). CGI is quite useful, but we may use another bugtracker too.
The server which actually hosts the dillo debian and openmoko packages should be an alternative. At least performance and bandwidth should be no problem. Maybe moving hg there is a starting point.
ok, try hg clone http://hg.dillo.org/dillo
just add entries for hg.dillo.org in your /etc/hosts to point to that server. 85.214.105.140 hg.dillo.org
It works very well!
push access (with ssl) is not set up yet. When it is done, of course the dns can be changed so that hg.dillo.org points to the right server.
Good. Just let me know when it's done. -- Cheers Jorge.-
yOn Fri, Jan 30, 2009 at 12:22:46PM -0300, Jorge Arellano Cid wrote:
On Fri, Jan 30, 2009 at 01:21:47PM +0000, Jeremy Henty wrote:
Am I the only one getting very poor performance from FreeHG ? Quite often I get a 404 Not Found and right now it's hanging. Everyone confirms that Mercurial itself is really fast and I've seen other reports criticising FreeHG's performance. Perhaps we should think about moving host? It's not always easy to find time to devote to Dillo so it's rather aggravating when that time is wasted just waiting for a connection to the server. I'm committed enough to grit my teeth and wait but I can see it putting off would-be contributors.
Just a thought,
Yes, I've also had trouble with it, and when normal it's slower than our Wearlab's CVS.
A couple of days ago (while developoing/reviewing patches) I digged a bit on it and it seems that bitbucket is much faster. We can try bitbucket while we find a long term solution (e.g. FSF's savannah is offering Mercurial and Git repos, but the applying process may take some time).
At some point in time we should move out from the Wearlab, as it may be closed soon. Currently we need webserver/CGI/python shell accounts and a DCVS (Hg or Git). CGI is quite useful, but we may use another bugtracker too.
Suggestions?
I agree. freehg.org is just very simple to setup so I chose that for the CSS prototype. I doubt that setting up a savannah project would take very long. Anyone volunteering? Cheers, Johannes
On Tue, Feb 03, 2009 at 01:47:48PM +0100, Hofmann Johannes wrote:
I doubt that setting up a savannah project would take very long.
Really? I just had a look and there's a long checklist. You have to supply a fairly detailed project description, so the core devs would have to agree to one before signing up. You have to list all your dependencies and assert that they are free too. You also have to check that all your files have a valid copyright notice, which is currently not true of most of our *.{h,hh} files. (Mind you, I got a laugh from their "I read carefully and won't check this" item.) I asked the local Linux Users Group for recommendations and bitbucket was mentioned. What do people think? Terms of service: http://bitbucket.org/site/terms/ Note the clauses: By submitting Content to Avantlumiere for inclusion on your Website, you grant Avantlumiere a world-wide, royalty-free, and non-exclusive license to reproduce, modify, adapt and publish the Content solely for the purpose of displaying, distributing and promoting your account or repository. I guess the "solely for the purpose of displaying ..." clause makes that OK. They presumably want to be able to advertise the fact that they host Dillo without us claiming copyright infringement, which is fair enough. Also: Avantlumiere reserves the right, at its sole discretion, to modify or replace any part of this Agreement. It is your responsibility to check this Agreement periodically for changes. Your continued use of or access to the Website following the posting of any changes to this Agreement constitutes acceptance of those changes. That makes me nervous, but bitbucket is popular so I guess people trust them not to mess their customers around. I'll set up a BitBucket repo if people agree. Regards, Jeremy Henty
On Tue, Feb 03, 2009 at 01:45:36PM +0000, Jeremy Henty wrote:
On Tue, Feb 03, 2009 at 01:47:48PM +0100, Hofmann Johannes wrote:
I doubt that setting up a savannah project would take very long.
Really? I just had a look and there's a long checklist. You have to supply a fairly detailed project description, so the core devs would have to agree to one before signing up. You have to list all your dependencies and assert that they are free too. You also have to check that all your files have a valid copyright notice, which is currently not true of most of our *.{h,hh} files. (Mind you, I got a laugh from their "I read carefully and won't check this" item.)
Oh sorry, should have checked more carefully...
I asked the local Linux Users Group for recommendations and bitbucket was mentioned. What do people think?
Terms of service: http://bitbucket.org/site/terms/
Note the clauses:
By submitting Content to Avantlumiere for inclusion on your Website, you grant Avantlumiere a world-wide, royalty-free, and non-exclusive license to reproduce, modify, adapt and publish the Content solely for the purpose of displaying, distributing and promoting your account or repository.
I guess the "solely for the purpose of displaying ..." clause makes that OK. They presumably want to be able to advertise the fact that they host Dillo without us claiming copyright infringement, which is fair enough.
Also:
Avantlumiere reserves the right, at its sole discretion, to modify or replace any part of this Agreement. It is your responsibility to check this Agreement periodically for changes. Your continued use of or access to the Website following the posting of any changes to this Agreement constitutes acceptance of those changes.
That makes me nervous, but bitbucket is popular so I guess people trust them not to mess their customers around.
Argh, I really hate this stuff. I guess we really want an independent server/virtual machine somewhere just as we have at wearlab until now.
I'll set up a BitBucket repo if people agree.
Maybe creating just frequently updated copy there would help already? Regards, Johannes
On Tue, Feb 03, 2009 at 03:10:11PM +0100, Hofmann Johannes wrote:
I guess we really want an independent server/virtual machine somewhere just as we have at wearlab until now.
I already own a virtual machine at bytemark.co.uk. I can look into setting up mercurial there. The Bytemark hosting crew are pretty geek-savvy. Regards, Jeremy Henty
* Jeremy Henty <onepoint@starurchin.org> wrote:
On Tue, Feb 03, 2009 at 01:47:48PM +0100, Hofmann Johannes wrote:
I doubt that setting up a savannah project would take very long. Really? I just had a look and there's a long checklist. ...
Did anyone ever look at launchpad? https://launchpad.net/+tour It's a "batteries included" type of project infrastructure host, feature-rich, easy, reliable, and free. It could provide hosting for almost everything the project needs and provide plenty of room to grow. The tour gives a pretty good overview... it may be a lot to absorb all at once, but it's worth a look. -- Scott
On Thu, Feb 05, 2009 at 05:52:40AM -0700, Scott Scriven wrote:
Did anyone ever look at launchpad?
It's a "batteries included" type of project infrastructure host, feature-rich, easy, reliable, and free. It could provide hosting for almost everything the project needs and provide plenty of room to grow.
Looks good, but I think Dillo would have to migrate away from Mercurial to use it. They use bzr, and although they integrate with some other VCSs, mercurial isn't one of them. Regards, Jeremy Henty
* Jeremy Henty <onepoint@starurchin.org> wrote:
Looks good, but I think Dillo would have to migrate away from Mercurial to use it.
After using hg for the past couple years and bzr for about a year, I've found bzr to be an upgrade. I still use both on a regular basis, but no longer choose hg for any new projects. The main differences to be aware of are: - Branches are directories instead of labels. Each directory has only one "head", and you switch between branches with "cd". Merging is done like "cd trunk ; bzr merge ../my-bugfix". - There are a lot of plugins available to extend functionality in various ways. A couple I recommend are bzr-gtk ("bzr vis" is a nice way to browse history) and bzr-bisect (helps isolate where bugs were introduced). - It has a concept of a main line of development, and meaningful version numbers. Merges are always explicit, even when hg would merge in-line. This makes feature branches more useful. That last one probably requires a little more explanation. Say you branch from trunk at r100 to add a feature. It requires some major changes, so you break everything while refactoring and spend a few revisions getting it all working again. It takes 10 revisions total. So, you send the changes upstream. They like it. They merge it... And nobody else checked anything in while you were working. Now (in hg) trunk is at r110, with your new feature. And the revision graph ends up being a straight line, so there's no evidence a merge occurred. If anyone tries to use r101 through r109, they'll find that it's all broken. The way bzr handles it is you submit 10 revisions, and when merged, trunk bumps up to r101. The revision graph shows a branch off to the side with 10 changes (r100.1.1 through r100.1.10) and a merge at the end (r101), and the trunk contains only non-broken versions. It makes more sense to me.
They use bzr, and although they integrate with some other VCSs, mercurial isn't one of them.
It's a one-time conversion, instead of the two-way conduit they support for subversion. I tried it just now (using bzr-fastimport) and it worked. The new branch is in my "junk" folder (launchpad equivalent of /tmp/) if anyone wants to try it: bzr branch lp:~toykeeper/+junk/dillo Personally, the main thing I find annoying about bzr is that it's not the easiest thing to type. I use "alias b=bzr" in my shell to fix that. -- Scott
participants (5)
-
akemnade＠tzi.de -
dillo-dev＠toykeeper.net -
jcid＠dillo.org -
Johannes.Hofmann＠gmx.de -
onepoint＠starurchin.org