You gave me orders in a private email, at least based on how you wrote emails 
and based on the "netiquette" (i am pretty sure you see what i am referring 
to). But anyway, you do not agree with the way i see the situation on that 
specific point and that is fine, i retract what i said on that topic and 
apologize i bring that up. Nothing i said initially was based on this anyway.

As for ODA, do a SVN copy implies that we have a place for branches, which we 
do not have. I do not have the time or do not feel the authority to do so.

I still do not understand why you are creating so much "discussions" when i 
only made a remark about future modifications to the database (again, i did not 
even reject your modification) and asked you to not modify Debian specific code 
without discussing with me first since i am the one in charge of this (i really 
do not see why this could not be acceptable).

Thanks,


----- Mail original -----
De: "LAHAYE Olivier" <olivier.lah...@cea.fr>
À: oscar-devel@lists.sourceforge.net
Envoyé: Vendredi 1 Février 2013 12:24:54
Objet: [Oscar-devel] RE : RE : RE : Remark about any modification to the 
database


Geoffroy,

I never ever explicitely or invasively told you that I did not like you as a 
project chair. Never ever! Far from that. Why would I have wished that??? 
You're one pilar of OSCAR.

It is true I was frustrated by delays in comminting my mods to the SVN (and I 
understood that you were doing that freely and thus had no obligations in doing 
this), but I never gave you any kind of ORDER for that. One day, after 3 
unanswered mails I sent you a capital letter subject mail thinking that you 
were flooded by work mails and hoped it would let you see my mail (but 
unfortunately you did interpret this in another way and despite my effort to 
explain this I had no way to be understood)

Honestly, I'd be very happy to have the relashionship we had in the past. This 
situation is hurting me a lot at the point it's hard to sleep sometimes :-(

I'm again really sorry if I broke things on your side. If I did modify, there 
was a reason, trust me, and it hit my big backport of all my work. This 
situation was exceptional and since now, developpent should be smooth again. 
there were 200+ commits on my local svn. It tooks hours to split in fewer 
coherent commits. What should I have done things then?

For you oda issue, couldn't you have done an svn copy of a released tag and do 
the fix in this copy (and backport later the fix in the trunk?).

Best regards,

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

________________________________________
De : geoffroy.val...@free.fr [geoffroy.val...@free.fr]
Date d'envoi : vendredi 1 février 2013 17:45
À : oscar-devel@lists.sourceforge.net
Cc: LAHAYE Olivier
Objet : Re: [Oscar-devel] RE : RE : Remark about any modification to the 
database

I explicitly said that i was ok with your modification but that in the future, 
it is always better to speak about the details on the mailing list. I tried to 
tell you how this group was working in the past: you modify the database, you 
speak about it first on the mailing list. If you are not ok with that's fine 
but you clearly go against the way we were working in the past.

Then you are claiming i am "fighting like a shark" (yet another accusation, 
thanks!)... where did you get this? I am ok with 95% of your modifications and 
did not say a thing. I am complaining about a few modifications that concern 
things i am working on, that you modified without any discussion. Am I supposed 
to be quiet, not raise any questions or remarks because i need to be careful 
about the way you feel? Which by the way i cannot know.

I am ok with every you said about trunk: yes it is reserved for developments 
and yes it is ok to break it. However, trunk is not a resource for a single 
developer or maintainer, you need to communicate. In other terms, when you 
suspect that a specific check-in will impact the work someone else is doing, 
you are supposed to synchronized with that person. If i modify anything related 
to RPM, i will make sure to contact you first (except if trunk is broken in 
that it is ok to modify directly). If you modify something related to Debian, i 
believe it is normal to contact me.

You explicitly told me you did not like me as project chair, i resigned; you 
clearly told me that you want to be able to move fast and do all modifications 
you want, i supported your write access to SVN. Do you want me now to be 
completely silent and do not raise concern and just deal with whatever you are 
doing?

Thanks,


----- Mail original -----
De: "LAHAYE Olivier" <olivier.lah...@cea.fr>
À: oscar-devel@lists.sourceforge.net
Envoyé: Vendredi 1 Février 2013 10:51:49
Objet: [Oscar-devel] RE : RE : Remark about any modification to the database

Ok,

Maybe I' wasn't clear.
I said that I did modify the database you could have warned me at that time, 
but you didn't. Whatever the mod would be, you could have raised a concern 
about that, but you didn't. I could have issued an RFC (I didn't know that I 
should have and will do in the future), but even without this RFC, you were 
aware that a change to the database was on its way and you could have warned me 
at that time. Insted uyou waited until I did the change and publicly criticised 
my way of doing things. This is very unfair :-(

I said that I would push my modifications, you could also have warned me at 
that time (but you didn't either).

Then I've pushed many update doing my best to have OSCAR ready for the future 
and you fight at me publicly like a shark. This is very demotivating I must 
admint.
I always accept all remarks at take them into account (I will for database and 
future modifications), but it is very unfair to imply that I've pushed 
everything without notice before. Maybe I was not exaustive, but I'll do my 
best and will learn from that.

As for the update process, maybe it is partially broken, but my understanding 
is that the svn trunk is a devel tree and is not meant for production. Your 
production systems shouldn't be affected by that. I cannot push 100% of all 
stuff ready for a release, but be assured, that the upgrade script will be 
provided. You can create a release with version before my commits a week ago 
and I can work on all issues generated by this massive commit so a after 
massive commit release can be made for testing purpose.

As for RHEL5, it juste entered a stage were minimal hardware evolution is 
provided. This means that RHEL5 will not be installable on future hardware 
releases (most likely).  Thus one  guy buying let say a new HP system released 
in june 2013 has great chance to be unable to run RHEL5 on it and thus will 
requires RHEL6. My experience is that latest stable oscar is unable to run on 
RHEL6, and all the work I've done so far on oscar is to remove this limitation 
and make OSCAR sustainable.

Regards,

Olivier.
--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

________________________________________
De : geoffroy.val...@free.fr [geoffroy.val...@free.fr]
Date d'envoi : vendredi 1 février 2013 16:14
À : oscar-devel@lists.sourceforge.net
Cc: LAHAYE Olivier
Objet : Re: [Oscar-devel] RE :  Remark about any modification to the database

I just looked at your post again and i am sorry but i do not see ANY detail 
about the database modification. Please read again my email and you will see 
that it is about what everybody should do in the future.

Then, you say you are new to the open source development thing but obviously 
you do not accept any kind of remarks about what you are doing the wrong way. 
So simple question: what are the other developers, including me, supposed to 
do? Let you do whatever you want silently?

Also by adding something to the database, you potentially break all update 
process: the database is already there, with the old schema, when updating, you 
do not recreate the database, so the new field is not included, later on you 
try to add a value to the field that is not there and therefore create a crash. 
When adding a field to the database the usage is, at lease, to provide a script 
that update an existing database.

About your RHEL5 remark, what does it mean? I simply do not see your point...

Thanks,

----- Mail original -----
De: "LAHAYE Olivier" <olivier.lah...@cea.fr>
À: oscar-devel@lists.sourceforge.net
Envoyé: Vendredi 1 Février 2013 04:47:55
Objet: [Oscar-devel] RE :  Remark about any modification to the database


I'm sorry if I've not been clear enought, but On Dec 13 2012, I annouved 
support for GPU in wizard AND DATABASE
http://sourceforge.net/mailarchive/message.php?msg_id=30224108 with no tech 
queries or warnings about this modification.

Then On January, 25 2013, I did announce that I would commit all my work 
http://sourceforge.net/mailarchive/message.php?msg_id=30401060 without 
receiving any warnings or advice.

I stated that I had tested the whole oscar on my cluster and that my 
modifications was able to pass all oscar steps including step 8. No more 
technical queries or warning.

Regarding the modification I madeto the database, there are several 
modifications level of danger.
Removing a column can be infinitely more harmfull that adding a column (our 
case). At worst, the added column is ignored. For GPU support, it was an 
addition.

Geoffroy, you know that I'm new to opensource developpement, so please, be a 
little bit more comprehensive with my mistakes.

Without my work, Oscar would still be stuck to RHEL5 wich entered Production2 
state on January 2013 (which means minor native hardware enhancements). As 
stated in this message 
http://sourceforge.net/mailarchive/message.php?msg_id=30401690 I know that 
while it works fine on my system, it is far to be ready for all systems and it 
may break things, but this is the way to go (on a developpent tree) if you want 
to reach the next step.

Best regards,

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

________________________________________
De : geoffroy.val...@free.fr [geoffroy.val...@free.fr]
Date d'envoi : jeudi 31 janvier 2013 22:29
À : oscar-devel@lists.sourceforge.net
Objet : [Oscar-devel] Remark about any modification to the database

A modification to the database was made a few days ago, i am totally ok with 
that modification, but no developer is allowed to modify the database without 
initiating a discussion on the mailing list first. The database is the very 
core of OSCAR, we _must_ be very cautious with every single modification made 
the database schema and ensure that everybody in the project is ok with the 
proposed modification.

In other terms, like in any other project, for core modifications (such as the 
database), it is always better to send a RFC on the developer mailing list 
first, especially since we have a few active developers/maintainers again.

Thanks,

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan
_______________________________________________
Oscar-devel mailing list
Oscar-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oscar-devel

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan
_______________________________________________
Oscar-devel mailing list
Oscar-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oscar-devel

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan
_______________________________________________
Oscar-devel mailing list
Oscar-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oscar-devel

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan
_______________________________________________
Oscar-devel mailing list
Oscar-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oscar-devel

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan
_______________________________________________
Oscar-devel mailing list
Oscar-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oscar-devel

Reply via email to