Studying, for now..
Version Control
Written by Flavio Adalberto Kubota   

My name is Flavio and I'll develop a version control system for article component.
I am new to the Joomla! community and I started with a little bit of history. I've read Joomla! hystory on wikipedia and I've been even more motivated after this.
In this last week I have studied Joomla!. I have read some articles from Joomla! Developers Documentation on http://docs.joomla.org/Developers. An important article that I want to cite is Coding style and standards, and I want to encourage my SoC colleagues to read it too.
I also have studied Joomla! database model. I want to alter database least as possible, and to keep database normalization. I want to create the version control system as a component and make installable to Joomla!. And after, it is possible to embed in the Joomla! core.
Version control system will create and manage revisions of article component. Version Control System log all changes when the document is saved, and make possible revert to any version. It is also possible to compare any different version.
In this first month, I will be focused on revision control functionality, and leave user interface for a later discuss. I am current studying this functionality.


Any feedback is appreciated.
I will post again soon..
 

 

Show other articles of this author

34 Votes

2 Comments

Feed
  1. Besides the existing projects "versioning" and "Egxact Revision Manager" I am really looking forward to get a working form of revision management. It sounds great, that you're going to develop it.
    Currently, I am in needs of such a component and in lack of solutions for Joomla 1.5, I have to build a workaround. The difficulty I have with the article management is, that besides the "normal" articles, I have JoomFish running with various translations for one "real" article. So it would be great, whether you could include the JoomFish-structure as well into the versioning system.
  2. A version management system for Joomla! sounds great, Flavio! We could use this. I would encourage you to design your component in such a way so as to not alter the core database. If this can be developed as an extension, those who require these advancements can take advantage of your work without increasing the size of the core for those who do not need this functionality. Plus, doing so removes any concern of backwards compatibility.

    Thanks for your work in this area. It is going to be a very popular and helpful project.

Add Comment


    • >:o
    • :-[
    • :'(
    • :-(
    • :-D
    • :-*
    • :-)
    • :P
    • :\
    • 8-)
    • ;-)



    Click to get a new image.