| Re: [tractusx-dev] Non-Committers Working on Eclipse Tractus-X |
|
Hi, I talked today with Fred from EF and its not possible.
Bye, Sigi From:
tractusx-dev <tractusx-dev-bounces@xxxxxxxxxxx> on behalf of Brunkow Moser, Mathias via tractusx-dev <tractusx-dev@xxxxxxxxxxx> Hi Malte, I believe that the answer to your question unfortunately is no. The permits in Tractus-X cannot be delegated in a personalized way. You can become a committer (approve PRs, see security tab, etc..) or first get a contributor (close issues, assign labels, see private packeges, request review in PR,
etc...) by requesting to an existing committer. If is not possible to work in Tractus-X directly, this person needs to work in a fork from her repo and create PRs that are approved by commiters. I agree with Evelyn’s point. We as Tractus-X are not responsible for deciding in which forked repo or GH Org they should work. The only thing that matters is that is
a fork. A best practices is to maintain the main branch synced, in this way when the PRs are merged there is no big conflicts with the main branch. Now about the email account point: Each github account can have more than one emails associated. Me for example, I have my company email as primary in the github account, however I can also have my personal one as a secondary one for example, This means that when a contributor is creating content in Tractus-X, in a Catena-X Fork or in his personal fork he shall be using his company email to commit. Therefore if we as tractus-x want to keep track in which company this person is working, he/she need to follow this steps first:
If he/she follows this steps always when he/she creates a pull request from a Fork will be able to know which company is contributing. About the Dependabot bot and commiting to other branches, in my understading this is just allowed to commiters. Since they are the ones that have the authority to merge
the PRs to any TX Branch not just main. What you can do is to execute the dash license by your own and then update the DEPENDENCIES file so you can see if there is already IP checks on the way. In this way maybe there is no need to a commiter to run the Dash
Tool for you if there is any restricted libraries. Tip: You can always comment in the PR that an IP check is needed to speed things up.
I hope it could help you a bit, Best Regards,
Mathias Brunkow Moser | Software
Engineer Consultant Industry 4.0, IoT & Catena-X
|
CGI Deutschland B.V. & Co. KG Leitzstraße, 45 | 70467 Stuttgart, Germany
M: + 49 1525 6723056
mathias.brunkowmoser@xxxxxxx
|
www.cgi.com/de/de CONFIDENTIALITY NOTICE: Proprietary/Confidential Information belonging to CGI Group Inc. and its affiliates may be contained
in this message. If you are not a recipient indicated or intended in this message (or responsible for delivery of this message to such person), or you think for any reason that this message may have been addressed to you in error, you may not use or copy or
deliver this message to anyone else. In such case, you should destroy this message and are asked to notify the sender by reply e-mail. From: tractusx-dev <tractusx-dev-bounces@xxxxxxxxxxx>
On Behalf Of Hellmeier, Malte
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 -------------------------------------------------------------------------------------------------- Folgen Sie uns:
|
