Re: Apache Local Community (ALC) Next Steps
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, the interested volunteer can contact ALC management committee. -- Reporting by ALC chapters To track the status, progress, and impact created by ALC chapter, the plan was, the ALC chapter will submit the status report to the ALC management committee in every three months. -- Guidance to ALC chapters The ALC chapters may have various queries and need guidance on topics like, like types of events that can be organized, how to organize any event, the format of the report to be submitted, etc. The idea was the ALC management committee will guide on this to ALC chapters. With your comments and suggestions, it makes sense to me that "we should be able to manage these things within ComDev and/or VP Conferences." So, I am now inclined towards, proceeding with the existing Apache structure and no longer need proposed 'Organizational Hierarchy'. We (ComDev) team can manage all the stuff mentioned above. Thanks again for sharing your valuable time! Best regards, Swapnil M Mane, www.apache.org On Tue, Aug 6, 2019 at 7:20 AM Ross Gardler wrote: > +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 this organizational hierarchy needed?" > > Ross > > > From: Ted Dunning > Sent: Monday, August 5, 2019 6:38 PM > To: dev@community.apache.org > Subject: Re: Apache Local Community (ALC) Next Steps > > > 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]. > > > > As a next step, we have documented various information, which will help > us > > in bringing ALC in action. > > > > # 1. ALC home page > > > https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FCOMDEV%2FApache%2BLocal%2BCommunity%2B-%2BALC&data=02%7C01%7C%7C5e171914f2b74a7239bf08d71a0ec644%7C84df9e7fe9f640afb435%7C1%7C0%7C637006523061433531&sdata=yXuLVZhp%2F%2Fieoq%2FUww1ImL9yBz2%2Fur6%2BJePP9FI7CLg%3D&reserved=0 > > > > > > This is the root wiki document for ALC and contains the following > > information > > -- About ALC > > -- ALC Roles and Responsibility > > -- How ALC Chapter will be formed > > -- Benefits of ALC > > -- Code of conduct > > -- Addition information > > -- Contact ALC > > > > # 2. ALC Resources > > > https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FCOMDEV%2FALC%2BResources&data=02%7C01%7C%7C5e171914f2b74a7239bf08d71a0ec644%7C84df9e7fe9f640afb435%7C1%7C0%7C637006523061433531&sdata=f8wsjmAxOvPURcR9%2B7dlcnbxKIkx9fFy%2BGpU%2BPzbEc4%3D&reserved=0 > > > > This document is used for collecting the information and resources > > (presentations, media, etc.) that will be helpful for ALC chapters. > > Currently, contain the following information > > -- Types of events organized by ALC Chapters > > -- Venue for the event > > -- Topics for the session > > > > # 3. ALC Chapters > > > https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FCOMDEV%2FALC%2BChapters&data=02%7C01%7C%7C5e171914f2b74a7239bf08d71a0ec644%7C84df9e7fe9f640afb435%7C1%7C0%7C637006523061443539&sdata=ZxM8gqhpEU3V%2FGxZvFnsphJI5TvFrn2oAIb2O3Wj8nM%3D&reserved=0 > > > > This wiki contains all the ALC Chapters detail. > > > > ## 3.1 ALC Indore > > > https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FCOMDEV%2FALC%2BIndore&data=02%7C01%7C%7C5e171914f2b74a7239bf08d71a0ec644%7C84df9e7fe9f640afb435%7C1%7C0%7C637006523061443539&sdata=kUlZcS7BLOV%2FUUtemIT3DWdHeJrhXB0VigAzhFRG9Co%3D&reserved=0 > > > > Each ALC Chapter will have its own wiki, which will contain details > > specific to that ALC Chapter. Since I am with Pranay Pandey starting the > > ALC Indore Chapter, thus created a wiki page for ALC Indore. > > Other chapters will also create their own wiki page. > > > > ### 3.1.1 ALC Indore Events > > > https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FCOMDEV%2FALC%2BIndore%2BEvents&data=02%7C01%7C%7C5e171914f2b74a7239bf08d71a0ec644%7C84df9e7fe9f640afb435%7C1%7C0%7C637006523061443539&sdata=eUJU%2BzGYHeEm%2Bp2k6%2Fomc2rKZ8J
Re: [Lazy Consensus] Changing the default reporter tool
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 community health score (https://reporter.apache.org/chi.py#), quickly view JIRA stats and PMC/committer changes, etc. Are all of those features available elsewhere, or will they be replaced by the new tool? Hi Christopher, I am wondering if you are perhaps looking at an older cached version of the tool? Or maybe I am misunderstanding what you mean by having the information available, but I'll attempt to answer in any case. PMC/committer changes should still very much be in the editor, under "Membership data", including new information bits such as the age of the project and the ratio between committers and pmc members. JIRA stats and a whole bunch of new stats, are available in the Community Health section, though they are not inserted into the report itself by default, as the board have expressed countless times that they do not wish to just see these figures, but rather a description of the significance of the numbers. When you are in the community health section, the right hand panel will display statistics such as: - jiras opened/closed - github prs/issues opened/closed - emails sent - commits done, committers active It will also allow you to see the most discussed issues/emails, and as a new thing, it will display how tickets/code/committer figures relate to the previous quarter. The 'Project activity' section lists recent releases or, in the case of no such things found, the last three releases, and has a link to managing the release data. As for the CHI score, we can have that displayed in the toolbut, it's a rather arbitrary figure that I made up, and it has caused some confusion in the past. Perhaps that warrants a longer discussion :) If, instead, you mean something along the lines of "I don't want help writing a report, I just want to casually look at the data available", perhaps what we could do is display that on a separate page that has the same information as the wizard, but just displays all the data on one big page? With regards, Daniel. On Mon, Aug 5, 2019 at 4: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 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, please do let me know, and please elaborate on what you'd like to see changed in the new tool for it to become the default. I'll let this run for a few days and see if anyone objects :) With regards, Daniel. [1] https://reporter.apache.org/ [2] https://reporter.apache.org/wizard/ - 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 - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Apache Local Community (ALC) Next Steps
+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 this organizational hierarchy needed?" Ross From: Ted Dunning Sent: Monday, August 5, 2019 6:38 PM To: dev@community.apache.org Subject: Re: Apache Local Community (ALC) Next Steps 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]. > > As a next step, we have documented various information, which will help us > in bringing ALC in action. > > # 1. ALC home page > https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FCOMDEV%2FApache%2BLocal%2BCommunity%2B-%2BALC&data=02%7C01%7C%7C5e171914f2b74a7239bf08d71a0ec644%7C84df9e7fe9f640afb435%7C1%7C0%7C637006523061433531&sdata=yXuLVZhp%2F%2Fieoq%2FUww1ImL9yBz2%2Fur6%2BJePP9FI7CLg%3D&reserved=0 > > > This is the root wiki document for ALC and contains the following > information > -- About ALC > -- ALC Roles and Responsibility > -- How ALC Chapter will be formed > -- Benefits of ALC > -- Code of conduct > -- Addition information > -- Contact ALC > > # 2. ALC Resources > https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FCOMDEV%2FALC%2BResources&data=02%7C01%7C%7C5e171914f2b74a7239bf08d71a0ec644%7C84df9e7fe9f640afb435%7C1%7C0%7C637006523061433531&sdata=f8wsjmAxOvPURcR9%2B7dlcnbxKIkx9fFy%2BGpU%2BPzbEc4%3D&reserved=0 > > This document is used for collecting the information and resources > (presentations, media, etc.) that will be helpful for ALC chapters. > Currently, contain the following information > -- Types of events organized by ALC Chapters > -- Venue for the event > -- Topics for the session > > # 3. ALC Chapters > https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FCOMDEV%2FALC%2BChapters&data=02%7C01%7C%7C5e171914f2b74a7239bf08d71a0ec644%7C84df9e7fe9f640afb435%7C1%7C0%7C637006523061443539&sdata=ZxM8gqhpEU3V%2FGxZvFnsphJI5TvFrn2oAIb2O3Wj8nM%3D&reserved=0 > > This wiki contains all the ALC Chapters detail. > > ## 3.1 ALC Indore > https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FCOMDEV%2FALC%2BIndore&data=02%7C01%7C%7C5e171914f2b74a7239bf08d71a0ec644%7C84df9e7fe9f640afb435%7C1%7C0%7C637006523061443539&sdata=kUlZcS7BLOV%2FUUtemIT3DWdHeJrhXB0VigAzhFRG9Co%3D&reserved=0 > > Each ALC Chapter will have its own wiki, which will contain details > specific to that ALC Chapter. Since I am with Pranay Pandey starting the > ALC Indore Chapter, thus created a wiki page for ALC Indore. > Other chapters will also create their own wiki page. > > ### 3.1.1 ALC Indore Events > https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FCOMDEV%2FALC%2BIndore%2BEvents&data=02%7C01%7C%7C5e171914f2b74a7239bf08d71a0ec644%7C84df9e7fe9f640afb435%7C1%7C0%7C637006523061443539&sdata=eUJU%2BzGYHeEm%2Bp2k6%2Fomc2rKZ8JIUsSK0BgxP4xQY%2Bo%3D&reserved=0 > > This document contains information about upcoming and past events organized > by ALC Indore Chapter. > > ### 3.1.2 ALC Indore Reports > https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FCOMDEV%2FALC%2BIndore%2BReports&data=02%7C01%7C%7C5e171914f2b74a7239bf08d71a0ec644%7C84df9e7fe9f640afb435%7C1%7C0%7C637006523061443539&sdata=rcnZlOOmSb4iDniQ0CeqcF94czggtw%2BcxKRsgVrZm%2BI%3D&reserved=0 > > The ALC Chapter shares the status report to the ALC Management Committee in > every two months. This wiki contains these reports. The report includes > details on the activities performed by the ALC Chapter and its impact. > > # 4 Reports > https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FCOMDEV%2FReports&data=02%7C01%7C%7C5e171914f2b74a7239bf08d71a0ec644%7C84df9e7fe9f640afb435%7C1%7C0%7C637006523061443539&sdata=yBMLzbVaCKpCujIdcpMUOhq3CyJVxiScMG8lu10ytjw%3D&reserved=0 > > This wiki contains the details of all the report shared to ALC Management > Committee by ALC Chapters. > > # 5 Organizational Hierarchy > https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FCOMDEV%2FOrganizational%2BHierarchy&data=02%7C01%7C%7C5e171914f2b74a7239bf08d71a0ec644%7C84df9e7fe9f640afb435%7C1%7C0%7C637006523061443539&sdata=4EPu7ePgrcrG1AdCv1%2BHcwlEBuzGyTbunRZZuT9mIr8%3D&r
Re: Apache Local Community (ALC) Next Steps
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]. > > As a next step, we have documented various information, which will help us > in bringing ALC in action. > > # 1. ALC home page > https://cwiki.apache.org/confluence/display/COMDEV/Apache+Local+Community+-+ALC > > > This is the root wiki document for ALC and contains the following > information > -- About ALC > -- ALC Roles and Responsibility > -- How ALC Chapter will be formed > -- Benefits of ALC > -- Code of conduct > -- Addition information > -- Contact ALC > > # 2. ALC Resources > https://cwiki.apache.org/confluence/display/COMDEV/ALC+Resources > > This document is used for collecting the information and resources > (presentations, media, etc.) that will be helpful for ALC chapters. > Currently, contain the following information > -- Types of events organized by ALC Chapters > -- Venue for the event > -- Topics for the session > > # 3. ALC Chapters > https://cwiki.apache.org/confluence/display/COMDEV/ALC+Chapters > > This wiki contains all the ALC Chapters detail. > > ## 3.1 ALC Indore > https://cwiki.apache.org/confluence/display/COMDEV/ALC+Indore > > Each ALC Chapter will have its own wiki, which will contain details > specific to that ALC Chapter. Since I am with Pranay Pandey starting the > ALC Indore Chapter, thus created a wiki page for ALC Indore. > Other chapters will also create their own wiki page. > > ### 3.1.1 ALC Indore Events > https://cwiki.apache.org/confluence/display/COMDEV/ALC+Indore+Events > > This document contains information about upcoming and past events organized > by ALC Indore Chapter. > > ### 3.1.2 ALC Indore Reports > https://cwiki.apache.org/confluence/display/COMDEV/ALC+Indore+Reports > > The ALC Chapter shares the status report to the ALC Management Committee in > every two months. This wiki contains these reports. The report includes > details on the activities performed by the ALC Chapter and its impact. > > # 4 Reports > https://cwiki.apache.org/confluence/display/COMDEV/Reports > > This wiki contains the details of all the report shared to ALC Management > Committee by ALC Chapters. > > # 5 Organizational Hierarchy > https://cwiki.apache.org/confluence/display/COMDEV/Organizational+Hierarchy > > This document details the Organizational Hierarchy structure for working of > Apache Local Community. > *Important Note* - This document is under review by Apache Community > Development PMC and not finalized yet. The ComDev PMC will take the final > decision on this. > > So, here is the documented hierarchy managed in confluence. > https://cwiki.apache.org/confluence/display/COMDEV/Apache+Local+Community+-+ALC > > Apache Local Community - ALC (Home page) > | ALC Resources > | ALC Chapters >| ALC Indore > | ALC Indore Events > | ALC Indore Reports > | [other ALC Chapter will for same hierarchy as ALC > Indore] > | Reports > | Organizational Hierarchy > > > Please have a look at this and share your valuable thoughts. > Please feel free to comments, we will be happy to incorporate your > suggestions in the ALC. > > [1] https://s.apache.org/t6nxd > > > Best regards, > Swapnil M Mane, > www.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [Lazy Consensus] Changing the default reporter tool
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/addrelease.html?), view > community health score (https://reporter.apache.org/chi.py#), > quickly view JIRA stats and PMC/committer changes, etc. > > Are all of those features available elsewhere, or will they be > replaced by the new tool? That was the exactly thing that came to mind, how about the actual widget be an action available from the ui where then it start the wizard to guide the creation of the report ? -- Luciano Resende http://twitter.com/lresende1975 http://lresende.blogspot.com/ - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [Lazy Consensus] Changing the default reporter tool
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.apache.org/chi.py#), quickly view JIRA stats and PMC/committer changes, etc. Are all of those features available elsewhere, or will they be replaced by the new tool? On Mon, Aug 5, 2019 at 4: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 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, > please do let me know, and please elaborate on what you'd like to see > changed in the new tool for it to become the default. > > I'll let this run for a few days and see if anyone objects :) > > With regards, > Daniel. > > [1] https://reporter.apache.org/ > [2] https://reporter.apache.org/wizard/ > > - > 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
[jira] [Resolved] (COMDEV-286) Projects Directory: multiple case for JavaScript language
[
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
> -
>
> Key: COMDEV-286
> URL: https://issues.apache.org/jira/browse/COMDEV-286
> Project: Community Development
> Issue Type: Bug
> Components: Projects Tool
>Reporter: Vincent Tuybens
>Priority: Trivial
>
> On Projects Directory Website, on Projects list by Programming Language :
> [https://projects.apache.org/projects.html?language]
> 2 "Javascript" groups : JavaScript + Javascript.
> Workaround :
> Request to owners the modification of balise on :
> [{color:#ff}http://milagro.incubator.apache.org/doap.rdf{color}]
> [{color:#ff}http://svn.apache.org/repos/asf/vcl/trunk/doap_vcl.rdf{color}]
>
> Possible Fix : scripts/cronjob/parsecommitteeinfo.py to manage character case.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Resolved] (COMDEV-319) Use Whimsy JSON data instead of ldapsearch
[ 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 > -- > > Key: COMDEV-319 > URL: https://issues.apache.org/jira/browse/COMDEV-319 > Project: Community Development > Issue Type: Task > Components: Reporter Tool >Reporter: Sebb >Priority: Minor > > Most of reporter.a.o uses the Whimsy JSON data files rather than ldapsearch. > Should fix addrelease.py and jiraversions.py to do likewise. > (This would have avoided COMDEV-318) -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Resolved] (COMDEV-299) appthology.net iCody
[ 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. > appthology.net iCody > > > Key: COMDEV-299 > URL: https://issues.apache.org/jira/browse/COMDEV-299 > Project: Community Development > Issue Type: Question >Reporter: Bruce Miller >Priority: Minor > > Developer has blocked my ip address and I cannot make contact. I use > appliction to read barcodes integrated in my website. I am happy to purchase > a license. This is the only contact that I have. I hope O am in the right > place. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Updated] (COMDEV-315) Fix Russian translation for Apache Brochure
[ 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 > --- > > Key: COMDEV-315 > URL: https://issues.apache.org/jira/browse/COMDEV-315 > Project: Community Development > Issue Type: Bug > Components: Comdev >Reporter: Dmitriy Pavlov >Assignee: Roman Shaposhnik >Priority: Major > > The Russian translation has a very messed up font kerning. > Related discussion: > https://lists.apache.org/thread.html/c926035ccb50282b9769770c8276c8c1f172ee6c68b32b37d6381cf7@%3Cdev.community.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-315) 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/marketing/brochure/ru/ > Fix Russian translation for Apache Brochure > --- > > Key: COMDEV-315 > URL: https://issues.apache.org/jira/browse/COMDEV-315 > Project: Community Development > Issue Type: Bug >Reporter: Dmitriy Pavlov >Assignee: Roman Shaposhnik >Priority: Major > > The Russian translation has a very messed up font kerning. > Related discussion: > https://lists.apache.org/thread.html/c926035ccb50282b9769770c8276c8c1f172ee6c68b32b37d6381cf7@%3Cdev.community.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Updated] (COMDEV-326) Committer invite template omits PMC role details
[ 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 > > > Key: COMDEV-326 > URL: https://issues.apache.org/jira/browse/COMDEV-326 > Project: Community Development > Issue Type: Bug > Components: Website > Environment: > https://community.apache.org/newcommitter.html#committer-invite-template >Reporter: Sebb >Priority: Major > > The committer invite template [1] is not very clear on the distinction > between an invitation as a committer, and invitation as a committer + PMC > member. > In particular, it describes the role of the committer, but largely ignores > the PMC role. > As a result, I have seen at least one acceptance reply that said "I accept to > become a committer" [2] - leaving unstated whether or not they agree to > become a PMC member. > I think any template needs to make very clear what is involved in the PMC > role, and also that the invitee has 3 choices: > - decline both invites > - accept the committer invite and decline the PMC invite > - accept both committer invite and PMC invite > [1] https://community.apache.org/newcommitter.html#committer-invite-template > [2] > https://lists.apache.org/thread.html/796c4b3e8c0f191add39c7d1b6cc154a5e316910df8120db1151c739@%3Cprivate.jackrabbit.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Should comdev and GSoC use different JIRA ids?
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.apache.org
GSoC2018 and earlier
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 additional commands, e-mail: dev-h...@community.apache.org
[jira] [Updated] (COMDEV-247) GSoc2018 SkyWalking project: Develop RabbitMQ plugin
[ 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) > GSoc2018 SkyWalking project: Develop RabbitMQ plugin > > > Key: COMDEV-247 > URL: https://issues.apache.org/jira/browse/COMDEV-247 > Project: Community Development > Issue Type: Improvement > Components: GSoC/Mentoring ideas >Reporter: Sheng Wu >Priority: Major > Labels: gsoc2018, mentor > > SkyWalking incubator project provides a auto instrument mechanism. The core > team has provide RocketMQ plugin already. And in Apache projects, there are > another two well known MQ projects: Kafka and RabbitMQ. > Tracing MQ is very important. And using RocketMQ as an example, it is > possible for a student. > The development Guide: > https://github.com/apache/incubator-skywalking/blob/master/docs/en/Plugin-Development-Guide.md > The RocketMQ plugin codes: > https://github.com/apache/incubator-skywalking/tree/master/apm-sniffer/apm-sdk-plugin/rocketMQ-4.x-plugin -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Updated] (COMDEV-256) GSoC Allura - importers / sync for Bitbucket and Gitlab
[ 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 Gitlab) > GSoC Allura - importers / sync for Bitbucket and Gitlab > --- > > Key: COMDEV-256 > URL: https://issues.apache.org/jira/browse/COMDEV-256 > Project: Community Development > Issue Type: New Feature > Components: GSoC/Mentoring ideas >Reporter: Dave Brondsema >Priority: Major > Labels: gsoc2018, mongodb, python > > Allura has a solid framework for doing imports, and has implemented this for > services like GitHub, Google Code and Trac. It covers aspects from > Git/Hg/SVN to tickets and wikis. > It would be great to enhance this to support importing & converting data from > Bitbucket and Gitlab. The level of integration & conversion may vary > depending on the format and structure of the services. > Beyond that, related improvements could be made in supporting ongoing > synchronization of Git/Hg/SVN repositories (not just a one-time import). Or > importers for JIRA, or improving importing of Allura's own formats. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Updated] (COMDEV-217) GSoc AJP client library and command line tools
[ 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 AJP client library and command line tools > -- > > Key: COMDEV-217 > URL: https://issues.apache.org/jira/browse/COMDEV-217 > Project: Community Development > Issue Type: New Feature > Components: GSoC/Mentoring ideas >Reporter: Mark Thomas >Priority: Major > Labels: gsoc, gsoc2017, gsoc2018 > > Apache Tomcat supports the AJP protocol for communication between reverse > proxies (httpd, IIS, etc) and Tomcat. It would be useful for various purposes > (bug investigation, testing, load testing, etc.) to have an wget/curl/ab etc. > equivalent for AJP. > A good starting point exists in the Apache JMeter project. This task is to > produce (probably but not necessarily starting from the JMeter code): > - A Java library that provides AJP client functionality > - integrate that client with JMeter > - provide a command line wrapper for that client library > and then use the library to (stress) test Tomcat's AJP implementations, > identify bugs and provide patches for those bugs. > For the history see https://bz.apache.org/bugzilla/show_bug.cgi?id=47242 -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Updated] (COMDEV-249) GSoC [RocketMQ]Message Delivery Once Semantic Implementation
[ 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 Semantic Implementation) > GSoC [RocketMQ]Message Delivery Once Semantic Implementation > > > Key: COMDEV-249 > URL: https://issues.apache.org/jira/browse/COMDEV-249 > Project: Community Development > Issue Type: Wish > Components: GSoC/Mentoring ideas >Reporter: vongosling >Priority: Major > > The duplicated messages will impose the extra cost if the user needs > non-repeating messages. > In most cases, the user needs to store the consumer records to determine if a > message is duplicated, and the store stage should guarantee consistency. So > we need to support a strict and non-redundant message delivery mechanism. > In this context, we hope to design a delivery once plugin, say, you could > design a global(but need raft guarantee multi-copy data) storage, using the > hooker of RocketMQ ConsumeMessageHook to finish the task. > -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Updated] (COMDEV-309) GSoC2019 Implement C++ database client adapters for Apache Arrow
[ 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 adapters for Apache Arrow) > GSoC2019 Implement C++ database client adapters for Apache Arrow > > > Key: COMDEV-309 > URL: https://issues.apache.org/jira/browse/COMDEV-309 > Project: Community Development > Issue Type: Improvement > Components: GSoC/Mentoring ideas >Reporter: Wes McKinney >Priority: Major > Labels: gsoc2019 > > A self contained and useful summer project would be building a bridge between > SQLite3 or libpq within the Arrow C++ project -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Resolved] (COMDEV-324) IOS app crashes on multiple upload of files
[ 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 files > --- > > Key: COMDEV-324 > URL: https://issues.apache.org/jira/browse/COMDEV-324 > Project: Community Development > Issue Type: Question > Environment: -IOS > -Reactjs and Redux > >Reporter: mehthab >Priority: Critical > Labels: cordova, ios, reactjs, redux > > IOS app crashes when uploading multiple file(especially those captured in iOS > camera). > i created the Cordova project using > -Reactjs and Redux > -Axios for server calls > the App crashes when there is too much to sent to server side.for eg: App > crashed when i upload more than 10 photos at time, but wont have any issue > when uploading less than 8 photos. > in Xcode its showing there is a memory pressure and app gets crashed. > So i don't know how to debug this, tried to cut down memory leak by reducing > the loops. > but still no hope > has anyone had the same issue or do you guys know how to solve it? > -- -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-326) Committer invite template omits PMC role details
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 Environment: https://community.apache.org/newcommitter.html#committer-invite-template Reporter: Sebb The committer invite template [1] is not very clear on the distinction between an invitation as a committer, and invitation as a committer + PMC member. In particular, it describes the role of the committer, but largely ignores the PMC role. As a result, I have seen at least one acceptance reply that said "I accept to become a committer" [2] - leaving unstated whether or not they agree to become a PMC member. I think any template needs to make very clear what is involved in the PMC role, and also that the invitee has 3 choices: - decline both invites - accept the committer invite and decline the PMC invite - accept both committer invite and PMC invite [1] https://community.apache.org/newcommitter.html#committer-invite-template [2] https://lists.apache.org/thread.html/796c4b3e8c0f191add39c7d1b6cc154a5e316910df8120db1151c739@%3Cprivate.jackrabbit.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Resolved] (COMDEV-325) New "wizard" missing one of my projects...
[ 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... > -- > > Key: COMDEV-325 > URL: https://issues.apache.org/jira/browse/COMDEV-325 > Project: Community Development > Issue Type: Bug > Components: Reporter Tool >Reporter: Daniel Kulp >Priority: Minor > Attachments: ScreenShot.png > > > The new wizard style reporter tool doesn't list all of my projects when "Your > projects" is selected. In particular, it's missing one of the projects for > which I'm the chair.(Web Services)If I click on "show all projects", > it does list it there so it's a minor inconvenience. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-325) 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 webservices, it should be fixed now. can you recheck that things are working now? :) > New "wizard" missing one of my projects... > -- > > Key: COMDEV-325 > URL: https://issues.apache.org/jira/browse/COMDEV-325 > Project: Community Development > Issue Type: Bug > Components: Reporter Tool >Reporter: Daniel Kulp >Priority: Minor > Attachments: ScreenShot.png > > > The new wizard style reporter tool doesn't list all of my projects when "Your > projects" is selected. In particular, it's missing one of the projects for > which I'm the chair.(Web Services)If I click on "show all projects", > it does list it there so it's a minor inconvenience. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Moved] (COMDEV-325) New "wizard" missing one of my projects...
[ 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 default workflow (was: jira) Key: COMDEV-325 (was: WHIMSY-287) Project: Community Development (was: Whimsy) > New "wizard" missing one of my projects... > -- > > Key: COMDEV-325 > URL: https://issues.apache.org/jira/browse/COMDEV-325 > Project: Community Development > Issue Type: Bug > Components: Reporter Tool >Reporter: Daniel Kulp >Priority: Minor > Attachments: ScreenShot.png > > > The new wizard style reporter tool doesn't list all of my projects when "Your > projects" is selected. In particular, it's missing one of the projects for > which I'm the chair.(Web Services)If I click on "show all projects", > it does list it there so it's a minor inconvenience. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Volunteers wanted: Hackathon organization at ApacheCon Berlin 2019
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 special focus on design. The Open Source Design Initiative is giving us an entire track of content. Best, Myrle On Mon, Aug 5, 2019 at 12:29 AM Mandi Kauffman wrote: > Hey, > > I just became privy to this conversation. > > I'm pretty well stuck in the middle of the U.S. - Wichita, Kansas. But if > there's any graphic design, planning, organizing, or promoting that still > needs done, I'd be more than happy to offer my services. > > My skills are pretty lay when it comes to actual coding / hacking so I've > been hesitant and haven't really know how to contribute in the past ... > even though I've really wanted to. > > I'm a whiz at Photoshop (although I use G.I.M.P. currently to fight the > good fight) and have quite a few connections throughout the Midwest. Please > LMK if there's any way I can be of assistance all the way out here in > no-man's-land. > > Mandi > > On Sun, Aug 4, 2019, 9:46 AM Myrle Krantz > > On Sat, Aug 3, 2019 at 10:21 AM Julian Feinauer < > > j.feina...@pragmaticminds.de> wrote: > > > > > Hi Myrle, > > > > > > Of course I'm happy to help (and I think we could perhaps organize to > > > provide an small iot lab for everybody that wants to try plc4x...). > > > > > > > That would be *so* awesome! If you're going to do that at a specific > time > > let me know so that we can announce it. > > > > > > > > > > Just to get everything right, the announcement is for all pmcs not just > > > ours as an invitation to the hackathon or to organize something there? > > > > > > > Exactly. For all PMCs. > > > > Thank you!, > > Myrle > > >
Re: [Lazy Consensus] Changing the default reporter tool
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.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, please do let me know, and please elaborate on what you'd like to see changed in the new tool for it to become the default. I'll let this run for a few days and see if anyone objects :) With regards, Daniel. [1] https://reporter.apache.org/ [2] https://reporter.apache.org/wizard/ - 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: [Lazy Consensus] Changing the default reporter tool
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 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, > please do let me know, and please elaborate on what you'd like to see > changed in the new tool for it to become the default. > > I'll let this run for a few days and see if anyone objects :) > > With regards, > Daniel. > > [1] https://reporter.apache.org/ > [2] https://reporter.apache.org/wizard/ > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
[Lazy Consensus] Changing the default reporter tool
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, please do let me know, and please elaborate on what you'd like to see changed in the new tool for it to become the default. I'll let this run for a few days and see if anyone objects :) With regards, Daniel. [1] https://reporter.apache.org/ [2] https://reporter.apache.org/wizard/ - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [EVENT] Add Flink Forward EU 2019 to the ASF event calendar
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 Krantz wrote: > > Hey y'all, > > > > Nobody seems to have picked this up, and I don't know how to edit the > > calendar. Can someone point me to some directions? > > > > Thanks, > > Myrle > > > > On Fri, Jul 26, 2019 at 11:15 AM Fabian Hueske > wrote: > > > >> Hi everyone, > >> > >> We got the brand approval for Flink Forward EU 2019. > >> > >> Could somebody please add the conference to the event calendar? > >> Flink Forward will take place 7th to 9th October 2019 in Berlin (two > weeks > >> before ApacheCon EU). > >> > >> Thank you very much, > >> Fabian > >> > >> Am Di., 9. Juli 2019 um 10:14 Uhr schrieb Fabian Hueske < > >> fhue...@apache.org > >>> : > >>> Thanks Rich! > >>> I'll reach out to ASF brand and get back here once once I got the OK > from > >>> them. > >>> > >>> Thanks, Fabian > >>> > >>> Am Mo., 8. Juli 2019 um 18:39 Uhr schrieb Rich Bowen < > rbo...@rcbowen.com > >>> : > >>> > > On 7/8/19 12:29 PM, Fabian Hueske wrote: > > Hi everyone, > > > > I'd like to ask to add "Flink Forward EU 2019" to the ASF event > calendar. > > Flink Forward will take place 7th to 9th October 2019 in Berlin (two > weeks > > before ApacheCon EU). > > > > This is the 9th Flink Forward (5th in Europe, 3 in US, 1 in China) > and > the > > last time we got ASF brand approval was for Flink Forward China in > December > > 2018. > > Since then, the branding did not change and website [1] was only kept > up to > > date. > > > > Can you add Flink Forward EU 2019 to the calendar or do we need ASF > brand > > permission before that? > > Yes, I would be glad to add it to the calendar, but, yes, you need the > OK from brand first. > > --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 > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
