Re: Bug postings on xaraya 1.2 release bugs

Dracos

You're such an ungrateful person and too involved with yourself to see.
Let me say this up front and for the last time:

All the work that I, and others did, in 'my private' branch (actually
the xarigami public branch as i have other private ones), is no more or
less of a fork than xaraya 2x, anacreon or marcel's private branches,
and the work done there was done over a period of YEARS.

Some of this work was done prior to 1.0 release and it was not pushed
because the changes were large and it was held off until after 1.0.

After 1.0 there was a large push from marc's branch and the merge debris
took some time to fix (at least to 1.1.2) which i worked on. Then the
decision was taken to not work on 1x branch at all, and focus on 2x.

At that time, over 2 years ago, now nearly 3 years ago, there was no use
keeping separate branches for the blocks code i did.  Since that time,
and  over the YEARS, I and others have been using this 'private' 1x
branch and fixing things because we continued to need it for projects.
The push here was 2x and no one wanted anyone to distract from it with
1x code focus here at the project.

Many of the bugs I logged in the xaraya bug tracker for 1x, i fixed in
our 'private branch' not thinking that it would ever see the light of
day given the freeze on 1x branch and 2x push.

Now, you have decided, after years of nothing going on here, to continue
with 1x.

Now you, after me and others spending literally hundreds of hours doing
the code, want me to go back over the years of work and tease out the
specific changes for YOU.

You would also realize that this 'private' branch is also php5 now (do
you understand that it won't run on php4 as i saw in another post you
didn't understand the difference to offering php5 support and being php5
only?) and want me to also take out the php4 vs php5 changes and adjust
for the current 1x and push it?

Well i'm sorry you're out of luck. I'm still busy here doing xaraya
modules and making them available to people that want them as well as
supporting myself and family. What are you doing?  What have you been
doing the last nearly 3 years since you've been 'manager' here.

If you want the code, it is there. Take it or leave it. If you don't
want it then that's your problem not mine. If other people want it, they
use it now on their sites.

I did ask for clarification - not just in relation to the post you
referred to which i have indeed read. But,  also in relation to
statements you made on irc about a pending release possibly 1.1.6 and
until that time only bug fixes would be accepted. It was also for
clarification about your inclusions of module bugs in the 1.2 release to
do list.

As for your comments in bugzilla - they are as useless as the comments
you make in this post and totally ignorable. If you can't take someone's
offer gracefully for what it is, then you have a problem and should just
be quiet.

I've been staying off IRC just so i don't have to put up with your
harrassment and intolerance - you do it stealthily. I've also been
making what some people deem to be useful posts on the xaraya forums and
working on xaraya modules for release. However you can't keep away and
stop harrassing can you?

Let me refer you to your post you made in the forums:
http://xaraya.com/index.php/xarbb/topic/3379

This was a typical, useful post about modules i was preparing for
release for xaraya cross posted from here for those that don't read here.

You're the one that turned that thread to what it ended up being -
dictating in that thread, for people to leave their day jobs and
websites if they discuss xaraya, and focus soley on xaraya project or
get out. Is that reasonable? No.

The  way you are treating anyone that does xaraya development, makes
suggestions, or offers code, that doesn't suck up to you will soon mean
you're own your own for 1x. And if your record of the last 2 nearly 3
years here on code commits is anything to go by, i'd say the 1x branch
is dead in the water already.


Jo

PS. For anyone that hasn't read the zillion useless posts in bugzilla,
the code is available, is public, has been for quite some time, and we
offer mtn access for whoever needs it.


Marty Vance wrote:
> jojodee wrote:
> 
>> Dracos
>>
>> You asked people to address the bugs for Xaraya 1.2 that you posted.
>>
>> I posted in the bugs were ones I logged myself in that list, and also in
>> bugs that i noticed were fixed some time ago in my own private branch,
>> when changes were not permitted in the xaraya 1x branch (either before
>> 1x for  reasons, or after due to the focus on 2x).
> 
> Fixes in your "private branch" (which I assume means your Xarigami fork)
> are irrelevant vapor as far as Xaraya is concerned *until you push them*.
> 
>>
>> You are now, implementing some type of focused attack on any of my posts
>> there. I've done a lot of work on the bugs that you want for 1.2, it's
>> been in openly available code for some time, I don't have the time now
>> because you've decided it's OK now to post to 1x - to go through and
>> tease it out just for you.
> 
> You see it as an attack because you want to be the victim.  I do not
> enjoy repeating myself, but you seem not to be listening.  Any work you
> have done on these bugs which is not available via mt.xaraya.com is
> irrelevant to Xaraya, and is not part of Xaraya.
> 
> Likewise, I don't have the time to "tease it out" either.  Perhaps
> someone else does.  Regardless, if someone did do you that favor, I
> would not be suprised if you later claimed the code was stolen, or not
> credited properly.  I am not taking your bait.
> 
> I take your use of the phrase "just for you" as evidence that you
> consider this ongoing tête à tête to be a personal matter between you
> and I, and despite statements to the contrary, you do have personal
> issues with me, which I have strongly suspected for years now.  If your
> issues with me now define your relationship with Xaraya, then I suggest
> it is beyond time for you to pursue other efforts.
> 
>>
>> If you want the code, then review it and use it, else not then please
>> desist on your misguided, self indulgent endeavours currently in
>> bugzilla, replying the way you are to my legitimate bug posts.
> 
> NO.  If anyone wants specific fixes to appear in Xaraya, it is their
> responsibility to push it or submit a patch.  If you don't have time to
> extract fixes from *your* repo, assume no one here has that time either.
>  Although, you do seem to have the time to troll through our Bugzilla,
> forums, and mail list... time which could be better spent extracting
> *your fixes* from *your repo* and pushing them.
> 
>>
>> I made legitimate posts on the bugs you requested people to focus on.
>> If you don't want that, you dont' want the code, then don't ask.
> 
> Are you not reading my comments?  They should be clear: IF YOU HAVE A
> FIX, PUSH IT OR SUBMIT A PATCH.  If you would rather keep taunting this
> community, I suggest you sit down and enjoy a nice tall glass of STFU
> instead.
> 
>>
>> As for the list of bugs for 1.2 release:
>>
>> 1. At least 2 are not bugs, the features exists
> 
> Which ones?
> 
>>
>> 2. At at least 3 possibly 6 that are probably already implemented some
>> years ago in the core.
> 
> Which ones?
> 
>>
>> 3. There are at least 10 that i can see off hand are imlemented during
>> the freeze on 1x work and in my private branch (calling it that because
>> you don't like mention of the word xarigami branch but in fact it has
>> other people's contributions other than just mine)
> 
> Which ones?
> 
> Again, your "private branch" (Xarigami fork) is irrelevant to Xaraya.
> Regardless of who has contributed to it, it's still a fork.
> 
>>
>> 4. There are some that will not be fixed unless there is major changes
>> in the underlying code of block layout, or the server files, or the
>> blocks module. Some of this was so major it was left for 2x. Is this
>> what you want for 1.2? Is it worth doing this in 1x when 2x is pending?
> 
> In case you missed it in the forum post of the bug list, some of these
> bugs may be assinged resolutions other than "fixed".
> 
>>
>> 5. There are non-core module bugs in that bug list. Previously for a
>> xaraya release we have focused on core and core module distribution
>> bugs. The other modules and issues related have not usually been
>> included in the release milestones. Is this an oversight or are you
>> changing this now?
> 
> Which ones?
> 
> Then this list needs to be triaged.
> 
>>
>> Finally, the last word here regarding 1x code changes was that there was
>> a release pending, and that no changes to the core API were to be
>> accepted and any already done were to be reviewed and removed if not
>> suitable.
>>
>> I think you need to clarify.
> 
> I think you need to read:
> 
> -------------------------------
> Subj: 1x (aruba) is no longer in maintenance mode
> Date: 13 Mar 2009 00:36:08 GMT
> 
> Aruba is now accepting bugfixes.
> 
> Any patches targeted to specific bugs known in Bugzilla should be pushed
> or submitted to Bugzilla as an attachment to the bug. Patches are vapor
> until they exist in the repository or in Bugzilla.
> 
> A roadmap for aruba is being worked on, which will commence with
> planning a 1.2 release. The previous 1.5 plan is scrapped.
> 
> Until the roadmap is complete, aruba is accepting bug fixes only. Any
> API and/or database changes which have been pushed to com.xaraya.core
> since 1.1.5 are subject to review, and may be reverted pending QA
> assessment. No further API or database changes will be accepted until
> the roadmap is worked out.
> 
> -------------------------------
> 
> News flash: the roadmap for 1.2 has been worked out in a rough form,
> published, announced, and the discussion/addition period has ended.  The
> milestones on it will be fleshed out in specific discussions beginning
> shortly.
> 
> If you continue to insist on wasting the time of everyone here, I
> implore you to follow through on your threats of leaving the project.
> 
>>
>> Jo
>>


-- 
http://xarigami.com :: Creative web development with Xaraya
http://2skies.com   :: Open source hosting and development