Skip to content

Move mdformat back into @hukkin's account #1238

Description

@choldgraf

@hukkin requested that we move the mdformat package back into his GitHub account, here's the request:

I'd really like to see this happen (given I keep dictatorship over mdformat (it can be less draining than shared governance)), or alternatively transfer mdformat (and any plugins you wish to give up) back to my account. It worries me a bit that there is no response here in almost 2 years.

Mdformat was transferred here mostly because years ago Chris S. happened to ask and I couldn't see much of a downside. Having it under the same organization as the parser it uses seemed reasonable. I was never well aware (still today am not 😄 ) of this organization's structure, funding, governance, product, values, or anything really, except for the fact that Chris S. had ported markdown-it under this org which was useful to me.

I feel today, for my maintenance, this organization is mostly a burden, setting false expectations of governance and processes. A few times I've noticed I don't have the permissions to do what I wanted. I often feel unsure about my rights to manage other repositories besides mdformat, even if I have the commit bit. Often having a clear single owner would've made things simpler.

@choldgraf's take

I think it makes sense to move the mdformat project back out into @hukkin's account. It wasn't created as part of the grant, and he's the original and current maintainer.

I suggest that @rowanc1 @jstac or @gregcaporaso chime in if they have any thoughts or objections. If not, then I'll plan to move the repository in a few days.

Suggestion

If there are no objections, then after Monday the 25th we'll move the following repositories to @hukkin 's account:

https://github.com/executablebooks/mdformat
https://github.com/executablebooks/mdformat-tables

@chrisjsewell if you prefer mdformat-tables to go under your account, just let me know and I can move them there instead. Otherwise @hukkin I'd ask that you respect Chris' wishes if he wants them moved under his account and communicates that to you later on. I think it's best for the mdformat project if all the extensions are in the same space if @hukkin is interested in maintaining them.

Will anything break?

Are there any considerations we need to take in doing the actual moving? E.g., things that might break?

To do

Activity

  1. hukkin commented on Nov 19, 2024

    @hukkin

    Thanks @choldgraf

    I'll also gladly take any direct or indirect dependencies of mdformat-gfm, which out of EBP owned mdformat plugins seems to be only mdformat-tables. But @chrisjsewell is the author so I think that's for him to decide.

    Regarding other EBP owned mdformat plugins, if there's someone to maintain them here (or elsewhere), that'd be great. If not (or I'm the expected maintainer), I'd rather have them transferred too.

  2. choldgraf commented on Nov 19, 2024

    @choldgraf
    MemberAuthor

    yeah for all the mdformat stuff I'm +1 on moving that to your (or some other) org

  3. hukkin commented on Nov 30, 2024

    @hukkin

    Friendly ping @choldgraf

    In case you transfer mdformat-tables to me too, please also do so on PyPI (my username is the same as here).

    I'd ask that you respect Chris' wishes if he wants them moved under his account and communicates that to you later on.

    Of course!

  4. choldgraf commented on Dec 1, 2024

    @choldgraf
    MemberAuthor

    I've moved mdformat to my account and initiated a transfer to @hukkin - can you accept? (apparently this is the only way to move an org repo like this).

    I've done the same for mdformat-tables but I need @hukkin to delete your fork first so that I can transfer.

    For PyPI it'll be a bit more time because I am temporarily locked out of my account. Perhaps @rowanc1 can do this part of the transfer if he has any cycles.

  5. hukkin commented on Dec 1, 2024

    @hukkin

    Thanks @choldgraf, I've accepted mdformat and removed mdformat-tables fork.

  6. chrisjsewell commented on Dec 1, 2024

    @chrisjsewell
    Member

    @chrisjsewell if you prefer mdformat-tables to go under your account

    yeh sure it's fine to go under @hukkin 's

    It would be nice if one day #841 could be addressed, as @hukkin notes, this organisation now a burden for any development

  7. KyleKing commented on Feb 2, 2025

    @KyleKing

    Hi, I'm adding a +1 to this issue. There is some work on mdformat-tables to support TOML configuration, which would be nice to release, but currently blocked by the transfer of the PyPi package (hukkin/mdformat-tables#31)

  8. choldgraf commented on Feb 2, 2025

    @choldgraf
    MemberAuthor

    I tried to do this a few weeks ago, and was blocked on these three issues that are linked together:

    Apologies that this is moving slowly but I have very little bandwidth to think about this right now. Things are pretty hectic in the USA open source world so it will likely be this way for the foreseeable future.

  9. hukkin commented on Sep 11, 2025

    @hukkin

    Hi @choldgraf, I hope you're well!

    It seems you may now have access to the ebp-bot PyPI account (if I interpret this correctyl: pypi/support#5347 (comment)). Would you be able to transfer mdformat-tables to hukkin on PyPI?

  10. choldgraf commented on Sep 11, 2025

    @choldgraf
    MemberAuthor

    If I recall, I got bogged down trying to resolve this one:

    and ran out of time because I had to manually ask for access to the account, and it became more complex than I expected. So no I don't have access to ebp-bot yet. I can double check whenever I have a moment but am very bandwidth limited right now.

  11. hukkin commented on Sep 15, 2025

    @hukkin

    The message I linked to (from PyPI support) says

    I have updated the primary email address on the account.

    So it seems like the gmail account may no longer be relevant here.

    Thanks for helping out!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions