I got some exciting news for you. The first part of these are already available today!
But, first, please note that we had to change our public SSH key fingerprint. The fingerprint is now 7e:af:8d:ec:f0:39:5e:ba:52:16:ce:19:fa:d4:b8:7d and the IP of the frontend server is 87.238.52.168. Easiest way to deal with this is to delete gitorious.org from your ~/.ssh/known_hosts and reaccept the connection when you push (please do double-check that that fingerprints are correct though)
I'm also happy to tell you that Gitorious and Gitorious.org is now officially Shortcut products. Shortcut (http://shortcut.no) is a norwegian development and design company I co-founded. By Gitorious being a Shortcut product means that we're able to fund its ongoing development through consulting and providing infrastructure for other companies in the open source sphere.
Please do make use of a much better, faster and stronger Gitorious.org, we've got some more exciting things to talk about next week which is when we'll push the updated codebase to http://gitorious.org/gitorious
Enjoy and don't forget to let me know if you experience any issues with the new release!
> I got some exciting news for you. The first part of these are already
> available today!
> But, first, please note that we had to change our public SSH key
> fingerprint. The fingerprint is now
> 7e:af:8d:ec:f0:39:5e:ba:52:16:ce:19:fa:d4:b8:7d and the IP of the
> frontend server is 87.238.52.168. Easiest way to deal with this is to
> delete gitorious.org from your ~/.ssh/known_hosts and reaccept the
> connection when you push (please do double-check that that
> fingerprints are correct though)
> I'm also happy to tell you that Gitorious and Gitorious.org is now
> officially Shortcut products. Shortcut (http://shortcut.no) is a
> norwegian development and design company I co-founded. By Gitorious
> being a Shortcut product means that we're able to fund its ongoing
> development through consulting and providing infrastructure for other
> companies in the open source sphere.
> Please do make use of a much better, faster and stronger
> Gitorious.org, we've got some more exciting things to talk about next
> week which is when we'll push the updated codebase tohttp://gitorious.org/gitorious
> Enjoy and don't forget to let me know if you experience any issues
> with the new release!
On Sat, May 9, 2009 at 7:53 AM, Johan Sørensen <jo...@johansorensen.com> wrote: > Please do make use of a much better, faster and stronger > Gitorious.org, we've got some more exciting things to talk about next > week which is when we'll push the updated codebase to > http://gitorious.org/gitorious
> Enjoy and don't forget to let me know if you experience any issues > with the new release!
Doesn't the AGPL forces you to release the source today with the deploy? Or did you rewrite all the contributed source code?
And Johan Sørensen writes: > Please take a look at a much improved http://gitorious.org and read a > more detailed overview of some of all the new things available at > http://blog.gitorious.org.
I can't. At least not until I wade through the new terms of service. And if I disagree with that terms, I'm locked out of the data I've stored there. Locking out users without any warning is not nice.
> I can't. At least not until I wade through the new terms of service. > And if I disagree with that terms, I'm locked out of the data I've > stored there. Locking out users without any warning is not nice.
+1
And there are things to disagree with.
"the Content is not spam, is not machine- or randomly-generated"
I guess code that includes base64-encoded images is no longer allowed...
The indemnification clause is also a little aggressive, especially when combined with the lack of promise to remove the content on request.
Another issue: all the links are now broken. Can you do something about this? (I actually liked the old URL organization better, but I suppose it wouldn't matter so much if proper redirects were in place.)
On Sat, May 9, 2009 at 9:08 PM, Patrick Aljord <patc...@gmail.com> wrote: > Doesn't the AGPL forces you to release the source today with the > deploy? Or did you rewrite all the contributed source code?
On Sat, May 9, 2009 at 10:20 PM, Jason Riedy <ja...@acm.org> wrote:
> And Johan Sørensen writes: >> Please take a look at a much improved http://gitorious.org and read a >> more detailed overview of some of all the new things available at >> http://blog.gitorious.org.
> I can't. At least not until I wade through the new terms of service. > And if I disagree with that terms, I'm locked out of the data I've > stored there. Locking out users without any warning is not nice.
Obviously we have little interest in keeping any data you don't want there. If chose not to agree and take go elsewhere that's fine, just let me know what you want removed.
However, we're not unreasonable, if you have a strong opinion on any terms of service or whatnot, I'll happily listen and answer.
On Sat, May 9, 2009 at 10:54 PM, Yuri Takhteyev <takhte...@gmail.com> wrote:
>> I can't. At least not until I wade through the new terms of service. >> And if I disagree with that terms, I'm locked out of the data I've >> stored there. Locking out users without any warning is not nice.
> +1
> And there are things to disagree with.
> "the Content is not spam, is not machine- or randomly-generated"
> I guess code that includes base64-encoded images is no longer allowed...
I see you point and agree, at least in your example. What the paragraph is referring to, in spirit, is things like spam-scripts hammering comment fields and so forth. Machine generated code in the terms of code-generation and so forth is fine. I'll talk to the people who know the legal aspects of these matters and find a way to reword it to what it's intended to convey.
> The indemnification clause is also a little aggressive, especially > when combined with the lack of promise to remove the content on > request.
I think you've misread it, we cannot reasonable remove cached or otherwise referenced (backups come to mind) content right away, but within reasonable time.
> Another issue: all the links are now broken. Can you do something > about this? (I actually liked the old URL organization better, but I > suppose it wouldn't matter so much if proper redirects were in place.)
I'll admit I still got a few redirects to do, could you send me the urls to the things that break? thanks
> terms of code-generation and so forth is fine. I'll talk to the people > who know the legal aspects of these matters and find a way to reword > it to what it's intended to convey.
Until then, is it possible to let existing users continue using the site?
> I think you've misread it, we cannot reasonable remove cached or > otherwise referenced (backups come to mind) content right away, but > within reasonable time.
Perhaps. It's a complicated license and I probably should read it a lot more carefully before making comments about it, but after a quick reading "world-wide, perpetual, royalty-free, and non-exclusive license to reproduce, modify, adapt and publish" doesn't sound like a fun proposition when combined with an indemnity clause. To me this reads like "we can change and redistribute your code forever, but if someone sues us over this, you pay our legal fees". Just to make it clear, I am not a lawyer, and my reading of the license may be totally off.
I understand your need to protect yourself and Shortcut, but I agree with Jason that when introducing a new click-through TOS, it is good to give a little warning, so that people have time to read the new terms, to think whether they can sign up for such terms, and to plan for a migration if they do not.
On the other hand, Jason: you can always just pull your data with git and push it to your favorite alternative service.
> I'll admit I still got a few redirects to do, could you send me the > urls to the things that break?
And Johan Sørensen writes: > However, we're not unreasonable, if you have a strong opinion on any > terms of service or whatnot, I'll happily listen and answer.
My point is that suddenly I cannot use anything I placed there without wading through yet another possibly legal document. And this was with no warning. I don't have time to read and think about it right now.
On Sat, May 9, 2009 at 6:13 PM, Johan Sørensen <jo...@johansorensen.com> wrote:
> On Sat, May 9, 2009 at 9:08 PM, Patrick Aljord <patc...@gmail.com> wrote: >> Doesn't the AGPL forces you to release the source today with the >> deploy? Or did you rewrite all the contributed source code?
http://gitorious.org/proview doesn't work yet But the rest of the changes I think is good so far... Keep up the good work... and thanks for a great service. Martin
On Sunday 10 May 2009 07:27:33 Yuri Takhteyev wrote:
> > terms of code-generation and so forth is fine. I'll talk to the people > > who know the legal aspects of these matters and find a way to reword > > it to what it's intended to convey.
> Until then, is it possible to let existing users continue using the site?
> > I think you've misread it, we cannot reasonable remove cached or > > otherwise referenced (backups come to mind) content right away, but > > within reasonable time.
> Perhaps. It's a complicated license and I probably should read it a > lot more carefully before making comments about it, but after a quick > reading "world-wide, perpetual, royalty-free, and non-exclusive > license to reproduce, modify, adapt and publish" doesn't sound like a > fun proposition when combined with an indemnity clause. To me this > reads like "we can change and redistribute your code forever, but if > someone sues us over this, you pay our legal fees". Just to make it > clear, I am not a lawyer, and my reading of the license may be totally > off.
> I understand your need to protect yourself and Shortcut, but I agree > with Jason that when introducing a new click-through TOS, it is good > to give a little warning, so that people have time to read the new > terms, to think whether they can sign up for such terms, and to plan > for a migration if they do not.
> On the other hand, Jason: you can always just pull your data with git > and push it to your favorite alternative service.
> > I'll admit I still got a few redirects to do, could you send me the > > urls to the things that break?
On Sun, May 10, 2009 at 7:40 AM, Martin Pettersson <mar...@siamect.com> wrote: > http://gitorious.org/proview doesn't work yet > But the rest of the changes I think is good so far... > Keep up the good work... and thanks for a great service.
Should work as of earlier today. Same with redirects of the /projects/... urls.
On Sat, May 9, 2009 at 5:53 AM, Johan Sørensen <jo...@johansorensen.com> wrote:
> Everyone,
> I got some exciting news for you. The first part of these are already
> available today!
> But, first, please note that we had to change our public SSH key
> fingerprint. The fingerprint is now
> 7e:af:8d:ec:f0:39:5e:ba:52:16:ce:19:fa:d4:b8:7d and the IP of the
> frontend server is 87.238.52.168. Easiest way to deal with this is to
> delete gitorious.org from your ~/.ssh/known_hosts and reaccept the
> connection when you push (please do double-check that that
> fingerprints are correct though)
> I'm also happy to tell you that Gitorious and Gitorious.org is now
> officially Shortcut products. Shortcut (http://shortcut.no) is a
> norwegian development and design company I co-founded. By Gitorious
> being a Shortcut product means that we're able to fund its ongoing
> development through consulting and providing infrastructure for other
> companies in the open source sphere.
> Please do make use of a much better, faster and stronger
> Gitorious.org, we've got some more exciting things to talk about next
> week which is when we'll push the updated codebase to
> http://gitorious.org/gitorious
> Enjoy and don't forget to let me know if you experience any issues
> with the new release!
> Looks great Johan! Lots of nice changes, thank you for all of your
> hard work! It's a great contribution to the F/L/OSS community.
> Erik
> On Sat, May 9, 2009 at 5:53 AM, Johan Sørensen <jo...@johansorensen.com> wrote:
> > Everyone,
> > I got some exciting news for you. The first part of these are already
> > available today!
> > But, first, please note that we had to change our public SSH key
> > fingerprint. The fingerprint is now
> > 7e:af:8d:ec:f0:39:5e:ba:52:16:ce:19:fa:d4:b8:7d and the IP of the
> > frontend server is 87.238.52.168. Easiest way to deal with this is to
> > delete gitorious.org from your ~/.ssh/known_hosts and reaccept the
> > connection when you push (please do double-check that that
> > fingerprints are correct though)
> > I'm also happy to tell you that Gitorious and Gitorious.org is now
> > officially Shortcut products. Shortcut (http://shortcut.no) is a
> > norwegian development and design company I co-founded. By Gitorious
> > being a Shortcut product means that we're able to fund its ongoing
> > development through consulting and providing infrastructure for other
> > companies in the open source sphere.
> > Please do make use of a much better, faster and stronger
> > Gitorious.org, we've got some more exciting things to talk about next
> > week which is when we'll push the updated codebase to
> >http://gitorious.org/gitorious
> > Enjoy and don't forget to let me know if you experience any issues
> > with the new release!
> I got some exciting news for you. The first part of these are already
> available today!
> But, first, please note that we had to change our public SSH key
> fingerprint. The fingerprint is now
> 7e:af:8d:ec:f0:39:5e:ba:52:16:ce:19:fa:d4:b8:7d and the IP of the
> frontend server is 87.238.52.168. Easiest way to deal with this is to
> delete gitorious.org from your ~/.ssh/known_hosts and reaccept the
> connection when you push (please do double-check that that
> fingerprints are correct though)
> I'm also happy to tell you that Gitorious and Gitorious.org is now
> officially Shortcut products. Shortcut (http://shortcut.no) is a
> norwegian development and design company I co-founded. By Gitorious
> being a Shortcut product means that we're able to fund its ongoing
> development through consulting and providing infrastructure for other
> companies in the open source sphere.
> Please do make use of a much better, faster and stronger
> Gitorious.org, we've got some more exciting things to talk about next
> week which is when we'll push the updated codebase tohttp://gitorious.org/gitorious
> Enjoy and don't forget to let me know if you experience any issues
> with the new release!
On Mon, May 11, 2009 at 2:50 PM, AkitaOnRails <fabioak...@gmail.com> wrote:
> Awesome news! I am eager to upgrade my company's installation to this > new version. Congrats and thanks for the efforts!
If you're upgrading an existing install you'd probably want to wait a few days, there's a few peculiars I haven't yet had time to fully document (last few days have been hectic!).
Thanks... but sorry I have it already and when I do rake db:create:all it works and the databases are created.
so there must be something else...
Martin
On Monday 11 May 2009 22:58:38 Johan Sørensen wrote:
> On Mon, May 11, 2009 at 3:21 PM, Martin Pettersson <mar...@siamect.com> wrote:
> > Sorry for being such a rails newbie... but I get something like this:
> > (in /home/martin/gitorious)
> > rake aborted!
> > undefined method `[]' for nil:NilClass
> Sounds like you need to copy the config/database.sample.yml to
> config/database.yml
On Mon, May 11, 2009 at 6:19 PM, Martin Pettersson <mar...@siamect.com> wrote: > Thanks... but sorry I have it already and when I do rake db:create:all it > works and the databases are created. > so there must be something else... [snip] >> > undefined method `[]' for nil:NilClass
>> Sounds like you need to copy the config/database.sample.yml to >> config/database.yml
Actually, I wrote that a bit too fast, I meant config/gitorious.sample.yml
> On Mon, May 11, 2009 at 6:19 PM, Martin Pettersson <mar...@siamect.com> wrote:
> > Thanks... but sorry I have it already and when I do rake db:create:all it
> > works and the databases are created.
> > so there must be something else...
> [snip]
> >> > undefined method `[]' for nil:NilClass
> >> Sounds like you need to copy the config/database.sample.yml to
> >> config/database.yml
> Actually, I wrote that a bit too fast, I meant config/gitorious.sample.yml
> JS
> development:
production:
test:
# The session secret key (`apg -m 64` is always useful for this kinda stuff)
cookie_secret: 8d6d8ce4437672a91be96396302c473b
# The path where git repositories are stored. The actual (bare) repositories resides
# in repository_base_path/#{project.slug}/#{repository.name}.git/:
repository_base_path: "/gitorious/repositories"
# Stuff that's in the html <head>. custom stats javascript code etc
extra_html_head_data:
# System message that will appear on all pages if present
system_message:
# Port the ./script/gitorious script should use:
gitorious_client_port: 3000
# Host the ./script/gitorious script should use:
gitorious_client_host: localhost
# Host which is serving the gitorious app, eg "gitorious.org"
gitorious_host: localhost
# User which is running git daemon
gitorious_user: root
# Email spam on server errors to:
exception_notification_emails: mar...@siamect.com
# Enable or Disable Public Mode (true) or Private Mode (false)
public_mode: true
# Define your locale
locale: en
# Where should we store generated tarballs?
# (should be readable by webserver, since we tell it to send the file using X-Sendfile)
archive_cache_dir: "/tmp"
# Which directory should we work in when we generate tarballs, before moving # them to the above dir?
archive_work_dir: "/tmp"
# is it only site admins who can create new projects?
only_site_admins_can_create_projects: false
# Should we hide HTTP clone urls?
hide_http_clone_urls: false
oauth:
adapter: test
consumer_key: foo
consumer_secret: bar
seems to be a problem with parsing the config files. I got the same
error message. When substituting config/environments/production.rb:34:
with my own hostname, the error message was gone. However, rails
aborted then with the following error message
config/initializers/gitorious_config.rb:4: undefined method `[]=' for
nil:NilClass (NoMethodError)
Hopefully, we get the new gitorious running on our servers soon too.
Regards,
Thomas
On May 11, 6:26 pm, Martin Pettersson <mar...@siamect.com> wrote:
> Thanks again but sorry again... The config/gitorious.yml is there too....
> I list is below
> Martin
> On Monday 11 May 2009 23:21:14 Johan Sørensen wrote:
> > On Mon, May 11, 2009 at 6:19 PM, Martin Pettersson <mar...@siamect.com>
> wrote:
> > > Thanks... but sorry I have it already and when I do rake db:create:all it
> > > works and the databases are created.
> > > so there must be something else...
> > [snip]
> > >> > undefined method `[]' for nil:NilClass
> > >> Sounds like you need to copy the config/database.sample.yml to
> > >> config/database.yml
> > Actually, I wrote that a bit too fast, I meant config/gitorious.sample.yml
> > JS
> > development:
> production:
> test:
> # The session secret key (`apg -m 64` is always useful for this kinda stuff)
> cookie_secret: 8d6d8ce4437672a91be96396302c473b
> # The path where git repositories are stored. The actual (bare) repositories
> resides
> # in repository_base_path/#{project.slug}/#{repository.name}.git/:
> repository_base_path: "/gitorious/repositories"
> # Stuff that's in the html <head>. custom stats javascript code etc
> extra_html_head_data:
> # System message that will appear on all pages if present
> system_message:
> # Port the ./script/gitorious script should use:
> gitorious_client_port: 3000
> # Host the ./script/gitorious script should use:
> gitorious_client_host: localhost
> # Host which is serving the gitorious app, eg "gitorious.org"
> gitorious_host: localhost
> # User which is running git daemon
> gitorious_user: root
> # Email spam on server errors to:
> exception_notification_emails: mar...@siamect.com
> # Enable or Disable Public Mode (true) or Private Mode (false)
> public_mode: true
> # Define your locale
> locale: en
> # Where should we store generated tarballs?
> # (should be readable by webserver, since we tell it to send the file using
> X-Sendfile)
> archive_cache_dir: "/tmp"
> # Which directory should we work in when we generate tarballs, before moving
> # them to the above dir?
> archive_work_dir: "/tmp"
> # is it only site admins who can create new projects?
> only_site_admins_can_create_projects: false
> # Should we hide HTTP clone urls?
> hide_http_clone_urls: false
> oauth:
> adapter: test
> consumer_key: foo
> consumer_secret: bar
> On Sun, May 10, 2009 at 7:40 AM, Martin Pettersson <mar...@siamect.com> wrote:
> >http://gitorious.org/proviewdoesn't work yet
> > But the rest of the changes I think is good so far...
> > Keep up the good work... and thanks for a great service.
> Should work as of earlier today. Same with redirects of the /projects/... urls.
