Re: Hello Apache Cordova- I am looking to contribute an article

[Javier Galindo]

Thanks For You.r Support Apache Cordova Sincerity Javier Galindo
Javier GalindoSent from my LG Mobile
-- Original message--From: Bertrand DelacretazDate: Fri, Sep 14, 2018 
6:46 AMTo: dev;Cc: Subject:Re: Hello Apache Cordova- I am looking to contribute 
an article
Hi,

On Fri, Sep 14, 2018 at 1:44 PM Charles Watson
 wrote:
> ...My name is Charles, I was wondering if Apache Cordova
>  was accepting contributor
> articles...

This list is for Apache-wide community topics, for Cordova please use
their Dev mailing list, https://cordova.apache.org/contact/

-Bertrand

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Keeping PMC communications public when possible -- is pmcs@ responsible?

[sebb]

On 14 September 2018 at 12:21, Rich Bowen  wrote:
> You are definitely not wrong. Two observations I'd make:
>
> 1) We should avoid sending anything to the pmc lists that isn't actually
> private, as you say. And the pmc members are all (probably? Should be?)
> also on the dev list.
>
> 2) if one uses an alias that forwards to multiple other lists, always
> explain in the message why they're getting it. Like "you are receiving this
> because you're subscribed to an Apache dev mailing list". This seems to
> reduce the angry responses considerably.
>
> Since your earlier note I have consciously avoided using the pmc lists and
> used dev lists instead.
>
> I'm not personally a fan of remaining lists but I can't say I strongly

renaming?

> object to it either. Just one more thing to relearn.

It should be possible to replace pmcs@ with an auto responder giving
the new alias names, and what they should be used for.

So there would be no need to remember the new alias.

Unfortunately not all PMCs have dev@ lists, but it should not be too
difficult to allow for this.

There is also ppmcs@, which is private@podlings.
This should be treated the same as pmcs@

>
>
>
> On Fri, Sep 14, 2018, 07:07 Julian Foad  wrote:
>
>> TL;DR: Is the "pmcs@" alias the root of the problem? Need "pmcs-private@"
>> and "pmcs-public@"?
>>
>> Rich Bowen wrote:
>> > I'm going to go out on a limb and guess that you've never sent an email
>> > message to all of the Apache dev lists.
>> > [It] *always* results in at least one angry response, and usually a lot
>> of them.
>>
>> You're right -- I haven't. If that happens, it sounds like the work on
>> Community Development is not yet finished, sadly. Anger distresses me even
>> when I know it's not really personal, so I would find that concerning. But
>> that's a digression, not the end of the matter.
>>
>> And I have some more insights now.
>>
>> Another non-private email recently came to private@, and the originator
>> referred to sending email "to the PMCs".
>> I don't know but suspect that they emailed the "pmcs@" alias in order to
>> email "the PMCs". That sounds like a recipe for confusion.
>>
>> I discovered that in 2005 a resolution [3] was passed to rename all the
>> mailing lists formerly called "p...@project.apache.org" (which were
>> already private) to "priv...@project.apache.org" and to use these only
>> for strictly private matters. This resolution is incorporated in the PMC
>> Required Policies [2] and referred to in [1].
>>
>> However, the "pmcs@" alias escaped the renaming and now points to all the
>> "private@" lists. It should therefore only be used for strictly private
>> matters, which is not suggested by its name. People aren't easily going to
>> learn that. It seems to me it would be a good idea to rename that alias to
>> something like "pmcs-private@" and remove "pmcs@".
>>
>> For matters which we wish to address to PMCs but need not be private, we
>> should have some other alias: "pmcs-public@"? This should point to each
>> project's most appropriate public mailing list. This would be "dev@" for
>> Apache Subversion and probably for most projects, while any project could
>> potentially use a public list that is separate from their dev list if they
>> wished (although I vaguely recall recommendations to keep both kinds of
>> discussions together for the sake of community over code).
>>
>> Although this is a fairly infrequent and individually small matter, it
>> appears to be causing unintended contraventions of the ASF policies and I
>> feel it contributes negatively to the Way by habituating people to
>> discussing matters in private.
>>
>> Thoughts, anyone? Is this something we could improve, perhaps quite easily?
>>
>>
>> [1] https://www.apache.org/foundation/how-it-works.html#confidential
>> [2] https://www.apache.org/dev/pmc.html#mailing-list-private
>> [3]
>> https://whimsy.apache.org/board/minutes/Rename_pmc_lists_to_private.html
>>
>> --
>> - Julian
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>> For additional commands, e-mail: dev-h...@community.apache.org
>>
>>

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Volunteers needed for reg desk at ApacheCon

[Rich Bowen]

If you're willing, please sign up at 
https://docs.google.com/document/d/1XZcY8R4PccDHyzA9gQpDhvFpAP5JVr-6gcB4tlRWBeU/edit



On 9/14/18 2:33 PM, Rich Bowen wrote:
If you'll be at ApacheCon, and are willing to take a couple of hours on 
the registration desk, please let me know.


Duties mostly include sitting there and smiling, checking people in and 
issuing badges, and telling people where the Viger B room is and where 
the restrooms are.


--Rich




--
Rich Bowen - rbo...@rcbowen.com
http://rcbowen.com/
@rbowen

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: ASF OFBiz instance for stuff ordering, shipping and tracking

[Kevin A. McGrail]

Out of interest, I am naive about OfBiz.  How could it help fundraising?  I
have resources to spin it up and we are looking at things like CRMs but I
know we are looking for example to improve our onboarding process.

Love to get some help on that and I can throw resources at it.

Regards,
KAM
On Fri, Sep 14, 2018, 09:21 Rich Bowen  wrote:

>
>
> On 9/14/18 7:50 AM, Pierre Smits wrote:
> > What are your thoughts on this?
>
> The OFBiz community has, on a number of occasions over the years,
> offered to spin up services to support various aspects of the ASF. It
> always seems to break down on two points: Where will this be hosted? Who
> will do the work?
>
> So, yes, enthusiastically +1 to the concept, but I have to admit that
> I'm skeptical as to it actually happening.
>
> --
> Rich Bowen - rbo...@rcbowen.com
> http://rcbowen.com/
> @rbowen
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Volunteers needed for reg desk at ApacheCon

[Rich Bowen]

If you'll be at ApacheCon, and are willing to take a couple of hours on 
the registration desk, please let me know.


Duties mostly include sitting there and smiling, checking people in and 
issuing badges, and telling people where the Viger B room is and where 
the restrooms are.


--Rich


--
Rich Bowen - rbo...@rcbowen.com
http://rcbowen.com/
@rbowen

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Volunteer needed to update archive.apachecon.com

[Rich Bowen]

We need someone to dig in and update archive.apachecon.com - 
https://svn.apache.org/repos/infra/apachecon/archive.apachecon.com - to 
reflect current reality.


Thanks.

--
Rich Bowen - rbo...@rcbowen.com
http://rcbowen.com/
@rbowen

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: ASF OFBiz instance for stuff ordering, shipping and tracking

[Rich Bowen]

On 9/14/18 7:50 AM, Pierre Smits wrote:

What are your thoughts on this?


The OFBiz community has, on a number of occasions over the years, 
offered to spin up services to support various aspects of the ASF. It 
always seems to break down on two points: Where will this be hosted? Who 
will do the work?


So, yes, enthusiastically +1 to the concept, but I have to admit that 
I'm skeptical as to it actually happening.


--
Rich Bowen - rbo...@rcbowen.com
http://rcbowen.com/
@rbowen

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: ASF OFBiz instance for stuff ordering, shipping and tracking

[Daniel Ruggeri]

Hi, Pierre;

   Interesting that you mention this - I had reached out to Sharan a
little while ago to inquire if OFBiz might be a tool we would want to
use for managing our fundraising day-to-day workflow. I must confess
that I lost focus on that effort, but came to see that it certainly
seems possible.

   So, aside from the idea of physical order lifecycle management, I
would be game for doing a POC of sorts for OFBiz as a CRM type of tool, too.

-- 
Daniel Ruggeri

On 9/14/2018 6:50 AM, Pierre Smits wrote:
> Hi all,
>
> This may not be the correct ml, but please forgive me.
>
> With the advent of the upcoming ACNA18 (plus other - planned -  future US
> and EU roadshows, collaborations with other event producers, like FOSDEM,
> etc. and the prospective ACEU19) I foresee an uptake in ordering, shipping
> & receiving, and tracking of ASF stuff [2].
>
> Currently we maintain (dare I say haphazardly?) our inventory via a page in
> confluence (see [1]) and the processes for requesting, ordering, shipping
> (including drop-shipping) & receiving ASF stuff are happening in various
> MLs and other comm channels (hip chat) and the procedures seem informal as
> well.
>
> Also, we are increasingly communicating/promoting that products like
> project specific consumables (powered-by stickers, business-cards etc.),
>  can be ordered/requested for 3rd party events, etc..
>
> With the recently - informally - announced image site by Daniel (Gruno) [3]
> we now have about approx 500 project logo and PB images that can be
> requested in various sizes.
> Combining all of the above we're potentially talking about dozens, if not
> hundreds, individual transactions for requesting, ordering, shipping,
> receiving, etc. over the course of the coming years
>
> I would think that an ASF specific OFBiz instance (to work with the
> aforementioned repo of - approved - images) could be of benefit here. With
> this we could have one (front-/back-end) location/solution where:
>
>1. (initially) approved parties could:
>1. order from suppliers to deliver to the - various - keepers (as listed
>   in [1]) and future keepers;
>   2. as ASF 3rd party event-coordinators, could order for the event
>   their coordinating to deliver directly (drop-shipment) to the event
>   location;
>   3. confirm receipt of shipped goods;
>   4. transfer inventory items from one keeper to another, with
>   automatic service orders for e.g. DHL, UPS, etc.;
>   5. have an approval process (for budget holders) in place for
>[#2],[#4] with automatic invoices to be sent to the Treasurer/Virtual
>   (and/or other stakeholders)
>   6. keep track of what the ASF has in stock/use at event/keeper
>   locations
>
>
> Of course, the above is only a short intro and there may be a lot of
> aspects that can/should be elaborated upon. I am happy to address such
> questions and/or remarks (from the various stakeholders) to see whether a
> PoC could establish additional insights.
>
> What are your thoughts on this?
>
>
> [1]
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=81789772
> [2] ASF consumables like stickers, bracelets, leaflets, etc., and ASF
> non-consumables like the feather, banners, recorders, etc.
> [3] http://www.apache.org/logos/
>
> Best regards,
>
> Pierre Smits
>
> *Apache Trafodion , Vice President*
> *Apache Directory , PMC Member*
> Apache Incubator , committer
> *Apache OFBiz , contributor (without privileges)
> since 2008*
> Apache Steve , committer
>


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Hello Apache Cordova- I am looking to contribute an article

[Swapnil M Mane]

Dear Charles,

Welcome to the Apache Community!
Every Apache project has it's own mailing list. To communicate with Cordova
Devs, please use Cordova's mailing list [1].

[1] https://cordova.apache.org/contact/


- Best Regards,
Swapnil M Mane,
HotWax Systems 

On Fri, Sep 14, 2018 at 5:14 PM Charles Watson 
wrote:

>  Hello friends at Apache Cordova,
>
> My name is Charles, I was wondering if Apache Cordova
>  was accepting contributor
> articles. I have a background in journalism and have an English degree from
> Central Michigan University. I am looking to expand my portfolio and I
> thought I would be a good match for your site.
>
> I am open to additional assignments and maybe even the chance to become a
> contributor.
>
> Also, are there any guidelines for me to check out?
>
> I look forward to working with you,
>
> --
> Charles L. Watson
>
> Twitter  | Published Work
> 
>

ASF OFBiz instance for stuff ordering, shipping and tracking

[Pierre Smits]

Hi all,

This may not be the correct ml, but please forgive me.

With the advent of the upcoming ACNA18 (plus other - planned -  future US
and EU roadshows, collaborations with other event producers, like FOSDEM,
etc. and the prospective ACEU19) I foresee an uptake in ordering, shipping
& receiving, and tracking of ASF stuff [2].

Currently we maintain (dare I say haphazardly?) our inventory via a page in
confluence (see [1]) and the processes for requesting, ordering, shipping
(including drop-shipping) & receiving ASF stuff are happening in various
MLs and other comm channels (hip chat) and the procedures seem informal as
well.

Also, we are increasingly communicating/promoting that products like
project specific consumables (powered-by stickers, business-cards etc.),
 can be ordered/requested for 3rd party events, etc..

With the recently - informally - announced image site by Daniel (Gruno) [3]
we now have about approx 500 project logo and PB images that can be
requested in various sizes.
Combining all of the above we're potentially talking about dozens, if not
hundreds, individual transactions for requesting, ordering, shipping,
receiving, etc. over the course of the coming years

I would think that an ASF specific OFBiz instance (to work with the
aforementioned repo of - approved - images) could be of benefit here. With
this we could have one (front-/back-end) location/solution where:

   1. (initially) approved parties could:
   1. order from suppliers to deliver to the - various - keepers (as listed
  in [1]) and future keepers;
  2. as ASF 3rd party event-coordinators, could order for the event
  their coordinating to deliver directly (drop-shipment) to the event
  location;
  3. confirm receipt of shipped goods;
  4. transfer inventory items from one keeper to another, with
  automatic service orders for e.g. DHL, UPS, etc.;
  5. have an approval process (for budget holders) in place for
   [#2],[#4] with automatic invoices to be sent to the Treasurer/Virtual
  (and/or other stakeholders)
  6. keep track of what the ASF has in stock/use at event/keeper
  locations


Of course, the above is only a short intro and there may be a lot of
aspects that can/should be elaborated upon. I am happy to address such
questions and/or remarks (from the various stakeholders) to see whether a
PoC could establish additional insights.

What are your thoughts on this?


[1]
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=81789772
[2] ASF consumables like stickers, bracelets, leaflets, etc., and ASF
non-consumables like the feather, banners, recorders, etc.
[3] http://www.apache.org/logos/

Best regards,

Pierre Smits

*Apache Trafodion , Vice President*
*Apache Directory , PMC Member*
Apache Incubator , committer
*Apache OFBiz , contributor (without privileges)
since 2008*
Apache Steve , committer

Hello Apache Cordova- I am looking to contribute an article

[Charles Watson]

 Hello friends at Apache Cordova,

My name is Charles, I was wondering if Apache Cordova
 was accepting contributor
articles. I have a background in journalism and have an English degree from
Central Michigan University. I am looking to expand my portfolio and I
thought I would be a good match for your site.

I am open to additional assignments and maybe even the chance to become a
contributor.

Also, are there any guidelines for me to check out?

I look forward to working with you,

-- 
Charles L. Watson

Twitter  | Published Work

Re: Keeping PMC communications public when possible -- is pmcs@ responsible?

[Rich Bowen]

You are definitely not wrong. Two observations I'd make:

1) We should avoid sending anything to the pmc lists that isn't actually
private, as you say. And the pmc members are all (probably? Should be?)
also on the dev list.

2) if one uses an alias that forwards to multiple other lists, always
explain in the message why they're getting it. Like "you are receiving this
because you're subscribed to an Apache dev mailing list". This seems to
reduce the angry responses considerably.

Since your earlier note I have consciously avoided using the pmc lists and
used dev lists instead.

I'm not personally a fan of remaining lists but I can't say I strongly
object to it either. Just one more thing to relearn.




On Fri, Sep 14, 2018, 07:07 Julian Foad  wrote:

> TL;DR: Is the "pmcs@" alias the root of the problem? Need "pmcs-private@"
> and "pmcs-public@"?
>
> Rich Bowen wrote:
> > I'm going to go out on a limb and guess that you've never sent an email
> > message to all of the Apache dev lists.
> > [It] *always* results in at least one angry response, and usually a lot
> of them.
>
> You're right -- I haven't. If that happens, it sounds like the work on
> Community Development is not yet finished, sadly. Anger distresses me even
> when I know it's not really personal, so I would find that concerning. But
> that's a digression, not the end of the matter.
>
> And I have some more insights now.
>
> Another non-private email recently came to private@, and the originator
> referred to sending email "to the PMCs".
> I don't know but suspect that they emailed the "pmcs@" alias in order to
> email "the PMCs". That sounds like a recipe for confusion.
>
> I discovered that in 2005 a resolution [3] was passed to rename all the
> mailing lists formerly called "p...@project.apache.org" (which were
> already private) to "priv...@project.apache.org" and to use these only
> for strictly private matters. This resolution is incorporated in the PMC
> Required Policies [2] and referred to in [1].
>
> However, the "pmcs@" alias escaped the renaming and now points to all the
> "private@" lists. It should therefore only be used for strictly private
> matters, which is not suggested by its name. People aren't easily going to
> learn that. It seems to me it would be a good idea to rename that alias to
> something like "pmcs-private@" and remove "pmcs@".
>
> For matters which we wish to address to PMCs but need not be private, we
> should have some other alias: "pmcs-public@"? This should point to each
> project's most appropriate public mailing list. This would be "dev@" for
> Apache Subversion and probably for most projects, while any project could
> potentially use a public list that is separate from their dev list if they
> wished (although I vaguely recall recommendations to keep both kinds of
> discussions together for the sake of community over code).
>
> Although this is a fairly infrequent and individually small matter, it
> appears to be causing unintended contraventions of the ASF policies and I
> feel it contributes negatively to the Way by habituating people to
> discussing matters in private.
>
> Thoughts, anyone? Is this something we could improve, perhaps quite easily?
>
>
> [1] https://www.apache.org/foundation/how-it-works.html#confidential
> [2] https://www.apache.org/dev/pmc.html#mailing-list-private
> [3]
> https://whimsy.apache.org/board/minutes/Rename_pmc_lists_to_private.html
>
> --
> - Julian
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: Keeping PMC communications public when possible -- is pmcs@ responsible?

[Julian Foad]

TL;DR: Is the "pmcs@" alias the root of the problem? Need "pmcs-private@" and 
"pmcs-public@"?

Rich Bowen wrote:
> I'm going to go out on a limb and guess that you've never sent an email 
> message to all of the Apache dev lists.
> [It] *always* results in at least one angry response, and usually a lot of 
> them.

You're right -- I haven't. If that happens, it sounds like the work on 
Community Development is not yet finished, sadly. Anger distresses me even when 
I know it's not really personal, so I would find that concerning. But that's a 
digression, not the end of the matter.

And I have some more insights now.

Another non-private email recently came to private@, and the originator 
referred to sending email "to the PMCs".
I don't know but suspect that they emailed the "pmcs@" alias in order to email 
"the PMCs". That sounds like a recipe for confusion.

I discovered that in 2005 a resolution [3] was passed to rename all the mailing 
lists formerly called "p...@project.apache.org" (which were already private) to 
"priv...@project.apache.org" and to use these only for strictly private 
matters. This resolution is incorporated in the PMC Required Policies [2] and 
referred to in [1].

However, the "pmcs@" alias escaped the renaming and now points to all the 
"private@" lists. It should therefore only be used for strictly private 
matters, which is not suggested by its name. People aren't easily going to 
learn that. It seems to me it would be a good idea to rename that alias to 
something like "pmcs-private@" and remove "pmcs@".

For matters which we wish to address to PMCs but need not be private, we should 
have some other alias: "pmcs-public@"? This should point to each project's most 
appropriate public mailing list. This would be "dev@" for Apache Subversion and 
probably for most projects, while any project could potentially use a public 
list that is separate from their dev list if they wished (although I vaguely 
recall recommendations to keep both kinds of discussions together for the sake 
of community over code).

Although this is a fairly infrequent and individually small matter, it appears 
to be causing unintended contraventions of the ASF policies and I feel it 
contributes negatively to the Way by habituating people to discussing matters 
in private.

Thoughts, anyone? Is this something we could improve, perhaps quite easily?


[1] https://www.apache.org/foundation/how-it-works.html#confidential
[2] https://www.apache.org/dev/pmc.html#mailing-list-private
[3] https://whimsy.apache.org/board/minutes/Rename_pmc_lists_to_private.html

-- 
- Julian

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org