Caffe weekly notes

[bhack]

@shelhamer It is not clear what happen to the @BVLC caffe agenda. Actually all the team seems MIA. Can you share something like opencv weekly reports to the community?

[shelhamer]

We actually had a BVLC meeting this weekend to figure out how to better broadcast changes and plans. Here's a rough sketch of ideas:

• issues + PRs rotations by BVLC members are helping to filter but a regular schedule could help more
• better catalogue and route labels
  • labels help fight noise since only BVLC can tag issues + PRs
  • include index of issue labels in README / docs to point to key types like "focus" and "interface"
• need to explain branches and releases
  • add note to README about release (stable) and master (latest)
  • make clear that site is for latest release, master docs are those bundled in caffe
  • releases should have their own branch, not just a tag, for including fixes (but not interface changes)
  • make an issue for each release to track maintenance changes
• plans for packaging: lots of posts are about installation and configuration so an official ubuntu package, homebrew formula, docker image, etc. deserve attention

Weekly notes are a good suggestion. I think a weekly / periodic issue to review new features, interface changes, and fixes should help the community track changes. It could otherwise be difficult to keep up with all the PRs and commits. Although our release PRs like #1849 give summaries these might be too much at once.

We are all working on the ICCV deadline 04/22. We'll catch up on issues, PRs, and new tutorial content once that's done. After a little rest and :coffee: of course.

[bhack]

Please consider also https://github.com/BVLC/caffe/issues/1623

[immars]

IMHO the problem is that BVLC team is already too busy to maintain another activity like weekly report. For me https://github.com/BVLC/caffe/pulse is good enough.

caffe is a really cool project, but I have to find and merge PRs, so I guess other people have to do the same. It works, but its duplicated effort if everyone do this.

@bhack is there anything we can do without requiring lots of core team member's effort? is there any follow up on #1623 ? can we start a

• caffe-dev maillist, or
• contrib branch

now?

[bhack]

@immars no. The only think we can do It is try to trainig a net to classify the hidden status of @BVLC members based on issue and PR activities if @shelhamer can give us some ground truths other that ones extracted from main conferences calendars.

[bhack]

ICCV deadline gone CVPR gone. What's next? Can you share weekly meetings news? Plans? Organize review priority?

[bhack]

Anybody can label this as abandoned by community managers?

[bhack]

See also how Torch it is planning https://github.com/torch/torch7/issues/326

[shelhamer]

This practice was never adopted. We participate in the mailing list and issues as we can and make release notes.