Dear Ted and Ross,
Thanks so much for your kind inputs and guidance.
The idea behind having this hierarchy was to manage the smooth functioning
of the ALC chapters and to address the following responsibilities.
-- New ALC Chapter formation
As mentioned, if ALC chapter doesn't exist in any town,
On 8/6/19 2:54 AM, Christopher wrote:
The new reporter wizard helps folks create a board report, but it
doesn't seem to have any of the other features of the current
reporeter.a.o tool. For example, helping them to manage recorded
releases (https://reporter.apache.org/addrelease.html?), view
comm
+1
ASF is a flat organization - by design. This proposal adds a level of hierarchy
without justifying the need for it.
If people are unable to conduct the business of this proposed structure within
ComDev and/or VP Conferences then fix that, don't work around it.
So, as Ted asks "Why is all th
This ALC stuff looks like a way to have local meetups.
Why is all this organizational hierarchy needed?
Why not just have meetups?
On 2019/08/01 13:29:41, Swapnil M Mane wrote:
> Dear all,
>
> Hope you are doing good.
> Thanks, everyone who shared their kind thoughts on ALC proposal [1].
>
On Mon, Aug 5, 2019 at 5:54 PM Christopher wrote:
>
> The new reporter wizard helps folks create a board report, but it
> doesn't seem to have any of the other features of the current
> reporeter.a.o tool. For example, helping them to manage recorded
> releases (https://reporter.apache.org/addrele
The new reporter wizard helps folks create a board report, but it
doesn't seem to have any of the other features of the current
reporeter.a.o tool. For example, helping them to manage recorded
releases (https://reporter.apache.org/addrelease.html?), view
community health score (https://reporter.apa
[
https://issues.apache.org/jira/browse/COMDEV-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved COMDEV-286.
-
Resolution: Fixed
Projects have updated their DOAPs
> Projects Directory: multiple case for JavaScript language
[
https://issues.apache.org/jira/browse/COMDEV-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved COMDEV-319.
-
Resolution: Fixed
Code was updated to use new ldap_info module
> Use Whimsy JSON data instead of ldapsearch
> --
[
https://issues.apache.org/jira/browse/COMDEV-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved COMDEV-299.
-
Resolution: Invalid
Sorry, we cannot help.
This is nothing to do with the Apache Software Foundation.
> appthol
[
https://issues.apache.org/jira/browse/COMDEV-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb updated COMDEV-315:
Component/s: Comdev
> Fix Russian translation for Apache Brochure
> ---
>
>
[
https://issues.apache.org/jira/browse/COMDEV-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16900312#comment-16900312
]
Sebb commented on COMDEV-315:
-
This relates to https://svn.apache.org/repos/asf/comdev/marke
[
https://issues.apache.org/jira/browse/COMDEV-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb updated COMDEV-326:
Component/s: Website
> Committer invite template omits PMC role details
> -
As the subject says.
It might be easier to manage the issues if there were separate JIRAs
for COMDEV and GSOC.
S.
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community
Can anything be done to close the COMDEV GSoC entries that have expired?
i.e. GSoC 2018 and earlier?
There seems little point in keeping them open now.
S.
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additi
[
https://issues.apache.org/jira/browse/COMDEV-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb updated COMDEV-247:
Summary: GSoc2018 SkyWalking project: Develop RabbitMQ plugin (was:
SkyWalking project: Develop RabbitMQ plugin)
[
https://issues.apache.org/jira/browse/COMDEV-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb updated COMDEV-256:
Summary: GSoC Allura - importers / sync for Bitbucket and Gitlab (was:
Allura - importers / sync for Bitbucket and
[
https://issues.apache.org/jira/browse/COMDEV-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb updated COMDEV-217:
Summary: GSoc AJP client library and command line tools (was: AJP client
library and command line tools)
> GSoc A
[
https://issues.apache.org/jira/browse/COMDEV-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb updated COMDEV-249:
Summary: GSoC [RocketMQ]Message Delivery Once Semantic Implementation
(was: [RocketMQ]Message Delivery Once Semant
[
https://issues.apache.org/jira/browse/COMDEV-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb updated COMDEV-309:
Summary: GSoC2019 Implement C++ database client adapters for Apache Arrow
(was: Implement C++ database client adap
[
https://issues.apache.org/jira/browse/COMDEV-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved COMDEV-324.
-
Resolution: Invalid
See https://github.com/apache/cordova-ios/issues/634
> IOS app crashes on multiple upload of
Sebb created COMDEV-326:
---
Summary: Committer invite template omits PMC role details
Key: COMDEV-326
URL: https://issues.apache.org/jira/browse/COMDEV-326
Project: Community Development
Issue Type: Bug
[
https://issues.apache.org/jira/browse/COMDEV-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved COMDEV-325.
Resolution: Fixed
Yep.. Fixed. Thanks!
> New "wizard" missing one of my projects...
> ---
[
https://issues.apache.org/jira/browse/COMDEV-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16900194#comment-16900194
]
Daniel Gruno commented on COMDEV-325:
-
There was some missing mapping from ws to webs
[
https://issues.apache.org/jira/browse/COMDEV-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb moved WHIMSY-287 to COMDEV-325:
Component/s: (was: General)
Reporter Tool
Workflow: classic def
Hey Mandi,
Are you any good at creating presentation templates? I believe at this
point we do not yet have presentation templates for either of the two
ApacheCons.
And of course anything you can do to promote ApacheCon is very much
appreciated. This year at ApacheCon Europe in Berlin we have a
On 8/5/19 10:53 AM, Myrle Krantz wrote:
Since it's the PMC chairs who use this, I'd much prefer you put this call
for consensus up over on board@.
mkay, let's do both! :D
Best,
Myrle
On Mon, Aug 5, 2019 at 10:41 AM Daniel Gruno wrote:
Hi folks,
I would like to change the default reporter
Since it's the PMC chairs who use this, I'd much prefer you put this call
for consensus up over on board@.
Best,
Myrle
On Mon, Aug 5, 2019 at 10:41 AM Daniel Gruno wrote:
> Hi folks,
> I would like to change the default reporter.a.o[1] to be the new wizard
> tool[2]. I think it's a good overall
Hi folks,
I would like to change the default reporter.a.o[1] to be the new wizard
tool[2]. I think it's a good overall improvement and honestly do not see
any downsides to switching. So I'm calling a lazy consensus "vote" for
this change. If there are people that strongly prefer the old one,
p
Hi Myrle and Sharan,
Thank you very much!
Best, Fabian
Am So., 4. Aug. 2019 um 19:04 Uhr schrieb sharanf :
> Hi Myrle
>
> Sorry I missed it. I can do it and will also see I can add you with
> admin for the calendar. The more the merrier :-)
>
> Thanks
> Sharan
>
> On 2019-08-04 17:44, Myrle Kr
29 matches
Mail list logo
