Count me as someone who will be VERY, VERY, VERY UNHAPPY ABOUT RESTRICTIONS!
Sorry for shouting, but it's hard for me to imagine how I can maintain the services that I provide without the access I currently have. Just as an example, I could not have developed this without such access:
I assume there must be extremely good reasons for this change of policy, no doubt related to ultra-secure security. I'm sure those reasons must be excellent and that you, or someone, will be able to articulate them. Please do so for the benefit of the community at large, given that you feel the need to announce this to the community at large, rather than to the "limited set of committers".
Perhaps a Bugzilla for such a discussion thread would be appropriate to reduce noise levels on the mailing list.
On 04.07.2019 21:49, Eclipse Webmaster wrote:
As some of you may know we have traditionally provided a limited set of committers with shell access to build.eclipse.org, and all other committers having restricted shells.
For the last couple of years we've been working to reduce that number as far as possible, and the time has come to finish the process.
Effective August 28th 2019 we will be transitioning all committers that still have a regular shell to our restricted shell. You will still be able to use SFTP and SCP to interact with the downloads and archive areas(but we suggest a job on your Eclipse CI instance!)
If you have any questions or concerns please feel free to contact Webmaster.
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit