search

AOSC-Archive / website-site-ng

Next-gen Community Portal
https://aosc.io/
6 stars 14 forks source link

TODO #41

Open liushuyu opened 7 years ago

liushuyu commented 7 years ago

This is a list of what we need to do

Higher priority - 优先事项

Lower priority - 次要事项

Enhancement - 润色

liushuyu commented 7 years ago

[WIP] i18n basic support in #40

liushuyu commented 7 years ago

[WIP] Dependencies monitoring in #42

liushuyu commented 7 years ago

[WIP] Test framework in #43

LionNatsu commented 7 years ago

TODO: Error message pages. 4xx, 5xx etc.

liushuyu commented 7 years ago

@LionNatsu So mocha test is good to merge ?

LionNatsu commented 7 years ago

Would you like to give a description of Mocha to me in some brief sentences? I'm not very clearly understand the relationship between Travis-CI and Mocha, and the status about them in this project now due to my such long time have not been exposed to this. My apologies.

LionNatsu commented 7 years ago

And @axionl and I are now ready to redesign and/or refactor (I believe it will not be redesigned ab-initio) this. How do you think of the plan of CI/testing system (such as this issue)? Will you modify after redesigning?

liushuyu commented 7 years ago

Would you like to give a description of Mocha to me in some brief sentences? I'm not very clearly understand the relationship between Travis-CI and Mocha, and the status about them in this project now due to my such long time have not been exposed to this. My apologies.

There's no relationship between Travis-CI and Mocha. They're independent and I just happened to use them together. The Travis-CI is a service provides sandboxes/virtual machines/containers for developers to test their projects in real-time (ah, maybe not). And Mocha is just a multi-functional Javascript unit testing framework. And what I have done was I combined these two mechanisms together: each push event will trigger a Travis CI build, which will utilize the Mocha tests I've written and check for problems. The default action is to send emails to everyone who own this repository if test fails. My original hope was to ease the collaborators and just leave the simple test task to an alien machine (Travis CI Builder in this case).

And @axionl and I are now ready to redesign and/or refactor (I believe it will not be redesigned ab-initio) this. How do you think of the plan of CI/testing system (such as this issue)? Will you modify after redesigning?

I think a CI system is necessary -- unless you're 100% sure about your coding ;-) Of course some parts of the test will be modified to match your changes.

I hope I have answered your questions clearly. If any further questions, don't hesitate to leave a comment here.

LionNatsu commented 7 years ago

Oh, brilliant. Yes, of course, CI system is necessary and also unit tests are necessary. Thanks!

liushuyu commented 7 years ago

[WIP] Test framework in #43

Finished

[WIP] Dependencies monitoring in #42

Finished

liushuyu commented 7 years ago

RSS Feed / RSS 订阅

Finished in d3d4941c12c00a50eeb2e02bf7a16403e1f9c0d7

liushuyu commented 7 years ago

GitHub Webhook 对接

@MingcongBai so consider drop this one?

MingcongBai commented 7 years ago

Could use this for security advisories, but it may require more detailed security-related issues.

But for pakreqs we are moving to @gumblex 's packages site, which should be going online soon.