Closed raboof closed 22 hours ago
I'd generally recommend transferring the repo, otherwise sending a PR would always default to this repo, but here it is - https://github.com/sbt/sbt-bom
I'd generally recommend transferring the repo, otherwise sending a PR would always default to this repo, but here it is - https://github.com/sbt/sbt-bom
Ah, that's a good point, thanks! Could you rename it to sbt-sbom
to disambiguate it a bit better from the various plugins that are about the separate Maven Bill of Materials concept (e.g. https://github.com/heremaps/here-sbt-bom, https://github.com/lightbend/sbt-bill-of-materials)?
ah wait, I see the repo is now indeed 'forked' rather than 'transferred' - do I understand correctly that you'd recommend @siculo 'transfer' it instead? Is that still possible now or would it need the fork to be removed first?
do I understand correctly that you'd recommend @siculo 'transfer' it instead?
Yea.
Is that still possible now or would it need the fork to be removed first?
We can try it, but I can always remove the fork.
I'm ok with transferring the repo. I've never done a transfer, so I'll have to look at the docs. I don't think it's complicated...
Who will take the ownership?
Another problem is to have others publish the same artifact on maven central. Maybe it's better to change group-id?
You can transfer it to me @eed3si9n first, and I can re-transfer it to sbt and create a team with you and others in it.
Another problem is to have others publish the same artifact on maven central. Maybe it's better to change group-id?
I think changing the group-id (to com.github.sbt
? https://repo1.maven.org/maven2/com/github/sbt/ ) makes sense
You can transfer it to me @eed3si9n first, and I can re-transfer it to sbt and create a team with you and others in it.
I have submitted the transfer request. You should receive a confirmation email.
I've re-transferred it to sbt/sbt-sbom. Y'all can decide if this should be sbt-bom or sbt-sbom.
@siculo There should be an invite to https://github.com/orgs/sbt/teams/sbt-bom in your inbox.
@siculo There should be an invite to https://github.com/orgs/sbt/teams/sbt-bom in your inbox.
@eed3si9n Would you mind adding me to that team as well? Thanks!
@siculo There should be an invite to https://github.com/orgs/sbt/teams/sbt-bom in your inbox.
I don't see it. Can you check?
p.s.: I can work on the project, but I didn't see the invitation, nor access the link above.
@mkurz Done.
@siculo Yea. Here's a screenshot of pending invite:
I'm a member of the sbt-bom team but my review of #62 is still 'grey' - could it be the team hasn't been given write access to the transferred repo yet?
Same here, I am just a member but not a maintainer
Fixed the access control. The team now should have maintain rights.
Looks good, thanks!
I guess we can keep this issue open until we've set things up to publish under com.github.sbt:sbt-sbom
Looks good, thanks!
I guess we can keep this issue open until we've set things up to publish under
com.github.sbt:sbt-sbom
I plan to use sbt-github-actions for this unless someone has strong objections
So I am going to close this issue as publishing is working (well at least the snapshot is), see https://github.com/sbt/sbt-sbom/actions/runs/11406505669/job/31740681174 .
If there are any more issues then we can open another ticket
I talked to @siculo about the plans for ongoing maintenance of this project. He mentioned the best way forward is probably to fork the project and publish it under a different groupId. I'd be interested in getting that off the ground, and @mdedetrich would like to help with this as well.
@eed3si9n would you like to fork this project into
sbt/sbt-sbom
so we can continue there?