Hi Stefan,

I do understand that the deletion of a Jenkins job would not harm the source 
code itself.

> Why should we maintain code that gives us no benefit?
Because the keeping does not cost us anything, but the removal plus a potential 
reanimation in the future would. You cannot compensate a missing benefit with 
the introduction of a new cost and risk.

> Just because the code is present and someone had written it?
> That is no argument.
Yes, indeed. But that's not my point. All I did was voting against the 
unnecessary deadline and suggesting a more convenient way of handling such 
issues. 

As I mentioned in my previous mail concerning the "broken commit history" I'm 
currently in a process of understanding the situation of Saros in order to 
provide the best possible advices and directives (with reasonable effort). I 
simply cannot pay attention to all of Saros' aspects and facets at once, hence 
I did not see the point of letting me pressurize by your deadline. 

There will be a decision on the Saros Widget Gallery, but you do not set the 
timeframe.


> Developer vs. Project Lead: Your knowledge must be superior compaired 
> against the current developers knowledge , normally you must advice us.
This is not true. There is no intrinsic need for a project leader (or leader in 
general) to possess more knowledge than his/her "inferiors" (*). The point of 
the matter is not the different *amounts* of knowledge, but the different 
*kinds* of knowledge. 
In the setting of a software project, in many cases there is a strong need for 
different experts amongst the developers. For a project leader it would be 
quite hindering in his daily work if he/she had to know all the tiny details of 
every aspect of the project. 
First of all, the project leader needs to see the "big picture". As you said, 
I'm quite new to the project, hence I have to learn many things. Such a leader 
is a "decision maker", not an inventor. 
Additionally, the project leader might have kind of a "process orientated" role 
to ensure that the developers' daily work is not disturbed by any distracting 
influences. Such influences may come from inside or outside the team. (You 
could read about Scrum and the role of the ScrumMaster in particular, if you 
are interested in this topic.)

Best wishes,
Franz

(*) I neither regard anyone of you as inferior, nor do I see me as superior -- 
I use these terms in an abstract way.

-----Original Message-----
From: Stefan Rossbach [mailto:srossb...@arcor.de] 
Sent: Thursday, May 10, 2012 1:53 AM
To: zie...@inf.fu-berlin.de
Cc: 'Saros'
Subject: Re: [Dpp-devel] Widget Gallery no longer produced

(1) & (2) see former Emails, I had described the problem.
(3) & (4)  We are not talking about code deletion. The code is still 
there and will remain in the SCM.

Currently the Job is deactivited, so the removal wont matter.

"Gegenfrage"

Why should we maintain code that gives us no benefit ? Just because the 
code is present and someone had written it ? That is no argument.
I had written hundreds LOC that had never seen the production. You have 
to deal with this as a developer.

Developer vs. Project Lead: Your knowledge must be superior compaired 
against the current developers knowledge , normally you must advice us.
Yes I know, you are a "new born" project lead, so feel free to explore 
Saros :P

Regards,
Stefan

Am 09.05.2012 12:00, schrieb Franz Zieris:
> Hi Stefan,
>
> I guess you refer to your announced permanent removal of the (currently 
> disabled) Jenkins Job "Saros_Widget_Gallery".
>
> First of all: Developers do not simply "announce" such things. I assume your 
> first mail (22nd April) was *meant* to be a proposal and since nobody 
> replied, you understood this as a tacit approval.
> The more convenient way of handling such situations would have been to
> (1) state the problem,
> (2) propose one or more alternative solutions,
> (3) optionally vote for one alternative and
> (4) ask the rest of the team for their opinions.
> And (5) if nothing happens, think twice if the silence is probably caused by 
> (a) approval, (b) rejection, (c) lack of interest or (d) lack of 
> knowledge/understanding.
>
> In the case at hand I believe (c) and (d) are the most likely explanations.
>
> To make a long story short: I appreciate your commitment, but I clearly vote 
> *against* the removal of the Jenkins Job.
>
> Best wishes
> Franz
>
>
> Side note: Although we use American English in most of our documents/source 
> codes, please do not use the counter-intuitive short American date format 
> "mm/dd/yyyy". You could e.g. state the name of the month instead.
>
>
> -----Original Message-----
> From: Stefan Rossbach [mailto:srossb...@arcor.de]
> Sent: Wednesday, May 09, 2012 2:39 AM
> To: Saros
> Subject: [Dpp-devel] Widget Gallery no longer produced
>
> Well the ETA was 6/1/2012,
>
> there were no changes to the code base so I assume that there will be no
> changes in the future.
>
> It was a nice idea, but it had not worked.
>
> For GUI development I would suggest:
>
> Copy some SWT Snippets (you will find many). Make
> a static method main method , running your GUI, stub all necessary
> things ... if you are done (layout),
> replace the stubs with logic, test it.
>
> Most JFace components running without a Eclipse installation, so this
> should be fine.
>
> Regards,
> Stefan
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Dpp-devel mailing list
> Dpp-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dpp-devel
>



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Dpp-devel mailing list
Dpp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dpp-devel

Reply via email to