Sorry couldn't answer sooner. Lot of things going on - including joining Red Hat (:
GMT -0300 here On Wednesday, July 12, 2017 at 5:26:23 PM UTC-3, Greg DeKoenigsberg wrote: > > On Wed, Jul 12, 2017 at 3:48 PM, <wre...@redhat.com <javascript:>> wrote: > >> Greg-- >> >> Again, thanks for suggesting and facilitating the creation of this group. >> Can you provide any guidance on where to go from here, besides what's >> already covered in the docs? Specifically, is there a process we can follow >> to get PR's reviewed and ultimately merged? >> > > In general, the process for getting module PRs reviewed and merged is > ultimately the same -- get the PR Bot to give you the thumbs up on all > tests, and get the maintainer of the module to agree that the PR is worth > merging. > > The tricky thing can be getting everyone on the same page on those things > in a timely manner. The async nature of distributed development can be a > significant hindrance. > > IMO, that's where Working Groups are valuable: they provide structure for > a group of people who are dedicated to solving these problems, in the same > place at the same time, to shorten the feedback loops. > > So I would say: > * make sure the owners of the various JBoss modules are in your working > group; > * make sure to set up regular IRC meetings when they can all be present to > review PRs; > * make sure everyone is hanging out in the #ansible-jboss channel so that > you have quick/easy access to each other. > > The Working Groups really aren't that complicated. They're just a very > simple way of encouraging people to work together, with just a little bit > of infrastructure/process to help. > > Take a look at how the Windows and Testing Working Groups operate. I feel > like they're setting the standard right now. > > --g > > >> On Tuesday, July 11, 2017 at 3:25:02 PM UTC-4, wre...@redhat.com wrote: >>> >>> Thanks Greg. >>> >>> On Tuesday, July 11, 2017 at 11:38:58 AM UTC-4, Greg DeKoenigsberg wrote: >>>> >>>> I'll be processing this one today. >>>> >>>> On Mon, Jul 10, 2017 at 11:01 AM, <wre...@redhat.com> wrote: >>>> >>>>> All-- >>>>> >>>>> I've created a creation request for the JBoss WG >>>>> <https://github.com/ansible/community/issues/188>. Once we have the >>>>> IRC channel, we should do an initial planning meeting via IRC, so let's >>>>> start thinking about when would be a good time for that. For starters, we >>>>> should figure out which time zone everyone is in. I'm US/Eastern >>>>> (UTC-4:00). >>>>> >>>>> >>>>> On Saturday, July 8, 2017 at 11:23:21 PM UTC-4, Will Refvem wrote: >>>>>> >>>>>> That's a really good point. Let's call the working gorup JBoss, and >>>>>> we can figure out module naming later. >>>>>> >>>>>> On Fri, Jul 7, 2017, 7:51 PM Jairo Junior <junior...@gmail.com> >>>>>> wrote: >>>>>> >>>>>>> Count me in. >>>>>>> >>>>>>> I used JBoss name because of existing modules and I believe JBoss >>>>>>> brand is more popular than Wildfly. More popular means more users, so >>>>>>> more >>>>>>> contributors, feedback and etc... (: >>>>>>> >>>>>>> One important thing to notice is that Wildfly is known as the >>>>>>> upstream project of JBoss EAP, but other projects that use JBoss' >>>>>>> Architecture and even carry JBoss name in their productized version >>>>>>> such as >>>>>>> Keycloak (Red Hat SSO), Infinispan (JDG), Teiid (JDV) and apiman can >>>>>>> also >>>>>>> be managed through Management API or JBoss-CLI. You just can't deploy >>>>>>> applications to them. >>>>>>> >>>>>>> So, they're not Wildfly (Infinispan, Teiid, apiman) but "are JBoss", >>>>>>> and in special cases they're neither (Keycloak). >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Fri, Jul 7, 2017 at 7:18 PM Antonio Insuasti Recalde < >>>>>>> ant...@insuasti.ec> wrote: >>>>>>> >>>>>>>> Hi all >>>>>>>> >>>>>>>> Let me know if you need some help, I'm working on my own module, >>>>>>>> but i like the idea to work together >>>>>>>> >>>>>>> -- >>>>>>> You received this message because you are subscribed to a topic in >>>>>>> the Google Groups "Ansible Development" group. >>>>>>> To unsubscribe from this topic, visit >>>>>>> https://groups.google.com/d/topic/ansible-devel/nttHHu0nMxI/unsubscribe >>>>>>> . >>>>>>> To unsubscribe from this group and all its topics, send an email to >>>>>>> ansible-deve...@googlegroups.com. >>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>> >>>>>> -- >>>>>> >>>>>> WILL REFVEM >>>>>> >>>>>> SOLUTION ARCHITECT (APP DEV) >>>>>> >>>>>> Red Hat NA Commercial (Southeast/West) <https://www.redhat.com/> >>>>>> >>>>>> 100 E Davie St >>>>>> >>>>>> Raleigh, NC 27601 >>>>>> >>>>>> wre...@redhat.com M: 9194389532 >>>>>> <https://red.ht/sig> >>>>>> >>>>> >>>> >>>> >>>> -- >>>> Greg DeKoenigsberg >>>> Ansible Community Guy >>>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "Ansible Development" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to ansible-deve...@googlegroups.com <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Greg DeKoenigsberg > Ansible Community Guy > -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-devel+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
