You are hereFeed aggregator / Categories / MSWL-cases: Case studies (I and II)

MSWL-cases: Case studies (I and II)

gitk, TCL/Tk utility for Git

Esther Parrilla-Endrino - Cases - Tue, 11/02/2010 - 20:25

Now that I have started uploading my notes from the different lessons of the Master into our Gitorius repo I had more time to start playing with Git in command-line mode.

Today, checking the ProGit book that Jesús recommended us, I discovered the gitk tool, which is a very simple graphical interface that can be installed with a simple:

$ apt-get install gitk

This is a screenshot of the mswl-notes repo, displaying the Legal Aspects session 2 file I have been working with (click in the image for full size display):

Is very interesting the timeline graph at the top left of the display, there we can see the commit log for the file with commiters name, messages etc… also is possible to make diff between versions etc etc…

Enjoy the tool!

[Update] I have tested also the EGit for Eclipse IDE, in Lars Vogel web site there is a short intro to this plug-in very useful for newbies!

Categories: MSWL-cases: Case studies (I and II)

Android Market vs App Store

Esther Parrilla-Endrino - Cases - Wed, 10/27/2010 - 14:47

A few days ago, a comparative about Android Market vs App Store appeared in LinuxHispano web site, I had the link in my TODO list but had no time to check it before, so now is time to comeback to it…

I have to say still I have not uploaded any application to both Android Market or Apple Store so I am completely newbie on this and the comparative brought to me a few ideas:

  • Is a good thing that anyone can upload an Android-app to the repository without passing strong checks from Google, because even though is good that Apple Store ensures the quality of the uploaded applications, who knows if any other non-fair criteria could be applied? This is something the Community does not control…
  • In the other hand, this is related to the article I posted some time ago in which the discussion was around if this proliferation of tools could decrease the quality of the overall Android repository.

Maybe Apple repository is only composed of well-tested apps but at the end is not free, which is the main issue here, do we want to have a so-called perfect bunch of apps, all portable and working fine but completely closed as a black-box? Or do we prefer to have a bunch of applications,some of them useful, some of them not so good but having us the control and freedom over those applications?

I think the response is clear, at least for the ones in the Libre Software Master should be…

Categories: MSWL-cases: Case studies (I and II)

Too Many Flavors Could Spoil the Android Platform?

Esther Parrilla-Endrino - Cases - Sun, 10/03/2010 - 17:41

Here I leave a link to this interesting article that I found via Slashdot and that opens a discussion for an important issue about Android. As you all know, Android is the Open Source platform developed by the Open Handset Alliance for mobile devices and it offers a simple API for developing applications that can run under its operative system…

The article empathizes the fact that the number of applications developed with Android is growing exponentially and not all of them offer the same quality so maybe end-users can start feeling that the platform is not so reliable and the overall evolution of Android is on hold as more and more low-quality components are released publicly.

I think this could be a good point of view to be discussed in the Master, in my opinion when you release a product as Libre Software for sure lots of poor quality forks and related components can be developed and downloaded for free, but those products will have a very short life as the FLOSS community itself will get rid of those ones and instead will go for the highest quality components, I mean, the community regulates itself the FLOSS market, which is something really powerful as the power to decide is more on the end-user side…

If you have some spare time, take a look at the article and people’s responses, some of them really quite interesting!

Categories: MSWL-cases: Case studies (I and II)

Git vs other control version systems

Esther Parrilla-Endrino - Cases - Sun, 09/19/2010 - 22:37

In the first sessions of the Case Studies I subject we had a seminary about Git, the distributed control version system used in the development of the Linux Kernel and that is becoming one of the most used platforms for collaborative implementations.

For those who have been using mostly CVS or Subversion there are several new things that Git and other distributed systems (like Mercurial or Bazaar) bring, the most weird and at the same time the most powerful is the idea that there is no centralized HEAD copy of the code and each developer has a local copy of the whole repository that is merged from time to time to synchronize the changes with the rest of the team…

As I am attending classes just on Fridays, we have not used Git yet but as an extra work from home I will try to take some time to install a new repo and play a bit with the tool to see how it works.

In the mean time, I have found an interesting comparative study of several version control systems that explains Git advantages and some guidelines in this article for SVN Users that start working with Git that will be useful for some of us for sure… hope you enjoy it!

[Updated 12/10/2010] Jesús explained last Friday that the collaborative notes have to be uploaded to Git, so now there is no excuse to start playing with the tool!

[Updated 13/10/2010] Another link that helps with the SVN-Git transition…

Categories: MSWL-cases: Case studies (I and II)

MSWL Twitter channel


Syndicate content