Skip to content

CCB Meeting #1

Jump to bottom
Matias Mora edited this page Feb 17, 2015 · 2 revisions
  • Date: Fr Jan 23rd 2015, 15:30 UTC
  • Location: Skype
  • Attendees: Jorge Avarias, Joseph Schwarz, Khushbu Verma, Matias Mora (representing ACB)

Pre-meeting Homework

Agenda

  • Explanation of CCB Role in the community.
  • Elect CCB roles.
  • Chairperson.
  • Approval of initial version of CCB guidelines.
  • Write a draft to define procedure to review, accept and merge contributions, it should contain, at least the following definitions:
  • Specify coding styles for each supported language (C++, Java and Python)
  • Define guides for required unit test set.
  • Define minimal design documentation in case of new features.
  • Write a draft to define protocol to merge patches from ALMA.
  • Write a draft to formalize the way how to give progress updates to the community.
  • Define a release plan (version numbers, when do we do a release?)
  • Does it make sense to merge ACS contributed code into github? If yes, how do we proceed?

Minutes

  • Absents: Tomas Staig, Rafael Hiriart

  • Starting with comments about the CCB guidelines draft.

    • Joe: The override decision part of the guideline is too generic, ot should be focused in the main acs community repository. AI Jorge The document needs to be modified.

  • Jorge explains what is the role of CCB within the community.

  • Elect roles:

    • Jorge will continue to be the chairperson for now, however this should be voted in the near future.

  • ACS coding standards:

    • Khushbu has prepared a draft with the C++ coding standard, she sent this only to Jorge AI Jorge Review the document and circulate among CCB members
    • Joe asks if it is possible to use ALMA standard. Matias told us that he talked with Erik A. regarding this and the decision is that ALMA will not make those document public.
    • AI Khushbu Prepare a document containing minimal guides for required unit test set.
    • AI Jorge Prepare a document containing minimal design documentation in case of new features.

  • Merging patches from ALMA

    • Joe suggests to integrate the patches as soon they are released
    • Jorge says that he want to wait until the are at least validated in ALMA
    • Matias suggests that patches can be merged as soon as available to the community Trunk to make them available to interested parties, while stable community releases should only contain exhaustively tested patches.
    • AI Jorge to ask to other acs community interested parties what versions of ACS they are using, and how likely they will use the newest ACS release as soon it is available.

  • ACS Community releases

    • Not clear yet when we do releases.

  • Write a draft to formalize the way how to give progress updates to the community.

    • The acs-community announcement list is good enough. The updates should be done only for announcements. Technical discussion should be carried on the tickets.

  • Does it make sense to merge ACS contributed code into github? If yes, how do we proceed?

    • Yes, we should put the contributions as they are, in a different repository. Then, some effort should be spent to build the contributions with the latest ACS community version.

  • Joe asks whether this is the right place to talk about future projects.

  • Joe talked about the progress Khushbu has done porting TMCDB to MySQL. Currently the improvements is being reviewed by Alessandro.

Clone this wiki locally