Open_Source_Community_Collaboration_presentation 

Sony wiki

Login

Open Source Community Collaboration presentation

Here are some notes for the open source community collaboration presentation:

  • James Bottomley talks about how to contribute to the kernel:
    • See https://lwn.net/Articles/502471/
    • key points:
      • don't try to make the patch perfect
        • imperfect patches help people feel like they're contributing
        • takes too long to make it perfect
          • get feedback early
        • but, sloppy patches will make you look bad
      • kernel is in late phase, where patches (besides bugfixes) need to be justified, mature, and not de-stabilizing
      • need to talk to others to socialize your patches
        • can meet at conferences
        • helps to build reputation
      • be prepared to explain and argue for your patch
        • tell the "why" of the patch, not the "what it does"
          • developers can read C
      • don't worry so much before sending the patch (just do it - says Hiramatsu-san)

Fukuchi-san feedback - 2016-06-29 [edit section]

Fukuchi-san feedback:

  • Before "How to participate?"(Page28,29), it is helpful for beginners' understanding to introduce community
    • for example, "Who/What is community?".
    • For beginners, community is unkown.

The followings are examples of my questions:

  • What kind of structure does community have?
  • Are there many small groups in a community and many ML?
  • Who is responsible? (Who is important to me?)
  • Who is Maintainer?
  • Who is Chair?
  • Who should I communicate? Maintainer? ML members?
  • What kind of activities are there in a community?

From the conference call:

  • what is a community
  • what is the structure of the community
  • how is it formed
  • what is a maintainer
    • what is the maintainer's job
  • what tools (online resources) are used (e.g. mail lists, IRC, patch tools, gerrit, github, forums, etc.)
  • what is governance model
    • basically, maintainers are mini-dictators
    • commit privileges, git and patch requests
  • examples of community interactions
    • e-mail with a patch
    • e-mail to discuss a bug
  • Ueda-san said to add gregkh slides about struct of the Linux community
    • maintainer graph??

Need to address concerns of newbies:

  • for each obstacle, what to do about it (as an individual)
    • english not good enough (should not be an issue)
    • fear of raising controversial issues
    • fear that an issue is too trivial to reply
  • page 19 - last line
  • page 25 - like metaphor of bicycle (needs explanation and pictures, though)

  • page ??
    • don't know what a 'treadmill' is
      • need to use picture, and explain 'product treadmill'
  • page 44 - what is 'name-calling'
    • need to explain rude behaviors that might be encountered
    • need to explain how to ignore rude behaviors

  • page ??
    • explain what social issues are
  • add something about starting small
    • how to contribute without sending a patch
      • lurk, and answer other people's questions
        • climb the newbie ladder
      • add to documentation
        • his helps your understanding, and helps others as well

Trainee categories:

  • curious - just want to see what this is about
  • beginners - want to start working with community - eager to join but don't know much
  • evangelists - know how to do it, or have already done it, but need to convince others to participate and explain how

specific items to fix [edit section]

  • page 20 - describe what lock-in is

media to add [edit section]

  • page 14 - people are messy: picture of an angry person

maintainers [edit section]

TBWiki engine 1.8.0 by Tim Bird