On Tuesday 06 March 2007, Johannes Stezenbach wrote:
> Marcel Siegert wrote:
> >
> > i do know mercurial and that one sucks.
>
> Hey :-(
>
hey :)
johannes, to be honest, dont take that so serious.
what i wanted to point out is, that, in fact as a result of mercurial
installation,
we have today 07.03.2007 11:56 including the master tree 70! repositories,
and no-one really is able to oversee what! is fixed and being in progress where.
a central repository can cause problems because someone may break builds
of drivers ect. due to some core-changes. but that must not happen.
there are ways to communicate and say "hey i am refactoring ....",
and people do know changes will happen sooner or later.
also their may be a rule on the development group itself NOT to break
compileable
status of the main repository.
they can merge mainline changes permanently _and_ get the advantage of
fixes, new ways immediately, maybe one merge to do, can save hours to search
for a somewhere_in_a_repository_worldwide existing patch.
you need an example? (ok - linux tv does not count on directfb repos, i must
admit freely)
<example>
what do i need by now, to get a dvb-s2 card running _or_ to have a
dvb-s2 repo, where
i could start developing a driver for a dvb-s2 frontend?
which trees must i pull and merge together?
and which one contains all fixes that have been meanwhile applied to
mainline?
and at least - which ones, that i may merge and use, will be later on
accepted by mainline?
the better concept _ or_ the one most people used to build their first
drivers on?
</example>
for me personal, it is annoying to have no central development model, where i
may rely on.
i don't exactly know - if there is a person like denis maintaining
git_or_some_other_scm scheme on
directfb - what will happen here. i do wish everybody to take a good decision
after thinking on _all_
dependencies.
questions (that may be answered by denis)
who is going to be able to commit to the mainline?
who is going to decide that a patch/pull whatever is accepted?
are we also going to introduce a s-o-b line?
must a pull request or patch be acked?
who is going to integrate patches into a pull repo, if the patch supplier is
not a dev or does not have commit
rights?
best regards
marcel
p.s.: i am not a main developer in directfb either linuxtv nor being that
active at least on tuxbox.org.
but while using those projects, i do contribute back. and, i found there
are different development
rules, that can be set up clearly, so working with those resources is
easy and integrating into
my own workflow/projects.
_______________________________________________
directfb-dev mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
