[jira] [Commented] (INCUBATOR-283) Please delete tag v2.0.0 in incubator-horaedb
[ https://issues.apache.org/jira/browse/INCUBATOR-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17828266#comment-17828266 ] Sebb commented on INCUBATOR-283: There is some git hook code that appears to protect certain tags by default. However, I mis-remembered and such tags are prefixed rel/, not releases/. So the project should be able to drop the incorrect tag. It's not clear if the asf.yaml file can change the default protections (if any) or merely add to them. I've raised https://issues.apache.org/jira/browse/INFRA-25622 about the asf.yaml documentation. > Please delete tag v2.0.0 in incubator-horaedb > - > > Key: INCUBATOR-283 > URL: https://issues.apache.org/jira/browse/INCUBATOR-283 > Project: Incubator > Issue Type: Task >Reporter: Chunshao Ren >Priority: Minor > > Please delete the tag v2.0.0, as it was created by mistake earlier. The > version 2.0.0 is currently undergoing a vote. > https://github.com/apache/incubator-horaedb/releases/tag/v2.0.0 > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-283) Please delete tag v2.0.0 in incubator-horaedb
[ https://issues.apache.org/jira/browse/INCUBATOR-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17828246#comment-17828246 ] Sebb commented on INCUBATOR-283: release tags are supposed to be immutable, and cannot normally be deleted. I think you will need to involve Infra to get this corrected. > Please delete tag v2.0.0 in incubator-horaedb > - > > Key: INCUBATOR-283 > URL: https://issues.apache.org/jira/browse/INCUBATOR-283 > Project: Incubator > Issue Type: Task >Reporter: Chunshao Ren >Priority: Minor > > Please delete the tag v2.0.0, as it was created by mistake earlier. The > version 2.0.0 is currently undergoing a vote. > https://github.com/apache/incubator-horaedb/releases/tag/v2.0.0 > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Assigned] (INCUBATOR-199) Extend podlings.xml to include old names and TLP parent
[ https://issues.apache.org/jira/browse/INCUBATOR-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb reassigned INCUBATOR-199: -- Assignee: (was: Sebb) > Extend podlings.xml to include old names and TLP parent > --- > > Key: INCUBATOR-199 > URL: https://issues.apache.org/jira/browse/INCUBATOR-199 > Project: Incubator > Issue Type: New Feature >Reporter: Sebb >Priority: Major > > Podling names change fairly often. > It would be useful to be able to list old names in the podlings file. > At present this info is only in the free-form text. > Also where a podling graduates as a project of a PMC, it would be useful to > be able to document the PMC. At present this would have to be extracted from > the url field (or the text) > AFAIK additional attributes do not cause problems for existing parsing > routines. However the DTD will have to be extended to allow for the new > entries. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-279) Tuweni retired, but cleanup is incomplete
[ https://issues.apache.org/jira/browse/INCUBATOR-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790241#comment-17790241 ] Sebb commented on INCUBATOR-279: The index page was updated to point to the Attic, but that was wrong, as the Attic only deals with PMCs (and so the link is broken). > Tuweni retired, but cleanup is incomplete > - > > Key: INCUBATOR-279 > URL: https://issues.apache.org/jira/browse/INCUBATOR-279 > Project: Incubator > Issue Type: Bug >Reporter: Sebb >Priority: Major > > The LDAP project list still needs to be removed. > Also podlings.xml and tuweni.xml need to be updated, and the website site > redirect needs to be set up. > Maybe the retirement instructions need to be reviewed. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-279) Tuweni retired, but cleanup is incomplete
[ https://issues.apache.org/jira/browse/INCUBATOR-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790240#comment-17790240 ] Sebb commented on INCUBATOR-279: Still not complete. The website needs to be redirected, see: https://github.com/apache/incubator/tree/master/assets/retired > Tuweni retired, but cleanup is incomplete > - > > Key: INCUBATOR-279 > URL: https://issues.apache.org/jira/browse/INCUBATOR-279 > Project: Incubator > Issue Type: Bug >Reporter: Sebb >Priority: Major > > The LDAP project list still needs to be removed. > Also podlings.xml and tuweni.xml need to be updated, and the website site > redirect needs to be set up. > Maybe the retirement instructions need to be reviewed. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-280) Datalab retired, but cleanup is incomplete
[ https://issues.apache.org/jira/browse/INCUBATOR-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790239#comment-17790239 ] Sebb commented on INCUBATOR-280: Still not complete. The website needs to be redirected; see [https://github.com/apache/incubator/tree/master/assets/retired] > Datalab retired, but cleanup is incomplete > -- > > Key: INCUBATOR-280 > URL: https://issues.apache.org/jira/browse/INCUBATOR-280 > Project: Incubator > Issue Type: Task >Reporter: Sebb >Priority: Major > > As the subject says -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-281) Broken link
[ https://issues.apache.org/jira/browse/INCUBATOR-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17787418#comment-17787418 ] Sebb commented on INCUBATOR-281: Noticed a blank line where sibling pages had a date, so I restored the date lost in the last commit. The page as been regenerated. Looks like there needs to be a check of the build to detect such failings. > Broken link > --- > > Key: INCUBATOR-281 > URL: https://issues.apache.org/jira/browse/INCUBATOR-281 > Project: Incubator > Issue Type: Bug >Reporter: Sebb >Priority: Major > > https://cwiki.apache.org/confluence/display/incubator/RetiringPodlings > links to > https://incubator.apache.org/guides/retirement.html > which does not exist. > Not sure whether it ever did exist. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Created] (INCUBATOR-281) Broken link
Sebb created INCUBATOR-281: -- Summary: Broken link Key: INCUBATOR-281 URL: https://issues.apache.org/jira/browse/INCUBATOR-281 Project: Incubator Issue Type: Bug Reporter: Sebb https://cwiki.apache.org/confluence/display/incubator/RetiringPodlings links to https://incubator.apache.org/guides/retirement.html which does not exist. Not sure whether it ever did exist. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-280) Datalab retired, but cleanup is incomplete
[ https://issues.apache.org/jira/browse/INCUBATOR-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17786220#comment-17786220 ] Sebb commented on INCUBATOR-280: The Incubator PMC is ultimately responsible. Some parts have to be done by Infra on request from the IPMC. > Datalab retired, but cleanup is incomplete > -- > > Key: INCUBATOR-280 > URL: https://issues.apache.org/jira/browse/INCUBATOR-280 > Project: Incubator > Issue Type: Task >Reporter: Sebb >Priority: Major > > As the subject says -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-280) Datalab retired, but cleanup is incomplete
[ https://issues.apache.org/jira/browse/INCUBATOR-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17785867#comment-17785867 ] Sebb commented on INCUBATOR-280: AFAIK, nothing has been done on this. For example, the LDAP group still exists https://dist.apache.org/repos/dist/dev/incubator/datalab/ still exists Various resources such as Git, Website, Wiki appear to be still active (they should have comments to say the podling is retired) etc. > Datalab retired, but cleanup is incomplete > -- > > Key: INCUBATOR-280 > URL: https://issues.apache.org/jira/browse/INCUBATOR-280 > Project: Incubator > Issue Type: Task >Reporter: Sebb >Priority: Major > > As the subject says -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-279) Tuweni retired, but cleanup is incomplete
[ https://issues.apache.org/jira/browse/INCUBATOR-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17778476#comment-17778476 ] Sebb commented on INCUBATOR-279: Ping > Tuweni retired, but cleanup is incomplete > - > > Key: INCUBATOR-279 > URL: https://issues.apache.org/jira/browse/INCUBATOR-279 > Project: Incubator > Issue Type: Bug >Reporter: Sebb >Priority: Major > > The LDAP project list still needs to be removed. > Also podlings.xml and tuweni.xml need to be updated, and the website site > redirect needs to be set up. > Maybe the retirement instructions need to be reviewed. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Created] (INCUBATOR-280) Datalab retired, but cleanup is incomplete
Sebb created INCUBATOR-280: -- Summary: Datalab retired, but cleanup is incomplete Key: INCUBATOR-280 URL: https://issues.apache.org/jira/browse/INCUBATOR-280 Project: Incubator Issue Type: Task Reporter: Sebb As the subject says -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Updated] (INCUBATOR-253) Issues with MXNet releases and their distribution
[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated INCUBATOR-253: --- Labels: CanBeClosed (was: ) > Issues with MXNet releases and their distribution > - > > Key: INCUBATOR-253 > URL: https://issues.apache.org/jira/browse/INCUBATOR-253 > Project: Incubator > Issue Type: Improvement >Reporter: Justin Mclean >Assignee: Justin Mclean >Priority: Major > Labels: CanBeClosed > > The main issues are: > 1. Source and convenance binary releases containing Category X licensed code. > 2. Website giving access to downloads of non released/unapproved code. > 3. Website giving access to releases containing Category X licensed code. > 4. Web site doesn't given enough warning to users of the issues with non > (P)PMC releases or making it clear that these are not ASF releases. > 5. Maven releases containing Category X licensed code. > 6. PiPy releases containing Category X licensed code. > 7. Docker releases containing Category X licensed code. > 8 Docker releases containing unreleased/unapproved code. > 9. Trademark and branding issues with PiPy and Docker releases. > 10. Trademark and brand issues with naming of releases. > 11. Developer releases available to users and public searchable > https://repo.mxnet.io / https://dist.mxnet.io > 12. Releases and other nightly builds on https://repo.mxnet.io / > https://dist.mxnet.io containing category X licensed code. > 13. Lack of clarity on all platforms for what is an ASF release and what is > not. > 14. Branding and release of 3rd parties containing unreleased code. (e.g. > https://docs.nvidia.com/deeplearning/frameworks/mxnet-release-notes/rel_20-03.html) > For PiPy see: > https://pypi.org/project/mxnet/ > For Docker see: > https://hub.docker.com/u/mxnet > For web site pages see: > https://mxnet.apache.org/get_started? > https://mxnet.apache.org/get_started/download > I may of missed something, if so please add it. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-253) Issues with MXNet releases and their distribution
[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767746#comment-17767746 ] Sebb commented on INCUBATOR-253: MXNet graduated in 2022, so this issue can be closed > Issues with MXNet releases and their distribution > - > > Key: INCUBATOR-253 > URL: https://issues.apache.org/jira/browse/INCUBATOR-253 > Project: Incubator > Issue Type: Improvement >Reporter: Justin Mclean >Assignee: Justin Mclean >Priority: Major > > The main issues are: > 1. Source and convenance binary releases containing Category X licensed code. > 2. Website giving access to downloads of non released/unapproved code. > 3. Website giving access to releases containing Category X licensed code. > 4. Web site doesn't given enough warning to users of the issues with non > (P)PMC releases or making it clear that these are not ASF releases. > 5. Maven releases containing Category X licensed code. > 6. PiPy releases containing Category X licensed code. > 7. Docker releases containing Category X licensed code. > 8 Docker releases containing unreleased/unapproved code. > 9. Trademark and branding issues with PiPy and Docker releases. > 10. Trademark and brand issues with naming of releases. > 11. Developer releases available to users and public searchable > https://repo.mxnet.io / https://dist.mxnet.io > 12. Releases and other nightly builds on https://repo.mxnet.io / > https://dist.mxnet.io containing category X licensed code. > 13. Lack of clarity on all platforms for what is an ASF release and what is > not. > 14. Branding and release of 3rd parties containing unreleased code. (e.g. > https://docs.nvidia.com/deeplearning/frameworks/mxnet-release-notes/rel_20-03.html) > For PiPy see: > https://pypi.org/project/mxnet/ > For Docker see: > https://hub.docker.com/u/mxnet > For web site pages see: > https://mxnet.apache.org/get_started? > https://mxnet.apache.org/get_started/download > I may of missed something, if so please add it. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-265) Maybe incorrect clarification in Graduation Guide
[ https://issues.apache.org/jira/browse/INCUBATOR-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767745#comment-17767745 ] Sebb commented on INCUBATOR-265: PR has been applied > Maybe incorrect clarification 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 > Labels: CanBeClosed > > 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.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Updated] (INCUBATOR-265) Maybe incorrect clarification in Graduation Guide
[ https://issues.apache.org/jira/browse/INCUBATOR-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated INCUBATOR-265: --- Labels: CanBeClosed (was: ) > Maybe incorrect clarification 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 > Labels: CanBeClosed > > 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.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Updated] (INCUBATOR-278) Outdated link to Apachecon 2022 on website
[ https://issues.apache.org/jira/browse/INCUBATOR-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated INCUBATOR-278: --- Labels: CanBeClosed (was: ) > Outdated link to Apachecon 2022 on website > -- > > Key: INCUBATOR-278 > URL: https://issues.apache.org/jira/browse/INCUBATOR-278 > Project: Incubator > Issue Type: Bug >Reporter: Sebb >Priority: Major > Labels: CanBeClosed > > The Incubator home page has a prominent link to > [https://www.apachecon.com/acna2022/] > > This is very out of date. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-278) Outdated link to Apachecon 2022 on website
[ https://issues.apache.org/jira/browse/INCUBATOR-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767744#comment-17767744 ] Sebb commented on INCUBATOR-278: Seems to have been fixed; this issue can be closed > Outdated link to Apachecon 2022 on website > -- > > Key: INCUBATOR-278 > URL: https://issues.apache.org/jira/browse/INCUBATOR-278 > Project: Incubator > Issue Type: Bug >Reporter: Sebb >Priority: Major > > The Incubator home page has a prominent link to > [https://www.apachecon.com/acna2022/] > > This is very out of date. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Updated] (INCUBATOR-270) Install osschat GitHub app
[ https://issues.apache.org/jira/browse/INCUBATOR-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated INCUBATOR-270: --- Labels: TOBECLOSED (was: ) > Install osschat GitHub app > -- > > Key: INCUBATOR-270 > URL: https://issues.apache.org/jira/browse/INCUBATOR-270 > Project: Incubator > Issue Type: Task > Components: git >Reporter: Heping Wang >Priority: Major > Labels: TOBECLOSED > > Dear Infra team, > Can you please install GitHub osschat([https://github.com/apps/osschat]) > application for our apache/incubator-linkis GitHub repo ? > Thanks -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Updated] (INCUBATOR-273) remove jul...@apache.org from moderators of heron and toree podlings mailing lists
[ https://issues.apache.org/jira/browse/INCUBATOR-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated INCUBATOR-273: --- Labels: TOBECLOSED (was: ) > remove jul...@apache.org from moderators of heron and toree podlings mailing > lists > -- > > Key: INCUBATOR-273 > URL: https://issues.apache.org/jira/browse/INCUBATOR-273 > Project: Incubator > Issue Type: Task >Reporter: Julien Le Dem >Priority: Major > Labels: TOBECLOSED > > * > [comm...@heron.apache.org|https://lists.apache.org/list.html?comm...@heron.apache.org] > as jul...@apache.org > * > [d...@heron.apache.org|https://lists.apache.org/list.html?d...@heron.apache.org] > as jul...@apache.org > * > [iss...@heron.apache.org|https://lists.apache.org/list.html?iss...@heron.apache.org] > as jul...@apache.org > * > [priv...@heron.apache.org|https://lists.apache.org/list.html?priv...@heron.apache.org] > as jul...@apache.org > * > [u...@heron.apache.org|https://lists.apache.org/list.html?u...@heron.apache.org] > as jul...@apache.org > * > [comm...@toree.apache.org|https://lists.apache.org/list.html?comm...@toree.apache.org] > as jul...@apache.org > * > [d...@toree.apache.org|https://lists.apache.org/list.html?d...@toree.apache.org] > as jul...@apache.org > * > [priv...@toree.apache.org|https://lists.apache.org/list.html?priv...@toree.apache.org] > as jul...@apache.org -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Updated] (INCUBATOR-277) Allow GitHub Actions to create PRs
[ https://issues.apache.org/jira/browse/INCUBATOR-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated INCUBATOR-277: --- Labels: TOBECLOSED (was: ) > Allow GitHub Actions to create PRs > -- > > Key: INCUBATOR-277 > URL: https://issues.apache.org/jira/browse/INCUBATOR-277 > Project: Incubator > Issue Type: Wish >Reporter: Junren Yu >Priority: Major > Labels: TOBECLOSED > > I am a committer of [DevLake|https://github.com/apache/incubator-devlake]. > Since we are still in the initial iteration, we need to cherry-pick the > previous version after submitting the pr repair. I created a GitHub action > named "Auto Cherry Pick" in our repository. Currently, this action cannot be > used because the repository has not enabled the permission to allow the > action to submit pr. We want to be able to enable this permission in the > repository. > > !https://user-images.githubusercontent.com/37237996/240861206-65885923-830e-47a3-866c-472f381267d6.jpeg! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Updated] (INCUBATOR-274) Gives Orbit (orbit.love) access to GitHub repos
[ https://issues.apache.org/jira/browse/INCUBATOR-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated INCUBATOR-274: --- Labels: TOBECLOSED (was: ) > Gives Orbit (orbit.love) access to GitHub repos > --- > > Key: INCUBATOR-274 > URL: https://issues.apache.org/jira/browse/INCUBATOR-274 > Project: Incubator > Issue Type: Task > Components: git >Reporter: Hezheng Yin >Priority: Major > Labels: TOBECLOSED > > *Update:* I just realized that I should open this issue at > [https://issues.apache.org/jira/projects/INFRA.] Please feel free to close > this issue. Sorry for the trouble. > > Dear Infra Team, > > I'm looking to set up Orbit (orbit.love, a community growth platform) for > DevLake. I ran into a permission issue when I tried to give Orbit access to > DevLake's repos as shown in this > [screenshot|https://user-images.githubusercontent.com/2908155/206342490-32d84f00-15df-49d3-b3d4-0b758c4ed3ac.png]. > > Is there any workaround that may get this integration working? Thanks in > advance for your guidance! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Created] (INCUBATOR-279) Tuweni retired, but cleanup is incomplete
Sebb created INCUBATOR-279: -- Summary: Tuweni retired, but cleanup is incomplete Key: INCUBATOR-279 URL: https://issues.apache.org/jira/browse/INCUBATOR-279 Project: Incubator Issue Type: Bug Reporter: Sebb The LDAP project list still needs to be removed. Also podlings.xml and tuweni.xml need to be updated, and the website site redirect needs to be set up. Maybe the retirement instructions need to be reviewed. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Created] (INCUBATOR-278) Outdated link to Apachecon 2022 on website
Sebb created INCUBATOR-278: -- Summary: Outdated link to Apachecon 2022 on website Key: INCUBATOR-278 URL: https://issues.apache.org/jira/browse/INCUBATOR-278 Project: Incubator Issue Type: Bug Reporter: Sebb The Incubator home page has a prominent link to [https://www.apachecon.com/acna2022/] This is very out of date. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-266) Update the website redirect page of weex
[ https://issues.apache.org/jira/browse/INCUBATOR-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17358611#comment-17358611 ] Sebb commented on INCUBATOR-266: Yes. > Update the website redirect page of weex > > > Key: INCUBATOR-266 > URL: https://issues.apache.org/jira/browse/INCUBATOR-266 > Project: Incubator > Issue Type: Task >Reporter: Willem Jiang >Priority: Major > > We can create an empty index.html for the retired project to redirect the > page to incubator project status page. > Here are the more information about in the mailing list. > https://lists.apache.org/thread.html/r361999f665b90434c285161925935f3da759c6f95d6959763860f4f2%40%3Cgeneral.incubator.apache.org%3E -- 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-262) Retired podlings with active websites
[ https://issues.apache.org/jira/browse/INCUBATOR-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17314742#comment-17314742 ] Sebb commented on INCUBATOR-262: The PR has been applied, so it should now just be a question of creating the appropriate directories under retired/ [1] Git does not checkout empty directories, so I suggest creating an empty index.html file in each one. [1] https://github.com/apache/incubator/tree/master/assets/retired > Retired podlings with active websites > - > > Key: INCUBATOR-262 > URL: https://issues.apache.org/jira/browse/INCUBATOR-262 > Project: Incubator > Issue Type: Bug >Reporter: Sebb >Priority: Major > > The following podlings have retired, but still have websites. > These should be redirected to the status files, i.e. > http://incubator.apache.org/projects/.html > ["amaterasu", "http://amaterasu.incubator.apache.org;] > ["ariatosca", "http://ariatosca.apache.org;, > "http://ariatosca.incubator.apache.org;] > ["edgent", "http://edgent.incubator.apache.org;] > ["hdt", "http://hdt.incubator.apache.org;] > ["myriad", "http://myriad.apache.org;, "http://myriad.incubator.apache.org;] > ["odftoolkit", "http://odftoolkit.apache.org;, > "http://odftoolkit.incubator.apache.org;] > ["provisionr", "http://provisionr.incubator.apache.org;] > ["s2graph", "http://s2graph.apache.org;, > "http://s2graph.incubator.apache.org;] > ["tamaya", "http://tamaya.apache.org;, "http://tamaya.incubator.apache.org;] > ["taverna", "https://taverna.incubator.apache.org/;] > ["warble", "http://warble.apache.org;, "http://warble.incubator.apache.org;] -- 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-262) Retired podlings with active websites
[ https://issues.apache.org/jira/browse/INCUBATOR-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17314099#comment-17314099 ] Sebb commented on INCUBATOR-262: All the retired podling websites need to point to the relevant status files, so it does not matter what they are showing currently. There are two ways to set up the necessary redirection: 1. Find the relevant website sources and set up the htaccess files. These are defined in the various podling git repos. Some of these repos are already marked read-only, so INFRA needs to get involved at some point. 2. Wait for INFRA to help with INFRA-21451 by applying PR 670. This would all Incubator to control redirection by simply creating the retired/podling directory marker file. Either way, progress requires Infra to get involved. I think the minimum work all round is for the PR to be applied, as that does not require any changes to the podling repos. Fixing the podling website builds is considerably more work. > Retired podlings with active websites > - > > Key: INCUBATOR-262 > URL: https://issues.apache.org/jira/browse/INCUBATOR-262 > Project: Incubator > Issue Type: Bug >Reporter: Sebb >Priority: Major > > The following podlings have retired, but still have websites. > These should be redirected to the status files, i.e. > http://incubator.apache.org/projects/.html > ["amaterasu", "http://amaterasu.incubator.apache.org;] > ["ariatosca", "http://ariatosca.apache.org;, > "http://ariatosca.incubator.apache.org;] > ["edgent", "http://edgent.incubator.apache.org;] > ["hdt", "http://hdt.incubator.apache.org;] > ["myriad", "http://myriad.apache.org;, "http://myriad.incubator.apache.org;] > ["odftoolkit", "http://odftoolkit.apache.org;, > "http://odftoolkit.incubator.apache.org;] > ["provisionr", "http://provisionr.incubator.apache.org;] > ["s2graph", "http://s2graph.apache.org;, > "http://s2graph.incubator.apache.org;] > ["tamaya", "http://tamaya.apache.org;, "http://tamaya.incubator.apache.org;] > ["taverna", "https://taverna.incubator.apache.org/;] > ["warble", "http://warble.apache.org;, "http://warble.incubator.apache.org;] -- 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] [Resolved] (INCUBATOR-260) warble podling retired, but the website is active
[ https://issues.apache.org/jira/browse/INCUBATOR-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved INCUBATOR-260. Resolution: Duplicate > warble podling retired, but the website is active > - > > Key: INCUBATOR-260 > URL: https://issues.apache.org/jira/browse/INCUBATOR-260 > Project: Incubator > Issue Type: Bug >Reporter: Sebb >Priority: Major > > as the subject says -- 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] [Resolved] (INCUBATOR-261) ariatosca podling retired, but the website is still active
[ https://issues.apache.org/jira/browse/INCUBATOR-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved INCUBATOR-261. Resolution: Duplicate > ariatosca podling retired, but the website is still active > -- > > Key: INCUBATOR-261 > URL: https://issues.apache.org/jira/browse/INCUBATOR-261 > Project: Incubator > Issue Type: Bug >Reporter: Sebb >Priority: Major > > As the subject says -- 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] [Created] (INCUBATOR-262) Retired podlings with active websites
Sebb created INCUBATOR-262: -- Summary: Retired podlings with active websites Key: INCUBATOR-262 URL: https://issues.apache.org/jira/browse/INCUBATOR-262 Project: Incubator Issue Type: Bug Reporter: Sebb The following podlings have retired, but still have websites. These should be redirected to the status files, i.e. http://incubator.apache.org/projects/.html ["amaterasu", "http://amaterasu.incubator.apache.org;] ["ariatosca", "http://ariatosca.apache.org;, "http://ariatosca.incubator.apache.org;] ["edgent", "http://edgent.incubator.apache.org;] ["hdt", "http://hdt.incubator.apache.org;] ["myriad", "http://myriad.apache.org;, "http://myriad.incubator.apache.org;] ["odftoolkit", "http://odftoolkit.apache.org;, "http://odftoolkit.incubator.apache.org;] ["provisionr", "http://provisionr.incubator.apache.org;] ["s2graph", "http://s2graph.apache.org;, "http://s2graph.incubator.apache.org;] ["tamaya", "http://tamaya.apache.org;, "http://tamaya.incubator.apache.org;] ["taverna", "https://taverna.incubator.apache.org/;] ["warble", "http://warble.apache.org;, "http://warble.incubator.apache.org;] -- 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] [Created] (INCUBATOR-261) ariatosca podling retired, but the website is still active
Sebb created INCUBATOR-261: -- Summary: ariatosca podling retired, but the website is still active Key: INCUBATOR-261 URL: https://issues.apache.org/jira/browse/INCUBATOR-261 Project: Incubator Issue Type: Bug Reporter: Sebb As the subject says -- 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] [Created] (INCUBATOR-260) warble podling retired, but the website is active
Sebb created INCUBATOR-260: -- Summary: warble podling retired, but the website is active Key: INCUBATOR-260 URL: https://issues.apache.org/jira/browse/INCUBATOR-260 Project: Incubator Issue Type: Bug Reporter: Sebb as the subject says -- 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] [Created] (INCUBATOR-259) Taverna retired in Feb 2020, yet has website and release dirs
Sebb created INCUBATOR-259: -- Summary: Taverna retired in Feb 2020, yet has website and release dirs Key: INCUBATOR-259 URL: https://issues.apache.org/jira/browse/INCUBATOR-259 Project: Incubator Issue Type: Bug Reporter: Sebb The Taverna website does not indicate that the podling has retired, and the release directories are still present: https://dist.apache.org/repos/dist/release/incubator/taverna/ https://dist.apache.org/repos/dist/dev/incubator/taverna/ -- 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] [Created] (INCUBATOR-258) S2graph podling retired, but still has website and release dirs
Sebb created INCUBATOR-258: -- Summary: S2graph podling retired, but still has website and release dirs Key: INCUBATOR-258 URL: https://issues.apache.org/jira/browse/INCUBATOR-258 Project: Incubator Issue Type: Bug Reporter: Sebb The s2graph podling retired in Nov 2020, but the website is still present as are: https://dist.apache.org/repos/dist/release/incubator/s2graph/ https://dist.apache.org/repos/dist/dev/incubator/s2graph/ -- 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] [Created] (INCUBATOR-257) Myriad retired in Jan 2020, yet website and releases are still present
Sebb created INCUBATOR-257: -- Summary: Myriad retired in Jan 2020, yet website and releases are still present Key: INCUBATOR-257 URL: https://issues.apache.org/jira/browse/INCUBATOR-257 Project: Incubator Issue Type: Bug Reporter: Sebb The myriad website is still present, as are the release and dev directories: https://dist.apache.org/repos/dist/release/incubator/myriad/ https://dist.apache.org/repos/dist/dev/incubator/myriad/ -- 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-256) Jenkins Clutch job does not trigger on source changes
[ https://issues.apache.org/jira/browse/INCUBATOR-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17211872#comment-17211872 ] Sebb commented on INCUBATOR-256: This seems to be working well -- thanks! > Jenkins Clutch job does not trigger on source changes > - > > Key: INCUBATOR-256 > URL: https://issues.apache.org/jira/browse/INCUBATOR-256 > Project: Incubator > Issue Type: Bug >Reporter: Sebb >Assignee: Dave Fisher >Priority: Major > > AFAICT, the Jenkins clutch job which builds the data still in SVN does not > detect changes to SVN. > It would help keep the site up to date if there was a regular check of SVN > Perhaps someone with karma could see to this? -- 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-256) Jenkins Clutch job does not trigger on source changes
[ https://issues.apache.org/jira/browse/INCUBATOR-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17211143#comment-17211143 ] Sebb commented on INCUBATOR-256: It should be sufficient to watch https://svn.apache.org/repos/asf/incubator/public/trunk/content. No point trying to narrow it further - there are unlikely to be other changes, and it does not matter too much if there are. Rather than trigger on every change, an hourly check would be a great improvement > Jenkins Clutch job does not trigger on source changes > - > > Key: INCUBATOR-256 > URL: https://issues.apache.org/jira/browse/INCUBATOR-256 > Project: Incubator > Issue Type: Bug >Reporter: Sebb >Priority: Major > > AFAICT, the Jenkins clutch job which builds the data still in SVN does not > detect changes to SVN. > It would help keep the site up to date if there was a regular check of SVN > Perhaps someone with karma could see to this? -- 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-256) Jenkins Clutch job does not trigger on source changes
[ https://issues.apache.org/jira/browse/INCUBATOR-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17211097#comment-17211097 ] Sebb commented on INCUBATOR-256: Or perhaps could set up a dummy job that watches SVN and triggers the existing job > Jenkins Clutch job does not trigger on source changes > - > > Key: INCUBATOR-256 > URL: https://issues.apache.org/jira/browse/INCUBATOR-256 > Project: Incubator > Issue Type: Bug >Reporter: Sebb >Priority: Major > > AFAICT, the Jenkins clutch job which builds the data still in SVN does not > detect changes to SVN. > It would help keep the site up to date if there was a regular check of SVN > Perhaps someone with karma could see to this? -- 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-256) Jenkins Clutch job does not trigger on source changes
[ https://issues.apache.org/jira/browse/INCUBATOR-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17211095#comment-17211095 ] Sebb commented on INCUBATOR-256: Configure Build Trigger / Poll SCM This assumes the SCM is defined as the SVN source of the data > Jenkins Clutch job does not trigger on source changes > - > > Key: INCUBATOR-256 > URL: https://issues.apache.org/jira/browse/INCUBATOR-256 > Project: Incubator > Issue Type: Bug >Reporter: Sebb >Priority: Major > > AFAICT, the Jenkins clutch job which builds the data still in SVN does not > detect changes to SVN. > It would help keep the site up to date if there was a regular check of SVN > Perhaps someone with karma could see to this? -- 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] [Created] (INCUBATOR-256) Jenkins Clutch job does not trigger on source changes
Sebb created INCUBATOR-256: -- Summary: Jenkins Clutch job does not trigger on source changes Key: INCUBATOR-256 URL: https://issues.apache.org/jira/browse/INCUBATOR-256 Project: Incubator Issue Type: Bug Reporter: Sebb AFAICT, the Jenkins clutch job which builds the data still in SVN does not detect changes to SVN. It would help keep the site up to date if there was a regular check of SVN Perhaps someone with karma could see to this? -- 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] [Created] (INCUBATOR-243) Are both cvs@ and commits@ mailing lists needed?
Sebb created INCUBATOR-243: -- Summary: Are both cvs@ and commits@ mailing lists needed? Key: INCUBATOR-243 URL: https://issues.apache.org/jira/browse/INCUBATOR-243 Project: Incubator Issue Type: Task Reporter: Sebb Incubator currently has both cvs@ and commits@ mailing lists. That seems unnecessary. Given that CVS has not been used for a long while, maybe that list should be shut down and any emails redirected to commits@. Please raise an INFRA JIRA if so. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Created] (INCUBATOR-236) Podling list does not show aliases
Sebb created INCUBATOR-236: -- Summary: Podling list does not show aliases Key: INCUBATOR-236 URL: https://issues.apache.org/jira/browse/INCUBATOR-236 Project: Incubator Issue Type: Bug Reporter: Sebb The podling list at http://incubator.apache.org/projects/ ought to show podling aliases to make it easier to search for renamed podlings. For example at present, there is no reference to SensSoft => Flagon. -- 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-234) Incubator Cookbook
[ https://issues.apache.org/jira/browse/INCUBATOR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16802834#comment-16802834 ] Sebb commented on INCUBATOR-234: Also podlings may become part of an existing TLP rather than a new TLP > Incubator Cookbook > -- > > Key: INCUBATOR-234 > URL: https://issues.apache.org/jira/browse/INCUBATOR-234 > Project: Incubator > Issue Type: Task > Components: site >Reporter: Bertrand Delacretaz >Priority: Major > > As discussed at [1] the goal is to create a single page Incubator Cookbook, > with all the details of the incubation process, in chronological order of the > incubation journey. > This should be as concise as possible, with links to more information where > strictly needed, and adopt a friendly tone in the sense of clearly making the > Incubator a service to our podlings. > Draft page at [http://incubator.apache.org/cookbook/] , built from small > pieces of content found under > [https://github.com/apache/incubator/tree/master/pages/cookbook] > As a next step I'll focus on getting a mostly consistent set of topics and we > can then share the writing work. > [1] > https://lists.apache.org/thread.html/51fe5d659778bed5b6385c7c39bbdf688d02f1b1dbe02d595d514cbb@%3Cgeneral.incubator.apache.org%3E -- 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-231) Cleanup Git-generated Incubator website
[ https://issues.apache.org/jira/browse/INCUBATOR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798287#comment-16798287 ] Sebb commented on INCUBATOR-231: When building locally, the process creates a lot of files under pages/clutch It would be useful to exclude these using something like the following: # Generated by clutch2.py: /pages/clutch/_includes/*.ad /pages/clutch/*.ad # This page is maintained in Git !/pages/clutch/index.ad Alternatively, perhaps create the pages with a different suffix (but still processed as asciidoc, e.g. .adoc) This would require changes to the includes, but would make clear which ones are temporary. Yet another approach might be to commit the files to the repo. As it is currently, clutch takes quite a long time to run. Having copies in the repo would allow builds to occur without running clutch every time. [Ideally clutch would only run if there was a change, but detecting that may be just as much effort.] > 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 > Attachments: clutch-analysis.tar.gz, clutch-pages.tar.gz, > clutch.py.diff.txt, clutch2data.txt, clutch2data.txt, clutch2status.txt, > gitbox.clutch.data.txt, gitbox.svn.diff.txt > > > [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] [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=16788396#comment-16788396 ] Sebb commented on INCUBATOR-231: [~wave] AIUI the entry in the DTD means that the value must be 1 or 2 or 3, so I think the DTD is correct. See [1] for sample failed job. I saw the Comdev thread. [~jmclean] Does your editor support the DTD? But I agree that it would be better to use an app to update the data. It could do other useful stuff like try and keep the group numbers roughly even. [1] [https://lists.apache.org/thread.html/bf1dbeed097eb07be02f77daab7bba956b0610030b73bd7e9f86a690@%3Cnotifications.whimsical.apache.org%3E] > 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 > Attachments: clutch2data.txt, gitbox.clutch.data.txt, > gitbox.svn.diff.txt > > > [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] [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=16788371#comment-16788371 ] Sebb commented on INCUBATOR-231: One of the Whimsy jobs that creates the public JSON files failed, because reporting group must be a single digit. I think there needs to be a way to test changes to the file before it is committed. A basic test would be to check for well-formed XML. It may be hard to check for errors in the data itself, although I think the DTD might have caught this particular error. Maybe there should be an app to do the editting? Similarly for other data files that need to be maintained. Might be a good GSOC task? Just a thought (I'm not volunteering as a mentor) > 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 > Attachments: clutch2data.txt, gitbox.clutch.data.txt, > gitbox.svn.diff.txt > > > [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] [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=16785507#comment-16785507 ] Sebb commented on INCUBATOR-231: The status pages are also used for current and graduated podlings. Before a podling creates its website, the status page is the place where details can be found by the public. > 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] [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=16784815#comment-16784815 ] Sebb commented on INCUBATOR-231: It's been a while since I worked on clutch, but I don't think it extracts all the information from the podling.xml files. Some of the content is free-format embedded HTML. It may not be possible to recreate the status html files from the pickled data, if that is the intention. > 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] [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=16784683#comment-16784683 ] Sebb commented on INCUBATOR-231: Note that content/projects/.xml is used to generate the web page incubator.a.o/project/.html The web page is referenced in many places; in particular if a podling retires it becomes the web page for the podling. e.g. http://incubator.apache.org/alois and gearpump.apache.org both redirect to their status pages. > 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] [Resolved] (INCUBATOR-131) airflow installation issue
[
https://issues.apache.org/jira/browse/INCUBATOR-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved INCUBATOR-131.
Resolution: Invalid
> airflow installation issue
> --
>
> Key: INCUBATOR-131
> URL: https://issues.apache.org/jira/browse/INCUBATOR-131
> Project: Incubator
> Issue Type: Bug
>Reporter: Afroz Hussain
>Priority: Major
>
> Before I tell you about my issue, let me describe my Airflow environment:
> Python Version: Python 2.6.6(tried on 2.7)
> Operating System: RedHat 6.5(tried on RedHat 7.5)
> Python packages: argparse==1.2.1 aws-cfn-bootstrap==1.3
> backports.ssl-match-hostname==3.4.0.2 boto==2.34.0 cas==0.15 chardet==2.0.1
> Cheetah==2.4.1 cloud-init==0.7.2 configobj==4.6.0 ethtool==0.6
> freeipa==2.0.0a0 iniparse==0.3.1 iotop==0.3.2 ipapython==3.0.0 iwlib==1.0
> kerberos==1.1 lockfile==0.9.1 lxml==2.2.3 M2Crypto==0.20.2 Markdown==2.0.1
> matplotlib==0.99.1.1 netaddr==0.7.5 nose==0.10.4 numpy==1.4.1
> ordereddict==1.2 paramiko==1.7.5 policycoreutils-default-encoding==0.1
> prettytable==0.6.1 pycparser==2.14 pycrypto==2.0.1 pycurl==7.19.0
> Pygments==1.1.1 pygpgme==0.1 pyOpenSSL==0.10 pystache==0.5.4
> python-daemon==1.5.5 python-dateutil==1.4.1 python-default-encoding==0.1
> python-dmidecode==3.10.13 python-ldap==2.3.10 python-nss==0.16.0 pytz===2010h
> PyYAML==3.10 requests==1.1.0 rhnlib==2.5.22 rhsm==1.12.5 setools==1.0
> simplejson==2.0.9 six==1.9.0 SSSDConfig==1.12.4 urlgrabber==3.9.1
> urllib3==1.5 yum-metadata-parser==1.1.2
> I am unable to install airflow using "pip install airflow", getting errors as:
> RHEL 6
> Complete output from command python setup.py egg_info:
> Traceback (most recent call last):
> File "", line 1, in
> File "/tmp/pip-build-bI9hiv/pandas/setup.py", line 631, in
> **setuptools_kwargs)
> File "/usr/lib64/python2.6/distutils/core.py", line 113, in setup
> setup_distribution = dist = klass(attrs)
> File "/usr/lib/python2.6/site-packages/setuptools/dist.py", line 221, in
> __init_
> self.fetch_build_eggs(attrs.pop('setup_requires'))
> File "/usr/lib/python2.6/site-packages/setuptools/dist.py", line 245, in
> fetch_build_eggs
> parse_requirements(requires), installer=self.fetch_build_egg
> File "/usr/lib/python2.6/site-packages/pkg_resources.py", line 550, in resolve
> raise VersionConflict(dist,req) # XXX put more info here
> pkg_resources.VersionConflict: (numpy 1.4.1
> (/usr/lib64/python2.6/site-packages), Requirement.parse('numpy>=1.7.0'))
>
> Command "python setup.py egg_info" failed with error code 1 in
> /tmp/pip-build-bI9hiv/pandas
> RHEL 7:
> Complete output from command python setup.py egg_info:
> Running from numpy source directory.
> /tmp/easy_install-9Yjxgb/numpy-1.11.0/setup.py:327: UserWarning: Unrecognized
> setuptools command, proceeding with generating Cython sources and expanding
> templates
> warnings.warn("Unrecognized setuptools command, proceeding with "
> /tmp/easy_install-9Yjxgb/numpy-1.11.0/numpy/distutils/system_info.py:1640:
> UserWarning:
> Atlas (http://math-atlas.sourceforge.net/) libraries not found.
> Directories to search for the libraries can be specified in the
> numpy/distutils/site.cfg file (section [atlas]) or by setting
> the ATLAS environment variable.
> warnings.warn(AtlasNotFoundError.doc)
> /tmp/easy_install-9Yjxgb/numpy-1.11.0/numpy/distutils/system_info.py:1649:
> UserWarning:
> Blas (http://www.netlib.org/blas/) libraries not found.
> Directories to search for the libraries can be specified in the
> numpy/distutils/site.cfg file (section [blas]) or by setting
> the BLAS environment variable.
> warnings.warn(BlasNotFoundError.doc)
> /tmp/easy_install-9Yjxgb/numpy-1.11.0/numpy/distutils/system_info.py:1652:
> UserWarning:
> Blas (http://www.netlib.org/blas/) sources not found.
> Directories to search for the sources can be specified in the
> numpy/distutils/site.cfg file (section [blas_src]) or by setting
> the BLAS_SRC environment variable.
> warnings.warn(BlasSrcNotFoundError.doc)
> /tmp/easy_install-9Yjxgb/numpy-1.11.0/numpy/distutils/system_info.py:1542:
> UserWarning:
> Atlas (http://math-atlas.sourceforge.net/) libraries not found.
> Directories to search for the libraries can be specified in the
> numpy/distutils/site.cfg file (section [atlas]) or by setting
> the ATLAS environment variable.
> warnings.warn(AtlasNotFoundError.doc)
> /tmp/easy_install-9Yjxgb/numpy-1.11.0/numpy/distutils/system_info.py:1553:
> UserWarning:
> Lapack (http://www.netlib.org/lapack/) libraries not found.
> Directories to search for the libraries can be specified in the
> numpy/distutils/site.cfg file (section [lapack]) or by setting
> the LAPACK environment variable.
> warnings.warn(LapackNotFoundError.doc)
> /tmp/easy_install-9Yjxgb/numpy-1.11.0/numpy/distutils/system_info.py:1556:
>
[jira] [Created] (INCUBATOR-212) Incorrect bounce message for retired podling mailing lists
Sebb created INCUBATOR-212: -- Summary: Incorrect bounce message for retired podling mailing lists Key: INCUBATOR-212 URL: https://issues.apache.org/jira/browse/INCUBATOR-212 Project: Incubator Issue Type: Bug Reporter: Sebb When a podling is retired, the mailing lists are shut down. Mails to the lists are returned with a message which says: "Hi. This is the qmail-send program at apache.org. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. : The project is retired. See https://attic.apache.org; However podlings are not handled by Attic. The bounce message for podlings ought to be changed to something more 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-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:all-tabpanel ] Sebb closed INCUBATOR-127. -- Resolution: Fixed > 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 >Priority: Major > > 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 (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-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:comment-tabpanel=16106664#comment-16106664 ] Sebb commented on INCUBATOR-201: No point assigning this to me; I don't make the decision. > 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 > > 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] [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 ] Sebb reassigned INCUBATOR-201: -- Assignee: (was: 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 > > 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] [Reopened] (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 ] Sebb reopened INCUBATOR-201: Incubator needs to decide ... > 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 > > 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.3.15#6346) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Updated] (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 ] Sebb updated INCUBATOR-201: --- INFRA-Members: (was: [infrastructure-team]) Component/s: (was: Mail Archives) (was: Mailing Lists) Workflow: classic default workflow (was: INFRA Workflow) Issue Type: Task (was: Bug) Key: INCUBATOR-201 (was: INFRA-12624) Project: Incubator (was: Infrastructure) > 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 > > 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.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=16019365#comment-16019365 ] Sebb commented on INCUBATOR-198: It does not seem right to delete any archives that were correctly published originally. I think the only reason should be an inadvertent publication (which would normally have been done at the time) or perhaps a take-down notice. > 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] [Commented] (INCUBATOR-130) Nuvem in limbo
[ https://issues.apache.org/jira/browse/INCUBATOR-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16019350#comment-16019350 ] Sebb commented on INCUBATOR-130: Tuscany has since moved to the Attic > Nuvem in limbo > -- > > Key: INCUBATOR-130 > URL: https://issues.apache.org/jira/browse/INCUBATOR-130 > Project: Incubator > Issue Type: Bug >Reporter: Sebb > > The Nuvem podling appears to be in limbo. > According to podling.xml it graduated, but the comment says: > "The podling was voted to become part of Tuscany in Nov 2012 but (as of Aug > 2014) nothing has happened." > The SVN tree still exists. > Either the graduation should be completed or the podling should be retired. -- 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-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-tabpanel=16019347#comment-16019347 ] Sebb commented on INCUBATOR-127: Podling has graduated - it looks as though the renames were done > 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.15#6346) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (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:comment-tabpanel=16019341#comment-16019341 ] Sebb commented on INCUBATOR-128: This has been fixed; the issue can be closed > 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] [Created] (INCUBATOR-199) Extend podlings.xml to include old names and TLP parent
Sebb created INCUBATOR-199: -- Summary: Extend podlings.xml to include old names and TLP parent Key: INCUBATOR-199 URL: https://issues.apache.org/jira/browse/INCUBATOR-199 Project: Incubator Issue Type: New Feature Reporter: Sebb Podling names change fairly often. It would be useful to be able to list old names in the podlings file. At present this info is only in the free-form text. Also where a podling graduates as a project of a PMC, it would be useful to be able to document the PMC. At present this would have to be extracted from the url field (or the text) AFAIK additional attributes do not cause problems for existing parsing routines. However the DTD will have to be extended to allow for the new entries. -- 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-130) Nuvem in limbo
Sebb created INCUBATOR-130: -- Summary: Nuvem in limbo Key: INCUBATOR-130 URL: https://issues.apache.org/jira/browse/INCUBATOR-130 Project: Incubator Issue Type: Bug Reporter: Sebb The Nuvem podling appears to be in limbo. According to podling.xml it graduated, but the comment says: "The podling was voted to become part of Tuscany in Nov 2012 but (as of Aug 2014) nothing has happened." The SVN tree still exists. Either the graduation should be completed or the podling should be retired. -- 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-125) How-to guide for Assembling LICENSE and NOTICE
[ https://issues.apache.org/jira/browse/INCUBATOR-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13440563#comment-13440563 ] Sebb commented on INCUBATOR-125: Very useful. compiled package = binary package would be clearer. I don't think it's advisable to incorporate the list of license types; just link to where the official list is found. How-to guide for Assembling LICENSE and NOTICE Key: INCUBATOR-125 URL: https://issues.apache.org/jira/browse/INCUBATOR-125 Project: Incubator Issue Type: Improvement Components: site Reporter: Marvin Humphrey Attachments: licensing_howto.mdtext While the ASF provides reference documentation for LICENSE and NOTICE, confusion persists and existing versions vary widely in quality. To address these problems, we should augment the reference documentation with a how-to guide which provides formulaic instructions for assembling LICENSE and NOTICE under common conditions. One key feature of this how-to should be a mapping of approved licenses to what they require as far as NOTICE. This mapping will help PMCs determine when the licensing information of a dependency contains a required third party notice which must be added to NOTICE. There are at least four possible locations where this how-to might live: * www.apache.org/dev/licensing_howto.html -- probably the best location, considering the intended audience. * www.apache.org/legal/licensing_howto.html -- if legal wants it. * incubator.apache.org/guides/licensing_howto.html -- probably not ideal, because the information applies to TLPs as well as podlings and we have a problem with duplication. * Somewhere on community.apache.org -- in theory. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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-110) Need access to incubator group
[ https://issues.apache.org/jira/browse/INCUBATOR-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13094937#comment-13094937 ] Sebb commented on INCUBATOR-110: This can be closed; eyang is in the incubator group: http://people.apache.org/committers-by-project.html#incubator Need access to incubator group -- Key: INCUBATOR-110 URL: https://issues.apache.org/jira/browse/INCUBATOR-110 Project: Incubator Issue Type: Wish Components: policy Reporter: Eric Yang Chukwa has been accepted into incubator, but my user account on people is not part of incubator group. I need this to move chukwa website to incubator. Thanks -- This message is automatically generated by JIRA. 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] (INCUBATOR-116) XML Beans CXX project is in limbo
XML Beans CXX project is in limbo - Key: INCUBATOR-116 URL: https://issues.apache.org/jira/browse/INCUBATOR-116 Project: Incubator Issue Type: Bug Environment: http://mail-archives.apache.org/mod_mbox/incubator-general/201108.mbox/%3ccaogo0vbxyrd_tktsgke+bkc8g0pzzpvjxuh7zzylu5wccjf...@mail.gmail.com%3E Reporter: Sebb The XML Beans C++ project is in limbo: It has a website [1], a status page [2] but is not mentioned in clutch [3] or the summary projects page [4] as dormant or retired. It still has a RW podling SVN directory [5] but that was last updated in 2007. AFAICT the project needs to be retired, and SVN deleted if the copyright issues have not been addressed, otherwise made read-only As an initial step, I have made SVN read-only (the access group was empty anyway). [1] http://incubator.apache.org/xmlbeanscxx/ [2] http://incubator.apache.org/projects/xmlbeanscxx.html [3] http://incubator.apache.org/clutch.html [4] http://incubator.apache.org/projects/index.html [5] http://svn.apache.org/repos/asf/incubator/xmlbeanscxx/ -- This message is automatically generated by JIRA. 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: (INCUBATOR-108) Incubator navigation still includes Subversion and Cassandra TLPs
Incubator navigation still includes Subversion and Cassandra TLPs - Key: INCUBATOR-108 URL: https://issues.apache.org/jira/browse/INCUBATOR-108 Project: Incubator Issue Type: Bug Components: site Reporter: Sebb Incubator navigation still includes links to the podlings Subversion and Cassandra, however these are now TLPs, so it's a bit confusing to still have them listed as podlings -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Commented: (INCUBATOR-106) MetaCarta Lucene Connector Framework code grant
[ https://issues.apache.org/jira/browse/INCUBATOR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12833785#action_12833785 ] Sebb commented on INCUBATOR-106: Try geronimo-javamail_1.3.1_spec-1.1.jar? MetaCarta Lucene Connector Framework code grant --- Key: INCUBATOR-106 URL: https://issues.apache.org/jira/browse/INCUBATOR-106 Project: Incubator Issue Type: New Feature Reporter: Karl Wright Assignee: Grant Ingersoll Attachments: apache-lcf-software-grant.tar.gz, apache-lcf-software-grant.tar.gz, apache-lcf-software-grant.tar.gz, build.xml kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ dpkg --list | grep coreutils ii coreutils 6.10-6 The GNU core utilities kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ md5sum apache-lcf-software-grant.tar.gz 1e429efbc2359a18912948411e09a76f apache-lcf-software-grant.tar.gz kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Commented: (INCUBATOR-103) [IP-GRANT] PyLucene
[ https://issues.apache.org/jira/browse/INCUBATOR-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12660077#action_12660077 ] Sebb commented on INCUBATOR-103: The NOTICE file is for any required attributions, including the ASF one. Normally it contains the copyright lines from 3rd parties as well; there is no COPYRIGHT file. The LICENSE file must contain the AL, and may either contain other licences in full or contain pointers to where the other required licences can be found. See http://www.apache.org/legal/src-headers.html http://www.apache.org/licenses/example-NOTICE.txt [IP-GRANT] PyLucene --- Key: INCUBATOR-103 URL: https://issues.apache.org/jira/browse/INCUBATOR-103 Project: Incubator Issue Type: Bug Reporter: Andi Vajda This is an archive of PyLucene's HEAD revision (488): http://people.apache.org/~vajda/PyLucene-2.4.0-2-488.tar.bz2 http://people.apache.org/~vajda/PyLucene-2.4.0-2-488.tar.bz2.md5 The md5 hash was created with Mac OS X 10.5.5's /sbin/md5: md5 PyLucene-2.4.0-2-488.tar.bz2 PyLucene-2.4.0-2-488.tar.bz2.md5 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Commented: (INCUBATOR-78) Unreliable report schedule and list of podlings
[ https://issues.apache.org/jira/browse/INCUBATOR-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12610817#action_12610817 ] Sebb commented on INCUBATOR-78: --- Note that some incubator projects don't currently have trunk directories. This probably needs to be sorted out. Having the file under trunk means that it will appear in branches and tags, and will probably appear in releases as well. This may or may not be seen as a problem. Might be worth considering storing the file at the same level as trunk? This is a bit more awkward to edit (need to check out non-recursively) but is easier to find when navigating SVN. Unreliable report schedule and list of podlings --- Key: INCUBATOR-78 URL: https://issues.apache.org/jira/browse/INCUBATOR-78 Project: Incubator Issue Type: Bug Reporter: Bertrand Delacretaz As discussed in http://markmail.org/message/le55q754m4eypu7r it would be useful to generate the podlings report schedule and the list of projects on the http://incubator.apache.org/ automatically from a master file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
