NexT v6.0.0 [Reloaded]

[ivan-nginx]

Hi guys!

NexT repository is moving here: https://github.com/theme-next and my maintenance will resume there in accordiance with this PR. It's include all from v5.1.4, rebase to v6.0.0 + have some small fixes & and some cool features like cache. Documentation is not totally ready yet, but domen "theme-next.org" already registered and i'll try to do my best.

I'll also try to do rebase as smooth as possible. So, don't worry about any hard breaking changes or anything else.

Any contributing and help will appreciate! Collobrators also needed. @iissnan @geekrainy @huiwang @Acris @uchuhimo @flashlab @Haocen @changyuheng @Doublemine @NoahDragon @AlynxZhou @jjandxa @shenzekun @xCss @LEAFERx @aimingoo @maple3142 and all wich i don't remember — Welcome!

And any questions or suggestions — ivan.nginx@gmail.com.

And happy NY!

[Raincal]

Happy New Year!

[geekrainy]

Good job! 😄🎉🎉

[at2008]

Happy New Year!

[ivan-nginx]

Thank's dudes.

@iissnan i know u make some contributing in Dec last year, can u please explain why u totally ignore NexT theme repo and my messages about it? I see u create a game but what about NexT? U not interesting in this anymore? This is static, static — is future. See, was pull on firebase db, so, we can save anything there, for example. Please, make some advantage to this all, especially u can. U a good coder, isn't it? Top 25 as i see at my life. Really. Soon in ~2025 only machines will anywhere. Machines and static blogs. With external databases. Kidding, yeah. But. Who knows? I think need to do all of u can because we have 1 life. Life it's not commit. U can't do revert to your life at previous commit, but u can always merge. And all logs will write, like on github. So, no need to live by past; need, i think, see in future and do what like, and especially, what u can. Please, make some respond. At least explain what's going on with you. Howbeit, happy NY, dude!

[LEAFERx]

HAPPY NEW YEAR!!

[huiwang]

lol, @ivan-nginx your message to @iissnan seems like you are selling a dream to him. 👍 👍 👍

[ivan-nginx]

@huiwang hi and HNY. I don't selling anything, i just don't understand why Vi don't answer to me. Maybe i was some hard in any commits/pulls or something else. I talk to him in April last year and all was fine. But a little time later hi's just dissapear, ok. But, now i see him commits and he's still ignore all of this. I don't understand, why? Just take a message. Just give some answer, that's all. I don't understand.

[huiwang]

@ivan-nginx do you have an email or something to chat more efficiently than github?

[ivan-nginx]

@huiwang yep, gitter and ivan.nginx@gmail.com (profile on github). More contacts on my site, but i not always here. Best is e-mail.

[aixiu]

@ivan-nginx Maybe he's got something, maybe he's forgotten, but you're an excellent engineer, too.thank you

[ivan-nginx]

@aixiu thank's, but i'm simple advance man. Russian man. Maybe a have some knowledge, but wich have iissnan — it's crazy. I see on servant branch about year ago and was wondering and in my head was questing only: how?

[aixiu]

@ivan-nginx If @iissnan has never been able to connect, I hope you can resist the hexo-theme-next banner, and the themes that so many people use can't disappear in this way.

[ivan-nginx]

@aixiu iissnan is creator of this repo. What are u talking about?)

[AlynxZhou]

First happy new year to you all, and I am also confusing about where @iissnan go ... And I don't if there is a live chat group for example Telegram group or maybe people here prefer to gitter? And if anyone here have more contact to @iissnan ? I think maybe something happened to him and he is so busy that he has no time about this theme.

[ivan-nginx]

@AlynxZhou the main trouble was in what i don't have the full rights in this repo. For example, @geekrainy suggest to me give him rights to merge, but i can't do this because i just Collobrator, not admin. And some other 3rd-party things to connect to this repo required admin confirmation too. If he's was busy, he's can just give me admin right's and repo was growing up next. But.. he's just keep silent.

[Haocen]

@ivan-nginx the beauty of open source project is you can free to fork, right? I believe it would be fine if he come back later and archive the repo instead without transferring ownership.

I lost all my own personal repos once when one of my GitHub account was turned into an organization account.

GitHub have rather weird permission control system and in most cases people grow tired of messing with it.

[AlynxZhou]

@ivan-nginx Maybe he just lost all tools helping him connect to GitHub/Gmail 233333 because we are in China :-P

[ivan-nginx]

OK, if that, i have E-Mail: ivan.nginx@gmail.com — he know my e-mail, he just can to write me something, anything, ok? Trying to explain situation and we will decide without any problems.

And how then he was make commits in Dec if he lost Github account?

It's very strange situation. I don't understand it totally, for real.

P.S. It's like when a girl dropped you but not explain why, u know? Similar situation, but with NexT theme. He's just droped he's own theme. Why?

[AlynxZhou]

emmmm Just a guess, I am obviously wrong, his ZhiHu account seems not updated for a long time too... Let me try to send him message in ZhiHu...

[Haocen]

I cannot say for others, but I have robots making commits on my behalf.

I suggest we leave him a message and move on in case he comes back later.

[ivan-nginx]

I cannot say for others, but I have robots making commits on my behalf.

@Haocen bots make a games too?

[Haocen]

My point is these commits could have being synced by some sort of CI or any other automation, without him logging into GitHub.

At the end of the day, if he prefers not to make any change to the current repo, it is his privilege to keep it as is.

[ivan-nginx]

@Haocen this repo still will be worked, i think. No need to cutting-out something in 5.1.x versions. I think there are still many peoples who just will use version 5 because at most cases all worked fine.

But for frequent users maybe will need updates / features / support / docs wich will be totally implemented in new repo.

[ivan-nginx]

without him logging into GitHub

Gitter:

Slack:

And i repeat: i'll be glad if at least he explain all this situation. Just — why?

[Haocen]

I don't honestly know.

I personally suggest we gently honor his privilege to remain silence.

[jcf94]

Oh, god ... I didn't realized that you @ivan-nginx and @iissnan are two different persons until just now !!!

No wonder I found that the maintainer of this theme is of different style.

[ivan-nginx]

@jcf94 what!? I'm from Russia, dude. Theme NexT was started maintain in 2014. It's really, really was maded from scratch (unlike other themes, like Material). In 2014 i don't know what is Hexo. Then, i install this theme at the begininng of 2016. Just install, no maintain. And do first pull in Aug 2016. If i'm was Vi, i don't do pulls to himself, lol.

---

maintainer of this theme is of different style

Initial style was Chinese. For now u see Russian style. :smiley: But both styles have cool harmony, that's why i want to @iissnan back.

[jcf94]

Haha, yeah, I get it now. Thanks very much for your work. Happy new year~ ^_^

And I think it's a good way to re-base the theme repo.

[ghost]

Happy New Year!😀

[Neveryu]

@ivan-nginx hello,dude,this is my first time use english my english is poor i know Russia is very cold so i'm very curious that In this very cold environment how to coding? your hand not felling cold ?

[ivan-nginx]

your hand not felling cold

And not only hand. :smile:

If u talking about location, so, u right, in China is a lot warmer then in our places. But, there is no too cold then u thinking. For example, now i can open my window and stay without shirt, and of cource my arms never been numb. Much more important that your legs always stay in warm; if legs will be in warm, any of part of your body will in normal vital temperature.

But when your head stay in some cold temperature, this is a little better to thinking because it's like cooler which cools your CPU in your PC, same here. Sometimes when hot a lot (in summer, for example), it's very hard to do anything because u stay like in bathhouse and your arms sweat everytime. Of course in this conditions any coding or gaming a little harder, then when u feel a little cold.

[ehlxr]

@ivan-nginx good jobs, thx for your contribution. hope @iissnan will be back. we really like this theme

[vinnyxiong]

@ivan-nginx Although I do not know why @iissnan gave up maintaining this Theme. But thank you for your contribution. We are waiting for Vi to come back. We really like this theme.

I am from China and I communicate with Russian programmers for the first time.

Happy New Year! 😄

[ruanyandong]

NexT theme can not show dynamic background

[ruanyandong]

how to solve

[ivan-nginx]

@ruanyandong NexT is rebased into organization repo. If you want new feature, fix, or support, create new in NexT v6.x repo (desirable in English).

There is instructions on English or Chinese how to update from v5.1.x to v 6.x

You also may read this for details.

[thyeun]

@ivan-nginx, this issue 5.1.0使用algolia搜索问题 #1084 are nothing related to upgrade to 6.xxx, it is related algolia issue on dependencies, but since you already locked that issue, than i will consider that you been given a solid solution/support to the user

And for open source projects, pls don't ever lock the issue even that it is solve, due to that some others ppls can provided better solution. hope you understand that. thanks!

p/s : @Innote is my another account too.

[ivan-nginx]

@thyeun thank's for reply in EN language!

I understand what this issue (#1084) may be not releated to NexT v6.x, but there are some things here:

1. This repo is no supported anymore. All maintenance from the begining of 2018 year resumed in new NexT repo with version 6. Actually, this repo must be archived or moved in Organization; but i still have no any response from @iissnan and i haven't admin privilegies for this repo.
2. In new repo exists some Algolia documentation and also was issues / fixes about Algolia. So, for now mb #1084 issue already fixed or maybe not. And if not, u can create same issue in new repo which have maintenance for now.
3. I just can't to lock everything in once, but as i say in this PR > «I'll also try to do rebase as smooth as possible.» — so, i do it possible as i can.

And for open source projects, pls don't ever lock the issue even that it is solve, due to that some others ppls can provided better solution.

I understand what it is not best decision to lock issues. But there are no possible solutions without admin right to do rebase NexT and resume maintenance for it's beautiful theme. > hope you understand that. thanks!

[thyeun]

@ivan-nginx, not i'm having any issue, just i can't given a solution/contribute for the user that need help.

let me explain further details on algolia issue, @iissnan been provided a solution for algolia, but some of the user still prefer using old version of NexT, and users still prefer minor change to make algolia work instead of doing too many changing (the fix provided by @iissnan ), and that is why users still prefer a small fix for the issue (that provided by me). it is why that #1084 always active even it been close.

for @iissnan not response to you, i might possible to help you up too, since i have been communication with @iissnan a few times.

i understand why you lock the issue, but not many users understanding your difficulties, if users can't getting a solution and they might think that NexT community/contributor are ignore them, than i think you know what happen next.

if you need malay or chinese for communicate with users that need it, i can help you up also, because NexT are not only for EN users, it been widely use by others language users too.

[ivan-nginx]

and that is why users still prefer a small fix for the issue (that provided by me)

So, why u can't to provide small fixes/solutions in new repo for this issue? And what's your suggestions?

[thyeun]

@ivan-nginx, review back my comment, @iissnan already provided in new version of NexT (not 6.xxx) or read back #1084 .

Give you an example User "A" using 5.1.0, and the solution provided by @iissnan are on version 5.1.4. And user "A" did not want to upgrade to 5.1.4 but user "A" need only a minor change to fix/make algolia to work. And that is why i did not make a new repo.

Even i make a new repo, it will be like a strange version 5.1.0.1, i dont think @iissnan will prefer that kind of version too, just to fix a minor change. And even i make a version 5.1.0.1, will you think that ppls will upgrade to 5.1.0.1, or just add a "path" to make thing work?

And keep in mind, i'm not a "true" contributor assign by @iissnan, i only provided solution on some particular issue and this is how open source project go on.

p/s : how @iissnan want to merge or create new version to fix each issue, it is depend on @iissnan, i just a user that provided a solution to another user that need it. How users want it, it depend on him/her (upgrade or just small change). i can't force people to do things.

Lastly, @iissnan always provided EN and chinese solution to users, if you want to kill all chinese users here, than it is up to you, i just a user, and i'm not racism (the way you doing now are just lock all chinese issue, are you racism?).

[ivan-nginx]

Lastly, @iissnan always provided EN and chinese solution to users, if you want to kill all chinese users here, than it is up to you, i just a user, and i'm not racism (the way you doing now are just lock all chinese issue, are you racism?).

Oh, no! Why u can do like this? I almost try to produce docs in EN/CN/RU (and other) languages and u can see it in new repo. And international language — is English language. In Github — EN language, not RU, not CN. All peoples from all world use English lang for understand each other. In this case u can say what «Github — racism», but we all know what this is not true. I already understand what not all Chenese users understand English language, and we can try to solve it, create discussion about this, for example. How it may be, documentation for Chinese users which don't know EN language, no problem. But if in this case u can say about «racism», then i also can say about «Chinese language propaganda». I'm not to try isolate or do propoganda on any language, my native language is Russian and as u can see, i trying to use International language (English), which always by default in global internet (and by default in Hexo too, BTW).

So, i still not see your possible suggestions. U want to resume maintenance in this repo and split NexT on 2 pieces, right? NexT EN and NexT CN versions? We can resume this discussion in any messanger if u want.

[thyeun]

@ivan-nginx, NexT EN also can let user to having CN here, why need only use EN? you can using RU here too, no peoples said that you need only EN here, if you can speak JP here, go ahead and use it here, there will be people from the contributor/users will provided you a solution in JP too. Even you, yourself can using RU here, i'm sure there will be users that can provided you RU solution too. so no matter the project are EN or not, everyone are free to use his/her language in github. you understand or not?

but the way you doing now are locking all CN issue, locking mean that you are not allow users to use CN here, it is rude and prove you are racism. Ask yourself it is right by doing that?

[ivan-nginx]

@thyeun

but the way you doing now are locking all CN issue

No, it's not true. I do smooth rebase from old to new repo and will lock issues no matter in which language they are.

locking mean that you are not allow users to use CN here

Not true, again. Locking mean i can only lock to produce rebase NexT to new place. Users must know what old NexT not support anymore and all new features (and bugfixes too) now in new repo. And if user want, he can recreate issue in any language he's want, i don't lock any CN issues in new repo, u can see it right now.

it is rude and prove you are racism

It's can only prove what you liar and there are some libel laws about this. I'm several times told to you about smooth rebase from old to new repo, but you still trying to prove me false. Again: anyone can recreate issue from old to new repo, that's why i'm lock issues in old repo (and no matter in which language they are).

Ask yourself it is right by doing that?

I'm asking yourself about year ago: why @iissnan not response on any messages and/or don't want to resume NexT maintenance. It was good reason to move NexT repo with ~10k stars and many opened issues, but it's still impossible because a have no admin rights in old NexT repo.

---

you understand or not?

I don't understand a little thing: who are you and what you do for NexT? I can't see your profile in NexT contributors list and seems like you do nothing for NexT (as for old and for new repo). For now i only see what you try to provocate me and seems like it's does not work.

---

Again: if you have any constructive solutions for better rebase NexT from old to new repo, i'm will be glad to start discussion about it.

[thyeun]

@ivan-nginx,

• to do rebase old to new repo, no need to lock. you can do branching.
• i already mention i'm not a contributor. i just provided particular solution.
• the liar here is you, i only see all CN issue been locking.

[ivan-nginx]

i already mention i'm not a contributor. i just provided particular solution.

Ok, i'm sorry, i just not find you in contributors list and not remember your strong activity here (at least in new repo).

the liar here is you, i only see all CN issue been locking.

You see only locking CN issues because there are 90% issues in CN. It's not mean i lock only CN issues, i lock:

1. Old issues with possible fixes with same issues in new repo
2. Issues, for which i get e-mail message if any new coment was added in this issue.

You told «i only see all CN issue been locking», but i see — there are still opened issues in CN and EN languages.

So, i do smooth rebase from old repo to new by trying to move this issues (if they still actual, of course, anyone can recreate they in new repo).

to do rebase old to new repo, no need to lock. you can do branching

What branching u mean? I don't und here. Can u explain some more? Mb i don't know some github features. For now i think rebase can succesfully do by lock issue and comment about new NexT repo. So, if issue still actual, anyone can create same (or similar) issue in new repo with future support for this. In our case, i think u can create same issue in CN language and resume your «particular solution» there. I just see what that our discussion was started from Algolia bugs, so, u can try to check this bug in new repo and if it still exists, recreate same or similar issue in new repo.

---

I understand what for some reasons you don't want use new version 6 but want use old version 5. And you can also trying to understand: old version is not supported anymore. Support it's mean:

1. No new features
2. No bugfixes
3. No new issues and no docs/solutions on old bugs which already may be fixed in new repo

Anyone can use old NexT repo (in which i was strong collobrator and was solve all possible issues i can), but old repo sounds like deprecated with no support and maintenance. It's like nodeJS: anyone can use old 0.XX version, version 3 and version 4, but for now minimal node version — 6.

[thyeun]

@ivan-nginx, sure i'm not as active as you are, because my particular solution seldom having issue, once there is no users facing issue, i won't be trigger.

branching here mean, let said the latest version is 5.1.4, than u create 5.1.4.1, and put all the old repo into it, and create a new repo 6.XXXX. so that old repo still remain the old issue, but once users make a new comment on old issue, than you can put a label with "solve in 6.xxx" and state the link changing in PR, so everyone will understand "this issue will be solve on version 6.xxx".

i dont care version 6 or 5 or 4 or 3, i only care provided solution to users. once users happy, i will feel happy.

question is how many users will care about new features/new repo? instead that old issue are still remain there? Not many users prefer to do new huge upgrade instead that they prefer to solve issue in a minor way/small change.

An example You using version 5.1.0, and you having "XYZ issue", but the newer version is 6.0.0, and the "XYZ issue" still remain, how is your feeling? will you care about the version or you care about the old issue?

case one if there are no support on old repo, you should fork this repo out, and create your own, so that user can have new features and etc from your fork. (in this case, you can do what ever you want, and you can remove what ever features you like so that the new repo on your fork will be as clean as always).

case two if you make a new repo, and you can't provided a solution for the old issue, what is the thinking from users? for me, i will think like this "WTH, old issue still not solve it, but a new repo already out", will you think users will continue using NexT EN version 6.0.0 or they will remain 5.1.4?

case three you solve all the old issue in your new repo, than i'm sure everyone will happy to move to your so call version 6.xxx. if you can't, the same way of thinking will be same like case two. And in this case, it will become more worse, because you are forcing people to recreate a same old issue in your new repo, will you like to doing that again?

Lastly, for me everyone that in this project that submit/report an issue, provided a solution or catching a bug, they actually are the contributor too. And this is how open source projects doing in github.

[ivan-nginx]

branching here mean, let said the latest version is 5.1.4, than u create 5.1.4.1, and put all the old repo into it, and create a new repo 6.XXXX.

I don't think it's good idea to create any new branches in this old repo. And i can't to put old repo (old versions, e.g. 5.1.4-5.1.0) because a have not admin rights to move old repo into new repo. Anyway, i don't see any strong reasons to force use 5.1.0 version (what u use) instead of 6.0.0 version, more lightweight (cutted out unnecessary 3rd-party libs).

so that old repo still remain the old issue, but once users make a new comment on old issue, than you can put a label with "solve in 6.xxx" and state the link changing in PR, so everyone will understand "this issue will be solve on version 6.xxx".

Yep, i was do like that several times. Maybe u don't see that.

i dont care version 6 or 5 or 4 or 3, i only care provided solution to users. once users happy, i will feel happy.

Exactly! And when user not understand in what version was fixed that or another bug and where that or another solution was provided, he will switch to new repo from old and vice versa. If solution/fix/issue will in one place (in new repo), user will not care about search issue, search separated commit, merge it or manually edit. He just install latest v6 and all troubles are gone. If old or new bug will appear and then will fixed in new repo, he may just update he's v6 with git and that's all. He will be very happy about he's minimum time spending.

question is how many users will care about new features/new repo? instead that old issue are still remain there?

Alright, this is actually good question. As i see u talking about features / bugfixes balance. U now say something about: new features added faster then old bugfixes, right? So, here is counter question on it: why some users do bugfixes only for theyself and not add it into centralized repo, not share this bugfix? I see it many times, but most people don't care. They just take current version (what they see on current moment) and do some own modifications in that version. And of course, if user not want to add this mods in centralized repo, he can't update this repo too. Same here: u trying to fix your 5.1.0 modded unsupported version, but not want to share this bugfix in new repo, am i right?

Not many users prefer to do new huge upgrade instead that they prefer to solve issue in a minor way/small change.

Not many users prefer to do

IDK from what stats u get this results, but not need to speak for all people. Most people prefer update for latest versions and many OS projects strongly recommended their users have latest versions (e.g. nodeJS, see above).

new huge upgrade

New repo smaller than old. I know it because i do rebase from 5 to 6.

instead that they prefer to solve issue in a minor way/small change.

Here is what i'm talking above: no need to think for all people. MB most people preffer just do minimal clicks and want just their NexT will work fast and stable. Version 5 is not so fast and not so small than version 6. And i don't think what simple user want to use:

• Larger NexT version 5 (instead of smaller 6)
• Slower NexT version 5 (instead of faster 6)

Here is changes between latest v5.1.4 and v6.0.0. U talking about «huge upgrade», but it's not true, again:

As a result whole size of repo (without git directory) decreased from ~3.9MB to ~1.6MB.

I know what in Chinese internet speed not so fast, so, i thinking about decrease repo size with cutting-out 3rd-party libs (thank's @geekrainy for get idea). BTW, in other countries (in our country, Russia, too) providers have more internet speed. So, for me no matter 4mb or 1.5mb — it's just 1 second downloading. It's mean i did it not for myself, but for people.

---

An example You using version 5.1.0, and you having "XYZ issue", but the newer version is 6.0.0, and the "XYZ issue" still remain, how is your feeling? will you care about the version or you care about the old issue?

how is your feeling

First of all, it's single and rare case. There are many issues with simple questions which already can be solved without code modifing. Actually, need to improve docs for around issues like this.

Feeling is bad if this issue still not appear in new repo (all people must jump from new repo to old and see there, when jump back again) Feeling is good if issue moved from old to new repo (all people see all issues in 1 place, no need to run from one repo to another)

will you care about the version or you care about the old issue?

Agree. As i say before: maybe we must to set something like bigger priority for bugfixes and lower for new features. Any good and constructive suggestions are welcome!

case one if there are no support on old repo, you should fork this repo out, and create your own, so that user can have new features and etc from your fork. (in this case, you can do what ever you want, and you can remove what ever features you like so that the new repo on your fork will be as clean as always).

if there are no support on old repo, you should fork this repo out, and create your own, so that user can have new features and etc from your fork

No. If there are not support for abandoned repo (with no my fault), which repo i was support and i in top contributors list, i think i can decide by myself — what i should and what not should. U can't told me about rules like that because u do nothing for NexT, instead of me. I just make rebase for repository with my work into new place and resume my work there. Who will fork he's own work just for rebase repo? Sounds like «— Ok, dude, you made it and spend a lot of time for it, but you can't have it, it's not yours and you not admin here, sorry and thank's for your work!».

case two if you make a new repo, and you can't provided a solution for the old issue, what is the thinking from users? for me, i will think like this "WTH, old issue still not solve it, but a new repo already out", will you think users will continue using NexT EN version 6.0.0 or they will remain 5.1.4?

i will think like this "WTH, old issue still not solve it, but a new repo already out", will you think users will continue using NexT EN version 6.0.0 or they will remain 5.1.4?

1. And i will think "ok, some bugs here in old version.. hm... WOW! That's mb because unsupported, here is label, what!? MB i need to update to v6 and this bugs will be solved?" So, different dudes have different thinking. No need to talk for all dudes.
2. That's i'm talknig about, need to do rebase. We can try to move all issues to new repo and close/lock all this duplicate issues in this, old repo. If your issue with Algolia not solved in new repo, welcome to recreate this issue! And i still don't understand: is it solved or not?

case three you solve all the old issue in your new repo, than i'm sure everyone will happy to move to your so call version 6.xxx. if you can't, the same way of thinking will be same like case two. And in this case, it will become more worse, because you are forcing people to recreate a same old issue in your new repo, will you like to doing that again?

As i right understand, your suggestion is: «— I think you must solve all issues in old repo before you can rebase it. You can't to lock any issues before you (or anyone else) will not solve it». So, yeah, here we back to case 2 and my answer under the second item:

2. That's i'm talknig about, need to do rebase. We can try to move all issues to new repo and close/lock all this duplicate issues in this, old repo. If your issue with Algolia not solved in new repo, welcome to recreate this issue! And i still don't understand: is it solved or not?

But here is 1 thing: as you can see and i say many times, need to do it very smoothly. Yes, i can to close/lock all issues for few hours, but i don't do that. And as i say in my previous answer: at most, old (stale/closed) issues may be locked. Your #1084 issue was created 28 Aug 2016 and was closed by iissnan on 17 Feb 2017. For now 7 may 2018 and issue like this likely not actual for now. So, i think what lock this issue — it's not catastrophe — and again — you can recreate it in new repo if this issue still exists in new repo.

Lastly, for me everyone that in this project that submit/report an issue, provided a solution or catching a bug, they actually are the contributor too. And this is how open source projects doing in github.

for me everyone that in this project that submit/report an issue, provided a solution or catching a bug, they actually are the contributor too

Not quite and not always. If it do like that, github add a badge or something like this for that. And actually, in some cases most people want to solve their own troubles/issues. They don't care for created by him issue; don't care about will this issue help somebody in future or not; don't care about will understand he's language the dude who can quickly solve his issue or will understand other people he's language in which issue will created. He just want one thing: he's problem must be solved, that's all. And here, BTW, we backing to question with «racism» which actually not like that, here is some examples:

1. User create issue in CN (or other) language. This language in most cases understand only Chinese guys, all other guys not understand it and google sometimes give wrong translate. When issue solved and will be decision in CN language — only Chinese users can understand this decision, this guide to solve this issue. So, same issue (solved or not) useful only for CN users. For all other users it's issue have no weight and useless.
2. And concept «racism» — it's when you do something like propogande single, not international language. It can be DE, FR, IT, RU, CN or any other language, but it can't be EN language, which may be (or not be) called «Internationalism». And as anybody can see, i don't do propogande my native language, because i don't want only Russian users can understand issues/docs and other similar things in NexT theme. English language always was and will international, and i don't want to try isolate NexT in single CN or RU or any other language; default is English, whether you like it or not.

And lastly, i'm will very glad for new contributors/members/reporters, anyone who want to do NexT better. And that's i'm talking about: OS must have 1 place, no need to try to separate it with 2 repo's. And there are some Chinese guys in new repo already collaborators/members/authors and if i was «racist» (as u say before), there was only Russian (or similar) guys or something like that, but it's not like that. Please, no need to make mountains out of molehills mixed with your own imagination. Thank's!

---

P.S. See, we spend a lot of time here with this discussion, but we can simply made something useful, something important for NexT. Mb you can do some docs in CN with FAQ on issues/bugs on 5 or 6 version in WIKI, for example. But not, instead of this we both sitting here and trying to say «i'm true and you are not right». Only time have weight in our live and i'm trying to merge both repos for economy of all our time.

[thyeun]

@ivan-nginx this is not an imagination, #1084 already is the example, after @iissnan created the new version to solve the algolia issue, but as you can see, after @iissnan posted the new version there, you still can see how many people/user (i'm not using users because you keep on misunderstanding it) not prefer to using/upgrade the new version that created by @iissnan .

you are totally wrong, not don't want to submit the bugfix by created a new repo, it is because @iissnan want a solid solution than only merge it with the latest version (if you don't know what happen here, pls dont assume you are right). And the solution i provided on #1084 , it is only a temporary solution, but it make algolia work. And i just take it as an example to show it to you. User (one dude for you, since you don't understand) are prefer small fix.

small fix/solution meaning here is temporary fix/solution, (everything need to said it so details, you are totally dont get the meaning i'm trying to explain to you)

fix/solution meaning here is fix or solution.

And don't ever split my comments one by one, it will have a different meaning, and because you are doing that, you misunderstanding the total meaning.

And i given you "an example", do you understand the meaning of an example? hahaha...you really lighten my day!

haiz, i make the case one - three just for you to understanding the clear picture, but end of the day, you more confusing, hahahaha, i given up on you.

enjoy what ever you like to do, since NexT is no more under @iissnan lead, i will also stop to make argument with you.

Peace out!!!!!

[ivan-nginx]

Seems here a little but misunderstanding: u want to say, what that (1cd5570) fix, provided by Vi, needed to rollback?

I'm sorry, i'm just don't understand what you guys write there, i think it fix for Algolia, but it's not like that?

Can u please not write so many things and write a little: in what trouble with Algolia? Because i'm already confised too.

---

Ok, i opened issue, seems need to fix this or something.