|
Hey Rok, a short write up sounds good and Dimo/Mike are the coding leads so you can always run things by them in irc. I'm not a coder, doing more of the concept and community work. Cheers And. On 5/09/11 10:18 AM, Rok Garbas wrote: On 05/09/11 01:19, Andrew Lowenthal wrote:<snip>On 4/09/11 1:12 AM, Rok Garbas wrote:If you look at milestone 4.5 in particular some of the issues are there http://plumi.org/report/3, but they are also dotted throughout the tracker.I see that some of the features you planned for 4.5 I would already need. I guess haviing them earlier it wouldn't be a problem, right?Only if it brings in additional bugs, but if it's modular I really can't see it being an issue. What were you thinking in particular?definitely ... something that would potentially brake things should be more carefully planned. I'm still a little bit undecided how to tackle this problem. since my client only requires video + transcoding. other things are removed. - first idea was to create new theme and hide those elements and stay "compatible" with plumi and future upgrades. but creating new theme in a way that we dont depend on plumi.skin. - second idea - since we share similar vision - would be to start factoring out things from plone.(app|content|skins) into ``plumi.video``. currently I'm more leaning on the second one, but I would still like your input on it. I think best would be to write short proposal what to include into ``plumi.video`` to the list and then you comment on it. maybe creating ``plumi.video`` would be a step into the future refactoring you were planning and might be even more appreciated from you then messing up current setup. lp rok _______________________________________________ Discuss mailing list [email protected] http://lists.plumi.org/listinfo/discuss |
_______________________________________________ Discuss mailing list [email protected] http://lists.plumi.org/listinfo/discuss
