Document how to do drive-by (one-time) contribution to Oniro

A one-time contribution requires the user to create an Eclipse account, set up their password for Gitlab and sign ECA. This procedure should be documented along with documenting pipeline behaviour for such contributions.

changed milestone to %goofy general availability

added teamdocumentation&UX label

changed title from Document how to do one-time contribution to Document how to do drive-by (one-time) contribution to Oniro

changed the description

@mrybczyn @idlethread Would it be enough to give links for registering and ECA or should we cover the filling in process itself?

@kristis and I have created the initial version of the docs, it's available here how-to-contribute.rst

It is a good start @kristis @gwozdzcfs. It would be good to add information on what people should actually click/fill in to add passwords etc. So that it is easy to follow.

Then it would be also good to cover the creation of the first MR. What to click on to create a fork, that you need to create a branch, push it, create MR in the system, get approvals and maintainers will merge it to the code base.

You can say that this is a standard fork-based process but it would be good to be specific. For example the Signed-off-by address must match the one in Eclipse account.

@mrybczyn we have extended the info how-to-contribute.rst. What do you think now?

Can we have an MR please? I'll have someone to do a test/review of this :)

@mrybczyn @kristis the MR is here

mentioned in merge request !13 (merged)

closed with merge request !13 (merged)