As Paul said you are welcome to use either.
My feeling is that it would be better to keep using eclipse-scripting-dev
though. This creates less noise for people interested in following only
the scripting work, and creates a focused place for in-depth scripting
discussions. Also if this becomes a separate project you could then migrate
or keep that list archive associated with the project.
09/20/2013 09:34 AM
scripting code going to the e4 project
I’m not sure which list
to use. Regarding the topic it would belong to scripting-dev, but posting
on e4-dev might draw more attention to the project. We just should avoid
to spam e4-dev with meeting requests and things like that.
From: Oberhuber, Martin [mailto:Martin.Oberhuber@xxxxxxxxxxxxx]
Sent: Friday, September 20, 2013 3:30 PM
To: Pontesegger Christian (IFAT DCGR CCS SYS); DAUSSY Arthur (arthur.daussy@xxxxxxxx)
Subject: scripting code going to the e4 project
Hi Christian, Arthur –
I see that your committer election to the
e4 project has been initiated, that’s great !
I was wondering whether I should also apply
for commit privileges on e4 but for now I won’t realistically have enough
time so I’m going to defer that one.
But this opens an important question, shall
we continue using the eclipse-scripting-dev mailing list for discussions
or move to the e4-dev mailing list ?
Martin Oberhuber, SMTS
/ Product Architect – Development Tools, Wind
River direct +43.662.457915.85 fax
eclipse-scripting-dev mailing list