It was <2014-01-13 pon 23:21>, when Thiago Macieira wrote:
> On segunda-feira, 13 de janeiro de 2014 11:14:01, Łukasz Stelmach wrote:
>> EHLO.
>
> 220

It's rather 250 at this point ;)

>> I'd like to propose providing personal git repositories as a part of
>> Tizen infrastructure the same way it is done at Freedesktop.org where
>> next to "project repositories" (e.g. systemd/systemd[1]) we can find
>> personal user repositories (e.g ~dvdhrm/systemd[2] or
>> ~jwrdegoede/qemu[3]).
>> 
>> The purpose is to enable developers to share their work even before
>> it can be pushed to Gerrit. For example a team of developers prepares
>> upgrades for several "upstream" packages (this requires rebasing and
>> forceful pushing bypassing review). Each developers pushes the
>> packages to their own repository. Integrator/maintainer takes the
>> repositories and pushes them to Gerrit.
>> 
>> The repositories would be just a space to share work with git(1) and
>> would not, of course, be connected to Gerrit or OBS in any way.
>> 
>> Tizen-Bug: TINF-429[4]
>
> I've heard a few opinions here and there and most people agree it's a
> good idea to allow Tizen devs to share unfinished code with each
> other.
>
> But we need to ensure that this is about work that benefits
> Tizen.

Definitely reasonable.

> Personal repositories or branches for projects that are already part
> of Tizen are fine.  We'll expect that the activity is related to
> Tizen, but I guess we have to be lenient -- not all crazy ideas might
> pan out!
>
> We should currently draw the line on automatically creating new
> repositories for projects not already part of Tizen. A simple ok from
> an Architect or from a Maintainer agreeing that this is related to
> Tizen will suffice, though.

How about temporary repos without anyone's consent? One could create a
repo even without maintainer's consent but it would be removed either:

+ after a fixed period (e.g. one week), or

+ after not using it for some time.

This seems to be necessary to apply for an official repository,
otherwise we've got catch 22[1] not being able to present a project and
its usefulness for Tizen. Of course a developers could use other hosting
service but should they?

> PS: I prefer personal branches, which Gerrit already supports.

This is a solution in certain situations, although it is not as general
and flexible as personal repositories. With personal repositories we
also avoid a risk of messing official repositories up even if by
accident.

Footnotes:

[1] http://en.wikipedia.org/wiki/Catch-22

-- 
Łukasz Stelmach
Samsung R&D Institute Poland
Samsung Electronics

Attachment: pgpcdi4cGUtDS.pgp
Description: PGP signature

_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev

Reply via email to