Excuse me for the mail copy Alejandro, it appears your sf.net's address
is not working anymore, I saw it this morning.
I'll try not to break all the things you've done ;-)
Alejandro Pedraza a =E9crit :
>Ralf and Regis,
>Thanks Ralf for having sent me a copy of the message. Indeed, I've been =
unactive lately in egroupware because of time constraints. I was waiting =
a bit to see how my laboral situation would evolve to take a decision on =
whether I would or not continue to contribute with the project. The final=
outcome is that I definetely won't have the time, so I'm glad to give my=
child in adoption to Regis, with whom I've worked a little recently to r=
aise him. I know he will be in good hands. On the other hand, I want you =
to know that I'll take care of all the outstanding bugs of my other son, =
the kb. Just haven't had the time, but I won't let that one orphan ;)
>Ralf Becker <RalfBecker@...> escribi=F3:=20
>>if Alejandro (?) no longer maintains the workflow (for whatever reason)=
>>we need a new maintainer and you're the first candidate :-)
>>If noone objects or other candidates appear, I would say you have the j=
>>Concerning the workflow dir in phpgwapi/inc: I also think it's better t=
>>have it in the dir of the workflow app. If an other app uses it, it can=
>>create a dependency to workflow.
>>regis leroy wrote:
>>>Let's talk about the workflow.
>>>Actually the official maintainer is Alejandro Pedraza, but in fact, as
>>>he told me, there's no more maintainer.
>>>So I purpose myself as a new maintainer.
>>>Basically I'm a dev working for a small consulting and open source dev
>>>society in France. I work on this workflow part of my day job and part
>>>of my spare time.
>>>My first works on this engine has been small bugfix. But I spend time =
>>>understanding and testing the stability the engine. So... I'd like to
>>>rename the version in 1.1.00.000 to reflect unstability. Actually the
>>>engine works well but only if all users act kindly with him and do not
>>>try to interact on the same parts at the same time. There's not a big
>>>road before a really stable release but:
>>>- still some bugfix, on stats or on administration tasks for example
>>>- the engine need works on concurrency and group management (and maybe
>>>default user/group assignation)
>>>- the application needs to be more like an egw app (nextmatchs,
>>>- a lot of functionnalities can make him look simplier for end users
>>>(basic forms parsed automically, etc)
>>>- integrate galaxia's own improvments and bugfixes
>>>- docs, docs, docs, examples
>>>- We have contributions from neomagic which contain some big improvmen=
>>>(on some of preceding tasks and on others) which have to be analized a=
>>>hopefully sometimes integrated (I'm still reading the whole re-written
>>>thing, it's a long job, if you guys can make incremental patches on
>>>future CVS workflow version you'll save me).
>>>The key point is that Galaxia lib should be, IMHO, moved in the workfl=
>>>repository. At least just because the workflow versionning and
>>>table_updates should match the /workflow directory content and not the
>>>/phpgwapi content and versionning.
>>>Now if someone want to purpose himself, or discuss about directions of
>>>this app he's welcome, I'm open to discussion and/or people.
>>>This SF.Net email is sponsored by Oracle Space Sweepstakes
>>>Want to be the first software developer in space?
>>>Enter now for the Oracle Space Sweepstakes!
>>>eGroupWare-core mailing list
>This SF.Net email is sponsored by Oracle Space Sweepstakes
>Want to be the first software developer in space?
>Enter now for the Oracle Space Sweepstakes!
>eGroupWare-core mailing list