Le lundi 16 décembre 2013 22:09:36, Till Theato a écrit : > You might want to search the mailing archive for the related threads at > the time (mainly spring/summer 2012) or have a look at the blog posts.
Hello, I took time to digg back into blog & sf list archive (not convenient!)... It was good to refresh a bit the memories ;) So you started around here: http://kdenlive.org/users/ttill/kdenlive-fundraising-campaign Kdenlive fundraising campaign Submitted by ttill on Thu, 03/15/2012 - 23:07 http://sourceforge.net/mailarchive/message.php?msg_id=29126923 Re: [Kdenlive-devel] Release roadmap From: Till Theato <root@tt...> - 2012-04-13 21:20 Then interesting midterm report: http://sourceforge.net/mailarchive/message.php?msg_id=29257003 [Kdenlive-devel] 1. Refactoring Update From: Till Theato <root@tt...> - 2012-05-13 13:04 Last status? http://sourceforge.net/mailarchive/message.php?msg_id=29483375 Re: [Kdenlive-devel] Refactoring From: Till Theato <root@tt...> - 2012-07-01 20:16 Later details: http://sourceforge.net/mailarchive/message.php?msg_id=30500526 Re: [Kdenlive-devel] Support for more clip types From: Till Theato <root@tt...> - 2013-02-18 17:58 Then after that JB followed in your footsteps: http://sourceforge.net/mailarchive/message.php?msg_id=31002165 [Kdenlive-devel] Refactoring merged From: jb <jb@kd...> - 2013-06-05 12:44 http://kdenlive.org/users/j-b-m/kdenlive-spring-cleaning Kdenlive: spring cleaning Submitted by j-b-m on Sat, 06/01/2013 - 22:57 Since the a reference could be: http://community.kde.org/Kdenlive/Roadmap > What kind of documentation are you looking for exactly? Gathering the info spread above could be a starting point, either on community.kde.org or in a readme file in the branch. Actually I would appreciate an overview/summary like this (past/present/future): - what are the problems you identified (not just "hard to maintain", but how the old architecture came to its limits) - what are the solutions you planned to put in place (how to split, abstract... maybe hand drawings could help) - what is done, what to do in which order Nothing big, just 10-20 lines on each point? (more if you like ;) ) I guess this might be the sort of things a team discusses regularly for "marathon" projects like this. We could think of "light" management techniques to apply to ourselves? (so that when someone leaves it is less painful to restart) Probably I forget many things but I'm not a professional in this area... BR, Vincent ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ Kdenlive-devel mailing list Kdenlive-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kdenlive-devel
