Finding the red thread

First post in a long time now. Managed to catch quite a nasty cold the other day, and the week before was pretty cramped with turning one open source CMS into a webshop (will post about it later).

One of the main issues with my thesis as now is that it lacks a red thread through it. The thesis is an answer to a question; a research question. Am I ready to specify a context of the question? See writing about open source and open standards in wcms is still too general. I need some sort of approach or specialty, an aspect I can attack.

In my experience, you have to be careful when reading through your own papers. Do it too often, and you grow tired of your own content. My technique will now be to first look quickly through the thesis (7500 words) and the blog (11000 words, bloglines is a great tool for viewing your whole blog on one page), and see if I can select an aspect based on the content I've already collected.

Afterwards, I will go through it again, more slowly this time, adding more content, references, generally putting in the fixes suggested by A.

The aspect

Been a while since I read my first blog-posts. Interesting to note that I've all along proclaimed customizability as the most important feature of a WCMS, especially in an off-the-shelf WCMS, or an open source WCMS. Reading through the blog gave me the impression that I've been bouncing back and forth between different aspects, roaming from knowledge management to the architecture of a WCMS, the social aspects of open source, and the concept of a web portal. I doubt all these concepts can be treated properly in the thesis.

Reading quickly through the thesis. Some chapters follow the the thread, others are immensly subjective and will have to be heavily edited. The abstract and introduction suggest the following red thread:

requirements of WCMS
how requirements are met by open source systems (OSS) and open standards
how OSS compares to proprietary WCMS
how to compare different OSWCMS

So the choice remains. What are the options?

The aspects of open source and open standards
WCMS as a knowledge management tool
A study of an open source content management system project (social and technical aspects)
The business case of using an open source WCMS
The technical implications of JSR-170

As previously mentioned, my current title is The Use of Open Standards and Open Source in Web Content Management Systems. Why can't I stick to this aspect? Is it too general? Too subjective?

Nonetheless, I've got material for aspect for all these aspects, especially number 3.

Depending on feedback from A, I want to try to make my current title the red thread. After this has been settled, I'll give the thesis a good write-thru and see how it goes.

Comments

Open source CMS evaluations

I have now seen three more or less serious open source CMS reviews. First guy to hit the field was Matt Raible ( 1 2 3 4 ), ending up with Drupal , Joomla , Magnolia , OpenCms and MeshCMS being runner-ups. Then there is OpenAdvantage that tries out a handful ( Drupal , Exponent CMS , Lenya , Mambo , and Silva ), including Plone which they use for their own site (funny/annoying that the entire site has no RSS-feeds, nor is it possible to comment on the articles), following Matt's approach by exluding many CMS that seem not to fit the criteria. It is somewhat strange that OpenAdvantage cuts away Magnolia because it "Requires J2EE server; difficult to install and configure; more of a framework than CMS", and proceed to include Apache Lenya in the full evaluation. Magnolia does not require a J2EE server. It runs on Tomcat just like Lenya does (maybe it's an idea to bundle Magnolia with Jetty to make it seem more lightweight). I'm still sure that OpenAdvant

Considerations for JavaScript in Modern (2013) Java/Maven Projects

Disclaimer: I'm a Java developer, not a JavaScript developer. This is just what I've picked up the last years plus a little research the last days. It's just a snapshot of my current knowledge and opinions on the day of writing, apt to change over the next weeks/months. We've gone all modern in our web applications, doing MVC on the client side with AngularJS or Ember , building single-page webapps with REST backends. But how are we managing the growing amount of JavaScript in our application? Yeoman 's logo (not necessarily the conclusion of this blog post) You ain't in Kansas anymore So far we've just been doing half-random stuff. We download some version of a library and throw it into our src/main/webapp/js/lib , or we use it from a CDN , which may be down or unreachable when we want to use the application.. Some times the JS is minified, other times it's not. Some times we name the file with version number, other times without. Some

Git Stash Blooper (Could not restore untracked files from stash)

The other day I accidentally did a git stash -a , which means it stashes *everything*, including ignored output files (target, build, classes, etc). Ooooops.. What I meant to do was git stash -u , meaning stash modifications plus untracked new files. Anyhows, I ended up with a big fat stash I couldn't get back out. Each time I tried, I got something like this: .../target/temp/dozer.jar already exists, no checkout .../target/temp/core.jar already exists, no checkout .../target/temp/joda-time.jar already exists, no checkout .../target/foo.war already exists, no checkout Could not restore untracked files from stash No matter how I tried checking out different revisions (like the one where I actually made the stash), or using --force, I got the same error. Now these were one of those "keep cool for a second, there's a git way to fix this"situation. I figured: A stash is basically a commit. If we look at my recent commits using git log --graph --

Managing dot-files with vcsh and myrepos

Say I want to get my dot-files out on a new computer. Here's what I do: # install vcsh & myrepos via apt/brew/etc vcsh clone https://github.com/tfnico/config-mr.git mr mr update Done! All dot-files are ready to use and in place. No deploy command, no linking up symlinks to the files . No checking/out in my entire home directory as a Git repository. Yet, all my dot-files are neatly kept in fine-grained repositories, and any changes I make are immediately ready to be committed: config-atom.git -> ~/.atom/* config-mr.git -> ~/.mrconfig -> ~/.config/mr/* config-tmuxinator.git -> ~/.tmuxinator/* config-vim.git -> ~/.vimrc -> ~/.vim/* config-bin.git -> ~/bin/* config-git.git -> ~/.gitconfig config-tmux.git -> ~/.tmux.conf config-zsh.git -> ~/.zshrc How can this be? The key here is to use vcsh to keep track of your dot-files, and its partner myrepos/mr for o

Leaving eyeo

Thirteen blog posts later, this one notes my departure from eyeo after 4 years and 3 months. I joined eyeo around the headcount of 80 employees, and now I think there's just over 250 people there. My role coming in was as operations manager, doing a mix of infrastructure engineering and technical project management. I later on took on organizational development to help the company deal with its growing pains . We introduced cross-functional teams, departments (kind of like guilds), new leadership structures, goal-setting frameworks, onboarding processes and career frameworks. And all of this in a rapidly growing distributed company. I'm proud and happy that for a long time I knew every employee by name and got to meet every single new-hire through training them on company structure and processes. At some point, we had enough experienced leaders and organizational developers that I could zoom back in on working in one team, consulting them on Git and continuous integration