v@flex.apache.org
> Subject: Re: Draft email to committers
>
> Hi,
>
> > I think that's why we should vote sending or not.
>
> In this case a single -1 (veto) is enough to stop the email from happening.
>
> I could put it up for a less restrictive vote but given
o:jus...@classsoftware.com]
Sent: Tuesday, March 18, 2014 3:59 AM
To: dev@flex.apache.org
Subject: Re: Draft email to committers
Hi,
> I think that's why we should vote sending or not.
In this case a single -1 (veto) is enough to stop the email from happening.
I could put it up for a less restrictive v
Hi,
> I think that's why we should vote sending or not.
In this case a single -1 (veto) is enough to stop the email from happening.
I could put it up for a less restrictive vote but given there no consensus I
don't think that would be fair.
Anyone to send this email to committers themselves bu
lify their status:
1) active
2 lurking
3) disengaged.
We could consider people not answering after a while are in 3).
Thoughts?
Maurice
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : mardi 18 mars 2014 04:59
À : dev@flex.apache.org
Objet : Re: Draft email to co
igine-
De : Justin Mclean [mailto:jus...@classsoftware.com]
Envoyé : mardi 18 mars 2014 04:20
À : dev@flex.apache.org
Objet : Re: Draft email to committers
Hi,
OK going to call this dead as we can't reach consensus and a VOTE would (I
assume) be vetoed.
Thanks,
Justin
>
> What's wrong that we can't even agree on a simple email asking people to
>>
> Nothing is wrong. Geeks are just not normally very good at expressing
> themselves and can easily take things the wrong way.
Like you calling me a "Geek"?
You *&%@#&*&#$!
EdB
P.S. :-P (just in case something got
On 18/03/14 05:47, Erik de Bruin wrote:
What's wrong that we can't even agree on a simple email asking people to
Nothing is wrong. Geeks are just not normally very good at expressing
themselves and can easily take things the wrong way.
Tom
I think that's why we should vote sending or not.
Piotr
-
Apache Flex Committer
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Draft-email-to-committers-tp35873p35991.html
Sent from the Apache Flex Development mailing list ar
> Let's not discuss this to death, please.
>
Well... I'm very sorry I was right :-(
What's wrong that we can't even agree on a simple email asking people to
help out - the essence of an Open Source project?
EdB
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I
OK. But I'm still wondering if there is a less "formal" way to try to get
the attention of committers who've stopped paying attention. Maybe not
now, but around the time we release the initial FlexJS alpha, I would like
to make sure all of our initial committers know about it. I wonder what
woul
Hi,
OK going to call this dead as we can't reach consensus and a VOTE would (I
assume) be vetoed.
Thanks,
Justin
On 3/16/2014 9:28 PM, Justin Mclean wrote:
Jeffry if you're still against this and there's no word changes that make it
acceptable to you I'll give up and move onto something else.
The wording is much better and less confrontational.
I still have reservations about the need for an email like
lex.apache.org
Objet : Re: Draft email to committers
Hi,
> Part of it is getting the right version, part of it is knowing how to
> make sure you didn't embarrass yourself with the fix.
Any fix is just a revert away - that's the great thing about version. I've
made plenty of
Is a 'fix' an attached file or a change in git?
If those git hooks are up and running that would be great to know. This
should probably be continued in another thread.
On Mar 17, 2014 9:02 AM, "Justin Mclean" wrote:
> Hi,
>
> > Part of it is getting the right version, part of it is knowing how
On 17/03/14 01:28, Justin Mclean wrote:
Here's my second draft. It's now intended to be sent directly to all committers.
I think it's too long. You can condense the four lines about install
numbers to just the first one, for instance.
I'd dump everything from 'We know you are' onwards. You don
HI,
> If you supply a fix that isn;t perfect that's also good and other people get
> to see it and hopefully improve on it. I noticed Maurice correct some
> spelling issues and Americanised my spelling on a patch I added a while back
> today.
Sorry that should be "Americanized" :-)
Justin
Hi,
> Part of it is getting the right version, part of it is knowing how to make
> sure you didn't embarrass yourself with the fix.
Any fix is just a revert away - that's the great thing about version. I've
made plenty of mistakes so I wouldn't be concerned about breaking stuff :-)
> Knowing w
Good question, I'm not sure exactly.
Part of it is getting the right version, part of it is knowing how to make
sure you didn't embarrass yourself with the fix. Knowing what counts as a
fix. Other vague uncertainties.
If there was a way to pull, and then just commit with a message about which
jir
On 3/16/14 9:22 PM, "Justin Mclean" wrote:
>Hi,
>
>> I think the note should be a call to action without comments on
>>people's time commitment or how hard it is to find time,
>
>The initial draft was more like that but there were objections - so not
>sure which is the best way here.
>
>Thanks
Hi,
> I think the note should be a call to action without comments on people's time
> commitment or how hard it is to find time,
The initial draft was more like that but there were objections - so not sure
which is the best way here.
Thanks for the feedback.
Justin
Hi,
> A lot has been going on in Apache Flex in recent months. In case you
> haven't been following on the dev list, Here's a brief overview of the
> current state of the project and milestones since becoming a top level
> project.
That reads much better thanks.
> And I would add to the list o
I think the note should be a call to action without comments on people's time
commitment or how hard it is to find time, etc. it is to be expected that
Committers will fade away and new ones replace old.
There is a reason that merit does not expire. We always welcome people back and
gladly.
Re
Hmm. I still don't like the first line. The "it's been hardŠ" assumes
that folks think it has been hard. Also, please propose a subject as well.
Maybe "Apache Flex Progress Report"?
How about for the first two lines:
A lot has been going on in Apache Flex in recent months. In case you
haven't
Hi,
> flex.apage.org ?
Yep :-)
Thanks,
Justin
flex.apage.org ?
Typo...
-Original Message-
From: Justin Mclean [mailto:jus...@classsoftware.com]
Sent: Sunday, March 16, 2014 8:28 PM
To: dev@flex.apache.org
Subject: Re: Draft email to committers
Hi,
Here's my second draft. It's now intended to be sent directly to all
Hi,
Here's my second draft. It's now intended to be sent directly to all committers.
--- start draft ---
Hi Apache Flex Committer,
A lot has been going on in Apache Flex in recent months and it’s been hard to
keep up to date with all of the news.
Here's a brief overview of the current state of
Hi,
> So maybe we should remove the first sentence "we have noticed you have been
> doing nothing for a while"
> And maybe simply describe the situation and ask if people are still
> interested in the project, and the areas where help is needed.
>
> Maybe we should send to ALL committers, so t
Hi,
> As a lurker, I will just say that it's still rather "scary" to make an
> official JIRA, or patch, or whatever the process is.
What's scary about it you just need to attach a fix to a JIRA. Hopefully it
will be reviewed and added to the SKD by a committer will and if all test pass
it will s
> De : Jeffry Houser [mailto:jef...@dot-com-it.com]
> Envoyé : dimanche 16 mars 2014 16:46
> À : Maurice Amsellem
> Cc : dev@flex.apache.org
> Objet : Re: Draft email to committers
>
> On 3/16/2014 10:23 AM, Maurice Amsellem wrote:
> > I see your point.
> Thanks!
>
> >
up to date on recent developments:
Maurice
-Message d'origine-
De : Jeffry Houser [mailto:jef...@dot-com-it.com]
Envoyé : dimanche 16 mars 2014 16:46
À : Maurice Amsellem
Cc : dev@flex.apache.org
Objet : Re: Draft email to committers
On 3/16/2014 10:23 AM, Maurice Amsellem wrote:
> I s
I personally know tons of old Flex developers that for all intensive
purposes believe Flex is still "Dead". When I inform them of all the great
stuff you guys have been accomplishing, they always get excited. Everybody
still loves Flex, it just hasn't been cool, hip, and trendy since HTML 5!!!
came
Everyone's workload ebbs and flows. Sending out nagging messages isn't
going to help that. However a message that gets sent out with just
positive updates / messages I'm fine.
-Mark
On 3/16/2014 10:23 AM, Maurice Amsellem wrote:
I see your point.
Thanks!
Maybe we should send to ALL committers, so that no-one feels "uncomfortable"
with that.
I thought it was the original intent to send to all committers.
WDYT?
I don't understand why the email needs to be sent at al
-it.com]
Envoyé : dimanche 16 mars 2014 14:58
À : dev@flex.apache.org
Objet : Re: Draft email to committers
On 3/16/2014 9:41 AM, Justin Mclean wrote:
> Hi,
>
>> I do not think the PMC--as a group--should be sending out emails like the
>> one you posted.
> Can expand on why?
On 3/16/2014 9:41 AM, Justin Mclean wrote:
Hi,
I do not think the PMC--as a group--should be sending out emails like the one
you posted.
Can expand on why? Email private@ or me off list if you feel for some reason it
shouldn't be discussed on this list.
I'm not sure what to expand upon beyo
Hi,
> I do not think the PMC--as a group--should be sending out emails like the one
> you posted.
Can expand on why? Email private@ or me off list if you feel for some reason it
shouldn't be discussed on this list.
Thanks,
Justin
>
> it is one of the PMC's duties to try to get as much people to
>> contribute to the project as possible.
>>
> Are you sure?
> I do not see that listed anywhere in Apache's PMC Guidelines:
> https://www.apache.org/dev/pmc.html
You are kidding, right? If "proper management and oversight" doe
On 3/16/2014 3:37 AM, Erik de Bruin wrote:
it is one of the PMC's duties to try to get as much people to
contribute to the project as possible.
Are you sure?
I do not see that listed anywhere in Apache's PMC Guidelines:
https://www.apache.org/dev/pmc.html
--
Jeffry Houser
Technical Entrepr
As a lurker, I will just say that it's still rather "scary" to make an
official JIRA, or patch, or whatever the process is. The bureaucracy itself
is rather scary to be honest.
brought to you by the letters A, V, and I
and the number 47
On Sun, Mar 16, 2014 at 3:11 PM, Jeffry Houser wrote:
> On
On 3/15/2014 9:13 PM, Justin Mclean wrote:
What changes do you think are required for it to sent from the PMC?
Thanks, Justin
I do not think the PMC--as a group--should be sending out emails like
the one you posted.
--
Jeffry Houser
Technical Entrepreneur
http://www.jeffryhouser.com
203-37
Let's not discuss this to death, please.
I very much like Justin's proposal. I think that he can sign on behalf of
the PMC, as it is one of the PMC's duties to try to get as much people to
contribute to the project as possible. As a PMC member you can't be against
an effort to get people to contri
On 3/15/14 11:22 PM, "Justin Mclean" wrote:
>Hi,
>
>> I see. Well, it sounds like a few PMC members are uncomfortable with it
>> being signed by the PMC.
>One so far yes but that's the only objection so far. I'd put it to a vote
>with a veto before sending out but would like to see what other
Hi,
> I see. Well, it sounds like a few PMC members are uncomfortable with it
> being signed by the PMC.
One so far yes but that's the only objection so far. I'd put it to a vote with
a veto before sending out but would like to see what other people think first.
Thanks,
Justin
On 3/15/14 10:51 PM, "Justin Mclean" wrote:
>Hi,
>
>> I think if they are still lurking you have already gotten their
>>attention.
>> If they are not listening at all, this won't help. I'm not clear a
>> signature from the PMC will be a difference maker.
>I wasn't going to send the email to th
Hi,
> I think if they are still lurking you have already gotten their attention.
> If they are not listening at all, this won't help. I'm not clear a
> signature from the PMC will be a difference maker.
I wasn't going to send the email to the list but directly to them - they may no
longer be sub
On 3/15/14 6:13 PM, "Justin Mclean" wrote:
>Hi,
>
>> As you know, we are all 'individuals' with differing priorities,
>>schedules, and responsibilities.
>Sure and they are free to ignore the email if they are unable to help but
>I do think the email needs to be from the PMC.
I think if they are
Hi,
> We need more examples for the community showcase
> => how could the committers contribute to that ?
Most committers are users of the SDK as well and would of been involved in many
project some of which I'm sure are suitable to the community showcase.
> Also, I would say help should not be
Hi,
> As you know, we are all 'individuals' with differing priorities, schedules,
> and responsibilities.
Sure and they are free to ignore the email if they are unable to help but I do
think the email needs to be from the PMC.
> Don't try to make it sound like the Apache Flex PMC is trying to
" for modem mobile OS versions" => modern.
We need more examples for the community showcase
=> how could the committers contribute to that ?
Also, I would say help should not be limited to these tasks.
Committers are also welcome to contribute in other ways (add new components,
improve existing
I have a sense of discomfort signing such an email from the Apache
Flex PMC Team.
As you know, we are all 'individuals' with differing priorities,
schedules, and responsibilities.
If you wish to 'rally the troops' to get certain things done; great.
But, sign your own name. Don't try t
50 matches
Mail list logo
