 |
|
Abhishek Pandit (Arm)
Ashutosh Singh (Arm)
Kevin Townsend (Linaro)
Julius Werner (Google)
Erik Shreve (TI)
David Brown (Linaro)
Bill Fletcher (Linaro Community Projects)
Andrej Butok (NXP)
NB: there was not a quorum present. No binding decisions were made.
Agenda/Minutes
Migrating to GitLab - proposal
DB: Why GitLab (vs GitHub)
BF: Self hosting and some concerns vs GitHub direction
AP: Need to improve vs current infrastructure
Built-in docs, wiki and issue tracker vs current cgit
GitHub and GitLab
JW: How is the reviewing system on GitLab? Previously used GitHub and it wasn’t great. Like Gerrit. Would be unfortunate to regress.
DB: Disadvantage vs GitHub - it’s (yet another) a separate system
KT: Same as for Gerrit today
DB: Is the aim for it to be an open source community project or just a small group (mostly within Arm) just ‘dump it’ on the world?
Andrey: GitHub is a more popular choice for NXP for hosting open source - SDK etc
Ashutosh: Most engineers like Gerrit. Only places we don’t like current infrastructure is documentation and issue tracking.
DB: Split implementation is likely to be painful. Depends on what kind of a community want to build.
AB: Internally NXP is using Jira for tracking but is moving projects to GitHub
ES: Seems that we are missing requirements - have requirements for a code review tool, issue tracking tool etc. If we resort to a survey to developers, Arm view will outweigh everything else. From TI PoV, would not recommend e.g. BitBucket. Code review is not good.
DB: Can’t make a decision unless we know what are the requirements and the relative importance.
AP: Can set up a Phabricator page to collect and provide space to review the requirements (action on Bill)
AOB
BF: Latest website mockup circulated based on previous feedback. Please take a look. Will keep the window open for a few days for any comments before we start implementing.
|
|