Hi,
I think it is a good idea.
So I propose a group relative to the video integration in the Asterisk.
There are a lot of dead projects (not supported by the last Asterisk
releases), or bugged features, issues...
Actually, Asterisk is loosing this video capabilities.
Regards,
Borja SIXTO from ulex.fr
Le 06/10/2016 à 12:44, Dan Jenkins a écrit :
On Wed, Oct 5, 2016 at 11:11 PM, Rodrigo Ramírez Norambuena
<[email protected] <mailto:[email protected]>> wrote:
On Tue, 2016-10-04 at 17:09 -0500, Matt Fredrickson wrote:
> Hey all,
Hello!,
> Welcome back to all of you who attended AstriDevCon. Thanks so much
> for all of you that attended and gave so much of your time to be
able
> to contribute.
>
I missed it :(, maybe can be there the next year.
> One of the ideas proposed in AstriDevCon was to create the notion of
> working groups within the Asterisk project, similarly to the way
that
> the node.js project operates. I think this would be separate from
> the
> notion of maintainers of modules or subsystems in Asterisk, which we
> already have, and be more targeted towards areas that are non code
> related or areas of new code contribution.
>
> I'm assuming that this would mean each working group has a directive
> or mission of some sort, a list of members, and someone responsible
> for the output of the group itself (someone to hang, in a manner of
> speaking :-) ).
>
> Presumably we initially would need to identify some key areas of
> coverage.
>
> Since the discussion began at Astricon, I'd love to see some
> continuation here on the list and welcome any additional
> thoughts/interest/disinterest.
Sound good the idea!.
There some one thing to worry me. I dont think the number of
people who
contribuite with Asterisk is near to Node.js.
Create more group may be split to much of the people to who
contribuite
now into the Asterisk.
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.
Regards!
--
Rodrigo Ramírez Norambuena
http://www.rodrigoramirez.com
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
<http://lists.digium.com/mailman/listinfo/asterisk-dev>
Hi Rodrigo,
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
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)
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.
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?
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.
Dan
--
Borja SIXTO (co-founder/manager)
Mail: [email protected]
Tel: +33(0)4 28 35 03 44 Ext. 11
Ulex Innovative Systems | 4 rue des Prairies, 38460 St Romain de Jalionas,
France
www.ulex.fr
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
