Hello Alexandre, my name is Timo Stollenwerk and I'm a student of computer science at bonn university. I'm currently preparing my diploma thesis in which I would like to develop a publishing workflow solution for the production of a print magazine.
My idea is pretty much the same as proposed in the Scribus wiki: http://wiki.scribus.net/index.php/Draft_of_end-to-end_publishing_solution Basicly I would like to integrate Scribus into a CMS application where the CMS app provides all the content and changes in Scribus are written back into the CMS. The CMS should also be able to generate layout templates that are able to adapt to different content elements and sizes (and not just provide fixed copy holes for the content). Until now I've played around a bit with the generation of .sla files out of a cms and layout generation with the scribus python API. While I was looking for use cases for my thesis I found the proposal of the development of a publishing workflow at the scribus bug tracker: http://bugs.scribus.net/view.php?id=3100 I've contacted the authors of the initial posting and found out that they already developed a working solution for an automated publishing worklflow with Typo3 and XML Technologies (XML, XSLT, FO) for their T3N magazine (www.t3n-magazin.de). I' going to meet them at March 22th and discuss the integration of Scribus as fat-client into their cm-system and I'll take a look at what they've archived so far with their automated system. I don't know if their current solution is released under an open source licence, but I would definitely release my code as open source (if I achieve something useful of course). The participation of the gsoc program would be a great opportunity for me to develop such a solution and to get support in my efforts from a experienced Scribus developer. I think such a solution could be beneficial for the scribus community and could convince more people to use scribus as DTP program. Beside my university studies I'm a Zope/Plone Developer, so Plone (www.plone.org) would be my preference as CMS, but I'm not stuck with it if there are other preferences. What do I have to do to participate in the gsoc Programm? Is there already a mentor for the end-to-end publishing solution? Timo Alexandre Prokoudine schrieb: > > Hi, > > > > This year we are applying to Google Summer of Code program [1]. > > > > What we need is: > > > > 1. Project ideas. Several ones are listed here: > > http://wiki.scribus.net/index.php/SoC2007_ideas. Please do tell us if > > you have other ideas -- a good thorough description with an > > explanation, why this is a really useful project, would be best (see > > http://wiki.inkscape.org/wiki/index.php/Googles_Summer_Of_Code_2007 > > for an example). Each possible project should have a mentor. > > > > 2. Students. We have none yet. > > > > 3. Mentors. Mentors should be team or, rather, core team members. > > > > 4. An organization administrator. This person sends an application and > > takes care of communication between Google and students. He needs a > > Google account. > > > > 5. A backup organization administrator. If primary administrator is > > not available, backup administrator steps in to help. He needs a > > Google account as well. > > > > To make sure Scribus has more chances to be chosen we started a list > > of individuals and organizations interested in SoC projects for > > Scribus: http://wiki.scribus.net/index.php/SoC2007_Supporters > > > > Last date of sending an application is March 12. The schedule is > > pretty tight, but I think we can make it ;-) > > > > [1] http://code.google.com/soc/ > > > > Alexandre > > _______________________________________________ > > Scribus mailing list > > Scribus at nashi.altmuehlnet.de > > http://nashi.altmuehlnet.de/mailman/listinfo/scribus > >
