Re: Xaraya2x actions to come

Marcel-

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.

This codebase will be available to be reviewed INDEFINITELY via the 
repository; benefits of open source and GPL.

Your message sounds far too emotionally charged, and I would caution you 
against labeling other people's intentions with negativity.

The PMC endorses the proposed changes as part of it's endorsement for 
the 2x lead. 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.

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.

The intent of the mentioned revisions (aside from the copyright update) 
is to improve upon, add to, and/or fix parts of 2x that are addressed by 
the code.

As to whether the intention is to merge the indicated repository as a 
whole or not will be a question for the 2x lead to answer, as will be 
answers regarding where the sources can be pulled prior to merge.

I understand that there will naturally be concerns regarding any changes 
to be made. I am not without my own reservations about how these changes 
may affect my own work. However, change is what the process is all about.

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.

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.

-St.Ego

Marcel van der Boom wrote:
> [email protected] wrote:
>   
>> c. my own bugfixes and minor enhancements to the above, which can be 
>> followed 
>> here:http://mtn.netspan.ch/viewmtn.py/core/branch/changes/ch.netspan.xaraya.core 
>>
>>     
> A 5 min. review of this shows this revision:
>
> http://mtn.netspan.ch/viewmtn.py/core/revision/info/cd9ce4ea9e623d5a97bfee2feebf59bbe53b2c6d
>
> and their predecessors. Not only is it a very questionable action to 
> remove all copyright lines in the code which are not yours to remove, 
> but this makes merging in your changes at least debateable. What is or 
> was your intent there?
>
> I'm a bit worried now, to say the least and I urge people to review this 
> codebase thoroughly. As said earlier, Marc and myself are the only two 
> people having done major work on the 2x codebase. I was not consulted 
> for input on 2x actions at all, which is fine, but I think people should 
> realize this.
>
> The fact as such, the removal of copyright, is bad, but the intention of 
> the person doing it is worse, for whatever reason. I dont think this 
> should go by silently.
>
> The questions I have are these:
> - what is / was your intent with the mentioned revisions?
> - is the intention to merge the indicated repository as a whole?
> - where can people pull the sources for the mentioned branches?
>
> marcel
>
>