weex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From 申远 <shenyua...@gmail.com>
Subject [ANNOUNCEMENT] The minute of Weex offline meetup - May 27, 2019
Date Mon, 27 May 2019 11:54:43 GMT
Attendances

The following PPMCs were present:

   - York Shen
   - Shihan Zheng

The following committers were present:

   - Hanks Zhang
   - Ling He
   - Peihan Chen
   - Qianyuan Wang
   - Yayun Dong

Minute of Weex MeetUp
Potential violation of ASF copyright or trademark
As it's discussed before, the following github repositories may violate the
trademark or copyright of ASF:

   - https://github.com/weexteam
   - https://github.com/weex-plugins

The copyright of above repositories is unclear, as most of the code is
developed by Alibaba employees with laptops/desktops, which are also
Alibaba asset. It's uncertain the copyright of above repositories belongs
to Alibaba or individuals. To make things easier, *@YorkShen* shall apply
the admin privilege and renaming the repos to "xxx for Apache Weex", like
what happened in Apache dubbo [1] .

Besides, Weex playground [2] may also violate the copyright of ASF, the
release of Weex playground would be hold permanently until the copyright
problem [3] is clear.

Inactive committers
It's unhealthy state that most committers are busysing coding and only a
few of them participate in the community. To get more committers
involved, *@Qianyuan
Wang *volunteer to be the release manager next time (e.g. Weex 0.25) after
the following issues are solved [4] :

   - *@YorkShen *is responsible for writing the document of weex release
   procedure
   - *@Yayun Dong* would solve License issue. (files under
   *weex_core/Source/include/JavaScriptCore* and
   *weex_core/Source/include/wtf*)

It's estimated that *@Qianyuan Wang *would start release weex 0.25 in the
early of next week.

Make development process transparent
The transparence of Weex development process is in low level, users
sometimes complains that they are unclear of weex roadmap and don't know
when a certain feature will release. In order to make things
more transparent, committers participated in this meetup agreed that every
PR, issue that they write or solve, shall be related to a certain Github
milestones [5] (like Weex 0.24, Weex 0.25), and Weex Release should be
based on Github milestones.

Processing Github Issue and PR
The number of unsolved github issue/PR [6] is not a small number,
committers would review and solved the issues on weekly base. In order to
save time for the committers and community*, issues that don't follow the
template will be closed and won't get response until the they are in right
format* [7]. Weex encourages developers submit issue in English, but not
enforced.

Next meetup
The time of next offline meetup is not clear but shall be scheduled two
weeks later, with email notification in this mailing list.

[1]
https://lists.apache.org/thread.html/dd36fa6c4ae4c1962be6c6a1235507eaa8c5c3ae009281e7cfdb2522@%3Cgeneral.incubator.apache.org%3E
[2] https://itunes.apple.com/cn/app/weex-playground/id1130862662
[3]
https://lists.apache.org/thread.html/6a08422bc28743e132ae23e002bf5713eb464447a9ef35236dd1b957@%3Cdev.weex.apache.org%3E
[4] https://github.com/apache/incubator-weex/issues/2482
[5] https://github.com/apache/incubator-weex/milestones
[6] https://github.com/apache/incubator-weex/issues
[7]
https://github.com/apache/incubator-weex/issues/new?assignees=&labels=Bug&template=bug-report.md&title=%5BAndroid%5D%5BiOS%5D%5BDev-tool%5D+Unexpected+behavior+when+xx+where+weex+version+is+0.aa.bb.cc

Best Regards,
YorkShen

申远

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message