On Fri, Mar 27, 2015 at 6:51 PM, Matt Franklin wrote:
>> The script is fiddly and hard to test. It's expanded beyond its
>> original scope and probably could stand to be refactored or rewritten.
>
> Where does it live?
https://git-wip-us.apache.org/repos/asf?p=infrastructure-puppet.git;a=blob;
On Sat, Mar 28, 2015 at 12:25AM, John D. Ament wrote:
> On Fri, Mar 27, 2015 at 8:19 PM Konstantin Boudnik wrote:
>
> > Just to make sure - first month after acceptance in the Incubator a podling
> > isn't expected to send their report, right? The point in question is
> > Groovy:
> > they are wor
On Fri, Mar 27, 2015 at 9:52 PM Matt Franklin
wrote:
> On Fri, Mar 27, 2015 at 9:31 PM Marvin Humphrey
> wrote:
>
> > On Fri, Mar 27, 2015 at 9:14 AM, Matt Franklin >
> > wrote:
> >
> > > Do we have a cause for the continued failure to send reminders?
> >
> > The script is fiddly and hard to te
On Fri, Mar 27, 2015 at 9:31 PM Marvin Humphrey
wrote:
> On Fri, Mar 27, 2015 at 9:14 AM, Matt Franklin
> wrote:
>
> > Do we have a cause for the continued failure to send reminders?
>
> The script is fiddly and hard to test. It's expanded beyond its
> original scope and probably could stand to
On Fri, Mar 27, 2015 at 9:14 AM, Matt Franklin wrote:
> Do we have a cause for the continued failure to send reminders?
The script is fiddly and hard to test. It's expanded beyond its
original scope and probably could stand to be refactored or rewritten.
> Every podling SHOULD know their repor
On Fri, Mar 27, 2015 at 5:35 PM, John D. Ament wrote:
> On Fri, Mar 27, 2015 at 8:30 PM jan i wrote:
>
>> On Saturday, March 28, 2015, Marvin Humphrey
>> wrote:
>>
>> > On Fri, Mar 27, 2015 at 5:18 PM, Konstantin Boudnik > > > wrote:
>> > > Just to make sure - first month after acceptance in the
On Fri, Mar 27, 2015 at 8:30 PM jan i wrote:
> On Saturday, March 28, 2015, Marvin Humphrey
> wrote:
>
> > On Fri, Mar 27, 2015 at 5:18 PM, Konstantin Boudnik > > wrote:
> > > Just to make sure - first month after acceptance in the Incubator a
> > podling
> > > isn't expected to send their repo
On Saturday, March 28, 2015, Marvin Humphrey wrote:
> On Fri, Mar 27, 2015 at 5:18 PM, Konstantin Boudnik > wrote:
> > Just to make sure - first month after acceptance in the Incubator a
> podling
> > isn't expected to send their report, right? The point in question is
> Groovy:
> > they are wor
On Fri, Mar 27, 2015 at 5:18 PM, Konstantin Boudnik wrote:
> Just to make sure - first month after acceptance in the Incubator a podling
> isn't expected to send their report, right? The point in question is Groovy:
> they are working on the report, but I don't think they really have to.
>
> Pleas
On Fri, Mar 27, 2015 at 8:19 PM Konstantin Boudnik wrote:
> Just to make sure - first month after acceptance in the Incubator a podling
> isn't expected to send their report, right? The point in question is
> Groovy:
> they are working on the report, but I don't think they really have to.
>
> Ple
On Fri, Mar 27, 2015 at 8:19 PM Konstantin Boudnik wrote:
> Just to make sure - first month after acceptance in the Incubator a podling
> isn't expected to send their report, right? The point in question is
> Groovy:
> they are working on the report, but I don't think they really have to.
>
> Ple
Just to make sure - first month after acceptance in the Incubator a podling
isn't expected to send their report, right? The point in question is Groovy:
they are working on the report, but I don't think they really have to.
Please correct me if I am wrong on that.
Thanks,
Cos
On Fri, Mar 27, 2
Podling commons-rdf fits that description. It started at GitHub in the
knowledge that ASF was a possible route; ALv2 from the start. (We
started at GH because there are people who would join discussions more
freely on GH.)
It so happens, the contributors are all ASF committers. With advice
The VOTE passes with 3, +1 binding votes from IPMC and no -1s.
Jean-Baptiste Onofré+1 (binding)
Billie Rinaldi +1 (binding)
Steve Loughran +1 (binding)
Thanks to everyone for the votes.
Next Steps:
Push the release out to the mirrors and announce.
-Gour
From: Gour Saha ma
On 2015-03-27 20:12, Guillaume Laforge wrote:
As a first step, I'll start with warning our users about that upcoming
change.
Also, I have a question.
So, the address during incubation is: d...@groovy.incubator.apache.org
But when we successfully get out of incubation, there will be an automati
As a first step, I'll start with warning our users about that upcoming
change.
Also, I have a question.
So, the address during incubation is: d...@groovy.incubator.apache.org
But when we successfully get out of incubation, there will be an automatic
transfer to: d...@groovy.apache.org
Correct? No
Not that I’m aware of, but sending a pile of emails isn’t out of this
world complicated.
If you gave me a list of email addresses of people who had explicitly
said “subscribe me”, I could do that very easily.
Upayavira
On Fri, Mar 27, 2015, at 04:57 PM, Roman Shaposhnik wrote:
> Do we have an op
“do that” == “subscribe them"
On Fri, Mar 27, 2015, at 05:01 PM, Upayavira wrote:
> Not that I’m aware of, but sending a pile of emails isn’t out of this
> world complicated.
>
> If you gave me a list of email addresses of people who had explicitly
> said “subscribe me”, I could do that very easi
Do we have an option of using our ML infrastructure in such
a way that it sends folks an email asking to confirm their
willingness to be subscribed? This could solve this I think.
Thanks,
Roman.
On Fri, Mar 27, 2015 at 9:42 AM, Shane Curcuru wrote:
> This is obviously a question for the new podl
This is obviously a question for the new podling's PPMC and the existing
Groovy community mailing lists to decide, but in most other situations
auto-subscribing people to a new list is usually a bad idea.
I would definitely give people plenty of notice and clear instructions
on how to unsubscribe
On Fri, Mar 27, 2015 at 11:58 AM Marvin Humphrey
wrote:
> Greets,
>
> With the chaos of the Members meeting this week it went unremarked,
> but Marvin failed to send out report reminders again. Reports are due
> next Wednesday.
>
> (Other Marvin. The robot.)
>
Do we have a cause for the contin
http://wiki.apache.org/incubator/April2015
Wed April 01 -- Podling reports due by end of day
Sun April 05 -- Shepherd reviews due by end of day
Sun April 05 -- Summary due by end of day
Tue April 07 -- Mentor signoff due by end of day
Wed April 08 -- Report submitted to Boa
Greets,
With the chaos of the Members meeting this week it went unremarked,
but Marvin failed to send out report reminders again. Reports are due
next Wednesday.
(Other Marvin. The robot.)
Marvin Humphrey
-
To unsubscribe, e-
Why do folks think that current list users can’t click on a mailto and hit
send? That’s all it takes to subscribe. It will weed out some dead email
addresses and give folks the option to use different email addresses.
Our project had over 800 folks join the dev@ list without auto-subscribing
fol
Great - it's good that was the understanding on the lists anyway and
notification of the action is a good idea as Bertrand notes; it's also
highlighting the move (can't assume all the user list subscribers have
groked that!). A read-only-ish list like commits is not an issue.
Andy
(Th
On Fri, Mar 27, 2015 at 08:42AM, Bertrand Delacretaz wrote:
> On Fri, Mar 27, 2015 at 12:25 AM, Konstantin Boudnik wrote:
> > ...Are you saying that the act of subscribtion to the dev@ list is
> > implicitely
> > similar to ICLA filing?...
>
> That's definitely not the case, that would be terrib
On Fri, Mar 27, 2015 at 12:25 AM, Konstantin Boudnik wrote:
> ...Are you saying that the act of subscribtion to the dev@ list is implicitely
> similar to ICLA filing?...
That's definitely not the case, that would be terrible.
What starts being similar to iCLA is making actual code contributions.
On Fri, Mar 27, 2015 at 7:25 AM, Paul King wrote:
> ...as long as we warn people and tell them how
> to unsubscribe, I think auto subscribing them would be OK?...
I don't like it too much, maybe at least an advance warning on the
existing Groovy lists that you are about to subscribe them here, wi
28 matches
Mail list logo
