Mail Archives: geda-user/2015/09/18/03:42:04
--001a113cd994306210052000a9d8
Content-Type: text/plain; charset=UTF-8
Hi,
2015-09-16 2:05 GMT+02:00 Vladimir Zhbanov (vzhbanov AT gmail DOT com) [via
geda-user AT delorie DOT com] <geda-user AT delorie DOT com>:
[...]
> OK, I can tell you my opinion on this.
> Two of the waiting of approval people are Bob and Carlos, they are the
> developers, who you'd call 'inactive'. That's why (I think) nobody
> decides (at least, I wouldn't) if there is any sense to add them now.
>
[...]
I haven't look at gaf code since a lot of years now, so yes, I'm one of the
inactive developers.
By now, I think there is no reason I should be on that list. There are
people here who dag into the code and know the internals better than me.
In fact, I don't remember when I applied to that list. I recently received
the rejection to being a member, and I think it's a logical and sane
decission.
I'm glad the activity on this list is growing. There is a lot of work being
done recently (thank you all!).
As I see, the people who is willing to expend the time coding should decide
how the work will be done.
Advice and others points of view are valuable, but the critical decissions
should be taken by those who are actively coding.
My opinion is that, if something is valuable for a dev/user, it could also
be valuable for others, so it should be thought to be integrated in the
main repo.
In fact, I added some tools I valued to the repo, and I don't know of
anyone who are using them. As they don't harm anyone, why don't have them
in?
Now everybody who wants to code can create a branch, there should be no
reason to not use this.
I mean, new features should always be welcome. If it adds new dependencies,
please add an option to switch it off at compile time.
If it conflicts internally with anything, then it can require consensus
from all active devs.
Some "old" devs like me may not be active and there may be no leader, but
you have now a way to have full access to everything, so you can agree what
should be done.
There are regression tests which should assure full backwards compatibility
after any change to the code.
If anyone cares about a special feature he is using in any tool, he should
provide a regression test to assure this feature is not changed over time.
If it's not included in the regression test suite, there is no warranty
about backwards compatibility and the devs should not be responsible of
any changes to it.
As John has pointed out many times, this is a toolkit, so I think it's sane
if new tools are added to the repository, even without asking, as long as
users have an option to disable them if they are introducing new
dependencies or the behaviour is changed. Just make the default the "least
surprising".
There should be no objection to this: whoever who don't like them, they
don't need to build/use them.
If they are useful or not, we will see in the future.
I think we should be thankful to all people doing the work (coding,
documenting, squashing bugs,..) and no one should be forgotten or taken
aside.
There are now many branches/forks/local work which I'm sure are very
valuable. I expect you can find a way to get them into the main branch, so
all could join in and have a good team to work with.
Please take aside personal feelings, and think that if someone expent time
to do that, it should be valued and valuable for others (even others than
you), so that's a very good reason to be integrated.
If there is any conflict and there is an option to switch it on or off, let
the users decide.
Real world is not black or white. Open source is about freedom: if we have
it, at least we can choose. If no one is working, we have no option.
Thank you very much for all your work!
Carlos
--001a113cd994306210052000a9d8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Hi,<br><div><div class=3D"gmail_extra"><br><div class=3D"g=
mail_quote">2015-09-16 2:05 GMT+02:00 Vladimir Zhbanov (<a href=3D"mailto:v=
zhbanov AT gmail DOT com">vzhbanov AT gmail DOT com</a>) [via <a href=3D"mailto:geda-user=
@delorie.com">geda-user AT delorie DOT com</a>] <span dir=3D"ltr"><<a href=3D"m=
ailto:geda-user AT delorie DOT com" target=3D"_blank">geda-user AT delorie DOT com</a>>=
;</span>:<br><div>[...]<br>=C2=A0<br></div><blockquote class=3D"gmail_quote=
" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);=
padding-left:1ex">
OK, I can tell you my opinion on this.<br>
Two of the waiting of approval people are Bob and Carlos, they are the<br>
developers, who you'd call 'inactive'. That's why (I think)=
nobody<br>
decides (at least, I wouldn't) if there is any sense to add them now.<b=
r></blockquote><div>[...]<br><br></div><div>I haven't look at gaf code =
since a lot of years now, so yes, I'm one of the inactive developers.<b=
r></div><div>By now, I think there is no reason I should be on that list. T=
here are people here who dag into the code and know the internals better t=
han me.<br></div><div>In fact, I don't remember when I applied to that =
list. I recently received the rejection to being a member, and I think it&#=
39;s a logical and sane decission.<br>=C2=A0<br></div><div>I'm glad the=
activity on this list is growing. There is a lot of work being done recent=
ly (thank you all!).<br>As I see, the people who is willing to expend the t=
ime coding should decide how the work will be done.<br>Advice and others po=
ints of view are valuable, but the critical decissions should be taken by t=
hose who are actively coding.<br><br>My opinion is that, if something is va=
luable for a dev/user, it could also be valuable for others, so it should b=
e thought to be integrated in the main repo.<br>In fact, I added some tools=
I valued to the repo, and I don't know of anyone who are using them. A=
s they don't harm anyone, why don't have them in?<br><br>Now everyb=
ody who wants to code can create a branch, there should be no reason to not=
use this.<br>I mean, new features should always be welcome. If it adds new=
dependencies, please add an option to switch it off at compile time.<br>If=
it conflicts internally with anything, then it can require consensus from =
all active devs.<br><br>Some "old" devs like me may not be active=
and there may be no leader, but you have now a way to have full access to =
everything, so you can agree what should be done.<br><br>There are regressi=
on tests which should assure full backwards compatibility after any change =
to the code. <br>If anyone cares about a special feature he is using in any=
tool, he should provide a regression test to assure this feature is not ch=
anged over time. <br>If it's not included in the regression test suite,=
there is no warranty about backwards compatibility and the devs should=C2=
=A0 not be responsible of any changes to it.<br><br>As John has pointed out=
many times, this is a toolkit, so I think it's sane if new tools are a=
dded to the repository, even without asking, as long as users have an optio=
n to disable them if they are introducing new dependencies or the behaviour=
is changed. Just make the default the "least surprising".<br>The=
re should be no objection to this: whoever who don't like them, they do=
n't need to build/use them.<br>If they are useful or not, we will see i=
n the future.<br><br>I think we should be thankful to all people doing the =
work (coding, documenting, squashing bugs,..) and no one should be forgotte=
n or taken aside.<br>There are now many branches/forks/local work which I&#=
39;m sure are very valuable. I expect you can find a way to get them into t=
he main branch, so all could join in and have a good team to work with.<br>=
Please take aside personal feelings, and think that if someone expent time =
to do that, it should be valued and valuable for others (even others than y=
ou), so that's a very good reason to be integrated.<br><br>If there is =
any conflict and there is an option to switch it on or off, let the users d=
ecide.<br>Real world is not black or white. Open source is about freedom: i=
f we have it, at least we can choose. If no one is working, we have no opti=
on.<br>=C2=A0<br></div>Thank you very much for all your work!<br></div><br>=
</div><div class=3D"gmail_extra">Carlos<br></div></div></div>
--001a113cd994306210052000a9d8--
- Raw text -