improving processes & contribution tools

8/9/2019 Improving Processes & Contribution Tools

1/10

ImprovingProcesses &ContributionTools

ImprovingProcesses &ContributionTools


2/10

Vision

Improve our contribution process and the

infrastructure around it, such that contributing tothe platform becomes easy and fast.

Copyright 2010 Symbian Foundation. 2


3/10

Scope: The Process


Including the handlingof contributions by

package owners &committers


4/10

Problem Areas Identified

1) Too many steps and different tools involved when making &

handling contributions, as well as monitoring progress

2) The process itself is not simple, nor intuitive

This is true for small as well as large contributions (councilinteractions)

3) Information related to the platform, contributing andaccepting contributions is hard to find and comprehend

4) No agreed working practices between Qt and Symbian opensource projects



5/10

1) Too many steps, too many tools

Making Contributions

Pretty much in line with other open source projects

But: we officially support 3 ways of contributing(FCL commits, patches, e-mail) creates complexity

Thus: focus on ONE approach only

Reduce # of steps by better tools integration (extensions to tools,e.g. when FCL commit is made, Bugzilla is updated)

Tracking Contributions

What happens to my contribution when it has been made?

Committer: what contributions are waiting to be handled?

Implement Contribution Dashboard per package & user

Handling Contributions

Member companies will always work with Foundation & their ownSCMs (creates extra steps & complexities)

Investigate how this mode of working can be bettersupported by the Foundation



6/10

2) Simple Process: Innovation

Innovation Process

Very Lightweight: Champion, Project Goals, Project Lead

Works alongside the Contribution Process

Examples of Incubation Projects Wild Ducks

Software Freedom Fighters

Python for Symbian

http://developer.symbian.org/wiki/index.php/Innovation_Processhttp://developer.symbian.org/wiki/index.php/Wild_ducks_projecthttp://developer.symbian.org/wiki/index.php/Wild_ducks_projecthttp://developer.symbian.org/wiki/index.php/Innovation_Process


7/10

2) Simple Process: Contribution

Contribution Process

The 3 categories of contributing are confusing

Bug Fixes

Enhancements Extensions

Have one contribution process

Centred around merge requests(the handshake between contributor and committer)

Council approvals will be treated as non-technical requirements thatneed to be satisfied before a contribution can go into the MCL

With increasing size & complexity of a contribution more upfrontdiscussion with the package owner is recommended



8/10

2) Simple Process: Large Contributions

Large Contributions

Contributors and committers areconfused by the council processes

WHEN and WHY is approval X needed? Not the same as for smaller contributions

(e.g. code can just appear in a package)

Clearly separate cause and effect, e.g.

CLEAR: A new package requires AC approval before the code is made available

UNCLEAR:

In which circumstance and when is an MCP needed?

In which circumstance and when is a UI concept needed?



9/10

3) Improving Information

Improvements

Splitting the top-level navigation from developer.com into acontributor and application developer page

One-click to resources related to latest S^x releases

New key content:

Get Involved

My first Contribution (step-by-step instructions of making acontribution)

Improving Process Documentation

Consolidate and improve Accepting Contributions

Use of more diagrams to describe the process

Improving Package and Project Pages

Improve navigation: e.g. filter & search, lifecycle information

More life information: e.g. commit meter, news, kudos, etc.



10/10

3) Example:Site Split


improving processes & contribution tools

Documents