Skip to content
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

📢 This repo has been transfered to hexojs organization #49

Closed
wzpan opened this issue Jan 18, 2023 · 8 comments
Closed

📢 This repo has been transfered to hexojs organization #49

wzpan opened this issue Jan 18, 2023 · 8 comments

Comments

@wzpan
Copy link
Member

wzpan commented Jan 18, 2023

Dear all,

It's obvious that I haven't maintained this repo for quite a long time, thanks to the help of @Ritsuka314 as a better contributor.

I think a better way to keep this plugin alive is to devote it to the hexojs community.

So I did it. 😄

@wzpan wzpan changed the title :octocat: this repo has been transfered to hexojs organization 📢 :octocat: this repo has been transfered to hexojs organization Jan 18, 2023
@wzpan wzpan changed the title 📢 :octocat: this repo has been transfered to hexojs organization 📢 This repo has been transfered to hexojs organization Jan 18, 2023
@yoshinorin
Copy link
Member

Honestly, we (the current active maintainers) are very busy and cannot maintain additional plugins. Actually, we archived some packages (not sure but maybe almost 10 packages) within the past year. Personally, I want to drop more plugins from the hexojs org.

Especially, this plugin doesn't have any test code. We can't understand correct behavior. Therefore, there is a high probability that it cannot be maintained.

@yoshinorin yoshinorin pinned this issue Apr 5, 2023
@yoshinorin
Copy link
Member

cc: @hexojs/core

@yoshinorin
Copy link
Member

cc: @wzpan @Ritsuka314

@wzpan
Copy link
Member Author

wzpan commented Apr 7, 2023

Well, I don't think the current active maintainers should watch all the plugins. That's why there is a sub team named "Plugins" and why I was invited as one of the member of it. Isn't it? :)
Currently no test inside the repo - for sure. It's a good idea to have some. Maybe we should add it later? @Ritsuka314

@yoshinorin
Copy link
Member

@wzpan

Well, I don't think the current active maintainers should watch all the plugins. That's why there is a sub team named "Plugins" and why I was invited as one of the member of it. Isn't it? :)

As far as I know all of the Plugin team members are inactive from at least end of 2018. I joined hexojs orgs in Oct 2018. I have not seen any activity from this team. Also Theme team.

So, actually the Core team maintaining most of the plugins and themes.

It's a good idea to have some. Maybe we should add it later? @Ritsuka314

Anyway I will send invitation to @Ritsuka314 if needed.

@Ritsuka314 Ritsuka314 unpinned this issue May 9, 2023
@Ritsuka314
Copy link
Collaborator

I am still (very occationally) maintaining the plugin. It is mostly functional; most of the issues are related to pandoc itself rather than to the plugin. That is because all the plugin does is pass arguments and post contents to pandoc.

There is however an ongoing issue that we may need to re-develop the argument interface #54.

I don't think this plugin need any test, really.

@Ritsuka314
Copy link
Collaborator

Good news: I've put some tests for this plugin!

@wzpan
Copy link
Member Author

wzpan commented May 11, 2023

I don't think this plugin need any test, really.

I agree. Even my hexo-generator-search has no tests at all.

But till now it still works well.

@uiolee uiolee pinned this issue Apr 18, 2024
@uiolee uiolee closed this as completed Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants