<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi,<br>
<br>
I think it is a good idea.<br>
<br>
So I propose a group relative to the video integration in the
Asterisk.<br>
There are a lot of dead projects (not supported by the last
Asterisk releases), or bugged features, issues...<br>
<br>
Actually, Asterisk is loosing this video capabilities.<br>
<br>
Regards,<br>
<br>
<br>
Borja SIXTO from ulex.fr<br>
<br>
<br>
Le 06/10/2016 à 12:44, Dan Jenkins a écrit :<br>
</div>
<blockquote
cite="mid:CAE89AUJyLz3Oqk2bEhjuYrQKNNrWhmNwBVJe05gvpw642DON=A@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Oct 5, 2016 at 11:11 PM,
Rodrigo Ramírez Norambuena <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:decipher.hk@gmail.com" target="_blank">decipher.hk@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">On Tue,
2016-10-04 at 17:09 -0500, Matt Fredrickson wrote:<br>
> Hey all,<br>
<br>
<br>
Hello!,<br>
<span class=""><br>
> Welcome back to all of you who attended
AstriDevCon. Thanks so much<br>
> for all of you that attended and gave so much of
your time to be able<br>
> to contribute.<br>
><br>
<br>
</span>I missed it :(, maybe can be there the next year.<br>
<span class=""><br>
> One of the ideas proposed in AstriDevCon was to
create the notion of<br>
> working groups within the Asterisk project,
similarly to the way that<br>
> the node.js project operates. I think this would
be separate from<br>
> the<br>
> notion of maintainers of modules or subsystems in
Asterisk, which we<br>
> already have, and be more targeted towards areas
that are non code<br>
> related or areas of new code contribution.<br>
><br>
> I'm assuming that this would mean each working
group has a directive<br>
> or mission of some sort, a list of members, and
someone responsible<br>
> for the output of the group itself (someone to
hang, in a manner of<br>
> speaking :-) ).<br>
><br>
> Presumably we initially would need to identify some
key areas of<br>
> coverage.<br>
><br>
> Since the discussion began at Astricon, I'd love to
see some<br>
> continuation here on the list and welcome any
additional<br>
> thoughts/interest/disinterest.<br>
<br>
</span>Sound good the idea!.<br>
<br>
There some one thing to worry me. I dont think the number
of people who<br>
contribuite with Asterisk is near to Node.js.<br>
<br>
Create more group may be split to much of the people to
who contribuite<br>
now into the Asterisk.<br>
<br>
For other hang. I think there should be a group that
get/help/guide the new people who have the intention to
contribute with the Asterisk. Or organize a bug squashing
or feature pushing where new people can experience the
process how contribuite like that break the fear to push
the first commit and know a little the code/documentation
of project.<br>
<br>
Regards!<br>
<span class="HOEnZb"><font color="#888888">-- <br>
Rodrigo Ramírez Norambuena<br>
<a moz-do-not-send="true"
href="http://www.rodrigoramirez.com"
rel="noreferrer" target="_blank">http://www.rodrigoramirez.com</a><br>
</font></span>
<div class="HOEnZb">
<div class="h5"><br>
<br>
--<br>
______________________________<wbr>______________________________<wbr>_________<br>
-- Bandwidth and Colocation Provided by <a
moz-do-not-send="true"
href="http://www.api-digital.com" rel="noreferrer"
target="_blank">http://www.api-digital.com</a> --<br>
<br>
asterisk-dev mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a moz-do-not-send="true"
href="http://lists.digium.com/mailman/listinfo/asterisk-dev"
rel="noreferrer" target="_blank">http://lists.digium.com/<wbr>mailman/listinfo/asterisk-dev</a></div>
</div>
</blockquote>
</div>
<br>
</div>
<div class="gmail_extra">Hi Rodrigo,</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">I'm not worried about the number of
people who "contribute" to Node.js vs the number who
"contribute" to Asterisk. Its all relative. There are probably
in the high tens of thousands of developers building something
with Node.js - that number isn't the same for Asterisk but the
key thing is that there are (putting it simply) 3 types of
people in the node.js community - core devs, devs who care
about the community and get involved in it and those who just
use it. Asterisk is pretty much the same (again, I'm
simplifying) but the number of developers who get involved in
the community I'd hope is proportionally higher than that of
Node.js</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">We can still make the idea of working
groups work. We only create working groups for things that
people feel we need to drive forward. If anything, it makes
putting your ideas forward and making a difference easier (in
my opinion) than trying to tackle X task and contribute it
back into the project (depending on your skillset etc)</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Right now; theres no concerted effort
of "this feature would be really cool and its got hundreds of
upvotes, maybe I should build that" - a C dev coming to the
project generally finds an issue that affects them and fixes
it and submits it (maybe) - It would be great if when an
Asterisk Core Dev (part of the core team or not) wants to just
go build something on a whim (or as more of a concerted
orchestrated thing) they could go to a working group and find
out what people really want from that part of the project. At
least thats one benefit I see.</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">So if I understand properly you'd like
to see a working group around "My first Asterisk Commit" -
which would drive forward making contributing to the project
easier - whether it was improving documentation, or trying to
remove some of the road blocks people hit (like running the
test suite locally) or getting gerrit/gitreview setup etc?</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">I should have said in devcon - each
working group would have a "mission statement" and once that
mission statement is complete, or when theres no activity in
the working group - the working group gets disbanded.</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Dan</div>
<div class="gmail_extra"><br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<br>
<p><br>
</p>
<pre class="moz-signature" cols="72">--
Borja SIXTO (co-founder/manager)
Mail: <a class="moz-txt-link-abbreviated" href="mailto:borja.sixto@ulex.fr">borja.sixto@ulex.fr</a>
Tel: +33(0)4 28 35 03 44 Ext. 11
Ulex Innovative Systems | 4 rue des Prairies, 38460 St Romain de Jalionas, France
<a class="moz-txt-link-abbreviated" href="http://www.ulex.fr">www.ulex.fr</a></pre>
</body>
</html>