SoC 2006/AbiCollab synchronization improvements

From AbiWiki

(Difference between revisions)
Jump to: navigation, search
Maintenance script (Talk)
(Importing text file)
Newer edit →

Revision as of 02:54, 17 October 2007


Name:Török Edvin

How much time do you expect to have for this project? Between June,12 and July,09 I have the exams period. I also have a full time job during the summer. I dont intend to leave on vacation during the SoC. Please describe any experience you have with: o C++ development: favourite language, 5+ years experience o C development: 5+ years experience, kernel module writing (recently) o Scripting languages: Python, Bash o Windows development: Delphi, MinGW o UNIX development: Linux: network oriented programs, recently: kernel, SELinux o Web development: PHP, HTML, Javascript, Java

Please describe any open source development experience: I have joined the fireflier project in sept. 2005, and became one of its main developers.

Did you participate in a 2005 Summer of Code project? No

Have you applied (or plan to apply) for any other 2006 Summer of Code projects? If so, which ones? Yes. Debian:reportbug, Debian:selinux, ClamAV: phishing detector,CrystalSpace: vfs,KDE: noseekIO NMap: scripting, OSDL: rapid spanning tree, GNUnet: UI port, Ubuntu, Gentoo

What school do you attend? Politehnica University of Timisoara, Automation and Computers Faculty How many years have you attended there? 2 (including current year) What is your specialty/major at the school? Computer Science Any professional/resume or personal/blog URLs you would like to list? http://edwintorok.googlepages.com/edwin_cv.pdf http://fireflier.isgeeky.com/wiki/Edwin%27s_blog

Please describe your proposed project in detail, including deliverables and expected timeline with milestones (answer in detail): Project goal: improve synchronization of AbiCollab sessions Secondary goal: let the user which parts are in-sync, and which are synchronizing, and which are in unknown state

  • notification of intention to modify a piece of the document

(generalization of typing notifications in IM networks)

  • marking of portions (paragraphs?) as being edited by somebody else
  • possibility to lock portions of document for editing by one party only

(with all collaborators agreement)

  • add possibility to collaboratively solve conflicts:
    • add possibility for mini-chats (out-of-document)
    • add possibility to postpone conflict resolution, and commenting on the

conflict (in case neither party knows which text would best fit there)


Timeline: May 23 - May 30: establish detailed plan with mentor/community, discuss implementation details; establish on what part I will focus upon June 12 - July 9: exams period, Ill establish with the mentor how well handle this situation. Ill try to work during this period too. July 9 - August 7: alpha implementation, test it by collaborating on a document with the mentor August 7 - August 21: polishing, performance improvements, prepare a stable release A detailed timeline/implementation plan will be established with the mentor.

Why are you well suited to complete this project? First of all, once I take on a project I really want done, I give up very hard. I try to overcome any problems I encounter along the way, even if this means changing the plan along the way to fit the new situation.(I can provide pointers to the kernel archive to back this up). Last, but not least, I am always open to learn new stuff (practically, by experimenting), although I have no experience with programming AbiCollab, I am not afraid of learning its internals. (FYI Ive written a LSM module for the kernel in ~2 months, and when I started out I had no knowledge of kernel programming)

Contributors

Retrieved from "http://www.abisource.com/wiki/SoC_2006/AbiCollab_synchronization_improvements"
Personal tools