PloneSurvey egg

[Sneridagh]

Hi,
We are interested in PloneSurvey to be eggified, since we are using
the product in our main web app in a production site. We wanted to
know if we can help with it and contribute also with the resolutions
of some "bugs" and unexpected behaviours that we have found.

We are going to commit an initial version as a branch in the
collective if you don't mind. Later we can create the definitive one
in the root of collective.

Thanks in advance.

----------------------------------------------
Víctor Fernández de Alba Encinas
Projectes Tecnològics
UPCnet - Universitat Politècnica de Catalunya
Edifici Vèrtex - Campus Nord UPC
08034 BARCELONA
Tel. centraleta: 93 401 16 00
----------------------------------------------

[Davis, Michael]

Hi,

I would not have a problem with that. The only issue will be with merging this with the trunk. What version are you eggifying from? Have you customised it from there?

Would be handy to see your list of bugs as well.

Cheers
Michael

[Davis, Michael]

Hi,

Did you create the new branch - PloneSurvey-UPCnet?

The way it's been added, means there is no connection between the trunk and this branch, so will make any merging between the trunk and this branch impossible.

Do you have a working copy to create a diff from, or can you replicate the changes you've made and add them to a branch copied from the trunk.

Cheers
Michael

-----Original Message-----
From: cmfque...@googlegroups.com [mailto:cmfque...@googlegroups.com] On Behalf Of Sneridagh
Sent: 16 December 2008 11:40
To: PloneSurvey
Subject: PloneSurvey egg

[Sneridagh]

Upppps!

Sorry about that... you have all the reason, I should have made the
switch, but the hurry in this case has betrayed me.

The question is that one member of my team made the changes localy,
and then uploaded to a local repository. And now we didn't have the
svn working copy original... I've tried to merge it up, but there are
some changes in the trunk too making it dificult to merge with ours.

The little bug that we found was related to the names of the
archtypes. We found that having spaces in them causes several problems
involving GenericSetup, for example, when we tried to reinstall the
product, or reinstall other products. So we renamed all of them to
make the problems solved. We managed to do so, and now is working
properly for us.

We could make the switch from the original, then modify again the
branch version, and if you agree, we can later do the merge.

Greetings,
Víctor.

[Davis, Michael]

Hi Victor,

No problem. The archetypyes name change may cause a problem with backward compatibility. Also check the folder reordering, as having a space in the meta_type name will cause this to break.