Jinjiang, it isn't working. And I am not pleased with the state. Since most (all?) of you work at the same place, put everyone in the same phone call and tell them that this needs to change.
EVERYONE; I expect that this mailing list contains; 1. Discussion of work in-progress. 2. Discussion of features to be implemented 3. Ideas on features. 4. Ideas and work on community development, i.e. how to attract non-Alibaba people to join the community. 5. Discussion on what is needed for releases. The absence of those items on this list, indicates that you are not understanding what it means to be an Apache project. Compare the dev@weex mailing list with any other, say dev@kylin (also China initiated project), and see the difference between a "github reflog" and a "community". Apache is NOT a source code repository. Apache is NOT a gang of GitHub accounts that work together. Apache is a COMMUNITY that survives if GitHub closes its operations tomorrow. We know the people in the community, we care and we sympathize with each other. In time, it becomes our larger family, people we see when we travel. End of the day, code is transient and not that important. If a piece of code dies, it is easily replaced. If the community dies, it is gone. Take a look at https://attic.apache.org. 40+ projects that are retired. Why? Codebase is as good as it was... but the COMMUNITY is dispersed, moved on and lost interest. That is the faith of Weex, if you continue on your path. In fact, Weex will not even make it to the Attic, as it will be an entry on retired podlings instead, together with another 50 or so projects that couldn't build a sustainable community; http://incubator.apache.org/projects/#retired I hate to think of my options if there is no improvement, but I will suggest the following to Infra if I have to; a. Disable GitHub Issues, b. Disable GitHub Pull Requests, c. Even Disable GitHub if a. and b. can't be done. Time to Listen and stop committing. Niclas On Mon, Mar 6, 2017 at 10:59 AM, Jinjiang Zhao <[email protected]> wrote: > Yes as you suspect, some of these PRs are from discussion in other ways > and some of them are from old pieces of work. 50% - 50% I think. But yes > it's not OK of course. > > Guys I have some suggestions: > * First we should put more old information here, just like what plan we > have made or how many issues we are doing with. > * Migrate old alibaba/weex issues to apache gradually. > * Stop replying new issues in alibaba/weex (at least at a appropriate time > if not from now on). > * Encourage Chinese users moving here MORE. > * Try to guide more users abroad go to Apache directly (through Twitter, > HackerNews ... I think). > * We should pay more attention here. > > Thanks. > > Jinjiang > > On Mar 03, 2017, at 06:29 PM, Niclas Hedhman <[email protected]> wrote: > > Gang, > I see a massive amount of work (well done) being done and pull requested > via GitHub. > > Are these old pieces of work that are pushed now, or is it new work? If the > latter, how does people know what to work on? > > Perhaps it is simply totally independent pieces, driven by personal > interest, BUT I SUSPECT that this is agreed upon at work, on some side > channel or otherwise. And that is NOT OK. > > Apache projects are expected to have discussions on features and fixes on > the mailing list. As the saying goes around here; "If it didn't happen on > the mailing list, it didn't happen!" > > Additionally, all communication in GitHub Pull Requests could disappear > tomorrow. The project's history would be gone as a result. No records of > anything, other than the commit messages. > > So, everyone, I know this is difficult, especially since most of you are > Chinese, probably with limited English fluency. But we need to get the > discussion going HERE... not at work, not on WeChat, not on Slack, not on > GitHub or any other medium... HERE. > > > Thanks for listening > -- > Niclas Hedhman, Software Developer > http://polygene.apache.org <http://zest.apache.org> - New Energy for Java > > -- Niclas Hedhman, Software Developer http://polygene.apache.org <http://zest.apache.org> - New Energy for Java
