Hi all First of all please accept my excuses if my answer sounded authoritive, this was not my intention, I just replied the email too quickly.
Thomas, your ideas are great and if I was a manager I would say 'yes' to this idea of letting a student code the switch from our current ezPO to the new ezcPO because it might cost less money. However from a developer/consultant point of view I would say this is a bad idea for the following reasons: - we have very important customers who are relying on the DB layer and who expects a lot from us. We can honnestly not say that the switch to eZComponents for one of the most important layer of our CMS will be done by a student. - the switch from the current ezPO to ezCPO must be done by someone who knows eZ Publish perfectly and who has always performances and big databases (30/40Go is a minimum) in mind to avoid beginner mistakes on the performance and design levels. - there is another important point, this person must also master eZ Publish cluster, and this is not a piece of cake. The code is pretty easy but the matter is on the design level, we are dealing with some really important problems (concurrent writes under very high load for example) sometimes and we must avoid making thoses mistakes again while switching to ezCPO. I know there is a lot of good students and you may know one of them, but it is all about eZ Publish knowledge and experience here. Have a very nice evening. Regards :) Derick Rethans a écrit : > Hello, > > On Thu, 21 Feb 2008, Thomas Koch wrote: > >> Rumour are going round, that there'll be another Google Summer of Code in >> 2008, but it's not sure yet. As one can expect the timeframe to be rather >> short, I already open the topic. >> >> How do you think about participating? Any ideas for projects or mentors? > > I am aware that there is another GSoC coming up, we will most likely try > again to apply - but no real ideas for projects yet. > >> If I'd have enough Karma, I'd volunteer to help in mentoring. > > If we'll be accepted, we should do the mentoring ourselves. > > regards, > Derick -- Components mailing list [email protected] http://lists.ez.no/mailman/listinfo/components
