-
Notifications
You must be signed in to change notification settings - Fork 7.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
reactivex.github.io needs a new administrator #6932
Comments
Can you explain a bit more? |
See also ReactiveX/reactivex.github.io#398 |
@DavidMGross do you need help with that yet? |
@DavidMGross Yes, I need help. |
Would you still need a hand on maintaining the website? It hasn't received any care in about 3 years. @akarnokd |
It would be great but the task is not for drive-by contributors. It needs knowledge of that build system, probably a Mac/Linux computer and dedication. Probably the best would be to recreate the site in plain HTML directly so no need for any special infrastructure. |
I built the site successfully on my Windows machine, and I have good experience with SSGs, primarily Zola, so I should be able to handle this task. I can try my best to keep it up to date, which should be better than it not being maintained for 3 years.
This might be a more long-term task given the site's complexity that I can try, and I am open to further discussion on this. |
Alright, let's see. I've merged a couple of trivial PRs. Could you build the site and post a PR against the master branch? |
Okay, figured out most of the infrastructure so I'll be able to maintain reactivex.github.io Already merged and deployed most outstanding PRs. |
Okay then, glad to help if anything pops up or if you change your mind on your willingness to maintain the website. I might also create some PRs if I see anything incomplete/wrong. |
I'm no longer able to devote time to maintaining the reactivex.github.io site and its associated ReactiveX repo. There are some outstanding PRs that need review/merging, but in general there hasn't been a whole lot of activity there over the past months, so this is probably not a particularly demanding position.
The text was updated successfully, but these errors were encountered: