I just invested some time to get my project websites online for jscsi.org.

Since jscsi.org is a multi-module project, the websites must respect this including its deployment process. Unfortunately, the github-maven-plugin is not hooking into the deployment process directly making a staging and deployment a little bit tricky.

After struggling around with some (now unsupported and not over maven-central hosted) third-party plugins, I cam up with a workflow including the original github-maven plugin and a simple ant-relying workflow.

The entire workflow is described over here.

cheers

Sebastian

within my time as a PhD student at the U KN, I wrote some documentation about technical issues ongoing with the software I developed.

I will start migrating some of the stuff in the wiki. Originally, it was planned to comment on this within the blog, but I fear that I don’t have time for this right now. Nevertheless, the content will be visible within the wiki and maybe I will found some time to explain some issues in detail.

Cheers

Sebastian

When I reached university today, I just realized the beautiful sunrise over the lake…

See some photos in the gallery.

cheers and enjoy the winter

sebastian

First of all: I am not a real fan of Dropbox: Storing my data in a cloud somewhere located in the USA relying on other cloud services (Amazon S3 in the case of Dropbox) without any transparent security measures makes me feel odd when I started to share private pictures or tax declarations over multiple computers utilizing Dropbox (or any similar tool).
I always find it quite brave when people upload their thesis in Dropbox believing that it is secure (and Amazon crashed multiple times including data loss [1,2]) when having the ability to store data on university infrastructures.

Since I am more and more working with git(hub), I recognized that in such a scenario, Dropbox is the perfect match for sharing local source code over multiple computers:

• Synchronization is one of the major benefits of Dropbox
• When working with different clients, you always have your (even uncommitted) work synchronized on multiple site really simplifying development on multiple sites.
• Data is secured at your repo anyhow (so you don’t have to have availability /integrity / accountability concerns about changes on your data).
• The open-source source code is public anyway so you don’t have to think about confidentiality.

The only thing that can happen at the beginning is the insertion of redundant branches when synchronized the first time. If so, just go to

.git/refs/remotes

and remove the irrelevant copies.

cheers

sebastian

[1]: http://www.informationweek.com/news/services/storage/209400122
[2]: http://money.cnn.com/2011/04/21/technology/amazon_server_outage/index.htm

Thanks to Markus, this domain acts as base for several Email-Adresses for several years, but unfortunately not for any content until now.
Konschtanz from now on represents a platform for IT-related issues, photos, thoughts and everything else that comes into the mind as well.

More concise:

• This platform contains a blog for providing some on-the-fly content.
• Besides the blog, a wiki is provided for some knowledge we want to share and we are looking for quite regularly.
• Last but not least, a gallery for some photos are provided: Some from Konstanz, other from somewhere else…