[tractusx-dev] Non-Committers Working on Eclipse Tractus-X

["Hellmeier, Malte" <Malte.Hellmeier@xxxxxxxxxxxxxxxxxx>]

Hello Tractus-X,

I want to discuss the best-practices of non-committers working on an Eclipse Tractus-X project (started this discussion Catena-X internally). Imaging a new developer who isn't part of any Eclipse / catenax-ng organization which starts working on a project. Is there any way to give the persons permissions to work on branches in Eclipse Tractus-X?

One possible way would be working in a catenax-ng fork, but as far as I know, the long-term strategy is to get rid of this catenax-ng organization. The second possible way is to create a personal fork of the project. However, this may become problematic with internal company guidelines because a GitHub account is associated with a person, making it difficult to distinguish between personal and business work.

 

Also, think about Dependabot. The bot creates a new branch in the Eclipse Tractus-X project for a dependency update. To be compliant with the Eclipse guidelines, the Dash Tool needs to be executed to update the DEPENDENCIES file. Is there any way to give external non-committers writing permissions to branches? I know that merging into main should only be possible by Committers.

 

 

It would be great to hear from you!

 

 

Thanks,

Malte

 

--

Malte Hellmeier, M. Sc.

Fraunhofer-Institut für Software- und Systemtechnik ISST

Wissenschaftlicher Mitarbeiter Logistik

Speicherstraße 6, 44147 Dortmund, Germany

Telefon +49 231 97677-464

malte.hellmeier@xxxxxxxxxxxxxxxxxx
www.isst.fraunhofer.de

 

--------------------------------------------------------------------------------------------------

 

Folgen Sie uns: 

 

       

 

Attachment: smime.p7s
Description: S/MIME cryptographic signature