+1 Upstream first . thanks to bring this . murat
On Wed, Aug 2, 2017 at 10:27 AM, Dhananjay Pavgi < dp00476...@techmahindra.com> wrote: > +1 on Upstream first. Some views on ONAP’s adoption in production > environments: > > > > 1. Regular Code Quality Analysis to be done. > > 2. Arrive at #TECHDEBT and have it tracked through Jira backlog > > 3. Every release plan MUST cover as to what % of #TECHDEBT would be > addressed in that release. > > 4. #TECHDEBT to be tracked for each component and entire platform > as such (imbibe Scrum of Scrum discipline) > > > > Afraid that we are too focused on functional aspects at the moment that > are tracked through Jira user stories and Sprint plans. However, we are > grossly ignoring #TECHDEBT. > > > > thanks & regards, > > Dhananjay Pavgi > > Mobile : +91 98220 22264 <+91%2098220%2022264> > > [image: cid:image002.png@01CE7323.F2727500] [image: > ONAP_logo_Sig] > > www.techmahindra.com Platinum Member. Visit : > http://www.onap.org > > > > *From:* onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-bounces@ > lists.onap.org] *On Behalf Of *Ed Warnicke > *Sent:* Wednesday, August 02, 2017 10:42 PM > *To:* Sauvageau, David <david.sauvag...@bell.ca> > *Cc:* onap-tsc@lists.onap.org > *Subject:* Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP > > > > +1 Upstream first is crucial. > > > > Happy to share sane strategies I've seen work in the past if folks are > interested. > > > > Ed > > > > On Wed, Aug 2, 2017 at 9:37 AM, Sauvageau, David <david.sauvag...@bell.ca> > wrote: > > Hi TSC members, > > > > I would like to bring to our attention one major opportunity for > improvement in the behaviour currently adopted by some of our community > members. > > > > I am observing a big number of very large commits (10’s of thousands of > lines of code in a single commit) which to me is a symptom of us not > working well as a community yet. In order to be successful, I believe > communities need to adopt an “Upstream first” approach, meaning that every > single day, the new code is committed upstream. We need to avoid the “we’ll > build it internally and then upstream the code” approach. This is the only > way we’ll get traction as a community rather than allowing individual > companies to push for internal agendas. > > > > With the current approach, it is very difficult for the community to start > contributing to ongoing projects, or even to know what’s coming up on the > projects as code is pushed by major chunks with no visibility on the > roadmap. If we continue supporting such behaviour this will slow down the > adoption of ONAP in production environments. > > > > I believe it is our responsibility as the TSC to change that behaviour, > first by educating different organizations how open source should be > handled, but probably also by putting technical mechanisms to prevent such > a behaviour (e.g. Limit commit size; enforce multi-company reviews before > merge, allow for unfinished code in the repo …, any suggestions welcome). > > > > I do not have a specific solution to propose, but I would ask the TSC to > open up the dialogue on such behaviour. The Amsterdam release is quickly > coming and I believe this needs to be addressed asap. > > > > I’d like to discuss the topic tomorrow during TSC. > > > > Comments, anyone? > > > > Thanks, > > > > > > > _______________________________________________ > ONAP-TSC mailing list > ONAP-TSC@lists.onap.org > https://lists.onap.org/mailman/listinfo/onap-tsc > > > > ============================================================ > ================================================================ > > Disclaimer: This message and the information contained herein is > proprietary and confidential and subject to the Tech Mahindra policy > statement, you may review the policy at http://www.techmahindra.com/ > Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html > internally within TechMahindra. > > ============================================================ > ================================================================ > > _______________________________________________ > ONAP-TSC mailing list > ONAP-TSC@lists.onap.org > https://lists.onap.org/mailman/listinfo/onap-tsc > >
_______________________________________________ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
