incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Konstantin Boudnik <>
Subject Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
Date Wed, 22 Jul 2015 23:16:48 GMT
After a quick walk through the master log I see that a bunch of the
questionable commits are resulted from the dev. branches histories not being
properly squashed before the feature is merged into the master.

This is something that mentors have asked to address before and, in fact, the
community is making changes as we speak

specifically under 'git workflow'. Arguably, squashing is a matter of taste
and I would refrain from pushing the community one way or another, although I
surely don't like non-squashed histories like that.

Development process is actually documented on the wiki and is followed by the
community. I don't see why it is looks closed or off-list, really. Any new
contributor can start picking up things using these tools. In fact, they do -
the community has new committers and active users that have no problems
figuring out how to contribute into the project (according to the dev@ and
user@ lists). Does it answer your concerns, Ted?


On Wed, Jul 22, 2015 at 11:07PM, Daniel Gruno wrote:
> On 07/22/2015 09:23 PM, Julian Hyde wrote:
> > I reviewed Ignite’s commit log and email lists. I got the impression of a
> > split personality: The dev list[1] is very open and clearly following the
> > Apache Way. Meanwhile, the commit log[2] is (to my eyes at least)
> > difficult to decipher.
> > 
> > In the commit log, messages such as "Merge remote-tracking branch
> > 'origin/master’” and "# master minor”, "GG-10559 - Improvements.” are
> > typical. Very few descriptive comments or references to IGNITE-xxx cases
> > that could provide further explanation. Those are indications to me that
> > development is been driven by off-list meetings.
> > 
> > If the Ignite committers want to build a diverse community of developers,
> > I think they need to make their commits more transparent to match the
> > excellent transparency they have achieved on their mailing list.
> > 
> > Julian
> > 
> > [1]
> > [2]
> >  
> > 
> The GG-10559 commit log (along with the 'oops' email sent to dev by
> mistake today) seems to indicate (this is just speculation, I would love
> for someone to answer whether this is the case) that commits are being
> based off an internal JIRA instance (or other bug tracking system) not
> hosted at the ASF.
> Furthermore, I have found that there are 207 JIRA tickets with NO
> description, discussion or useful information other than ownership
> changing hands and then suddenly the tickets have been resolved with no
> explanation, suggesting that either people have not been properly taught
> about how to share information and collaborate as a community, or the
> actual discussions and 'ping-pong' happen elsewhere, outside our view.
> I naturally hope there is no reason for concern, and I would love to get
> some insight into why these things pop into view when you examine the
> development process.
> With regards,
> Daniel.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message