Hey Elisey, it is described here: https://www.apache.org/licenses/contributor-agreements.html#submitting
It basically goes to secret...@apache.org Subject something like: "SGA for Storm Docker". In the mail just add the signed SGA (as described under the link), a link to the GitHub Repo (is most likely already inside the SGA) and a link to this mail thread: https://lists.apache.org/thread/34kkzbcfr4qxcxmclgqmjc08o9s28gjz Gruß Richard Am 9. Januar 2024 11:33:48 MEZ schrieb Elisey Zanko <elisey.za...@gmail.com>: >Hi Richard, > >Sounds good to me. >Where do I send the signed SGA and with what subject? > >Thanks, >Elisey > >> On 9 Jan 2024, at 15:20, Richard Zowalla <r...@apache.org> wrote: >> >> Hi all, >> >> just got a response from the incubator. >> >> What we would need from you (@Elisey) is a signed Software License >> Grant (SGA) [1] downloadable here [2]. >> >> It would need to follow the procedere described under "HOW-TO: >> SUBMITTING LICENSE AGREEMENTS AND GRANTS". >> >> Let us know, if you feel, that this would work for you. >> >> Gruß & thx >> Richard >> >> [1] https://www.apache.org/licenses/contributor-agreements.html#grants >> [2] https://www.apache.org/licenses/software-grant-template.pdf >> >> >> Am Dienstag, dem 09.01.2024 um 09:11 +0100 schrieb Richard Zowalla: >>> Hi all, >>> >>> great news. I reached out to the ASF incubator people to check, which >>> guidelines we need to follow in order to integrate / migrate >>> ownership >>> of the code (repository) to the Storm project. Let's see what they >>> say >>> would be the best strategy (even if it is just fork and re-license) >>> and >>> if a CLA would be required. (Side note: I can totall understand, if >>> you >>> wouldn't want to sign one, so we hope for the best). >>> >>> It might be best to put the related Docker code into a separate repo >>> under the ASF org on GitHub (apache/storm-docker), so we can publish >>> under the "official" Storm Docker location and under apache/storm on >>> Docker. By doing so, we can preserve git history. >>> >>> Infra told me, that it has some benefits to put it under apache/storm >>> since the ASF has all the premium features (rate limit, ...) on >>> Dockerhub. Sadly, there seems to be no easy way to do an automatic >>> "redirect" (similar to a Maven relocation) on Dockerhub. >>> >>> Gruß >>> Richard >>> >>> >>> Am Montag, dem 08.01.2024 um 11:47 +0000 schrieb Julien Nioche: >>>> Hi Elisey, >>>> >>>> Thanks for your email and great to hear that you'd be happy to >>>> contribute >>>> the code. I am CCing the Storm dev list so that our discussion is >>>> in >>>> the >>>> open and members of the community can contribute to it. >>>> >>>> For the people on dev@, Elisey is the author of the Storm images on >>>> Docker >>>> <https://hub.docker.com/_/storm> that many of us in the community >>>> have been >>>> using, let's thank him for that! See my message with him below as >>>> well as >>>> STORM-4014 <https://issues.apache.org/jira/browse/STORM-4014> >>>> >>>> @Elisey - we might need you to sign a contributor agreement >>>> <https://www.apache.org/licenses/contributor-agreements.html> >>>> beforehand >>>> and ideally change the license to be ASF v2. Would that be OK? >>>> >>>> I initially thought we'd have the Docker files as part of the Storm >>>> repo >>>> but maybe it would be simpler to have a separate repository for it >>>> and copy >>>> the whole git history from your repository. >>>> We already have the following on Dockerhub -> >>>> https://hub.docker.com/repository/docker/apache/storm/general, not >>>> sure how >>>> that would work with the 'official images'. >>>> >>>> Cheers >>>> >>>> Julien >>>> >>>> On Fri, 5 Jan 2024 at 12:00, Elisey Zanko <elisey.za...@gmail.com> >>>> wrote: >>>> >>>>> Hi Julien, >>>>> >>>>> I’d be happy to contribute the image! >>>>> Especially because I no longer actively use it myself and don’t >>>>> have much >>>>> time to maintain it. >>>>> >>>>> If you haven’t seen it already I’d suggest you to have a look at >>>>> “Maintainership” section of the Docker Official Images repo: >>>>> https://github.com/docker-library/official-images#maintainership >>>>> >>>>> From that doc I think the most important part is: >>>>> >>>>>> When taking over an existing repository, please ensure that the >>>>>> entire >>>>> Git history of the original repository is kept in the new >>>>> upstream-maintained repository to make sure the review process >>>>> isn't >>>>> stalled during the transition. >>>>> >>>>> Let me know how would you prefer to transfer the repo to the >>>>> upstream >>>>> (e.g., fork, copy commits or move ownership). >>>>> >>>>> Once transferred we’ll need to create a commit to >>>>> https://github.com/docker-library/official-images/blob/master/library/storm >>>>> to update image maintainers and git repo. >>>>> >>>>> Thanks, >>>>> Elisey >>>>> >>>>>> On 4 Jan 2024, at 19:56, Julien Nioche >>>>>> <jul...@digitalpebble.com> >>>>>> wrote: >>>>>> >>>>>> Hi Elisey, >>>>>> >>>>>> Happy New Year! >>>>>> >>>>>> I am a committer on the Apache Storm project and have been >>>>>> using >>>>>> the >>>>> images you created and maintained for a while, in particular for >>>>> my >>>>> own >>>>> project StormCrawler. So a massive thank you for that, I am very >>>>> grateful >>>>> for your work! >>>>>> >>>>>> We've recently had a discussion about handling the Docker >>>>>> images >>>>>> within >>>>> the project. We could of course start from scratch but given that >>>>> you have >>>>> built them, I was wondering whether you would consider >>>>> contributing >>>>> them to >>>>> the project? >>>>>> >>>>>> Given that your files are under MIT, I assume it would also be >>>>>> an >>>>>> option >>>>> to copy them over to Storm along with the license. >>>>>> >>>>>> Looking forward to hearing your thoughts on this. >>>>>> >>>>>> Kind regards >>>>>> >>>>>> -- >>>>>> Julien Nioche >>>>>> Director >>>>>> >>>>>> >>>>>> digitalpebble.com >>>>> >>>>> >>> >> >
