Project Maintenance Discussion

[azerupi]

Since last year, due to other projects, interests and scholar obligations, I have less and less time to maintain this project. I initially started this project to familiar myself with Rust and I think I achieved that goal. I now have different interests where I want to invest some time in. Therefore, I don't have the bandwidth anymore to maintain this project. In the last months, a lot of people have shown interest in this project and have contributed. I appreciate that a lot! But at this point, I feel like I can't devote enough time to review issues and PRs within a time frame that I still consider to be respectful to the persons that contribute.

I don't want to block progress and leave contributors hanging, so I think it is time that I pass over the role of main maintainer to one or more interested persons.

@steveklabnik @budziq @frewsxcv @Michael-F-Bryan

[steveklabnik]

Thank you for making this, and putting in all this work over such a long period of time! <3

I'm happy to at least help, but can't devote a ton of time; mostly working on stuff that's relevant to the features we use for the books in the rust distribution.

Given that we do use this internally, I wonder what the libs team would think about moving it to the nursery.

[Michael-F-Bryan]

Thanks for everything you've done so far @azerupi! This has turned out to be a massively useful project and even now I use it all the time for documentation or writing up little guides on the side :)

I'm happy to put my hand up as a maintainer. Although it may also be a good idea to have two or three core maintainers to help share the load and increase the bus factor a bit.

[budziq]

Thanks for this awesome project and all the help you have given the community!
Recently I'm finding myself with little free time to work on my Open Source commitments so taking on full maintainership here might be detrimental to the project 😞. But I'll try to help out some more especially in the areas relevant to rust-cookbook.

I second Steve on puling the repo to rust-lang-nursery, this is a very important project for the rust community which makes writing high quality and consistent guides a breeze. Moving mdBook there would get more eyes and hands working on the project.

[Michael-F-Bryan]

@steveklabnik, do you know what would be required to move mdbook to the nursery?

[budziq]

do you know what would be required to move mdbook to the nursery?

From purely technical point. @azerupi Will have to initiate the transfer to rust-lang-nursery account and one of the org members will have to accept.

From the logistics point of view I'm guessing that Steve will discuss the issue with libs team if they are interested in accepting the ownership.

[steveklabnik]

Yes, that's correct. I actually even have permissions over there, IIRC, so it's really just the social bit. I'm travelling right now so it's a bit complicated for me, but should be able to find out in the next week or so.

…

On Thu, Nov 9, 2017 at 10:16 AM, Michał Budzyński ***@***.***> wrote: do you know what would be required to move mdbook to the nursery? From purely technical point. @azerupi <https://github.com/azerupi> Will have to initiate the transfer to rust-lang-nursery account and one of the org members will have to accept. From the logistics point of view I'm guessing that Steve will discuss the issue with libs team if they are interested in accepting the ownership. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <https://github.com/azerupi/mdBook/issues/482#issuecomment-343185968>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABsiiPd1i_7MyXeJ7dfee7PfLpgyt9Mks5s0xdngaJpZM4QTZVQ> .

[azerupi]

Given that we do use this internally, I wonder what the libs team would think about moving it to the nursery.

That would be awesome, I would be honored. :)
When you have more information about that, let me know so that I transfer the repository. In the mean time, @Michael-F-Bryan I will add you as a maintainer!

[Michael-F-Bryan]

In the mean time, @Michael-F-Bryan I will add you as a maintainer!

Awesome! In the meantime I've got a couple hours to kill so I might start doing a couple code reviews. I'm in the same boat as @budziq though in that I'm more of a systems-level programmer than a front-end dev.

[steveklabnik]

I've gotten the green light to transfer it; feel free to initiate whenever you have time, @azerupi !

Basically, it will be similar to rustdoc: committers to mdbook will be "tool peers" under the devtools/doc team. :)

[Michael-F-Bryan]

Basically, it will be similar to rustdoc: committers to mdbook will be "tool peers" under the devtools/doc team. :)

Just out of curiosity, what is a "tool peer"?

[steveklabnik]

It's something slightly less than "team member", that is, you're a team member for that tool rather than for the team as a whole. It's jargon specific to the dev-tools team.

[budziq]

Basically you retain the collaborator/commit rights to the repo

[Michael-F-Bryan]

you're a team member for that tool rather than for the team as a whole

Sounds good to me 👍

I guess the big question is... How will this affect the project from an organisational/logistical standpoint?

As it stands I really like what this project does and have a couple core features I'd like to see incorporated in some day (e.g. alternate backends and plugins), so I'm more than happy to keep helping out.