On Thu, Jun 5, 2014 at 3:16 PM, Alex Harui <aha...@adobe.com> wrote: > I know that requiring Jude to use patches will slow things down, but right > now his work isn't happening at Apache so it isn't clear we can/should use > that in considering committership for him, and also, all of his work is > not granted to Apache so really, you can't land your changes back in the > Apache repo without having Jude file an ICLA and/or Software Grant. > > I think we could argue that a commit hook would put his work "in" the > open, but I'm still concerned about the legal issues around his work. > > Having Jude sign an ICLA with ASF is probably the easiest approach.
Jude, will that work? Thanks, Om > -Alex > > On 6/5/14 2:56 PM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote: > > >On Thu, Jun 5, 2014 at 2:48 PM, Harbs <harbs.li...@gmail.com> wrote: > > > >> Well, I’m open to suggestions. I could invite other folks to the > >> repository to see what we’re doing. I could also make it public. I could > >> also port the code over to the main Apache git repository. > >> > >> I’m kind of hesitant to do the last option right now, because I can’t > >> really afford the time it would take me to do that right now… It’s > >>going to > >> be quite a bit of work merging the code back. > >> > >> > >You could do one of these based on your preference: > > > >1. In your github project, add comm...@flex.apache.org as your > >post-commit > >email hook. This way, we can all take a look at the progress of the > >feature. We can keep track of Jude's contribution directly as well. When > >the feature is complete, just copy over the code to the Apache Flex git > >repo. > > > >2. Create a new branch in our own git and continue to check in stuff > >there. You might have to keep getting patches from Jude and keep > >committing them with appropriate comments. > > > >3. Fork your current project into a whiteboard project on ApacheFlex > >github repo. Jude can in turn fork the whiteboard project and send your > >pull requests as needed. I can hook it up to send commit emails to > >comm...@flex.apache.org. (I think this is the most straightforward and > >best option) > > > >Thanks, > >Om > > > > > > > >> On Jun 6, 2014, at 12:19 AM, Alex Harui <aha...@adobe.com> wrote: > >> > >> > IMO, it would have been better to have Jude work via JIRA for a bit > >>so we > >> > could see his work and collaboration in the open which would have > >> probably > >> > resulted in him being voted in as a committer. > >> > > >> > And, of course, it isn't too late to start doing that. > >> > > >> > -Alex > >> > > >> > On 6/5/14 2:02 PM, "Harbs" <harbs.li...@gmail.com> wrote: > >> > > >> >> BTW, ³very active² is 59 commits since March 26. (I was working on it > >> >> myself before that.) > >> >> > >> >> On Jun 5, 2014, at 11:58 PM, Harbs <harbs.li...@gmail.com> wrote: > >> >> > >> >>> FWIW, Jude and I have both been very active on the TLF table > >>support. > >> >>> > >> >>> We¹ve been working on a private Github repository because Jude is > >>not a > >> >>> committer and things are still quite unstable. > >> >>> > >> >>> Current status is as follows: > >> >>> * Tables render with cell strokes and backgrounds > >> >>> * Selections of cell content and cell ranges work. > >> >>> * Editing of cell content and surrounding text works > >> >>> * Tables recompose as needed when cell content changes. > >> >>> > >> >>> We¹ve radically changed the way table and sub elements are handled. > >> >>> * Columns and rows are not normal children. They are informational > >> only. > >> >>> * Content within cells belong to a separate TextFlow. > >> >>> * We¹ve introduced the concept of nested TextFlows and > >> >>> SelectionManagers/EditManagers which are nested within each other. > >> >>> Control is passed between parent and child SelectionManagers as > >>needed. > >> >>> * We¹ve introduced table blocks used for composition in a similar > >> >>> manner to how TextFlowLines are used. > >> >>> * The logic used for composition and selection is much more > >> >>> understandable than what was originally written. > >> >>> > >> >>> Work still needed: > >> >>> * Lots of little rendering issues need to be resolved. > >> >>> * Some normalization logic still needs to be implemented. > >> >>> * Cell range selection needs to be improved. > >> >>> * Text selection which spans tables needs work. > >> >>> * Table editing operations still need to be done. > >> >>> * Work still needs to be done relating to header and footer cells > >> >>> * There¹s probably bugs related to cells which span rows/columns. > >> >>> * Lots of tests need to be created. > >> >>> * Markup import needs work. > >> >>> > >> >>> That¹s about it. > >> >>> > >> >>> I¹m guessing it¹ll be in shape where we can think about merging it > >>back > >> >>> into the develop branch in a couple of weeks. > >> >>> > >> >>> Harbs > >> >>> > >> >>> On Jun 5, 2014, at 5:35 PM, Alex Harui <aha...@adobe.com> wrote: > >> >>> > >> >>>> > >> >>>> > >> >>>> On 6/5/14 5:00 AM, "Justin Mclean" <jus...@classsoftware.com> > >>wrote: > >> >>>> > >> >>>>> Hi, > >> >>>>> > >> >>>>>> In the past three months we've continued to see: > >> >>>>>> - Continued JIRA activity (more bugs raised than resolved > >>however) > >> >>>>> Yep - we need more user and committers active here in helping to > >>fix > >> >>>>> bugs. > >> >>>>> > >> >>>>>> - More committers becoming active again. > >> >>>>> Looks steady to me: > >> >>>>> http://www.ohloh.net/p/ApacheFlex/contributors/summary > >> >>>> Hmm. It felt like we saw more activity like Fred on FDB, Chris on > >> >>>> Maven > >> >>>> and contributions from Nick and MikeL. I'm tempted to leave it in. > >> >>>> > >> >>>>> > >> >>>>>> - Fewer new folks contributing and eventually becoming > >>committers. > >> >>>>> IMO (from mail list sign ups and installs that we have increased > >>user > >> >>>>> activity but we don't seem to be good at encouraging them to > >> >>>>> contribute > >> >>>>> more than JIRA reports. There's been a few exceptions ie we've > >>just > >> >>>>> had > >> >>>>> some help with the Android skins. > >> >>>> Are you suggestion that we not say this in the report? > >> >>>> > >> >>>> -Alex > >> >>>> > >> >>> > >> >> > >> > > >> > >> > >
