You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Brian LeRoux <b...@brian.io> on 2011/11/26 01:18:33 UTC
catchup phone call, issue gardening, group therapy session, planning
and updating
2011-11-28 at 11:00 AM.
https://www1.gotomeeting.com/join/207561816
Dial +1 (647) 724-3550
Access Code: 207-561-816
Meeting ID: 207-561-816
Re: catchup phone call, issue gardening, group therapy session,
planning and updating
Posted by Filip Maj <fi...@adobe.com>.
Thanks for keeping track Mike!
On 11-11-28 12:13 PM, "Michael Brooks" <mi...@michaelbrooks.ca> wrote:
>Below are the meeting notes from today's issue gardening call.
>
>There is also a gist rendered in markdown:
>https://gist.github.com/1401833
>
>Goals for the call
>==================
>
>- Disable issues on GitHub/PhoneGap
>- Mirror issues from GitHub/Callback to JIRA
>- Typical issue gardening (culling, assign, prioritize, and update)
>
>GitHub Issues
>=============
>
>- Our users are still logging issues under GitHub instead of JIRA
>- We do not want to force users to use JIRA, because they will simply stop
>logging issues
>- So, our maintainers will take on the responsibility of mirroring GitHub
>issues on JIRA. This includes comments.
>- We will need to transfer existing GitHub issues to JIRA
>- Brian will be creating JIRA issues to transfer these tickets
>
>Disabling GitHub/PhoneGap Issues
>================================
>
>- At the moment, user's are logging issues on both github.com/phonegap and
>github.com/callback
>- We will disable the github.com/phonegap issue tracker and make
>github.com/callback the only point of entry
>- Brian will create JIRA issues to do this for each platform
>
>Platform Specific Tasks
>=======================
>
>Android
>-------
>
>- Simon has already taken care of transferring issues from GitHub
>
>iOS
>---
>
>- JIRA issue for Shaz to transfer issues from GitHub
>- Becky is not on the call, so we will not be walking through the iOS
>issues
>
>BlackBerry
>----------
>
>- JIRA issue for Michael to transfer issues GitHub
>
>WP7
>---
>
>- JIRA issue for Jesse to transfer issues GitHub
>
>Docs
>----
>
>- Michael will move the existing GitHub issues to JIRA
>
>Side Discussions and TODOS
>==========================
>
>Renaming GitHub repositories
>----------------------------
>
>- Hold off on renaming Cordova until it's finalized
>- It's confusing enough for our users
>
>Committers and Contributors
>---------------------------
>
>- Brian will look into how to find a list of approved committers
>- Where "committers" are those who have signed the CLA
>- At the moment, we aren't sure how to check if someone has signed the
>Apache CLA
>
>PhoneGap Documentation
>----------------------
>
>- In the future, we need to create code style guides for each language
>
>White-listing
>-------------
>
>- We need to standardize the format for white-listing
>- We will open up a discussion on callback-dev about the format to use
>- We do not want to use a regex because each platform has a different
>parser
>
>Multiple Issue Trackers
>-----------------------
>
>- We should kick up a discussion on callback-dev about using both GitHub
>and JIRA or just JIRA
>- It's difficult to maintain both, but most of our community will not be
>interested in signing up for Apache Callback's JIRA to log a bug
>
>Copyright License
>-----------------
>
>- We need to remove copyright references in the license files
>- Brian will follow up with our release procedure
>
>On Sat, Nov 26, 2011 at 8:17 AM, Brian LeRoux <b...@brian.io> wrote:
>
>> Understood guys, and just to be clear:
>>
>> - everyone is invited; the time is usually agreed upon the week before
>> but we're going to kick up a vote thread for a common time
>> - we'll post notes, any actions taken will be public
>>
>> The main purpose is to quell our issue tracker and a quick phone call
>> is faster to get this done. For example, iOS has, as of the past month
>> or so, 41 issues. We will go through them as a group and discuss. Its
>> good for the devs on iOS, Android, Blackberry and Windows Phone to
>> understand the user community forces each is dealing with. Helps guide
>> our mutual understanding of what cross platform is.
>>
>> Again, anything seriously actionable will be made public, put to
>> proposal if necessary, and voted. Most of this stuff will be us
>> vetting issues, logged by the community, for validity. Often folks
>> will volunteer to work on them in the call. I'm going to assume that
>> much is ok.
>>
>>
>> On Sat, Nov 26, 2011 at 5:01 AM, Ross Gardler
>> <rg...@opendirective.com> wrote:
>> > Sent from my mobile device, please forgive errors and brevity.
>> > On Nov 26, 2011 12:42 PM, "Andrew Savory" <as...@apache.org> wrote:
>> >>
>> >> Hi,
>> >>
>> >> On 26 November 2011 10:04, Ross Gardler <rg...@opendirective.com>
>> > wrote:
>> >>
>> >>
>> >> > The important thing is that you have to work very hard to ensure
>>those
>> > who
>> >> > cannot attend are not excluded by that fact. I'll not be at the
>> > meeting, so
>> >> > I'll be watching carefully to see how you include me and others
>>like
>> me.
>> >> >
>> >>
>> >> As a followup to this and a second gentle nudge, you'll recall last
>> month:
>> >>
>> >
>>
>>http://apache.markmail.org/search/?q=org.apache.incubator.callback-dev#qu
>>ery:org.apache.incubator.callback-dev%20from%3A%22Brian%20LeRoux%22+page:
>>1+mid:hgwb5snb67qnpdbd+state:results
>> >>
>> >> Not wanting to sound like a broken record, but "if it didn't happen
>>on
>> the
>> >> mailing list then it didn't happen", so I'd really like to see some
>>sort
>> > of
>> >> brief summary of the call to help include the rest of the community
>>that
>> >> can't be on the call. It helps people to understand when decisions
>>were
>> >> made, why they were made, and once it's in the mail archive it
>>becomes a
>> >> useful part of the searchable history of the project. It also serves
>>as
>> > one
>> >> indicator to the wider community that there's activity in the
>>project,
>> >> clear governance and direction.
>> >
>> > I agree with the intent of Andrews comments. However, I must stress
>> > decisions cannot be made on these calls. They can come up with
>>proposals,
>> > but the decisions must be made enlist.
>> >
>> > To repeat: " if it didn't happen on the mailing list then it didn't
>> happen"
>> >
>> > Ross
>> >
>> >>
>> >> Also, you might want to mention what timezone the 11am call is at,
>>and
>> who
>> >> is invited (I assume it's open to the whole community since you're
>> posting
>> >> it here, but it would be good to be explicit for the avoidance of
>> doubt.)
>> >>
>> >> Cheers,
>> >>
>> >> Andrew.
>> >> --
>> >> asavory@apache.org / contact@andrewsavory.com
>> >> http://www.andrewsavory.com/
>> >
>>
Re: catchup phone call, issue gardening, group therapy session,
planning and updating
Posted by Michael Brooks <mi...@michaelbrooks.ca>.
Below are the meeting notes from today's issue gardening call.
There is also a gist rendered in markdown:
https://gist.github.com/1401833
Goals for the call
==================
- Disable issues on GitHub/PhoneGap
- Mirror issues from GitHub/Callback to JIRA
- Typical issue gardening (culling, assign, prioritize, and update)
GitHub Issues
=============
- Our users are still logging issues under GitHub instead of JIRA
- We do not want to force users to use JIRA, because they will simply stop
logging issues
- So, our maintainers will take on the responsibility of mirroring GitHub
issues on JIRA. This includes comments.
- We will need to transfer existing GitHub issues to JIRA
- Brian will be creating JIRA issues to transfer these tickets
Disabling GitHub/PhoneGap Issues
================================
- At the moment, user's are logging issues on both github.com/phonegap and
github.com/callback
- We will disable the github.com/phonegap issue tracker and make
github.com/callback the only point of entry
- Brian will create JIRA issues to do this for each platform
Platform Specific Tasks
=======================
Android
-------
- Simon has already taken care of transferring issues from GitHub
iOS
---
- JIRA issue for Shaz to transfer issues from GitHub
- Becky is not on the call, so we will not be walking through the iOS issues
BlackBerry
----------
- JIRA issue for Michael to transfer issues GitHub
WP7
---
- JIRA issue for Jesse to transfer issues GitHub
Docs
----
- Michael will move the existing GitHub issues to JIRA
Side Discussions and TODOS
==========================
Renaming GitHub repositories
----------------------------
- Hold off on renaming Cordova until it's finalized
- It's confusing enough for our users
Committers and Contributors
---------------------------
- Brian will look into how to find a list of approved committers
- Where "committers" are those who have signed the CLA
- At the moment, we aren't sure how to check if someone has signed the
Apache CLA
PhoneGap Documentation
----------------------
- In the future, we need to create code style guides for each language
White-listing
-------------
- We need to standardize the format for white-listing
- We will open up a discussion on callback-dev about the format to use
- We do not want to use a regex because each platform has a different parser
Multiple Issue Trackers
-----------------------
- We should kick up a discussion on callback-dev about using both GitHub
and JIRA or just JIRA
- It's difficult to maintain both, but most of our community will not be
interested in signing up for Apache Callback's JIRA to log a bug
Copyright License
-----------------
- We need to remove copyright references in the license files
- Brian will follow up with our release procedure
On Sat, Nov 26, 2011 at 8:17 AM, Brian LeRoux <b...@brian.io> wrote:
> Understood guys, and just to be clear:
>
> - everyone is invited; the time is usually agreed upon the week before
> but we're going to kick up a vote thread for a common time
> - we'll post notes, any actions taken will be public
>
> The main purpose is to quell our issue tracker and a quick phone call
> is faster to get this done. For example, iOS has, as of the past month
> or so, 41 issues. We will go through them as a group and discuss. Its
> good for the devs on iOS, Android, Blackberry and Windows Phone to
> understand the user community forces each is dealing with. Helps guide
> our mutual understanding of what cross platform is.
>
> Again, anything seriously actionable will be made public, put to
> proposal if necessary, and voted. Most of this stuff will be us
> vetting issues, logged by the community, for validity. Often folks
> will volunteer to work on them in the call. I'm going to assume that
> much is ok.
>
>
> On Sat, Nov 26, 2011 at 5:01 AM, Ross Gardler
> <rg...@opendirective.com> wrote:
> > Sent from my mobile device, please forgive errors and brevity.
> > On Nov 26, 2011 12:42 PM, "Andrew Savory" <as...@apache.org> wrote:
> >>
> >> Hi,
> >>
> >> On 26 November 2011 10:04, Ross Gardler <rg...@opendirective.com>
> > wrote:
> >>
> >>
> >> > The important thing is that you have to work very hard to ensure those
> > who
> >> > cannot attend are not excluded by that fact. I'll not be at the
> > meeting, so
> >> > I'll be watching carefully to see how you include me and others like
> me.
> >> >
> >>
> >> As a followup to this and a second gentle nudge, you'll recall last
> month:
> >>
> >
> http://apache.markmail.org/search/?q=org.apache.incubator.callback-dev#query:org.apache.incubator.callback-dev%20from%3A%22Brian%20LeRoux%22+page:1+mid:hgwb5snb67qnpdbd+state:results
> >>
> >> Not wanting to sound like a broken record, but "if it didn't happen on
> the
> >> mailing list then it didn't happen", so I'd really like to see some sort
> > of
> >> brief summary of the call to help include the rest of the community that
> >> can't be on the call. It helps people to understand when decisions were
> >> made, why they were made, and once it's in the mail archive it becomes a
> >> useful part of the searchable history of the project. It also serves as
> > one
> >> indicator to the wider community that there's activity in the project,
> >> clear governance and direction.
> >
> > I agree with the intent of Andrews comments. However, I must stress
> > decisions cannot be made on these calls. They can come up with proposals,
> > but the decisions must be made enlist.
> >
> > To repeat: " if it didn't happen on the mailing list then it didn't
> happen"
> >
> > Ross
> >
> >>
> >> Also, you might want to mention what timezone the 11am call is at, and
> who
> >> is invited (I assume it's open to the whole community since you're
> posting
> >> it here, but it would be good to be explicit for the avoidance of
> doubt.)
> >>
> >> Cheers,
> >>
> >> Andrew.
> >> --
> >> asavory@apache.org / contact@andrewsavory.com
> >> http://www.andrewsavory.com/
> >
>
Re: catchup phone call, issue gardening, group therapy session,
planning and updating
Posted by Brian LeRoux <b...@brian.io>.
Understood guys, and just to be clear:
- everyone is invited; the time is usually agreed upon the week before
but we're going to kick up a vote thread for a common time
- we'll post notes, any actions taken will be public
The main purpose is to quell our issue tracker and a quick phone call
is faster to get this done. For example, iOS has, as of the past month
or so, 41 issues. We will go through them as a group and discuss. Its
good for the devs on iOS, Android, Blackberry and Windows Phone to
understand the user community forces each is dealing with. Helps guide
our mutual understanding of what cross platform is.
Again, anything seriously actionable will be made public, put to
proposal if necessary, and voted. Most of this stuff will be us
vetting issues, logged by the community, for validity. Often folks
will volunteer to work on them in the call. I'm going to assume that
much is ok.
On Sat, Nov 26, 2011 at 5:01 AM, Ross Gardler
<rg...@opendirective.com> wrote:
> Sent from my mobile device, please forgive errors and brevity.
> On Nov 26, 2011 12:42 PM, "Andrew Savory" <as...@apache.org> wrote:
>>
>> Hi,
>>
>> On 26 November 2011 10:04, Ross Gardler <rg...@opendirective.com>
> wrote:
>>
>>
>> > The important thing is that you have to work very hard to ensure those
> who
>> > cannot attend are not excluded by that fact. I'll not be at the
> meeting, so
>> > I'll be watching carefully to see how you include me and others like me.
>> >
>>
>> As a followup to this and a second gentle nudge, you'll recall last month:
>>
> http://apache.markmail.org/search/?q=org.apache.incubator.callback-dev#query:org.apache.incubator.callback-dev%20from%3A%22Brian%20LeRoux%22+page:1+mid:hgwb5snb67qnpdbd+state:results
>>
>> Not wanting to sound like a broken record, but "if it didn't happen on the
>> mailing list then it didn't happen", so I'd really like to see some sort
> of
>> brief summary of the call to help include the rest of the community that
>> can't be on the call. It helps people to understand when decisions were
>> made, why they were made, and once it's in the mail archive it becomes a
>> useful part of the searchable history of the project. It also serves as
> one
>> indicator to the wider community that there's activity in the project,
>> clear governance and direction.
>
> I agree with the intent of Andrews comments. However, I must stress
> decisions cannot be made on these calls. They can come up with proposals,
> but the decisions must be made enlist.
>
> To repeat: " if it didn't happen on the mailing list then it didn't happen"
>
> Ross
>
>>
>> Also, you might want to mention what timezone the 11am call is at, and who
>> is invited (I assume it's open to the whole community since you're posting
>> it here, but it would be good to be explicit for the avoidance of doubt.)
>>
>> Cheers,
>>
>> Andrew.
>> --
>> asavory@apache.org / contact@andrewsavory.com
>> http://www.andrewsavory.com/
>
Re: catchup phone call, issue gardening, group therapy session,
planning and updating
Posted by Ross Gardler <rg...@opendirective.com>.
Sent from my mobile device, please forgive errors and brevity.
On Nov 26, 2011 12:42 PM, "Andrew Savory" <as...@apache.org> wrote:
>
> Hi,
>
> On 26 November 2011 10:04, Ross Gardler <rg...@opendirective.com>
wrote:
>
>
> > The important thing is that you have to work very hard to ensure those
who
> > cannot attend are not excluded by that fact. I'll not be at the
meeting, so
> > I'll be watching carefully to see how you include me and others like me.
> >
>
> As a followup to this and a second gentle nudge, you'll recall last month:
>
http://apache.markmail.org/search/?q=org.apache.incubator.callback-dev#query:org.apache.incubator.callback-dev%20from%3A%22Brian%20LeRoux%22+page:1+mid:hgwb5snb67qnpdbd+state:results
>
> Not wanting to sound like a broken record, but "if it didn't happen on the
> mailing list then it didn't happen", so I'd really like to see some sort
of
> brief summary of the call to help include the rest of the community that
> can't be on the call. It helps people to understand when decisions were
> made, why they were made, and once it's in the mail archive it becomes a
> useful part of the searchable history of the project. It also serves as
one
> indicator to the wider community that there's activity in the project,
> clear governance and direction.
I agree with the intent of Andrews comments. However, I must stress
decisions cannot be made on these calls. They can come up with proposals,
but the decisions must be made enlist.
To repeat: " if it didn't happen on the mailing list then it didn't happen"
Ross
>
> Also, you might want to mention what timezone the 11am call is at, and who
> is invited (I assume it's open to the whole community since you're posting
> it here, but it would be good to be explicit for the avoidance of doubt.)
>
> Cheers,
>
> Andrew.
> --
> asavory@apache.org / contact@andrewsavory.com
> http://www.andrewsavory.com/
Re: catchup phone call, issue gardening, group therapy session,
planning and updating
Posted by Andrew Savory <as...@apache.org>.
Hi,
On 26 November 2011 10:04, Ross Gardler <rg...@opendirective.com> wrote:
> The important thing is that you have to work very hard to ensure those who
> cannot attend are not excluded by that fact. I'll not be at the meeting, so
> I'll be watching carefully to see how you include me and others like me.
>
As a followup to this and a second gentle nudge, you'll recall last month:
http://apache.markmail.org/search/?q=org.apache.incubator.callback-dev#query:org.apache.incubator.callback-dev%20from%3A%22Brian%20LeRoux%22+page:1+mid:hgwb5snb67qnpdbd+state:results
Not wanting to sound like a broken record, but "if it didn't happen on the
mailing list then it didn't happen", so I'd really like to see some sort of
brief summary of the call to help include the rest of the community that
can't be on the call. It helps people to understand when decisions were
made, why they were made, and once it's in the mail archive it becomes a
useful part of the searchable history of the project. It also serves as one
indicator to the wider community that there's activity in the project,
clear governance and direction.
Also, you might want to mention what timezone the 11am call is at, and who
is invited (I assume it's open to the whole community since you're posting
it here, but it would be good to be explicit for the avoidance of doubt.)
Cheers,
Andrew.
--
asavory@apache.org / contact@andrewsavory.com
http://www.andrewsavory.com/
Re:catchup phone call, issue gardening, group therapy session,
planning and updating
Posted by Ross Gardler <rg...@opendirective.com>.
Apache projects do not do these kind of meetings, officially.
Of course it is silly to say they never happen. Some ASF people would say
"no you can't do it", I believe that would just result in such meetings not
being announced here, but still taking place. So I say "go ahead, but be
very careful."
The important thing is that you have to work very hard to ensure those who
cannot attend are not excluded by that fact. I'll not be at the meeting, so
I'll be watching carefully to see how you include me and others like me.
I'm happy to help you work on a strategy, but if you already have one from
your pre-incubator days I'm happy to see it in action before I interfere.
Ross
Sent from my mobile device, please forgive errors and brevity.
On Nov 26, 2011 12:19 AM, "Brian LeRoux" <b...@brian.io> wrote:
> 2011-11-28 at 11:00 AM.
>
> https://www1.gotomeeting.com/join/207561816
>
> Dial +1 (647) 724-3550
> Access Code: 207-561-816
> Meeting ID: 207-561-816
>
Re: catchup phone call, issue gardening, group therapy session, planning and updating
Posted by Michael Brooks <mi...@gmail.com>.
+1 I like
On 2011-11-25, at 6:48 PM, Simon MacDonald <si...@gmail.com> wrote:
> +1
>
> On Friday, November 25, 2011, Dave Johnson <da...@gmail.com> wrote:
>> can we schedule a monthly meeting of this sort so that it's easier for
>> people to make sure they are free?
>>
>> On Fri, Nov 25, 2011 at 4:18 PM, Brian LeRoux <b...@brian.io> wrote:
>>> 2011-11-28 at 11:00 AM.
>>>
>>> https://www1.gotomeeting.com/join/207561816
>>>
>>> Dial +1 (647) 724-3550
>>> Access Code: 207-561-816
>>> Meeting ID: 207-561-816
>>>
>>
>
> --
> Simon Mac Donald
> http://hi.im/simonmacdonald
Re: catchup phone call, issue gardening, group therapy session,
planning and updating
Posted by Simon MacDonald <si...@gmail.com>.
+1
On Friday, November 25, 2011, Dave Johnson <da...@gmail.com> wrote:
> can we schedule a monthly meeting of this sort so that it's easier for
> people to make sure they are free?
>
> On Fri, Nov 25, 2011 at 4:18 PM, Brian LeRoux <b...@brian.io> wrote:
>> 2011-11-28 at 11:00 AM.
>>
>> https://www1.gotomeeting.com/join/207561816
>>
>> Dial +1 (647) 724-3550
>> Access Code: 207-561-816
>> Meeting ID: 207-561-816
>>
>
--
Simon Mac Donald
http://hi.im/simonmacdonald
Re: catchup phone call, issue gardening, group therapy session,
planning and updating
Posted by Dave Johnson <da...@gmail.com>.
can we schedule a monthly meeting of this sort so that it's easier for
people to make sure they are free?
On Fri, Nov 25, 2011 at 4:18 PM, Brian LeRoux <b...@brian.io> wrote:
> 2011-11-28 at 11:00 AM.
>
> https://www1.gotomeeting.com/join/207561816
>
> Dial +1 (647) 724-3550
> Access Code: 207-561-816
> Meeting ID: 207-561-816
>