Thanks Marvin for the pointers. But my question is not so much whether we can accept pull requests or handle GH issues. It is whether it is ok to be the *primary* workflow and dev@ is an archive.
The podling is coming from a GitHub-only culture, and the core team in the same company. Soooo... 1. I think all development is pull requests, whether it is from committers or external contributors. I.e. RTC. Hard to tell external from internal patches, so to speak 2. the dev@ list receives all the Issue comments and pull requests. 3. A somewhat large number (300) of open GH issues are on the old GH repository, brought over selectively, seemingly along with the work that goes with them (but I could be wrong here). 3. Some decision-making is _likely_ happening face-to-face. The overall effect is that if you are used to ASF projects, this podling feels very different than most other projects here. dev@ is a cold place at the moment, and I don't like it. A bit like some projects have tried to do (nearly) "JIRA only" discussions, which I also found somewhat "off-putting". Anyway, I will continue to nudge them in the "common direction" and shout again if I feel there is a problem. Cheers Niclas On Tue, Mar 7, 2017 at 2:23 PM, Greg Stein <gst...@gmail.com> wrote: > On Mon, Mar 6, 2017 at 11:34 PM, Marvin Humphrey <mar...@rectangular.com> > wrote: > >... > > > So, the questions I would ask are, are all those comments making it to > the > > list? And are the podling participants showing through their actions > that > > they understand inclusiveness, by ensuring that dev list readers are able > > to > > follow along? > > > > Pull requests and issues, and the comments upon them are all delivered to > an archived PMC mailing list. These tend to go to dev@, issues@, or > notifications@ ... as a PMC chooses. > > I checked with Legal, and we are required to forward this stuff to a list. > > > > For what it's worth, on one dev list I'm on, pull requests make it to the > > dev > > list, but commenting on a commit via the Github interface only triggers a > > private notification -- the comment never makes it to our dev list. We > > mostly > > avoid Github commit comments for that reason, so inclusiveness is not > > harmed > > -- but people new to Apache might not handle things that way. > > > > We can forward those, if you want. Probably should. > > Cheers, > -g > -- Niclas Hedhman, Software Developer http://polygene.apache.org <http://zest.apache.org> - New Energy for Java
