+1, It will be much more convenient to communicate among developers. 2017-11-24 17:58 GMT+08:00 陈泽峰 <chenzef...@ymt360.com>:
> I think it's good for Weex Community to open github issues.It's a easy way > for Weex users to discuss features or report a bug. > Only thing I worry about is the language issue.Too many github issues > were committed and replied in chinese, and it seems not got controled in > the old Weex github project.Will it be a problem that may stop Weex go > farther in Apache? > > > Anyway,I still say yes to github issues. > > > > > > > > > > ------------------ Original ------------------ > From: "Hanks Zhang"<zhanghan...@gmail.com>; > Date: Fri, Nov 24, 2017 04:33 PM > To: "Weex问题列表"<dev@weex.incubator.apache.org>; > > Subject: Re: Community building? > > > Hi Raphael, > > Sorry for reminding you again. I really want to be informed about the > process of opening GitHub issues. > > Looking forward to further discussion. > > Best regards, Hanks > > 2017-11-10 13:06 GMT+08:00 Adam Feng <cxfe...@gmail.com>: > > > +1, We can give it a try, for Github issues are easier to manage. > > > > Thanks. > > Adam Feng > > > > On 24 Oct 2017, 1:29 PM +0800, Raphael Bircher <rbircherapa...@gmail.com > >, > > wrote: > > > Hi all > > > > > > First of all, thanks for the work. We at Apache tend to do not a vote > on > > > such a Topic. This one is a typical case for lazy consensus. > > > > > > We let this thread now open and allow a discussion. It gives us the > > chance > > > to make a good proposal even better. You have not this chance if you > > vote, > > > you can only say yes or no. That's the reason we normally avoid voting > > (if > > > possible) > > > > > > Sometimes you have no discussion on a proposal, this means for as: "all > > > are happy". Often people who are happy with the proposal simply give a > > +1, > > > to show the support. > > > > > > If a discussion starts, we discuss it out and try to rich consensus > > within > > > the community. Normally this goes much quicker then anyone expect. If > the > > > discussion is settle down. the proposal is accepted. > > > > > > I will answer to the other points in a separate mail > > > > > > Regards, Raphael > > > > > > Am .10.2017, 06:39 Uhr, schrieb Hanks Zhang <zhanghan...@gmail.com>: > > > > > > > Hi, Raphael > > > > > > > > As far as I know, our workflow is adjusted, documents are reorganized > > and > > > > assigned to the specific person to rewritten them. We all take part > in > > > > it. > > > > After all the documents are ready we'll deploy the new website to the > > > > server. > > > > > > > > 1. The "contribution" related documents [1] are finished and being > > > > reviewed. > > > > 2. The "<image>" component document is treated as the template, > > > > its structure and details are under adjusting. > > > > 3. The tutorial document [2] is on the halfway. > > > > > > > > There is another thing we are discussing: whether to use GitHub to > > manage > > > > issues. > > > > > > > > I think is more convenient to use GitHub issue if we have permissions > > to > > > > manage them, such as close, assign, add labels, etc. We can also use > a > > > > bot > > > > to close or fast reply issues, in order to keep the quality and > remove > > > > redundancy. > > > > > > > > Should we start a vote on this question? > > > > > > > > [1] https://github.com/apache/incubator-weex-site/pull/2 > > > > [2] > > > > https://github.com/apache/incubator-weex-site/blob/ > > master/source/guide/index.md > > > > > > > > > > > > 2017-10-24 11:50 GMT+08:00 Raphael Bircher <rbircherapa...@gmail.com > >: > > > > > > > > > Hi everybody > > > > > > > > > > Can someone bring me update about the community building efforts at > > the > > > > > weex project? Thanks a load! > > > > > > > > > > Regards Raphael > > > > > > > > > > -- > > > > > My introduction https://youtu.be/Ln4vly5sxYU > > > > > > > > > > > > > > -- > > > My introduction https://youtu.be/Ln4vly5sxYU > > >
