<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 10/ 9/14 01:15 AM, Bayard Bell
wrote:<br>
</div>
<blockquote
cite="mid:CAB=GcTL9QkRdMouzSBMdjGkF6-x_iAQ4d2giOn43JzQUZHAvmA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On 8 October 2014 23:36, Nikola M. <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:minikola@gmail.com" target="_blank">minikola@gmail.com</a>></span>
wrote:<br>
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">It was
probably lack of organization that killed many efforts
before.<br>
</blockquote>
<div><br>
</div>
<div>From my experience trying to walk a mile in his shoes,
I fully endorse Alasdair's observation that a clearly
established historical problem for OI was having meetings
to talk about organisation and process with people in the
hope that they might contribute. When it comes to
established practice, there is nothing novel about the
proposition that one earns a say in the workings of an
open-source community with sweat equity. One encourages
people to contribute rather than bargains.<br>
<br>
If you think this claim is simply polemical, you might as
well argue with the wind.<br>
</div>
</div>
</div>
</div>
</blockquote>
Idea of reviving /dev sureley needs work. No one questions that.<br>
If you think to start polemical talk, that is no issue here.<br>
<br>
It is about exact ways of releasing /dev and that it can not be just
'releasing snapshot' without TESTING. <br>
Because next thing you know is people complain new /dev have too
many bugs in it.<br>
And it is because making /dev is not possible without testing
updating from current /dev to Hipster snapshot, If that is the way
to go.<br>
<br>
I used and tested Hipster for a very long time and all that time i
did reporting of bugs and problems with update, apps, mounting
datasets in /opt, GNOME bugs, update bugs, etc.<br>
And it all went through IRC and not on mailing list, because of
number of people involved actually that was fastest way to do it.<br>
<br>
So in a nutshell, things get tested and reported and I was testing
everything i can for a very long time. <br>
And there are positions too that people take to contribute in
distribution, that are not measured by Github logs. (And why Github
but OI's own repositories etc.).<br>
<br>
</body>
</html>