Re: [OM Cooker] desktop-common-data soft dir

--001a11c269ac8f6c0d04e2c356dd
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

2013/7/30 Jochen Sch=F6nfelder <[email protected]>

> On Tue, 30 Jul 2013 20:40:30 +0200
> Per =D8yvind Karlsen <[email protected]> wrote:
>
> > 2013/7/30 Jochen Sch=F6nfelder <[email protected]>
> >
> > > On Tue, 30 Jul 2013 10:55:22 -0600
> > > Matthew Dawkins <[email protected]> wrote:
> > >
> > > > > No point in creating separate branches of everything under
> moondrake/*
> > > > > when I'm the one who's the main maintainer of everything under
>  there
> > > and
> > > > > what is to be consdered as upstream.
> > > nope.
> > >
> > > Upstream is depending on the package. For some it's Mageia, for other=
s
> it's
> > > ourselves, ...
> >
> > Which for all of the packages in question are the repos that I'm using.
> >
> > I'm not sure of what packages you refer to that has Mageia as upstream,=
 I
> > have myself been the one maintaining all of these for the past couple o=
f
> > years.
> I had stuff like control center on the list for that, eg. Or renamings li=
ke
> OnlineUpdate or omvonline.

Not really such a great priority, my plan was however to just rename them
to something less vendor specific, ie. like in stead of <vendor> Control
Center, just name it DrakX Control Center.
Tainting name with vendor name is rarely a good idea and the perfect way to
best try prevent adoption and collaboration with anyone on the outside..

>
> > And since I've imported everything to one place already and is doing th=
e
> > wast majority of all the maintenance work, there's no sense in forking
> > stuff into separate repos just to satisfy someone's obsession over
> naming.
> >
> > Also you most possibly will strongly disagree when we change default
> > > configs and artwork for omv.
> >
> > No, you don't change the default for everyone, you change the default f=
or
> > whatever flavour that you want to maintain.
> I didn't get the impression that everything in abf's moondrake repo is
> build to
> be easily flavoured. If that's the case or going to be, it for sure would
> be
> very welcome.
>
Where it makes sense, that's the idea, for many places it makes far more
sense to make things more neutral in "flavour"..

>
> > Everything related to this has support for multiple without the need fo=
r
> > separate repos or anything, everything can go into one master branch,
> > unless anyone has some specific need for other trees for their work
> that's
> > not suitable to go "upstream".
> which could be which kind of needs?
>
That's entirely arbitrary.

--
Regards,
Per =D8yvind

--001a11c269ac8f6c0d04e2c356dd
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">2013/7/30 Jochen Sch=F6nfelder <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:[email protected]" target=3D"_blank">[email protected]</a>&gt;</=
span><br><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid=
;padding-left:1ex">
On Tue, 30 Jul 2013 20:40:30 +0200<br>
<div class=3D"im">Per =D8yvind Karlsen &lt;<a href=3D"mailto:proyvind@moond=
rake.net">[email protected]</a>&gt; wrote:<br>
<br>
</div><div class=3D"im">&gt; 2013/7/30 Jochen Sch=F6nfelder &lt;<a href=3D"=
mailto:[email protected]">[email protected]</a>&gt;<br>
&gt;<br>
&gt; &gt; On Tue, 30 Jul 2013 10:55:22 -0600<br>
&gt; &gt; Matthew Dawkins &lt;<a href=3D"mailto:[email protected]">mattyda=
[email protected]</a>&gt; wrote:<br>
&gt; &gt;<br>
&gt; &gt; &gt; &gt; No point in creating separate branches of everything un=
der moondrake/*<br>
&gt; &gt; &gt; &gt; when I&#39;m the one who&#39;s the main maintainer of e=
verything under =A0there<br>
&gt; &gt; and<br>
&gt; &gt; &gt; &gt; what is to be consdered as upstream.<br>
&gt; &gt; nope.<br>
&gt; &gt;<br>
&gt; &gt; Upstream is depending on the package. For some it&#39;s Mageia, f=
or others it&#39;s<br>
&gt; &gt; ourselves, ...<br>
&gt;<br>
&gt; Which for all of the packages in question are the repos that I&#39;m u=
sing.<br>
&gt;<br>
&gt; I&#39;m not sure of what packages you refer to that has Mageia as upst=
ream, I<br>
&gt; have myself been the one maintaining all of these for the past couple =
of<br>
&gt; years.<br>
</div>I had stuff like control center on the list for that, eg. Or renaming=
s like<br>
OnlineUpdate or omvonline.</blockquote><div style>Not really such a great p=
riority, my plan was however to just rename them to something less vendor s=
pecific, ie. like in stead of &lt;vendor&gt; Control Center, just name it D=
rakX Control Center.</div>
<div style>Tainting name with vendor name is rarely a good idea and the per=
fect way to best try prevent adoption and collaboration with anyone on the =
outside..</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">
<div class=3D"im">
<br>
&gt; And since I&#39;ve imported everything to one place already and is doi=
ng the<br>
&gt; wast majority of all the maintenance work, there&#39;s no sense in for=
king<br>
&gt; stuff into separate repos just to satisfy someone&#39;s obsession over=
 naming.<br>
&gt;<br>
&gt; Also you most possibly will strongly disagree when we change default<b=
r>
&gt; &gt; configs and artwork for omv.<br>
&gt;<br>
&gt; No, you don&#39;t change the default for everyone, you change the defa=
ult for<br>
&gt; whatever flavour that you want to maintain.<br>
</div>I didn&#39;t get the impression that everything in abf&#39;s moondrak=
e repo is build to<br>
be easily flavoured. If that&#39;s the case or going to be, it for sure wou=
ld be<br>
very welcome.<br></blockquote><div style>Where it makes sense, that&#39;s t=
he idea, for many places it makes far more sense to make things more neutra=
l in &quot;flavour&quot;..=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<div class=3D"im"><br>
&gt; Everything related to this has support for multiple without the need f=
or<br>
&gt; separate repos or anything, everything can go into one master branch,<=
br>
&gt; unless anyone has some specific need for other trees for their work th=
at&#39;s<br>
&gt; not suitable to go &quot;upstream&quot;.<br>
</div>which could be which kind of needs?<br></blockquote><div style>That&#=
39;s entirely arbitrary.</div><div style><br></div><div style>--</div><div =
style>Regards,</div><div style>Per =D8yvind</div></div></div></div>

--001a11c269ac8f6c0d04e2c356dd--