It seems like there are two concerns around Weex, branding and independent community.
For branding part, I understand this is a serious issue, and it takes me months to solve this kinds of issues, like donating weex-loader[1], weex-cli [2] to ASF, upgrading POM meta [3], changing package name [4], etc.. Again, there are over 1 million pages of Weex in Google, I can't promosie all of them are fine(without branding issue). And due to the fact that Weex once belongs to a company, not ASF, there are some NPM/POM publishing records reflects that Weex once belongs to a commnay, and I can't undo or delete that history. But we shall fix the brand issues once we know it, maybe we could also write down a brand protection procedure. For independent community part, I think there are two issues need to solve, and two issues to make it clear. - Many committers were coming from the same company, though some of them (3 or 4, including some 2 PPMC members) have resigned from the commany. But still to many, I guess. - We used to ignore the difference between committers and PPMC members, that's reason why so many new committers and so less PPMC members. We are tyring to fix this issue by inviting all committers to Weex PMC during its graduaiton procedure. But we could fix it in another way, if its' needed. - Though there are 13 committers according to the initial proposal [5], but many of them are not committers today. Even me, listed as an inital commiter of Weex, but actually joined Weex community 4 months aftter its into the incubator. Just take the committers on the initial proposal as an inacurrate records, there are some mistakes on this list. Actually, if you considered fact that Weex Joined the Incubator in Dec, 2016, there are 4 committer account created at that time [6]. So I guess the four of them are actually the inital committers(or PPMC members), rest of them are not (including me). - There are developers out of the comany make their own tools around Weex, and try to donate it to Weex. Currently, we're trying to encourage them to go through the IP clearance procedure and then nominate them as committer [7]. I guess this is some kinds of proof for independency, or diverse and active community at least. [1] https://incubator.apache.org/ip-clearance/weex_loader.html [2] https://incubator.apache.org/ip-clearance/weex_cli.html [3] https://bintray.com/weex/Android/sdk [4] https://weex.apache.org/download/major_change.html#_0-28 [5] https://lists.apache.org/thread.html/b53537fea384f1d75c9921f71e13d17780381504cff971e5f18bda96@%3Cgeneral.incubator.apache.org%3E [6] https://whimsy.apache.org/roster/ppmc/weex [7] https://mail-archives.apache.org/mod_mbox/weex-dev/201910.mbox/%3Ctencent_EA5069E21326C37D64F20CC18D885B3BAE05%40qq.com%3E Best Regards, YorkShen 申远 Justin Mclean <jus...@classsoftware.com> 于2019年10月29日周二 下午4:04写道： > Hi, > > If the project can show they are acting independently of a single company > that would help them convince the board/IPMC they can graduate. What has > the project done to attract developers out side of that company to work on > the project? > > Are there any barriers that hinders outside involvement? e.g. off list or > internal communication or having synchronous meetings can be an issue. (I > don’t know this is happening on this project. These are just suggestions to > the type of things that might hinder outside involvement.) > > Of the committers voted in during incubation, do all work for the same > company? Could any be considered as candidates for PPMC membership? > > Thanks, > Justin > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
