Re: Xaraya2x actions to come

St.Ego wrote:
> The intent is to add needed fixes and enhancements while at the same 
> time removing the unnecessary replication of copyright notice. The two 
> actions are not tied together in any way, as you seem to indicate.
I dont think 'unnecessary replication of copyright notices' is the 
proper description of the changes I pointed to. The copyright lines are 
structurally *replaced* in every file in a repository not in the public 
xaraya location.  Even if there is unnecessary replication, which i have 
never heard before until now,  replacing them would not be proper 
without some preparation, no? (such as formally documenting it and 
informing the current copyright holders before the fact)
> Your message sounds far too emotionally charged, and I would caution 
> you against labeling other people's intentions with negativity.
As for labelling negativity, I dont know. Replacing copyright in a 
repository not in the xaraya location,  not accessible by everyone does 
indeed not go down very well upfront and was not a welcome surprise. I'm 
sure you can understand my position in this. The line of disagree-ing 
strongly and labelling negativity is thin one. I meant to convey my 
strong disagreement.

> The PMC endorses the proposed changes as part of it's endorsement for 
> the 2x lead.
Does that include the copyright changes?

I just have questions regarding *those* changes, for I think they are 
improper at this time. I have not looked at the functionality in other 
revisions yet. My concerns initially are about the revisions changing 
the copyright lines and their comment "Remove DDF from the core". If the 
intent is to not share the copyright to the DDF anymore, perhaps that is 
a proposal to be discussed?

> In the event that a change is introduced which, for whatever reason, 
> proves not to work out, it can be modified, removed or reverted back, 
> depending on case. We do not understand why this would be a concern. 
> EVERY new commit has the potential to introduce a bug; that is 
> accepted as part of the process.
That bit is indeed not so much a concern, if it regards *functionality* 
or features.  I was not referrring to those changes. Even if i dont 
agree with the functional changes ( i dont know,  Marc and I were pretty 
much aligned on most functionality), those are pretty easy, discussion 
wise. Everything can be undone if new insights arise regarding 
functional changes.

My question is about the intent of the copyright removal which, at the 
time (Dec. 2008) was not yet discusssed at all, nor done in a proper 
way.  I maintain my view this is a remarkable change introduced at the 
time and not to be merged, as is.

> And, for what it's worth, NONE of this is going by SILENTLY. There has 
> been considerable discussion about the copyright matter, and the issue 
> of adding to the 2x repository has been addressed above.
Good, although i think the discussion on the copyright matter you are 
referring to is about the 'form details' (ranges vs explicit years). Not 
about removing them altogether. (And even then the question of timing 
remains)

> I agree that change needs to be monitored, but we must all keep in 
> mind that change management is about adapting. I welcome any and all 
> technical, business and legal discussion concerning the project, but 
> using charged language like stating that the "intention of the person 
> doing it is worse" justified only by "for whatever reason" will cause 
> negative feelings in the community and hurt progress.
If that was the general feeling, i apologize.  I maintain my scepticism 
on the change and the explanation you gave. Asking for elaboration on 
it, even if ill formulated, is justified i think, especially considering 
the state the project has been in.
> That being said, I would like to see a summarized list of the proposed 
> changes to 2x prior to them being integrated with the core. This 
> simple request is all that we should really need.
Can we have the discussion on the functionality separated from the 
copyright?

marcel

-- 
Marcel van der Boom -- http://hsdev.com/mvdb.vcf
HS-Development BV   -- http://www.hsdev.com
So! webapplicaties  -- http://make-it-so.info
Cobra build site    -- http://cobra.mrblog.nl