[jira] [Commented] (INCUBATOR-265) Maybe typo in Graduation Guide
[ https://issues.apache.org/jira/browse/INCUBATOR-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17346217#comment-17346217 ] John D. Ament commented on INCUBATOR-265: - I don't think typo is correct but clarification sure. The board would not vote on an existing TLP consuming a podling as a subproject. Typically though, a podling would only graduate into an existing TLP if that TLP was the sponsor instead of the incubator being the sponsor. > Maybe typo in Graduation Guide > -- > > Key: INCUBATOR-265 > URL: https://issues.apache.org/jira/browse/INCUBATOR-265 > Project: Incubator > Issue Type: Improvement > Components: guides >Reporter: Yonglun Zhang >Priority: Major > > The second section of > [http://incubator.apache.org/guides/graduation.html#whether_to_graduate_to_subproject_or_to_top_level_project] > > Graduation *as a project* requires the formation of the new project by the > [Board|http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#board]. > > I think change *as a project* to *as a top level project* makes sense. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Closed] (INCUBATOR-245) Slider - Auditing Capability
[ https://issues.apache.org/jira/browse/INCUBATOR-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament closed INCUBATOR-245. --- Resolution: Won't Fix > Slider - Auditing Capability > > > Key: INCUBATOR-245 > URL: https://issues.apache.org/jira/browse/INCUBATOR-245 > Project: Incubator > Issue Type: Task >Reporter: Krishnadevan Purushothaman >Priority: Critical > > As far as I understand, Slider outputs only logs for debugging use as details > of executing containers, and etc. > Can we believe Slider doesn't have any logs for auditing of Slider itself? > (i.e. when & who used Slider for what application, etc.) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-245) Slider - Auditing Capability
[ https://issues.apache.org/jira/browse/INCUBATOR-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17311756#comment-17311756 ] John D. Ament commented on INCUBATOR-245: - sure > Slider - Auditing Capability > > > Key: INCUBATOR-245 > URL: https://issues.apache.org/jira/browse/INCUBATOR-245 > Project: Incubator > Issue Type: Task >Reporter: Krishnadevan Purushothaman >Priority: Critical > > As far as I understand, Slider outputs only logs for debugging use as details > of executing containers, and etc. > Can we believe Slider doesn't have any logs for auditing of Slider itself? > (i.e. when & who used Slider for what application, etc.) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Updated] (INCUBATOR-245) Slider - Auditing Capability
[ https://issues.apache.org/jira/browse/INCUBATOR-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament updated INCUBATOR-245: Attachment: (was: Twitter-Social-Icons (1).zip) > Slider - Auditing Capability > > > Key: INCUBATOR-245 > URL: https://issues.apache.org/jira/browse/INCUBATOR-245 > Project: Incubator > Issue Type: Task >Reporter: Krishnadevan Purushothaman >Priority: Critical > > As far as I understand, Slider outputs only logs for debugging use as details > of executing containers, and etc. > Can we believe Slider doesn't have any logs for auditing of Slider itself? > (i.e. when & who used Slider for what application, etc.) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Updated] (INCUBATOR-245) Slider - Auditing Capability
[ https://issues.apache.org/jira/browse/INCUBATOR-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament updated INCUBATOR-245: Attachment: (was: iyyd.log) > Slider - Auditing Capability > > > Key: INCUBATOR-245 > URL: https://issues.apache.org/jira/browse/INCUBATOR-245 > Project: Incubator > Issue Type: Task >Reporter: Krishnadevan Purushothaman >Priority: Critical > > As far as I understand, Slider outputs only logs for debugging use as details > of executing containers, and etc. > Can we believe Slider doesn't have any logs for auditing of Slider itself? > (i.e. when & who used Slider for what application, etc.) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Updated] (INCUBATOR-245) Slider - Auditing Capability
[ https://issues.apache.org/jira/browse/INCUBATOR-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament updated INCUBATOR-245: Attachment: (was: iyyd.log) > Slider - Auditing Capability > > > Key: INCUBATOR-245 > URL: https://issues.apache.org/jira/browse/INCUBATOR-245 > Project: Incubator > Issue Type: Task >Reporter: Krishnadevan Purushothaman >Priority: Critical > > As far as I understand, Slider outputs only logs for debugging use as details > of executing containers, and etc. > Can we believe Slider doesn't have any logs for auditing of Slider itself? > (i.e. when & who used Slider for what application, etc.) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Closed] (INCUBATOR-255) Rename "DLab" to "DataLab" on https://incubator.apache.org/clutch/datalab.html
[ https://issues.apache.org/jira/browse/INCUBATOR-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament closed INCUBATOR-255. --- Resolution: Not A Problem > Rename "DLab" to "DataLab" on https://incubator.apache.org/clutch/datalab.html > -- > > Key: INCUBATOR-255 > URL: https://issues.apache.org/jira/browse/INCUBATOR-255 > Project: Incubator > Issue Type: Task > Components: site >Reporter: Vira Vitanska >Priority: Major > Attachments: Rename.png > > > This ticket follows > https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-145 and > https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-184. > So now our podling is in process of replacing old name by new one from DLab > to DataLab. > > There is a page [https://incubator.apache.org/clutch/datalab.html] > Could you replace dlab by datalab in: > # project website link name > # issue tracker link name > # wiki link name? > I guess that I've reported to an appropriate side (Project Incubator) if I am > wrong please correct me. > Thanks. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-255) Rename "DLab" to "DataLab" on https://incubator.apache.org/clutch/datalab.html
[ https://issues.apache.org/jira/browse/INCUBATOR-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17210856#comment-17210856 ] John D. Ament commented on INCUBATOR-255: - [~vvitanska] you should reach out to your mentors to do this. > Rename "DLab" to "DataLab" on https://incubator.apache.org/clutch/datalab.html > -- > > Key: INCUBATOR-255 > URL: https://issues.apache.org/jira/browse/INCUBATOR-255 > Project: Incubator > Issue Type: Task > Components: site >Reporter: Vira Vitanska >Priority: Major > Attachments: Rename.png > > > This ticket follows > https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-145 and > https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-184. > So now our podling is in process of replacing old name by new one from DLab > to DataLab. > > There is a page [https://incubator.apache.org/clutch/datalab.html] > Could you replace dlab by datalab in: > # project website link name > # issue tracker link name > # wiki link name? > I guess that I've reported to an appropriate side (Project Incubator) if I am > wrong please correct me. > Thanks. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-231) Cleanup Git-generated Incubator website
[ https://issues.apache.org/jira/browse/INCUBATOR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16784552#comment-16784552 ] John D. Ament commented on INCUBATOR-231: - The YAML files were created as an eventual replacement for the content in the XML files since it was already noticed that much of the data is duplicated in other locations. The YAML were meant to be a minimal representation of the data not found in other sources, and is currently used to display information in whimsy for the podling whenever it is filled out. > Cleanup Git-generated Incubator website > --- > > Key: INCUBATOR-231 > URL: https://issues.apache.org/jira/browse/INCUBATOR-231 > Project: Incubator > Issue Type: Task >Reporter: Bertrand Delacretaz >Priority: Major > > [http://incubator.apache.org/] is generated from > [https://github.com/apache/incubator] but a few things (clutch, project > pages) are still maintained under > [http://svn.apache.org/repos/asf/incubator/public/trunk/] > We should cleanup and unify for consistency, and there's a number of folders > in svn that are not used anymore. Everything should move to Git to avoid > confusion. > Also, a lot of the projects information in the XML files found under > [http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/] is > duplicated in other places, LDAP, podlings websites etc - it would be good to > clean that up and simplify those pages to adapt to our current workflows, > while preserving history where it makes sense. > There are also YAML files with yet more duplicated information at > [http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/] , > not sure if that's used or useful. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Closed] (INCUBATOR-211) ECharts todo list of next release
[ https://issues.apache.org/jira/browse/INCUBATOR-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament closed INCUBATOR-211. --- Resolution: Fixed Not for this project, working with podling on dev list. > ECharts todo list of next release > - > > Key: INCUBATOR-211 > URL: https://issues.apache.org/jira/browse/INCUBATOR-211 > Project: Incubator > Issue Type: Task >Reporter: Ovilia >Priority: Major > > We are about to release ECharts 4.1.0 next week, hopefully on Tuesday or > Wednesday. > We will list new features or bugs to be fixed of next release everytime after > we issue a new release. But since we just joined ASF and our last release was > on 28th Feb, there are many issues we've already fixed since then. We are > sorry about it, and from next release, we will discuss todo list before we > actually get started to do them. > > # Enhance: optimize candlestick rendering and zooming in hundreds of > thousand of data. > # Enhance: enhance the category axis ticks and labels when there was no > enough space to display all labels. > ## Make the animation appropriate for label, ticks, splitLine, splitArea > when view window moving (by dataZoom) in category axis. > ## Category axis tick and label was not corresponding to each other. > ## Make the choose of ticks and labels stable when view window moving (by > dataZoom) in category axis. > # Enhance: order of nodes for sankey diagram. #3390 #3543 #6365 #4880 #4986 > # Feature: Add zoom and drag interactions for tree diagram. > # Fix: SVG axisPointer text position bug #7947 > # Enhance: performance of bar chart in hundreds of thousand of data. (done) > # Enhance: sampling performance in progressive mode. (done) > # Enhance: parallel performance in progressive mode. (done) > # Fix: large lines chart render bug in large mode. (done) > # Fix: The last day of a month was not displayed in calendar #8045. (done) > # Fix: dataSample caused incorrect extent when data is NaN. (done) > # Fix: data sample worked abnormally when using `series.encode`. #8017 (done) > # Fix: `legendHoverLink: false` did not work appropriately when multiple > series have the same name. #8010 (done) > # Fix: Some of the graph hover style did not work. (done) > # Enhance: currently do not filter empty data item in data zoom, which makes > line chart keeping broken. #7955 (done) > # Enhance: support toolbox.feature merge. (done) > # Fix: currently we fetch name from dateItem.name firstly in list. #7966 > (done) > # Fix: typed array incorrect usage in WeChat app. (done) > # Fix: option in axis data item did not work. #7954 (done) > # Fix: markArea only displayed the last one. #7902 (done) > # Fix: rounding error in clip symbol for line chart. #7913 (done) > # Fix: bar chart start point was incorrect when multiple axes exist. #7412 > (done) > # Fix: markArea did not display when using ordinal string. #7849 (done) > # Fix: dataZoom threw error when series was empty. #7666 (done) > # Enhance: add tree directions from right to left, from bottom to top for > tree series. #7351 #7154 (done) > ## The corresponding values of the configuration 'orient' are 'RL' and 'BT'. > # Fix: resolve browser become unresponsive when the data of sankey series > has cycle. #7495 #8117 #7583 #7325 #6555 (done) > # Fix: add compatibility of data exceptions for sankey series. #2867 (done) > # Fix: error when remove node or render again for the tree series. #8038 > #8040 #7720 #7363 # 7315 (done) > # Fix: sunburst chart roll-up element is not removed when chart.setOption > called. #8132 (done) > ## A roll-up element is for going back from drilling down in sunburst charts. > # Feature: support keeping-aspect for legend path. #7831 (done) > ## Path defined in legend was not keeping aspect, but fitting the aspect of > default legend size, which is not ideal for most path shapes. > > Please send some feedback about them. Thanks! > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Closed] (INCUBATOR-210) Servicecomb当前性能统计不支持时延分布的统计，这个对于业务有重要意义
[ https://issues.apache.org/jira/browse/INCUBATOR-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament closed INCUBATOR-210. --- Resolution: Won't Fix I believe you already resolved this via the service comb podling. > Servicecomb当前性能统计不支持时延分布的统计，这个对于业务有重要意义 > --- > > Key: INCUBATOR-210 > URL: https://issues.apache.org/jira/browse/INCUBATOR-210 > Project: Incubator > Issue Type: Task >Reporter: renyingxin >Priority: Major > > Servicecomb当前性能统计不支持时延分布的统计，这个对于业务有重要意义,也就是类似[0,200),[200,400）这种时延分布的统计，平均时延可能会掩盖系统的部分问题，比如部分高延时，但是被正常平均值掩盖了 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-210) Servicecomb当前性能统计不支持时延分布的统计，这个对于业务有重要意义
[ https://issues.apache.org/jira/browse/INCUBATOR-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16378967#comment-16378967 ] John D. Ament commented on INCUBATOR-210: - Are we saying this is spam? > Servicecomb当前性能统计不支持时延分布的统计，这个对于业务有重要意义 > --- > > Key: INCUBATOR-210 > URL: https://issues.apache.org/jira/browse/INCUBATOR-210 > Project: Incubator > Issue Type: Task >Reporter: renyingxin >Priority: Major > > Servicecomb当前性能统计不支持时延分布的统计，这个对于业务有重要意义,也就是类似[0,200),[200,400）这种时延分布的统计，平均时延可能会掩盖系统的部分问题，比如部分高延时，但是被正常平均值掩盖了 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Closed] (INCUBATOR-209) Give "read" permissions on the apache/incubator-trafficcontrol repository to contributors
[ https://issues.apache.org/jira/browse/INCUBATOR-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament closed INCUBATOR-209. --- Resolution: Won't Do The Incubator does not give permissions out like this. At the same time, we will not likely modify our github permission structure to add non-committers. You should consider adding these folks as committers. You may want to ask further on users@infra to get some insight on ways they may be able to help you. > Give "read" permissions on the apache/incubator-trafficcontrol repository to > contributors > - > > Key: INCUBATOR-209 > URL: https://issues.apache.org/jira/browse/INCUBATOR-209 > Project: Incubator > Issue Type: Improvement >Reporter: Jeremy Mitchell > > On the Traffic Control project, we have a large number of Github issues > (https://github.com/apache/incubator-trafficcontrol/issues) that need to be > assigned to our contributors. > Unfortunately, issues can only currently be assigned to project committers. > This makes it very difficult to manage issues and assign them to the people > actually doing the work. > It is my understanding that issues can be assigned to contributors only if > they have "read" permission on the apache/incubator-trafficcontrol repository. > https://help.github.com/articles/repository-permission-levels-for-an-organization/ > Can you give "read" permissions on the apache/incubator-trafficcontrol > repository to the following github users? > https://github.com/DylanVolz > https://github.com/alficles > https://github.com/zhilhuan > https://github.com/rawlinp > https://github.com/ryandurfey > https://github.com/ezelkow1 > https://github.com/jhg03a > https://github.com/serDrem > This might involve adding these users as members to the following team: > https://github.com/orgs/apache/teams/trafficcontrol-committers/members > and giving them only "read" permissions to the > apache/incubator-trafficcontrol repository > thanks! -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-205) Marking the master branch of "incubator-mxnet" protected
[ https://issues.apache.org/jira/browse/INCUBATOR-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16190606#comment-16190606 ] John D. Ament commented on INCUBATOR-205: - [~gautamkmr] Same with this, did you mean infra? > Marking the master branch of "incubator-mxnet" protected > > > Key: INCUBATOR-205 > URL: https://issues.apache.org/jira/browse/INCUBATOR-205 > Project: Incubator > Issue Type: Improvement >Reporter: Gautam Kumar > > Hi, > Community has decided to mark the master branch of incubator-mxnet repo to > be protected. > We all agreed on protected branch feature mentioned in > https://help.github.com/articles/about-protected-branches/. > Appreciate your help. > Regards, > Gautam -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-206) Please white list the following EIPs to the master, so that can attach them to our slaves
[ https://issues.apache.org/jira/browse/INCUBATOR-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16190605#comment-16190605 ] John D. Ament commented on INCUBATOR-206: - [~gautamkmr] I'm not sure how we can help you on this one. Did you mean to create this in infra? > Please white list the following EIPs to the master, so that can attach them > to our slaves > -- > > Key: INCUBATOR-206 > URL: https://issues.apache.org/jira/browse/INCUBATOR-206 > Project: Incubator > Issue Type: Bug >Reporter: Gautam Kumar > > Currently we have 7 slaves for mxnet, we want to attach them to elastic ips. > Would you please whitelist following ips from the master side ? > 34.214.192.126 > 34.215.164.129 > 34.215.63.11 > 35.165.101.22 > 52.11.34.14 > 52.42.204.40 > 52.89.1.253 > Thank you. > Gautam -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Updated] (INCUBATOR-202) Graduation steps guide enhancements
[ https://issues.apache.org/jira/browse/INCUBATOR-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament updated INCUBATOR-202: Description: Related to this section: - Clarify that anyone from the new PMC can create the infra tickets. This should happen after its clear that the resolution was accepted. - Direct users to use Service Desk for ticket creation - Most of 3.1 needs to be removed, as TLPs don't have incubator.a.o domains - All of 3.2 can be removed - Section 6, infra does a move so just create a ticket. Sub project specific: - Don't require the IPMC to vote, instead use a 72 hour lazy consensus to graduate a podling to a sub-project was: Related to this section: - Clarify that anyone from the new PMC can create the infra tickets. This should happen after its clear that the resolution was accepted. - Direct users to use Service Desk for ticket creation - Most of 3.1 needs to be removed, as TLPs don't have incubator.a.o domains - All of 3.2 can be removed - Section 6, infra does a move so just create a ticket. > Graduation steps guide enhancements > --- > > Key: INCUBATOR-202 > URL: https://issues.apache.org/jira/browse/INCUBATOR-202 > Project: Incubator > Issue Type: Improvement >Reporter: John D. Ament > > Related to this section: > - Clarify that anyone from the new PMC can create the infra tickets. This > should happen after its clear that the resolution was accepted. > - Direct users to use Service Desk for ticket creation > - Most of 3.1 needs to be removed, as TLPs don't have incubator.a.o domains > - All of 3.2 can be removed > - Section 6, infra does a move so just create a ticket. > Sub project specific: > - Don't require the IPMC to vote, instead use a 72 hour lazy consensus to > graduate a podling to a sub-project -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Assigned] (INCUBATOR-201) Missing archiver/archives for dev@incubator - is it needed?
[ https://issues.apache.org/jira/browse/INCUBATOR-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament reassigned INCUBATOR-201: --- Assignee: Sebb > Missing archiver/archives for dev@incubator - is it needed? > --- > > Key: INCUBATOR-201 > URL: https://issues.apache.org/jira/browse/INCUBATOR-201 > Project: Incubator > Issue Type: Task >Reporter: Sebb >Assignee: Sebb > > The dev@incubator mailing list is still active and has 6 messages: > dev Digest of: get.1_6 > Topics (messages 1 through 6) > HashPartitioner, strange behavior > 1 by: Erik Thorson > 2 by: Erik Thorson > [ANNOUNCE] CFP open for ApacheCon North America 2016 > 3 by: Rich Bowen > FOSDEM 2016 - take action by 4th of December 2015 > 4 by: Roman Shaposhnik > Re: Spawning an Apache Geode Summit - March 9 2016 in Palo Alto, CA > 5 by: Greg Chase > ApacheCon Seville CFP closes September 9th > 6 by: Rich Bowen > However there does not appear to be an ASF archive for it, and the one on > lists.apache.org only contains the latest message [1] > It should probably be shut down. > If not, then the archiver needs to be set up. > Also the missing messages should be retrieved if possible. > It looks like dev-get recovers the message bodies, but not the headers. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Created] (INCUBATOR-204) Create a Creating Releases section
John D. Ament created INCUBATOR-204: --- Summary: Create a Creating Releases section Key: INCUBATOR-204 URL: https://issues.apache.org/jira/browse/INCUBATOR-204 Project: Incubator Issue Type: Improvement Components: guides Reporter: John D. Ament While we have a stripped down pointer to the ASF policy for releases, it would be good to provide some knowledge share on how to create good releases. - Can we link to Justin's videos? - Can we point to examples on how to do this for common languages (Java, C++, Python come to mind)? -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Created] (INCUBATOR-203) Rename Proposals to something else, add more how to get in information
John D. Ament created INCUBATOR-203: --- Summary: Rename Proposals to something else, add more how to get in information Key: INCUBATOR-203 URL: https://issues.apache.org/jira/browse/INCUBATOR-203 Project: Incubator Issue Type: Improvement Components: guides Reporter: John D. Ament The current proposal top level menu item is good, but lacks some useful information. Instead of being called proposals, maybe call it "Becoming an Apache Project" and include some information: - Proposal process - Update entry to give a higher level how it works - Include docs on SGAs, IP Clearance, when each is needed -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Created] (INCUBATOR-202) Graduation steps guide enhancements
John D. Ament created INCUBATOR-202: --- Summary: Graduation steps guide enhancements Key: INCUBATOR-202 URL: https://issues.apache.org/jira/browse/INCUBATOR-202 Project: Incubator Issue Type: Improvement Reporter: John D. Ament Related to this section: - Clarify that anyone from the new PMC can create the infra tickets. This should happen after its clear that the resolution was accepted. - Direct users to use Service Desk for ticket creation - Most of 3.1 needs to be removed, as TLPs don't have incubator.a.o domains - All of 3.2 can be removed - Section 6, infra does a move so just create a ticket. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Closed] (INCUBATOR-200) The incubator openwhisk does not have "squash and merge" as the default option to merge a PR
[ https://issues.apache.org/jira/browse/INCUBATOR-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament closed INCUBATOR-200. --- Resolution: Won't Fix Vincent, you should raise this with infra. > The incubator openwhisk does not have "squash and merge" as the default > option to merge a PR > > > Key: INCUBATOR-200 > URL: https://issues.apache.org/jira/browse/INCUBATOR-200 > Project: Incubator > Issue Type: Task > Components: policy >Reporter: Vincent Hou > Attachments: screenshot.png > > > This ticket asks to force the PRs default to “Squash and merge” (green > button) for all the openwhisk projects. A reference article can be found via > https://github.com/blog/2141-squash-your-commits. > There are three choices for each PR: “Allow merge commits”, "Allow squash > merging" and "Allow rebase merging". > Please uncheck the first one “Allow merge commits”, and check the other two: > "Allow squash merging" and "Allow rebase merging" as it indicates in the > attachment. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Closed] (INCUBATOR-128) Wrong email address in sample PPMC invitation email
[ https://issues.apache.org/jira/browse/INCUBATOR-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament closed INCUBATOR-128. --- Resolution: Fixed > Wrong email address in sample PPMC invitation email > --- > > Key: INCUBATOR-128 > URL: https://issues.apache.org/jira/browse/INCUBATOR-128 > Project: Incubator > Issue Type: Bug >Reporter: Julian Hyde > > The sample invitation email http://incubator.apache.org/guides/ppmc-offer.txt > is very useful (thank you!). But the sample email address should be > private-subscr...@frizzle.incubator.apache.org and not > frizzle-private-subscr...@incubator.apache.org since that is the style for > mailing lists these days. > It's a minor point, but it wasted a couple of hours of a few people's time. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-198) clean up archive.a.o
[
https://issues.apache.org/jira/browse/INCUBATOR-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15956069#comment-15956069
]
John D. Ament commented on INCUBATOR-198:
-
Policy page: http://incubator.apache.org/guides/graduation.html
Transferring Resources #6
{quote}
Distribution mirrors
After you have a release at your new home (/dist/${project}/ area), remove any
distribution artefacts from your old /dist/incubator/${project}/ area. Remember
from the mirror guidelines that everything is automatically added to
archive.apache.org anyway.
{quote}
I would recommend that you reach out to individual TLPs to clean up their
incubator remains.
> clean up archive.a.o
>
>
> Key: INCUBATOR-198
> URL: https://issues.apache.org/jira/browse/INCUBATOR-198
> Project: Incubator
> Issue Type: Task
>Reporter: Greg Stein
>Priority: Minor
>
> The Incubator area at https://archive.apache.org/dist/incubator/ contains
> historical release artifacts for many projects that are no longer in the
> Incubator. I believe these need to be managed in some way. For example:
> * any podling that graduated should have its archive.a.o assets moved to
> their current TLP archive directory
> * the above would include those who may be in the Attic now. we do not change
> their release archive when they enter the Attic
> * for podlings that were retired, we should delete any artifacts from our
> archive since they are not ASF artifacts
> This is an Incubator policy issue, along with the many TLPs who had
> incubator-based releases. Infra can/will move any files as appropriate, but
> we need instructions from the stakeholders.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Created] (INCUBATOR-146) Test
John D. Ament created INCUBATOR-146: --- Summary: Test Key: INCUBATOR-146 URL: https://issues.apache.org/jira/browse/INCUBATOR-146 Project: Incubator Issue Type: Task Reporter: John D. Ament Assignee: John D. Ament Attachments: TestingPyramid.jpg Test -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Created] (INCUBATOR-145) test
John D. Ament created INCUBATOR-145: --- Summary: test Key: INCUBATOR-145 URL: https://issues.apache.org/jira/browse/INCUBATOR-145 Project: Incubator Issue Type: Task Components: policy Reporter: John D. Ament Assignee: John D. Ament test only -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Updated] (INCUBATOR-142) Testing - Sally graphics submission
[ https://issues.apache.org/jira/browse/INCUBATOR-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament updated INCUBATOR-142: Component/s: (was: LogoSubmission) > Testing - Sally graphics submission > --- > > Key: INCUBATOR-142 > URL: https://issues.apache.org/jira/browse/INCUBATOR-142 > Project: Incubator > Issue Type: Task > Environment: no idea - what does this mean? >Reporter: Sally-Testing > Attachments: Apache_twitter_header_photo.png, Screenshot 2016-12-30 > at 07.50.29.png > > > testing ... is there a word limit? > needs to map against the call (perhaps in the instructions) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Updated] (INCUBATOR-141) Test
[ https://issues.apache.org/jira/browse/INCUBATOR-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament updated INCUBATOR-141: Component/s: (was: LogoSubmission) > Test > > > Key: INCUBATOR-141 > URL: https://issues.apache.org/jira/browse/INCUBATOR-141 > Project: Incubator > Issue Type: Task >Reporter: John D. Ament > Attachments: test.txt, thunder-christmas.jpg > > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Updated] (INCUBATOR-143) SallyTest - 2
[ https://issues.apache.org/jira/browse/INCUBATOR-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament updated INCUBATOR-143: Component/s: (was: LogoSubmission) > SallyTest - 2 > - > > Key: INCUBATOR-143 > URL: https://issues.apache.org/jira/browse/INCUBATOR-143 > Project: Incubator > Issue Type: Task >Reporter: Sally-Testing > Attachments: echarts.png > > > Testing again. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-127) Project name still shows as Apache Argus - It should be Apache Ranger.
[ https://issues.apache.org/jira/browse/INCUBATOR-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14228859#comment-14228859 ] John D. Ament commented on INCUBATOR-127: - [~sneethiraj] You need to have one of your mentors update podlings.xml - or better yet you can probably do it yourself. Project name still shows as Apache Argus - It should be Apache Ranger. -- Key: INCUBATOR-127 URL: https://issues.apache.org/jira/browse/INCUBATOR-127 Project: Incubator Issue Type: Bug Components: site Reporter: Selvamohan Neethiraj Project name in Apache Incubator site is still showing up as Argus (after it got renamed as Ranger) http://incubator.apache.org/ - In the List of all current Incubator projects -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-126) Sometimes its not clear that the who vets the podling name
[ https://issues.apache.org/jira/browse/INCUBATOR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13667772#comment-13667772 ] John D. Ament commented on INCUBATOR-126: - Isn't it stated here? http://www.apache.org/foundation/marks/naming.html That only the VP of Branding may approve the names? Sometimes its not clear that the who vets the podling name -- Key: INCUBATOR-126 URL: https://issues.apache.org/jira/browse/INCUBATOR-126 Project: Incubator Issue Type: Improvement Reporter: Alan Cabrera We should make it more clear in the documentation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-126) Sometimes its not clear that the who vets the podling name
[ https://issues.apache.org/jira/browse/INCUBATOR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13667801#comment-13667801 ] John D. Ament commented on INCUBATOR-126: - It also states (one line up) The trademarks team will interpret your findings... Perhaps if it's not clear, under the section Create an Name Search issue some text should be added, along the lines of At this point, you should begin filling in the research information described below. Sometimes its not clear that the who vets the podling name -- Key: INCUBATOR-126 URL: https://issues.apache.org/jira/browse/INCUBATOR-126 Project: Incubator Issue Type: Improvement Reporter: Alan Cabrera We should make it more clear in the documentation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Created] (PODLINGNAMESEARCH-31) Establish whether Apache DeltaSpike is a suitable name
John D. Ament created PODLINGNAMESEARCH-31: -- Summary: Establish whether Apache DeltaSpike is a suitable name Key: PODLINGNAMESEARCH-31 URL: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-31 Project: Podling Suitable Names Search Issue Type: Suitable Name Search Reporter: John D. Ament DeltaSpike is a portmanteau of Delta (for change) and Spike (for 'an abrupt sharp increase'). From the ASF perspective, it is a library of reusable CDI extensions and components. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
