I received security coverage opt-in permission before and would like to own and maintain this module/workspace which currently has no working code yet. There is only an initial commit with an info file and a composer file.
I'm already the maintainer of the Module "Kanban" and currently working on the "kanban style board" logic technically based on HTMX: #1989546: Drag and Drop. I just created a proof of concept and like to move on with a good namespace for boards with drag and drop cards functionality. It seems that the old maintainer had the same intention when claiming the namespace at first. My Kanban module will still focus on additional kanban logic and I already think about additional modules based on this board for timeslots in a table or dashboards.
This is part of the official process How to become project owner, maintainer, or co-maintainer.
Link to project page: board
Comments
Comment #2
c-logemannComment #3
c-logemannComment #4
c-logemannI just used the contact form of the current owner/matainer.
Comment #5
c-logemannComment #6
c-logemannComment #7
avpadernosierkje last logged in more than five years ago. I made c-logemann maintainer.
Comment #8
avpadernoThe intention seems to use the namespace for a different project; probably the request should have been to take over the namespace. (Since the repository does not contain any project, any committed project would be a different project.)
Comment #10
c-logemann@avpaderno I believe it's the the same intention. But because there is no code only the old owner can tell. So take over namespace would have been the better way. But I thought I applied to become the new owner especially because the current didn't log in a long time. But now I can start working on code which is the most important part.
Comment #11
avpadernoI apologize: In to own and maintain, i read just maintain. I made you the new project owner.
Since sierkje has been inactive on drupal.org for more than five years, I did not have to contact him before appointing a new project owner, in the same way I did not have to contact him to appoint a new maintainer.
Comment #12
c-logemann@avpaderno An apology of you is not really needed but full accepted by me. There are so many similar issues especially in this issue queue where it's easy to miss something. Thanks for your work on drupal.org.