I know that answer "in line" has its hard to read some
times, but I´ve no choice in this case:
> Hi Esteban,
> > But, Thibault remmember a mail which him copy in
> > mail, where ask for new "blood" for the project.
> > Lamentably, by now my work is only
> > viewed in the translation into Spanish.
> > I try to "publish" it, but I can´t do because
> there is
> > a lot of "debuging" work to do...
> This is just because you've joined the team when the
> main goal of the
> project manager was to release a stable new version
> of phpSV. Thus, in order
> to avoid new issues, a Feature Freeze has been
Ok.. my appologies, I not understood this then, but
now is clear for me. My appologies again.
> I know this is really disappointing, it is as well
> for me because I'd like
> to add new stuffs.
> But your patience will be rewarded since the next
> release is approaching.
Thanks, I know that my work isn´t a jewell, but I know
too is usefull, IMHO of course...
> To Carsten: may be we could add a new devel branch
> for Esteban to push his
> fixes ? Would it be easy to make it in synch with
> current RC develloppement
> given the fact that only small fixes are expected ?
Thats would be great! (I´m jumping like a child!)
> > So, the question is:
> > If every one of us who wants to collaborate with
> > functions or enhanced ones, functions that doesn´t
> > impact critically in the internal structure of the
> > code or the database, we can´t "publish" our
> apport if
> > it isn´t a "critical" one... how is supposed that
> > project grows up?
> Again, you're missing just the fact that the team is
> limitted to Carsten,
> Machaven, sometimes me when I have time...
> If we just decide to introduce your patches
> immediately, we won't be able to
> mark the new tree as stable, and we won't be able to
> release a long awaited
> stable version...
This is fully understandable.
> As far as I am concerned I joined the project team 2
> months before you, at a
> time where adding functionnality was still possible,
> and I found the team
> very reactive at that time. I must admit that
> currently we are all crushing
> under work, and trying to fix as much bugs as we can
> for the next release:
> it will be a great relief as soon as it is done.
Ok, it is a "secure" method which you use: first
stable after new stuff... Again, now is clear to me
what this means... I don´t know why I thinked that you
have 2 separated branchs, and why I understand that
you are working in version 2... Again, my
> > I must say that in a "welcome" mail from Carsten
> > Machaven (I don´t remember, sorry) they encouraged
> > for my suggestions and invites me to join the
> > But I tried (and I want) to share my work but I
> > because they tell me than I must wait to the
> > 2.
> No, not version 2. You're just waiting for version
> 1.50-stable (because I
> think there will be a new 1.49RC, but am not sure).
BTW, it will sounds a little "spooky" but I´m updating
every day what you publish in SVN, and of course I´m
using as production version (so it is tested in the
wild... risky?.. perhaps, but the road is made walking
as said Machado and singed by Serrat)
> > Ok. This is acceptable... But I´m affraid than in
> > version 2 you use one of the models propossed and
> > my work goes unusable...
> I think work on version 2 is stalled (because we
> lack task force, and we're
> all working on current release).
> I think version 2 will require a lot of work, and is
> not soon to come if the
> team doesn't grow. You seem interrested in working
> in this, so please go on.
> However, if you need to get your work featured
> quickly, I think you'd better
> work on current 1.48RC which will not be that
> different form 1.50-stable.
OK.. so, I´m going ahead as until now...
> > Or worst: some one publish a
> > modification and my work isn´t compatible...
> In 1.50, I don't think so ;-) It is only bugfixes
Pfiuuuu!... this is lightening...
> > I remark that: I´m only talking about the date
> > and some improves done to the conditional part of
> > questions just this, these improves are related to
> > actual work, they are working at 80%, with a
> > effort get the 100% but my times are not good with
> > so first I focused on the obligations and after on
> > bonuses... (I´m offering to document the code,
> give my work
> > force to do what you instruct me, etc)
> I get the same aim: improve phpSV following my
> company needs, and then give
> a little more work from my leasure time.
Well, I´m felling less guilty now... In other words,
I´m starting to undrestand what means work in a Open
Source Project: every one adds something used in his
every day work, at least...
> > So.. Please, I request you, I beg you let me sent
> > someone the modifications I done before they gone
> > unable to be used...
> You can send them to me, with the approriate
> documentation (in english, but
> if you really don't have time to translate, I can
> understand simple
Ok... this night I´ll prepare the files and the notes
for you... I´m trying in my Spanglish, just for avoid
more babilonic missunderstandings (another joke.. )
> However, like Carsten and Machaven, I'm more
> currently committed to fixing
I´ve that clear, but I preffer to share the changes at
least as an antecedent, or in the worst case, a
> Again, I think a new devel repo should be great. If
> its not possible to
> define a new official devel repo, I could try to
> raise a private repo for
> you and me and others, and when the new official
> branch will be opened we'll
> merge changes.
Just instruct me what I must do...
> > Thanks in advance for your time, and my appologies
> > I wrotte something rude, it wasn´t itentionally...
> I understand your meaning.
Thanks for your support...
> I think next RC will occur within the week so
> Carsten and Machaven will be
> able to give us feedback by the end of the week I
I´m following your updates via SVC...
Preguntá. Respondé. Descubrí.
Todo lo que querías saber, y lo que ni imaginabas,
está en Yahoo! Respuestas (Beta).