brillout / awesome-vue-refactor Goto Github PK

referencing this vuejs/awesome-vue#1001 (comment)

One of my vue.js libs that has 30+ stars (not a big deal surely) is marked as "vue-audio ★9 too specific" - what do you mean? ppl use it so why not?

My question is - what's the problem with this one? Why it was removed?
The only misguidance I saw is missing a CONTRUBITING section - is that such a big of a deal for some random lib to be excluded? doesnt's the default path work - fork and create a PR ... this looks like a bureaucracy a bit to me if that's the problem.

I've checked further for the label "too specific" and saw some other libs doing some other types of improvements/UI. it looks pretty strange to me that someone states that some lib is too specific in open source. if you didn't deal with some area why you'd make this statement?

I updated the readme of my project: added the required Vue verion and removed the Chinese description.

As described the the Clean Process ticket we split & assign the reviewing into chunks;

• Learning Material (including Podcasts, Tutorials, Examples, Talks) unassigned
• Development Tools & Syntax Highlighting & Snippets assigned to @brillout
• Component Collections assgined to @brillout
• Routing assgined to @brillout
• Ajax/Data assgined to @brillout
• State Management & Event Management assgined to @brillout
• Validation assgined to @brillout
• UI Components assgined to @brillout
• i18n assigned to @brillout
• Analytics & Advertising & Autocomplete assgined to @brillout
• Boilerplates & Scaffolding assigned to @brillout
• Integrations assgined to @brillout
• General Plugins/Directives assigned to @brillout
• SEO & typescript assgined to @brillout
• Projects Using Vue.js assigned to @Ffloriel

@brillout Great thanks for your hard work. I am the author of vue-fullstack. I have push a commit to update the readme which contains vue version description and update the github topics.

E.g. https://github.com/airyland/vux doesn't have any English documentation.

On one hand English docs can be seen as a quality requirement and on the other hand it is useful for the people speaking the language of the doc to be able to discover the library.

Reviewing one library entry could be done as following.

Replace the description of the entry in the markdown with good or rejection reason e.g. no v2 for libraries that don't have a v2 compatible version.
E.g. I've started with the Component Collections section: https://github.com/brillout/awesome-vue#component-collections.

If not rejected, add the enty to https://github.com/brillout/awesome-vue/blob/master/README_CLEANED.md using the format - [npm-package-name](https://github.com/org/repo). (After we processed all entries I will use a script I wrote for devarchy to automatically add the GitHub description to all entries)

You are being pinged because you have at least one resource listed under the Awesome Vue list.

As per vuejs/awesome-vue#836 we have reviewed the list and created a new one; brillout/awesome-vue/README_CLEANED.md.

We removed many resources. Removal reasons can be found at brillout/awesome-vue/README.md. If you have addressed the removal reason of your resource then please create a new issue at brillout/awesome-vue.

Projects using Vue.js have been reviewed by @Ffloriel and I reviewed all components & libraries.

I tried my best but I am sure that I did many mistakes. Let us know if you catch such mistake or if you disagree with a decision. (By creating a new issue at brillout/awesome-vue.)

Also, many libraries are missing a note to state what Vue version is supported. Be sure that your library includes such note. Ideally right a the beginning of the readme text. (A badge or a GitHub tag can be easily overseen.)

I've not included libraries that have no English documentation as stated in https://github.com/brillout/awesome-vue/issues/5.

ping

@10quality @AStaroverov @Akryum @Alex-Fun @alextoudic @AlexandreBonaventure @Angarsk8 @Astray-git @atinux @BirdEggegg @BosNaufal @bubblings @CYBAI @CaiYiLiang @ChangJoo-Park @codefalling @Coffcer @CroudSupport @DanielZhu @David-Desmaisons @ElemeFE @F-loat @FE-Driver @FranckFreiburger @FranzSkuffka @GeoffZhu @Ginhing @Gomah @Grottolabs @GuillaumeLeclerc @Haixing-Hu @HerringtonDarkholme @JALBAA @jack85 @JackGit @JosephusPaye @Justineo @Kashio @KoRiGaN @kocisov @KyleRoss @LancerComet @MMF-FE @Ma63d @MacArthurJustin @MarkPieszak @martywallace @Mati365 @MatteoGabriele @MattyRad @Memkits @MetinSeylan @Metnew @MiCottOn @MillerRen @Monine @MopTym @MovingToHTTPS @N3-components @NeutroniumCore @NewDadaFE @NightCatSama @OYsun @OnsenUI @PeachScript @PeakTai @PetervMeijgaard @Plortinus @Polyconseil @QingWei-Li @Radyushin @RashadSaleh @RobinCK @Roeefl @SSENSE @ScreamZ @SevenOutman @SidKwok @SimulatedGREG @SkewedAspect @Socketize @Sopamo @SortableJS @TIGERB @TahaSh @Teddy-Zhu @Treri @Twiknight @Vanthink-UED @VueCluster @Vuedeux @Vuedo @Wanderxx @XeonPowder @XingzheFE @ZeroDark1991 @Zhangdroid @aarondfrancis @abdullah @airbnb @airyland @akifo @alidcastano @andylei18 @antongorodezkiy @apertureless @appcomponents @approach0 @arexio @arvidkahl @asika32764 @astralapp @atwxp @aweber1 @ayamflow @bbonnin @bkzl @blue0728 @bootstrap-vue @bpierre @bradstewart @brandonjpierce @brianvoe @bstavroulakis @budiadiono @buhrmi @c01nd01r @calebroseland @caolinjian @ceolter @cezardasilva @charliekassel @cheapsteak @chenz24 @cklmercer @cngu @codecasts @coderdiaz @compmeist @crossjs @cs1707 @cucygh @dalphyx @dangvanthanh @danielschmitz @danmademe @dargue3 @darrynten @davidmoshal @dealloc @declandewet @delay @devfake @dgerber @didierfranc @dkfbasel @doodlewind @drewjbartlett @dwightjack @ealves-pt @ecerroni @echoVic @eddyerburgh @eduardostuart @egoist @eliep @eljefedelrodeodeljefe @erguotou520 @ericmcdaniel @fancellu @fenivana @fergaldoyle @filipemeneses @firework @fishenal @forehalo @formly-js @foxbenjaminfox @freearhey @fritx @fundon @galenyuan @gismall @gluons @gocanto @greyby @groupwrite-io @gurghet @gustaYo @hal0gen @happilymarrieddad @happyDemon @haydenbbickerton @hchstera @heatherbooker @hedefalk @helpbase @hilongjw @hjeti @holic @huanleguang @iFgR @iatsiuk @icebob @ihanyang @ilyashubin @imcvampire @inca @irwansyahwii @italomaia @itsFrank @iview @jade-press @javisperez @jbaysolutions @jcc @jfelsinger @jiakeqi @jiangjiu @jinzhe @joearcher @joseluisq @jrainlau @julesbou @kaorun343 @karol-f @kartsims @katik @kazupon @kevinongko @kewah @kfei @kikyous @klummy @knpwrs @ktquez @ktsn @kylestlb @lajosbencz @lakb248 @laoshu133 @leaves4j @legeneek @leonardovilarinho @lian-yue @lithiumjake @liujians @lmk123 @locoslab @logaretm @lokyoung @loujiayu @lsycxyj @ludo237 @luojilab @madskristensen @mahmoudmy @marcosmoura @mark-hahn @matfish2 @matiastucci @matt-sanders @mbouclas @metricloop @mgyongyosi @mhayes @miaolz123 @mint- @mint-ui @misterGF @mlyknown @moip @monterail @moonou @mrgodhani @mtorromeo @mul14 @museui @mustardamus @myronliu347 @mysticatea @nblackburn @neposoft @nguyenvanduocit @nicolasbeauvais @niksmr @njleonzhang @nolimits4web @noru @nuxt @octref @okoala @oldj @pagekit @palerdot @pandao @partyka95 @paulpflug @pepf @petervmeijgaard @phanan @phoenixwong @phphe @pinguinjkeke @pluto1114 @pmsaue0 @postalservice14 @posva @pramjeet @processing @qazbnm456 @quasarframework @qxl1231 @rafaelpimpa @rahulgaba16 @rajabishek @rascada @ratiw @rawcreative @rayfranco @reinerBa @revue @rhyzx @ridermansb @rigor789 @robinvdvleuten @rodzzlessa24 @rokups @ropbla9 @rpkilby @rstoenescu @sabrinaluo @sagalbot @saivarunk @saman @samcrosoft @samiheikki @samturrell @sandeepk01 @sant123 @santiblanko @sapjax @scaccogatto @scottbedard @scriptPilot @se-panfilov @sebastian-software @sejr @semisleep @shakee93 @shershen08 @shhdgit @shinygang @shiye515 @simplesmiler @sinchang @sjerrys @skyrpex @staskjs @steven5538 @storyblok @suguangwen @sunabozu @super-dev @superlloyd @superman66 @superwf @surfbirdapp @surmon-china @surveyjs @syropian @taoeffect @termosa @text-mask @the6thm0nth @thelinuxlich @theomessin @thetutlage @tyllo @typicode @uniquezhuo @vace @varHarrie @viko16 @villeristi @vmaimone @vue-bulma @vue-comps @vue-play @vue-typed @vuedev-com @vuejs-br @vuetifyjs @vuets @vuikit @wangdahoo @waynecz @weavingbird @websemantics @weibangtuo @weifeiyue @weilao @weinot @weizhenye @wlada @wovue @wyzant-dev @xanf @xiaokaike @xiaoluoboding @xlsdg @xpepermint @xrado @yang-wei @ycwalker @ye-will @yetaai @yjj5855 @yodfz @yujiahaol68 @zerostatic @zhangxin840 @zhouzhuojie @zllovesuki @znck @zurb @zxdong262

This section has in my opinion two purposes.

• To showcase what we can build with vue.js.
• For the Open Source section, to give the possibility for developers to contribute and be a part of a opensource project using their knowledge of vue.

That means that the repository should have some of the same restriction as the libraries. It is preferable that the documentation is in English, the project is active and maintained. The link provided should be a link to the github repository. If the project is finished, no need for any contribution, then it should be in the app/website section.

There is still a question about how to select the app/website. Should we remove the websites considered too simple, like this one with only 1 vue component?

http-vue-loader is marked as "readme doesn't say how it works" but http-vue-loader has an "How it works" section : https://github.com/FranckFreiburger/http-vue-loader#how-it-works

Place one of these in your readme up the top to display which version of Vue.js your library supports...

Please edit it in the format

https://img.shields.io/badge/vue- {version number} -green.svg

Examples

https://img.shields.io/badge/vue-2+-green.svg
https://img.shields.io/badge/vue-2.2.4-green.svg

I've not included libraries that have no English documentation. One reason is that I can't review documentation in a language I don't understand. But also because English is the de facto open source language and it's a good habit to try to always write in English in the context of programming.

Maybe we could create a separate Awesome Vue list for every other language.

As the list is in a cleanup / review state, I would like to propose, to remove the stars / stargazers.

1. Most other awesome list also does not have stargazers
2. IMO there are more downsides
3. Includes a rating which does not represent the quality of the package
4. Gets outdated quickly

I think someone started including stargazers to the list and the rest just kept doing it too. (Me included) However imo there are more downsides to this.

Most people will submit their packages pretty early with a low stargazers count. After some time they may have way more stargazers but the list does not update.

Which leads to the second point, that stargazers mostly introduce a rating of the package. More stargazers = more people liking the package = better package. However this is not true. So packages which are older and submitted with more stargazers, will mostly get more attention.

By removing the stars, we make all packages equal.

/discuss ☕

@brillout I have revise vue-data-tables according to our discuss in #6

would you please add vue-data-tables back to the list?