Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [escet-dev] Openness/transparency
  • From: "Hofkamp, Albert" <A.T.Hofkamp@xxxxxx>
  • Date: Fri, 18 Jun 2021 14:21:28 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=tue.nl; dmarc=pass action=none header.from=tue.nl; dkim=pass header.d=tue.nl; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=5R1R++66p2xTyMZnXICvqPmXTFiZx4CBhXc94BoBpg8=; b=PM8DEuJRHESx69J1bXWQd8du2t4+LeGzwM5/gfeim35Tf5SuNPiT2ZrEt+3CUbZuGGTgxf9NNMWYg4lawSVfOE28yEqvSjZf610+2LSvI8evn4INNOWLOZQIFNypxZuq39dJ8+rE68Iu/AHAJ5vniMCJZL9jtoqJqN6xRPSoJGet0VNwsKvxHLlIrLpdahMSA2LxgXw5CfsB8/MkJznTvAvS76uN6xyVE0ybVo8+ObFkRl1g19WzyTGjBbj7L9m4ZZ1+NkAQ/s5P1H7xit4/dDztZi+Cq4uCHwZPbiacgI0dJ3cTgB4NRWMcwwN7GxoPZnfSLRf8CYgG9Zg1U5Tl8w==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=nuMYdN+vbM5wBmseWzQw3ViyxKe2F7eyVU/Cd29kW0NdTxCsXzfJhcYHwSC+VKBPwfguFuz965xC1nCzT+eDNs3wOW1dTu3Vkr34wKjqrHBCYHtZrPt2DwrwEKms0l+0n8yAN7QOp6UMAWqCt8Cqo7llGYxT+CCpkV08CfDFGlABpcy1yP9G2SexjO4UWJA2wt3Y9ngjYchSuRzeTf2URAYSoS+UEPW7CCt2O6yfoOoALYB2DTUM7oZg4t/8cf5giOVputDp+o4ELgRDWt2fDxOTyJ9sDT71NqgRiuVKP86ypAj/sFE7Ww2PYcUFZ3aTTyfwQahqMHs+9xAPq9JFAw==
  • Delivered-to: escet-dev@xxxxxxxxxxx
  • List-archive: <https://dev.eclipse.org/mailman/private/escet-dev/>
  • List-help: <mailto:escet-dev-request@eclipse.org?subject=help>
  • List-subscribe: <https://dev.eclipse.org/mailman/listinfo/escet-dev>, <mailto:escet-dev-request@eclipse.org?subject=subscribe>
  • List-unsubscribe: <https://dev.eclipse.org/mailman/options/escet-dev>, <mailto:escet-dev-request@eclipse.org?subject=unsubscribe>
  • Thread-index: AQHXZDrmiRlGh0AdF0K/Q/BRfxEdlasZsCBo
  • Thread-topic: Openness/transparency
Controller check (#122) is work that already existed (part of PhD work of Ferdie), which is just converted to ESCET, modulo some code that relates to other tools.

Empty container type-safety (#124) was something I noticed, which literally took less than an hour to change to a better standard Java alternative.

For the former, I am not sure what there is to discuss. ESCET is not the primary development platform. ESCET is a platform for publishing finished work. Stuff comes as-is. If this is a problem, the higher-level process should be discussed.

For the latter, could be done, but on the other hand, discussing whether we want more type-safe code seems like a question with only one possible answer.

To be honest, I am not sure I would want to develop in ESCET. Everything is so nailed down, tools are panicking all the time and would be breaking my flow.

From: escet-dev <escet-dev-bounces@xxxxxxxxxxx> on behalf of Dennis Hendriks <dh_tue@xxxxxxxxxxx>
Sent: Friday, June 18, 2021 14:13
To: escet developer discussions <escet-dev@xxxxxxxxxxx>
Subject: [escet-dev] Openness/transparency
 
Hi Albert

I noticed you created issues like #122 and #124 and then immediately provided a branch / merge request. Are these things that have been worked on in the past (in a fork for a closed-source research project), that are now being contributed to open source? Or did you do work on them specifically for Eclipse ESCET?

It would be preferable if you could create the issue before you start working on it, to improve openness and transparency. Now suddenly there is an issue and a solution, without the possibility for the other committers and the larger community to discuss the ideas.

Dennis

Back to the top