Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

[Meta] Maintaining the project #563

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

Closed
TLouf opened this issue Apr 22, 2021 · 2 comments
Closed

[Meta] Maintaining the project #563

TLouf opened this issue Apr 22, 2021 · 2 comments
Labels
documentation Changes to documentation only (e.g., README, Guide, Wiki Pages, etc.)
Milestone

Comments

@TLouf
Copy link

TLouf commented Apr 22, 2021

Hi,

First I'd like to thank everyone who contributed so far to @academicpages (and especially @staeiou for initiating it) which has certainly, as it has for me, saved a lot of time for researchers around the world who try to publicise their work. However, despite its popularity, proven by the frequency of issue opening or the sheer number of forks, no commit has been made since more than two years ago. It seems that @staeiou is the only collaborator able to merge PRs on the repo, and it is normal that with time, one ends up contributing less time to such a project for all sorts of reasons. Hence the current situation. Naturally then, new collaborators should come in to keep it alive. I have no idea how new collaborators could be selected, and it is up to @staeiou I guess, but there are many small things one can do with minimal experience.

#545 for instance is a trivial PR to merge, and there are more. Most issues can be answered and closed extremely simply by anyone who made their own page. I personally have ideas I've implemented on my personal page for which I could write PRs, but with no hope of a merge these kinds of initiatives are killed in the egg. So whether it is implementing new ideas or even changes made upstream in Minimal Mistakes (like the search), there are a lot of things that could be done, and, I'm sure, the people willing to contribute. I myself have no legitimacy in this regard because I'm no web developer, but I'd be glad to help!

Cheers!

@armack
Copy link

armack commented May 2, 2021

I very much agree with this, as it seems there are several little issues/annoyances that people have been fixing for a couple of years which are sitting as pull requests. There's also possibility to port in changes from Minimal Mistakes as it continues to have active development and some of those changes could possibly be useful.

I do want to point out though, that the change in #545 would seemingly break multi-author support on the publications page. And while that would be fine for probably 99.9+% of people using the theme, it seems silly to break an existing feature when there's an equally trivial copy/paste that fixes it without breaking anything which I just requested in #566.

@rjzupkoii rjzupkoii added the documentation Changes to documentation only (e.g., README, Guide, Wiki Pages, etc.) label Feb 14, 2024
@rjzupkoii rjzupkoii pinned this issue Feb 14, 2024
@rjzupkoii
Copy link
Collaborator

@staeiou has stepped back from active maintenance of the project and has handed things off to me. I'll be working the next couple days to clear out the backlog and setup a process for pull requests. In the meantime, please reach out if you might also be interested in helping to maintain the project!

@rjzupkoii rjzupkoii modified the milestones: 2024 Refresh, Documentation Feb 15, 2024
@academicpages academicpages locked and limited conversation to collaborators Mar 12, 2024
@rjzupkoii rjzupkoii converted this issue into discussion #1982 Mar 12, 2024
@rjzupkoii rjzupkoii unpinned this issue Mar 12, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
documentation Changes to documentation only (e.g., README, Guide, Wiki Pages, etc.)
Projects
None yet
Development

No branches or pull requests

4 participants
@rjzupkoii @TLouf @armack and others