Re: [VOTE] Graduation of Apache Allura from the Incubator
HI, Just a minor thing (IMO). I was just taking a look at [1] and what strikes me is a lack of ASF branding. While it's clear in the text and from the domain that the project is an ASF one, the subtitles Forge software for hosting software projects and Brought to you by: brondsem, masterbunnyfu, rbowen, vansteenburgh and lack of links back to the ASF don't immediately give that impression. I also looked at where I thought the release should be published [2] and it contains no files. Is that the correct location? That's the path in the release guidelines. [2] It also quite hard for someone outside the project to see what is happing on the mailing list due to the large amount at allure ticket emails. Have you consider having a separate issues list? Thanks, Justin 1. https://forge-allura.apache.org/p/allura/wiki/Apache%20Allura%20(incubating)%20Wiki/ 2. https://dist.apache.org/repos/dist/dev/incubator/allura/ 3. https://forge-allura.apache.org/p/allura/wiki/ASF%20Release%20Guidelines/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Apache Allura from the Incubator
On 15 March 2014 01:23, Justin Mclean jus...@classsoftware.com wrote: HI, Just a minor thing (IMO). I was just taking a look at [1] and what strikes me is a lack of ASF branding. While it's clear in the text and from the domain that the project is an ASF one, the subtitles Forge software for hosting software projects and Brought to you by: brondsem, masterbunnyfu, rbowen, vansteenburgh and lack of links back to the ASF don't immediately give that impression. That's a good point. The board decided a long time ago that @author tags were deprecated in code; partly because they get out of date, but mainly because the ASF is a community, and code is a co-operative effort. Seems to me the Brought to you sentence has similar problems, and should be removed. [There are other ways to attribute contributions, e.g. on a page that lists committers, in the Maven POM (if used) etc.] Also I think (almost?) all other TLPs include the ASF feather which links back to the main ASF page. I also looked at where I thought the release should be published [2] and it contains no files. Is that the correct location? That's the path in the release guidelines. [2] Yes and no - [2] is where RCs can be uploaded for voting; actual releases are published from [2a], e.g. by moving them from [2]. There are files at [2a]. It also quite hard for someone outside the project to see what is happing on the mailing list due to the large amount at allure ticket emails. Have you consider having a separate issues list? +1 Thanks, Justin 1. https://forge-allura.apache.org/p/allura/wiki/Apache%20Allura%20(incubating)%20Wiki/ 2. https://dist.apache.org/repos/dist/dev/incubator/allura/ 2a. https://dist.apache.org/repos/dist/release/incubator/allura/ 3. https://forge-allura.apache.org/p/allura/wiki/ASF%20Release%20Guidelines/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Apache Allura from the Incubator
On Mon, Mar 17, 2014 at 6:58 AM, sebb seb...@gmail.com wrote: On 15 March 2014 01:23, Justin Mclean jus...@classsoftware.com wrote: While it's clear in the text and from the domain that the project is an ASF one, the subtitles Forge software for hosting software projects and Brought to you by: brondsem, masterbunnyfu, rbowen, vansteenburgh and lack of links back to the ASF don't immediately give that impression. That's a good point. The board decided a long time ago that @author tags were deprecated in code; partly because they get out of date, but mainly because the ASF is a community, and code is a co-operative effort. Seems to me the Brought to you sentence has similar problems, and should be removed. Well, I should note that the Brought to you by line is actually automatically generated from the project permissions, so there is little chance of it getting out of date. That said, it will be more useful as we move more of the Allura work (specifically, ticket activity) over from the old SourceForge location to the Apache hosted Allura instance, as is the plan. Also I think (almost?) all other TLPs include the ASF feather which links back to the main ASF page. I have updated the page at https://forge-allura.apache.org/p/allura/ to include the ASF feather logo which links to http://www.apache.org/foundation/ It also quite hard for someone outside the project to see what is happing on the mailing list due to the large amount at allure ticket emails. Have you consider having a separate issues list? +1 This has been raised before and some things have been done to improve the tracker notifications on the mailing list (combining status change and comment notifications, fixing threading, etc) and it was decided at the time that it was reasonable to continue to include that traffic (with improvements) on the list. However, I believe the possibility of splitting it in the future was left open, should anyone continue to feel it was a problem. Still, this doesn't seem to me like something that should block graduation, as the tracker communications are indeed related to Allura development.
Re: [VOTE] Graduation of Apache Allura from the Incubator
On Mar 17, 2014, at 11:17 AM, Cory Johns john...@gmail.com wrote: On Mon, Mar 17, 2014 at 6:58 AM, sebb seb...@gmail.com wrote: On 15 March 2014 01:23, Justin Mclean jus...@classsoftware.com wrote: While it's clear in the text and from the domain that the project is an ASF one, the subtitles Forge software for hosting software projects and Brought to you by: brondsem, masterbunnyfu, rbowen, vansteenburgh and lack of links back to the ASF don't immediately give that impression. That's a good point. The board decided a long time ago that @author tags were deprecated in code; partly because they get out of date, but mainly because the ASF is a community, and code is a co-operative effort. Seems to me the Brought to you sentence has similar problems, and should be removed. Well, I should note that the Brought to you by line is actually automatically generated from the project permissions, so there is little chance of it getting out of date. That said, it will be more useful as we move more of the Allura work (specifically, ticket activity) over from the old SourceForge location to the Apache hosted Allura instance, as is the plan. It should still be removed... It's brought to you by (1) The Allura PMC and (2) The ASF. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Apache Allura from the Incubator
On 17 March 2014 15:17, Cory Johns john...@gmail.com wrote: On Mon, Mar 17, 2014 at 6:58 AM, sebb seb...@gmail.com wrote: On 15 March 2014 01:23, Justin Mclean jus...@classsoftware.com wrote: While it's clear in the text and from the domain that the project is an ASF one, the subtitles Forge software for hosting software projects and Brought to you by: brondsem, masterbunnyfu, rbowen, vansteenburgh and lack of links back to the ASF don't immediately give that impression. That's a good point. The board decided a long time ago that @author tags were deprecated in code; partly because they get out of date, but mainly because the ASF is a community, and code is a co-operative effort. Seems to me the Brought to you sentence has similar problems, and should be removed. Well, I should note that the Brought to you by line is actually automatically generated from the project permissions, so there is little chance of it getting out of date. What about when people move on from Allura and no longer have permissions? That does not necessarily mean that their contribution to the project is no longer important. Even if their code has been entirely replaced by later changes, they still contributed to the software. That said, it will be more useful as we move more of the Allura work (specifically, ticket activity) over from the old SourceForge location to the Apache hosted Allura instance, as is the plan. Same issue; the ASF is about community-developed code, not individual coders. Individuals come and go; the ASF hopeully will outlast us all! Also I think (almost?) all other TLPs include the ASF feather which links back to the main ASF page. I have updated the page at https://forge-allura.apache.org/p/allura/ to include the ASF feather logo which links to http://www.apache.org/foundation/ The ASF feather is normally present in the header, not just the home page. Is it possible to add it there? It also quite hard for someone outside the project to see what is happing on the mailing list due to the large amount at allure ticket emails. Have you consider having a separate issues list? +1 This has been raised before and some things have been done to improve the tracker notifications on the mailing list (combining status change and comment notifications, fixing threading, etc) and it was decided at the time that it was reasonable to continue to include that traffic (with improvements) on the list. However, I believe the possibility of splitting it in the future was left open, should anyone continue to feel it was a problem. Still, this doesn't seem to me like something that should block graduation, as the tracker communications are indeed related to Allura development. Agreed the destination of tracker notifications is not a blocker to graduation. But could perhaps become a blocker to community growth, so needs to be monitored. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Apache Allura from the Incubator
Since we're still piling on, I just went to https://forge-allura.apache.org/p/allura/ and was pretty sure I had been redirected to SourceForge. It look and feel of that page looks like all of the other SourceForge projects like the Open@Adobe sites I have visited. I would think that: 1) Apache wouldn't want to have SourceForge branding on Apache infrastructure 2) SourceForge wouldn't want Apache to have SourceForge branding on Apache infrastructure. Are folks sure this is ok? -Alex On 3/17/14 9:09 AM, sebb seb...@gmail.com wrote: On 17 March 2014 15:17, Cory Johns john...@gmail.com wrote: On Mon, Mar 17, 2014 at 6:58 AM, sebb seb...@gmail.com wrote: On 15 March 2014 01:23, Justin Mclean jus...@classsoftware.com wrote: While it's clear in the text and from the domain that the project is an ASF one, the subtitles Forge software for hosting software projects and Brought to you by: brondsem, masterbunnyfu, rbowen, vansteenburgh and lack of links back to the ASF don't immediately give that impression. That's a good point. The board decided a long time ago that @author tags were deprecated in code; partly because they get out of date, but mainly because the ASF is a community, and code is a co-operative effort. Seems to me the Brought to you sentence has similar problems, and should be removed. Well, I should note that the Brought to you by line is actually automatically generated from the project permissions, so there is little chance of it getting out of date. What about when people move on from Allura and no longer have permissions? That does not necessarily mean that their contribution to the project is no longer important. Even if their code has been entirely replaced by later changes, they still contributed to the software. That said, it will be more useful as we move more of the Allura work (specifically, ticket activity) over from the old SourceForge location to the Apache hosted Allura instance, as is the plan. Same issue; the ASF is about community-developed code, not individual coders. Individuals come and go; the ASF hopeully will outlast us all! Also I think (almost?) all other TLPs include the ASF feather which links back to the main ASF page. I have updated the page at https://forge-allura.apache.org/p/allura/ to include the ASF feather logo which links to http://www.apache.org/foundation/ The ASF feather is normally present in the header, not just the home page. Is it possible to add it there? It also quite hard for someone outside the project to see what is happing on the mailing list due to the large amount at allure ticket emails. Have you consider having a separate issues list? +1 This has been raised before and some things have been done to improve the tracker notifications on the mailing list (combining status change and comment notifications, fixing threading, etc) and it was decided at the time that it was reasonable to continue to include that traffic (with improvements) on the list. However, I believe the possibility of splitting it in the future was left open, should anyone continue to feel it was a problem. Still, this doesn't seem to me like something that should block graduation, as the tracker communications are indeed related to Allura development. Agreed the destination of tracker notifications is not a blocker to graduation. But could perhaps become a blocker to community growth, so needs to be monitored. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Apache Allura from the Incubator
The Brought to you by line has been hidden. On Mon, Mar 17, 2014 at 11:29 AM, Jim Jagielski j...@jagunet.com wrote: On Mar 17, 2014, at 11:17 AM, Cory Johns john...@gmail.com wrote: On Mon, Mar 17, 2014 at 6:58 AM, sebb seb...@gmail.com wrote: On 15 March 2014 01:23, Justin Mclean jus...@classsoftware.com wrote: While it's clear in the text and from the domain that the project is an ASF one, the subtitles Forge software for hosting software projects and Brought to you by: brondsem, masterbunnyfu, rbowen, vansteenburgh and lack of links back to the ASF don't immediately give that impression. That's a good point. The board decided a long time ago that @author tags were deprecated in code; partly because they get out of date, but mainly because the ASF is a community, and code is a co-operative effort. Seems to me the Brought to you sentence has similar problems, and should be removed. Well, I should note that the Brought to you by line is actually automatically generated from the project permissions, so there is little chance of it getting out of date. That said, it will be more useful as we move more of the Allura work (specifically, ticket activity) over from the old SourceForge location to the Apache hosted Allura instance, as is the plan. It should still be removed... It's brought to you by (1) The Allura PMC and (2) The ASF. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Apache Allura from the Incubator
Alex, The project is Allura, which does power the developer tools at SourceForge, and we're using an Allura instance on an Apache VM to self-host the project. Since Allura is a project management platform, in the interests of eating our own dogfood, we obviously want to continue to use Allura to manage the Allura project (and eventually open it up for other Apache projects to use as well). There shouldn't be any SourceForge branding or references on the Apache Allura instance, aside from the overall look and feel of the platform being similar, since it is in fact the same platform (though SourceForge does theme Allura to some degree, for example in the tools menu). On Mon, Mar 17, 2014 at 12:23 PM, Alex Harui aha...@adobe.com wrote: Since we're still piling on, I just went to https://forge-allura.apache.org/p/allura/ and was pretty sure I had been redirected to SourceForge. It look and feel of that page looks like all of the other SourceForge projects like the Open@Adobe sites I have visited. I would think that: 1) Apache wouldn't want to have SourceForge branding on Apache infrastructure 2) SourceForge wouldn't want Apache to have SourceForge branding on Apache infrastructure. Are folks sure this is ok? -Alex On 3/17/14 9:09 AM, sebb seb...@gmail.com wrote: On 17 March 2014 15:17, Cory Johns john...@gmail.com wrote: On Mon, Mar 17, 2014 at 6:58 AM, sebb seb...@gmail.com wrote: On 15 March 2014 01:23, Justin Mclean jus...@classsoftware.com wrote: While it's clear in the text and from the domain that the project is an ASF one, the subtitles Forge software for hosting software projects and Brought to you by: brondsem, masterbunnyfu, rbowen, vansteenburgh and lack of links back to the ASF don't immediately give that impression. That's a good point. The board decided a long time ago that @author tags were deprecated in code; partly because they get out of date, but mainly because the ASF is a community, and code is a co-operative effort. Seems to me the Brought to you sentence has similar problems, and should be removed. Well, I should note that the Brought to you by line is actually automatically generated from the project permissions, so there is little chance of it getting out of date. What about when people move on from Allura and no longer have permissions? That does not necessarily mean that their contribution to the project is no longer important. Even if their code has been entirely replaced by later changes, they still contributed to the software. That said, it will be more useful as we move more of the Allura work (specifically, ticket activity) over from the old SourceForge location to the Apache hosted Allura instance, as is the plan. Same issue; the ASF is about community-developed code, not individual coders. Individuals come and go; the ASF hopeully will outlast us all! Also I think (almost?) all other TLPs include the ASF feather which links back to the main ASF page. I have updated the page at https://forge-allura.apache.org/p/allura/ to include the ASF feather logo which links to http://www.apache.org/foundation/ The ASF feather is normally present in the header, not just the home page. Is it possible to add it there? It also quite hard for someone outside the project to see what is happing on the mailing list due to the large amount at allure ticket emails. Have you consider having a separate issues list? +1 This has been raised before and some things have been done to improve the tracker notifications on the mailing list (combining status change and comment notifications, fixing threading, etc) and it was decided at the time that it was reasonable to continue to include that traffic (with improvements) on the list. However, I believe the possibility of splitting it in the future was left open, should anyone continue to feel it was a problem. Still, this doesn't seem to me like something that should block graduation, as the tracker communications are indeed related to Allura development. Agreed the destination of tracker notifications is not a blocker to graduation. But could perhaps become a blocker to community growth, so needs to be monitored. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Apache Allura from the Incubator
I'm not a branding expert. Has the Apache VP of Branding approved the look? You are correct that the word SourceForge is not on the site, but I thought branding included colors, icons, and layout and the goal is to prevent confusion, and I was definitely confused, but it could just be me. There are several Adobe links that take you to SourceForge so maybe I've experienced that more than others. -Alex On 3/17/14 9:53 AM, Cory Johns john...@gmail.com wrote: Alex, The project is Allura, which does power the developer tools at SourceForge, and we're using an Allura instance on an Apache VM to self-host the project. Since Allura is a project management platform, in the interests of eating our own dogfood, we obviously want to continue to use Allura to manage the Allura project (and eventually open it up for other Apache projects to use as well). There shouldn't be any SourceForge branding or references on the Apache Allura instance, aside from the overall look and feel of the platform being similar, since it is in fact the same platform (though SourceForge does theme Allura to some degree, for example in the tools menu). On Mon, Mar 17, 2014 at 12:23 PM, Alex Harui aha...@adobe.com wrote: Since we're still piling on, I just went to https://forge-allura.apache.org/p/allura/ and was pretty sure I had been redirected to SourceForge. It look and feel of that page looks like all of the other SourceForge projects like the Open@Adobe sites I have visited. I would think that: 1) Apache wouldn't want to have SourceForge branding on Apache infrastructure 2) SourceForge wouldn't want Apache to have SourceForge branding on Apache infrastructure. Are folks sure this is ok? -Alex On 3/17/14 9:09 AM, sebb seb...@gmail.com wrote: On 17 March 2014 15:17, Cory Johns john...@gmail.com wrote: On Mon, Mar 17, 2014 at 6:58 AM, sebb seb...@gmail.com wrote: On 15 March 2014 01:23, Justin Mclean jus...@classsoftware.com wrote: While it's clear in the text and from the domain that the project is an ASF one, the subtitles Forge software for hosting software projects and Brought to you by: brondsem, masterbunnyfu, rbowen, vansteenburgh and lack of links back to the ASF don't immediately give that impression. That's a good point. The board decided a long time ago that @author tags were deprecated in code; partly because they get out of date, but mainly because the ASF is a community, and code is a co-operative effort. Seems to me the Brought to you sentence has similar problems, and should be removed. Well, I should note that the Brought to you by line is actually automatically generated from the project permissions, so there is little chance of it getting out of date. What about when people move on from Allura and no longer have permissions? That does not necessarily mean that their contribution to the project is no longer important. Even if their code has been entirely replaced by later changes, they still contributed to the software. That said, it will be more useful as we move more of the Allura work (specifically, ticket activity) over from the old SourceForge location to the Apache hosted Allura instance, as is the plan. Same issue; the ASF is about community-developed code, not individual coders. Individuals come and go; the ASF hopeully will outlast us all! Also I think (almost?) all other TLPs include the ASF feather which links back to the main ASF page. I have updated the page at https://forge-allura.apache.org/p/allura/ to include the ASF feather logo which links to http://www.apache.org/foundation/ The ASF feather is normally present in the header, not just the home page. Is it possible to add it there? It also quite hard for someone outside the project to see what is happing on the mailing list due to the large amount at allure ticket emails. Have you consider having a separate issues list? +1 This has been raised before and some things have been done to improve the tracker notifications on the mailing list (combining status change and comment notifications, fixing threading, etc) and it was decided at the time that it was reasonable to continue to include that traffic (with improvements) on the list. However, I believe the possibility of splitting it in the future was left open, should anyone continue to feel it was a problem. Still, this doesn't seem to me like something that should block graduation, as the tracker communications are indeed related to Allura development. Agreed the destination of tracker notifications is not a blocker to graduation. But could perhaps become a blocker to community growth, so needs to be monitored. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Apache Allura from the Incubator
On 17 March 2014 16:53, Cory Johns john...@gmail.com wrote: Alex, The project is Allura, which does power the developer tools at SourceForge, and we're using an Allura instance on an Apache VM to self-host the project. Since Allura is a project management platform, in the interests of eating our own dogfood, we obviously want to continue to use Allura to manage the Allura project (and eventually open it up for other Apache projects to use as well). There shouldn't be any SourceForge branding or references on the Apache Allura instance, aside from the overall look and feel of the platform being similar, since it is in fact the same platform (though SourceForge does theme Allura to some degree, for example in the tools menu). Sourceforge pages are all clearly part of Sourceforge, as they all have the sourceforge banner across the top. The sourceforge branding is present on all SF projects. Can this be done for the Allura pages (except of course using an ASF banner) ? Probably it could be done for the entire instance, as presumably any sub-projects in it would have to be ASF projects or at least ASF content. On Mon, Mar 17, 2014 at 12:23 PM, Alex Harui aha...@adobe.com wrote: Since we're still piling on, I just went to https://forge-allura.apache.org/p/allura/ and was pretty sure I had been redirected to SourceForge. It look and feel of that page looks like all of the other SourceForge projects like the Open@Adobe sites I have visited. I would think that: 1) Apache wouldn't want to have SourceForge branding on Apache infrastructure 2) SourceForge wouldn't want Apache to have SourceForge branding on Apache infrastructure. Are folks sure this is ok? -Alex On 3/17/14 9:09 AM, sebb seb...@gmail.com wrote: On 17 March 2014 15:17, Cory Johns john...@gmail.com wrote: On Mon, Mar 17, 2014 at 6:58 AM, sebb seb...@gmail.com wrote: On 15 March 2014 01:23, Justin Mclean jus...@classsoftware.com wrote: While it's clear in the text and from the domain that the project is an ASF one, the subtitles Forge software for hosting software projects and Brought to you by: brondsem, masterbunnyfu, rbowen, vansteenburgh and lack of links back to the ASF don't immediately give that impression. That's a good point. The board decided a long time ago that @author tags were deprecated in code; partly because they get out of date, but mainly because the ASF is a community, and code is a co-operative effort. Seems to me the Brought to you sentence has similar problems, and should be removed. Well, I should note that the Brought to you by line is actually automatically generated from the project permissions, so there is little chance of it getting out of date. What about when people move on from Allura and no longer have permissions? That does not necessarily mean that their contribution to the project is no longer important. Even if their code has been entirely replaced by later changes, they still contributed to the software. That said, it will be more useful as we move more of the Allura work (specifically, ticket activity) over from the old SourceForge location to the Apache hosted Allura instance, as is the plan. Same issue; the ASF is about community-developed code, not individual coders. Individuals come and go; the ASF hopeully will outlast us all! Also I think (almost?) all other TLPs include the ASF feather which links back to the main ASF page. I have updated the page at https://forge-allura.apache.org/p/allura/ to include the ASF feather logo which links to http://www.apache.org/foundation/ The ASF feather is normally present in the header, not just the home page. Is it possible to add it there? It also quite hard for someone outside the project to see what is happing on the mailing list due to the large amount at allure ticket emails. Have you consider having a separate issues list? +1 This has been raised before and some things have been done to improve the tracker notifications on the mailing list (combining status change and comment notifications, fixing threading, etc) and it was decided at the time that it was reasonable to continue to include that traffic (with improvements) on the list. However, I believe the possibility of splitting it in the future was left open, should anyone continue to feel it was a problem. Still, this doesn't seem to me like something that should block graduation, as the tracker communications are indeed related to Allura development. Agreed the destination of tracker notifications is not a blocker to graduation. But could perhaps become a blocker to community growth, so needs to be monitored. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Apache Allura from the Incubator
The ASF banner has been moved to the top right header, and will apply to all pages in the Project neighborhood. (Currently that should cover everything except user pages, but this is a temporary work-around until we can get a proper ASF theme started.) On Mon, Mar 17, 2014 at 1:06 PM, sebb seb...@gmail.com wrote: On 17 March 2014 16:53, Cory Johns john...@gmail.com wrote: Alex, The project is Allura, which does power the developer tools at SourceForge, and we're using an Allura instance on an Apache VM to self-host the project. Since Allura is a project management platform, in the interests of eating our own dogfood, we obviously want to continue to use Allura to manage the Allura project (and eventually open it up for other Apache projects to use as well). There shouldn't be any SourceForge branding or references on the Apache Allura instance, aside from the overall look and feel of the platform being similar, since it is in fact the same platform (though SourceForge does theme Allura to some degree, for example in the tools menu). Sourceforge pages are all clearly part of Sourceforge, as they all have the sourceforge banner across the top. The sourceforge branding is present on all SF projects. Can this be done for the Allura pages (except of course using an ASF banner) ? Probably it could be done for the entire instance, as presumably any sub-projects in it would have to be ASF projects or at least ASF content. On Mon, Mar 17, 2014 at 12:23 PM, Alex Harui aha...@adobe.com wrote: Since we're still piling on, I just went to https://forge-allura.apache.org/p/allura/ and was pretty sure I had been redirected to SourceForge. It look and feel of that page looks like all of the other SourceForge projects like the Open@Adobe sites I have visited. I would think that: 1) Apache wouldn't want to have SourceForge branding on Apache infrastructure 2) SourceForge wouldn't want Apache to have SourceForge branding on Apache infrastructure. Are folks sure this is ok? -Alex On 3/17/14 9:09 AM, sebb seb...@gmail.com wrote: On 17 March 2014 15:17, Cory Johns john...@gmail.com wrote: On Mon, Mar 17, 2014 at 6:58 AM, sebb seb...@gmail.com wrote: On 15 March 2014 01:23, Justin Mclean jus...@classsoftware.com wrote: While it's clear in the text and from the domain that the project is an ASF one, the subtitles Forge software for hosting software projects and Brought to you by: brondsem, masterbunnyfu, rbowen, vansteenburgh and lack of links back to the ASF don't immediately give that impression. That's a good point. The board decided a long time ago that @author tags were deprecated in code; partly because they get out of date, but mainly because the ASF is a community, and code is a co-operative effort. Seems to me the Brought to you sentence has similar problems, and should be removed. Well, I should note that the Brought to you by line is actually automatically generated from the project permissions, so there is little chance of it getting out of date. What about when people move on from Allura and no longer have permissions? That does not necessarily mean that their contribution to the project is no longer important. Even if their code has been entirely replaced by later changes, they still contributed to the software. That said, it will be more useful as we move more of the Allura work (specifically, ticket activity) over from the old SourceForge location to the Apache hosted Allura instance, as is the plan. Same issue; the ASF is about community-developed code, not individual coders. Individuals come and go; the ASF hopeully will outlast us all! Also I think (almost?) all other TLPs include the ASF feather which links back to the main ASF page. I have updated the page at https://forge-allura.apache.org/p/allura/to include the ASF feather logo which links to http://www.apache.org/foundation/ The ASF feather is normally present in the header, not just the home page. Is it possible to add it there? It also quite hard for someone outside the project to see what is happing on the mailing list due to the large amount at allure ticket emails. Have you consider having a separate issues list? +1 This has been raised before and some things have been done to improve the tracker notifications on the mailing list (combining status change and comment notifications, fixing threading, etc) and it was decided at the time that it was reasonable to continue to include that traffic (with improvements) on the list. However, I believe the possibility of splitting it in the future was left open, should anyone continue to feel it was a problem. Still, this doesn't seem to me like something that should block graduation, as
Re: [VOTE] Graduation of Apache Allura from the Incubator
On 17 March 2014 18:23, Cory Johns john...@gmail.com wrote: The ASF banner has been moved to the top right header, and will apply to all pages in the Project neighborhood. (Currently that should cover everything except user pages, but this is a temporary work-around until we can get a proper ASF theme started.) That looks much better, thanks. On Mon, Mar 17, 2014 at 1:06 PM, sebb seb...@gmail.com wrote: On 17 March 2014 16:53, Cory Johns john...@gmail.com wrote: Alex, The project is Allura, which does power the developer tools at SourceForge, and we're using an Allura instance on an Apache VM to self-host the project. Since Allura is a project management platform, in the interests of eating our own dogfood, we obviously want to continue to use Allura to manage the Allura project (and eventually open it up for other Apache projects to use as well). There shouldn't be any SourceForge branding or references on the Apache Allura instance, aside from the overall look and feel of the platform being similar, since it is in fact the same platform (though SourceForge does theme Allura to some degree, for example in the tools menu). Sourceforge pages are all clearly part of Sourceforge, as they all have the sourceforge banner across the top. The sourceforge branding is present on all SF projects. Can this be done for the Allura pages (except of course using an ASF banner) ? Probably it could be done for the entire instance, as presumably any sub-projects in it would have to be ASF projects or at least ASF content. On Mon, Mar 17, 2014 at 12:23 PM, Alex Harui aha...@adobe.com wrote: Since we're still piling on, I just went to https://forge-allura.apache.org/p/allura/ and was pretty sure I had been redirected to SourceForge. It look and feel of that page looks like all of the other SourceForge projects like the Open@Adobe sites I have visited. I would think that: 1) Apache wouldn't want to have SourceForge branding on Apache infrastructure 2) SourceForge wouldn't want Apache to have SourceForge branding on Apache infrastructure. Are folks sure this is ok? -Alex On 3/17/14 9:09 AM, sebb seb...@gmail.com wrote: On 17 March 2014 15:17, Cory Johns john...@gmail.com wrote: On Mon, Mar 17, 2014 at 6:58 AM, sebb seb...@gmail.com wrote: On 15 March 2014 01:23, Justin Mclean jus...@classsoftware.com wrote: While it's clear in the text and from the domain that the project is an ASF one, the subtitles Forge software for hosting software projects and Brought to you by: brondsem, masterbunnyfu, rbowen, vansteenburgh and lack of links back to the ASF don't immediately give that impression. That's a good point. The board decided a long time ago that @author tags were deprecated in code; partly because they get out of date, but mainly because the ASF is a community, and code is a co-operative effort. Seems to me the Brought to you sentence has similar problems, and should be removed. Well, I should note that the Brought to you by line is actually automatically generated from the project permissions, so there is little chance of it getting out of date. What about when people move on from Allura and no longer have permissions? That does not necessarily mean that their contribution to the project is no longer important. Even if their code has been entirely replaced by later changes, they still contributed to the software. That said, it will be more useful as we move more of the Allura work (specifically, ticket activity) over from the old SourceForge location to the Apache hosted Allura instance, as is the plan. Same issue; the ASF is about community-developed code, not individual coders. Individuals come and go; the ASF hopeully will outlast us all! Also I think (almost?) all other TLPs include the ASF feather which links back to the main ASF page. I have updated the page at https://forge-allura.apache.org/p/allura/to include the ASF feather logo which links to http://www.apache.org/foundation/ The ASF feather is normally present in the header, not just the home page. Is it possible to add it there? It also quite hard for someone outside the project to see what is happing on the mailing list due to the large amount at allure ticket emails. Have you consider having a separate issues list? +1 This has been raised before and some things have been done to improve the tracker notifications on the mailing list (combining status change and comment notifications, fixing threading, etc) and it was decided at the time that it was reasonable to continue to include that traffic (with improvements) on the list. However, I believe the possibility of splitting it in the future was left open, should anyone continue to feel it was a
Re: [VOTE] Graduation of Apache Allura from the Incubator
On 03/17/2014 01:05 PM, Alex Harui wrote: I'm not a branding expert. Has the Apache VP of Branding approved the look? You are correct that the word SourceForge is not on the site, but I thought branding included colors, icons, and layout and the goal is to prevent confusion, and I was definitely confused, but it could just be me. There are several Adobe links that take you to SourceForge so maybe I've experienced that more than others. -Alex Sourceforge is the largest and most visible user of Apache Allura (incubating). It's not the Allura looks like SourceForge. It's that SourceForge looks like Allura. --Rich -- Rich Bowen - rbo...@rcbowen.com - @rbowen http://apachecon.com/ - @apachecon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Apache Allura from the Incubator
On 3/17/14 1:30 PM, Rich Bowen rbo...@rcbowen.com wrote: On 03/17/2014 01:05 PM, Alex Harui wrote: I'm not a branding expert. Has the Apache VP of Branding approved the look? You are correct that the word SourceForge is not on the site, but I thought branding included colors, icons, and layout and the goal is to prevent confusion, and I was definitely confused, but it could just be me. There are several Adobe links that take you to SourceForge so maybe I've experienced that more than others. -Alex Sourceforge is the largest and most visible user of Apache Allura (incubating). It's not the Allura looks like SourceForge. It's that SourceForge looks like Allura. If our VP of Branding is ok with it, I can't argue. But for me, the first impression I get is that Apache is hosting this project at SourceForge. Yes, the word SourceForge doesn't actually exist on that page, but the colors and layout are as significant to me as the colors and layout of any major department store. This may be because most of my visits to SourceForge are for Adobe projects now hosted on SourceForge like this one: https://sourceforge.net/adobe/flexsdk/wiki/About/ -Alex - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Apache Allura from the Incubator
On 16 March 2014 03:43, Dave Brondsema d...@brondsema.net wrote: On 3/14/14 8:19 PM, sebb wrote: On 14 March 2014 20:16, Cory Johns john...@gmail.com wrote: Ok, I think we've addressed all of the issues. Namely: * The status page (http://incubator.staging.apache.org/projects/allura.html) has been updated, and now the correct canonical project web page (namely https://forge-allura.apache.org/p/allura/), as well as having an improved project description, links to the docs, and updated news items * The aforementioned docs are now hosted at https://forge-allura.apache.org/docs/ (which is also linked to from the main project page at https://forge-allura.apache.org/p/allura/) * The footer on https://forge-allura.apache.org/p/allura/ has been fixed with the correct trademark and copyright information and links * All Apache Allura (incubating) references have been corrected on http://incubator.staging.apache.org/projects/allura.html, https://forge-allura.apache.org/p/allura/, and https://sourceforge.net/projects/allura/ Additionally, the unused page at http://incubator.apache.org/allura/ has been updated to automatically redirect to the main project page at https://forge-allura.apache.org/p/allura/, and its associated (unused) download page has been updated with a link to the releases repository, so that they are useful for people who may have bookmarked them previously, even though they are no longer linked to from anywhere. This should cover all of the concerns that have been raised thus far, save for the location of the issue tracker which, as previously mentioned, is a difficult undertaking that will be addressed in the future (and the status page indicates this). Well, there is still the issue of the download page. There does not seem to be any way to find it from the new site. There's a download button in the middle of the page. Not sure how I missed that before - I was expecting to find a top-level link. However there needs to be a link to the KEYS file [1] otherwise users cannot easily use the signature. BTW, Allura 1.0.1 should now be removed from the dist area - only the latest supported release(s) should remain on the main mirrors. [1] http://www.apache.org/dist/incubator/allura/KEYS Also there are some branding requirements that are missing from the site. See http://www.apache.org/foundation/marks/pmcs.html In particular http://www.apache.org/foundation/marks/pmcs.html#navigation I've added these links to our main navigation page. I've also added the (tm) as required. Thanks for your feedback on all this. Is there anything else we're missing for graduation? Looks a lot better now, thanks! With these changes, we are hopeful that we can proceed with and pass the graduation vote. On Fri, Mar 14, 2014 at 8:18 AM, sebb seb...@gmail.com wrote: If the home page really is [1] http://forge-allura.apache.org/p/allura then why does the status page [2] http://incubator.apache.org/projects/allura.html point to [3] http://incubator.apache.org/allura/ ? The host [1] is described on the status page [2] as being the Wiki, which is normally separate from the project page. There seems to be very little on [3] that is not on [1] so it could probably be dropped. However the Wiki [1] does not have the correct footer, it only says: This project is powered by Allura. That should be Apache Allura. And the pages also need the standard trademark attributions. The site [3] does have the following: Copyright (c) 2011 The Apache Software Foundation, Licensed under the Apache License, Version 2.0. Apache and the Apache feather logo are trademarks of The Apache Software Foundation. However that fails to mention Apache Allura and Allura as being trademarks of the ASF. On 14 March 2014 04:32, Dave Brondsema d...@brondsema.net wrote: On 03/13/2014 10:00 PM, David Nalley wrote: On Thu, Mar 13, 2014 at 9:54 PM, David Nalley da...@gnsa.us wrote: On Thu, Mar 13, 2014 at 1:29 PM, Roman Shaposhnik r...@apache.org wrote: After looking at it for some time, my optimistic outlook on the project would be +0 vote at best. On the plus side, the community seems to be really active and reasonably diverse. But if feels, like ASF has not yet become a true home for the project. Here's what I'm talking about: as a casual bystander who was trying to view Allura as an ASF project -- I had difficult time. First of all, I couldn't even get to the releases easily enough: https://incubator.apache.org/allura/downloads.html When I managed to get there the first thing that the README instructed me to do is to go to https://forge-allura.apache.org/ What is that? How does it relate to the project? In fact, from the dev list it feels like there may be yet another canonical place for the Allura -- over at sourceforge: http://mail-archives.apache.org/mod_mbox/incubator-allura-dev/201402.mbox/%3C52F80CA5.8060209%40brondsema.net%3E I am
Re: [VOTE] Graduation of Apache Allura from the Incubator
On 3/16/14 3:46 AM, sebb wrote: On 16 March 2014 03:43, Dave Brondsema d...@brondsema.net wrote: On 3/14/14 8:19 PM, sebb wrote: On 14 March 2014 20:16, Cory Johns john...@gmail.com wrote: Ok, I think we've addressed all of the issues. Namely: * The status page (http://incubator.staging.apache.org/projects/allura.html) has been updated, and now the correct canonical project web page (namely https://forge-allura.apache.org/p/allura/), as well as having an improved project description, links to the docs, and updated news items * The aforementioned docs are now hosted at https://forge-allura.apache.org/docs/ (which is also linked to from the main project page at https://forge-allura.apache.org/p/allura/) * The footer on https://forge-allura.apache.org/p/allura/ has been fixed with the correct trademark and copyright information and links * All Apache Allura (incubating) references have been corrected on http://incubator.staging.apache.org/projects/allura.html, https://forge-allura.apache.org/p/allura/, and https://sourceforge.net/projects/allura/ Additionally, the unused page at http://incubator.apache.org/allura/ has been updated to automatically redirect to the main project page at https://forge-allura.apache.org/p/allura/, and its associated (unused) download page has been updated with a link to the releases repository, so that they are useful for people who may have bookmarked them previously, even though they are no longer linked to from anywhere. This should cover all of the concerns that have been raised thus far, save for the location of the issue tracker which, as previously mentioned, is a difficult undertaking that will be addressed in the future (and the status page indicates this). Well, there is still the issue of the download page. There does not seem to be any way to find it from the new site. There's a download button in the middle of the page. Not sure how I missed that before - I was expecting to find a top-level link. However there needs to be a link to the KEYS file [1] otherwise users cannot easily use the signature. Added a link alongside the 'sig' link, under the download button. BTW, Allura 1.0.1 should now be removed from the dist area - only the latest supported release(s) should remain on the main mirrors. Fixed. Doc reference for anyone interested: http://www.apache.org/dev/release.html#when-to-archive [1] http://www.apache.org/dist/incubator/allura/KEYS Also there are some branding requirements that are missing from the site. See http://www.apache.org/foundation/marks/pmcs.html In particular http://www.apache.org/foundation/marks/pmcs.html#navigation I've added these links to our main navigation page. I've also added the (tm) as required. Thanks for your feedback on all this. Is there anything else we're missing for graduation? Looks a lot better now, thanks! If Sebb, Roman or David Nalley would like to voting on this release in light of the recent improvements to Allura branding and web presence, that would be much appreciated. I think I will tally the results soon (tomorrow perhaps). -- Dave Brondsema : d...@brondsema.net http://www.brondsema.net : personal http://www.splike.com : programming - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Apache Allura from the Incubator
On 3/14/14 8:19 PM, sebb wrote: On 14 March 2014 20:16, Cory Johns john...@gmail.com wrote: Ok, I think we've addressed all of the issues. Namely: * The status page (http://incubator.staging.apache.org/projects/allura.html) has been updated, and now the correct canonical project web page (namely https://forge-allura.apache.org/p/allura/), as well as having an improved project description, links to the docs, and updated news items * The aforementioned docs are now hosted at https://forge-allura.apache.org/docs/ (which is also linked to from the main project page at https://forge-allura.apache.org/p/allura/) * The footer on https://forge-allura.apache.org/p/allura/ has been fixed with the correct trademark and copyright information and links * All Apache Allura (incubating) references have been corrected on http://incubator.staging.apache.org/projects/allura.html, https://forge-allura.apache.org/p/allura/, and https://sourceforge.net/projects/allura/ Additionally, the unused page at http://incubator.apache.org/allura/ has been updated to automatically redirect to the main project page at https://forge-allura.apache.org/p/allura/, and its associated (unused) download page has been updated with a link to the releases repository, so that they are useful for people who may have bookmarked them previously, even though they are no longer linked to from anywhere. This should cover all of the concerns that have been raised thus far, save for the location of the issue tracker which, as previously mentioned, is a difficult undertaking that will be addressed in the future (and the status page indicates this). Well, there is still the issue of the download page. There does not seem to be any way to find it from the new site. There's a download button in the middle of the page. Also there are some branding requirements that are missing from the site. See http://www.apache.org/foundation/marks/pmcs.html In particular http://www.apache.org/foundation/marks/pmcs.html#navigation I've added these links to our main navigation page. I've also added the ™ as required. Thanks for your feedback on all this. Is there anything else we're missing for graduation? With these changes, we are hopeful that we can proceed with and pass the graduation vote. On Fri, Mar 14, 2014 at 8:18 AM, sebb seb...@gmail.com wrote: If the home page really is [1] http://forge-allura.apache.org/p/allura then why does the status page [2] http://incubator.apache.org/projects/allura.html point to [3] http://incubator.apache.org/allura/ ? The host [1] is described on the status page [2] as being the Wiki, which is normally separate from the project page. There seems to be very little on [3] that is not on [1] so it could probably be dropped. However the Wiki [1] does not have the correct footer, it only says: This project is powered by Allura. That should be Apache Allura. And the pages also need the standard trademark attributions. The site [3] does have the following: Copyright © 2011 The Apache Software Foundation, Licensed under the Apache License, Version 2.0. Apache and the Apache feather logo are trademarks of The Apache Software Foundation. However that fails to mention Apache Allura and Allura as being trademarks of the ASF. On 14 March 2014 04:32, Dave Brondsema d...@brondsema.net wrote: On 03/13/2014 10:00 PM, David Nalley wrote: On Thu, Mar 13, 2014 at 9:54 PM, David Nalley da...@gnsa.us wrote: On Thu, Mar 13, 2014 at 1:29 PM, Roman Shaposhnik r...@apache.org wrote: After looking at it for some time, my optimistic outlook on the project would be +0 vote at best. On the plus side, the community seems to be really active and reasonably diverse. But if feels, like ASF has not yet become a true home for the project. Here's what I'm talking about: as a casual bystander who was trying to view Allura as an ASF project -- I had difficult time. First of all, I couldn't even get to the releases easily enough: https://incubator.apache.org/allura/downloads.html When I managed to get there the first thing that the README instructed me to do is to go to https://forge-allura.apache.org/ What is that? How does it relate to the project? In fact, from the dev list it feels like there may be yet another canonical place for the Allura -- over at sourceforge: http://mail-archives.apache.org/mod_mbox/incubator-allura-dev/201402.mbox/%3C52F80CA5.8060209%40brondsema.net%3E I am not quite sure if penalizing the project with a failed graduation vote is the right thing to do, but the state of the outwards facing project assets doesn't inspire a feel of a strong ASF community in me Just my 2c worth of feedback. The projects bug tracker also seems to be at sourceforge.net, which means you need a sf.net account to participate in the project. Based on a quick perusal most of the dev@ traffic seems to be bug tracker - which means most of this
Re: [VOTE] Graduation of Apache Allura from the Incubator
If the home page really is [1] http://forge-allura.apache.org/p/allura then why does the status page [2] http://incubator.apache.org/projects/allura.html point to [3] http://incubator.apache.org/allura/ ? The host [1] is described on the status page [2] as being the Wiki, which is normally separate from the project page. There seems to be very little on [3] that is not on [1] so it could probably be dropped. However the Wiki [1] does not have the correct footer, it only says: This project is powered by Allura. That should be Apache Allura. And the pages also need the standard trademark attributions. The site [3] does have the following: Copyright © 2011 The Apache Software Foundation, Licensed under the Apache License, Version 2.0. Apache and the Apache feather logo are trademarks of The Apache Software Foundation. However that fails to mention Apache Allura and Allura as being trademarks of the ASF. On 14 March 2014 04:32, Dave Brondsema d...@brondsema.net wrote: On 03/13/2014 10:00 PM, David Nalley wrote: On Thu, Mar 13, 2014 at 9:54 PM, David Nalley da...@gnsa.us wrote: On Thu, Mar 13, 2014 at 1:29 PM, Roman Shaposhnik r...@apache.org wrote: After looking at it for some time, my optimistic outlook on the project would be +0 vote at best. On the plus side, the community seems to be really active and reasonably diverse. But if feels, like ASF has not yet become a true home for the project. Here's what I'm talking about: as a casual bystander who was trying to view Allura as an ASF project -- I had difficult time. First of all, I couldn't even get to the releases easily enough: https://incubator.apache.org/allura/downloads.html When I managed to get there the first thing that the README instructed me to do is to go to https://forge-allura.apache.org/ What is that? How does it relate to the project? In fact, from the dev list it feels like there may be yet another canonical place for the Allura -- over at sourceforge: http://mail-archives.apache.org/mod_mbox/incubator-allura-dev/201402.mbox/%3C52F80CA5.8060209%40brondsema.net%3E I am not quite sure if penalizing the project with a failed graduation vote is the right thing to do, but the state of the outwards facing project assets doesn't inspire a feel of a strong ASF community in me Just my 2c worth of feedback. The projects bug tracker also seems to be at sourceforge.net, which means you need a sf.net account to participate in the project. Based on a quick perusal most of the dev@ traffic seems to be bug tracker - which means most of this is happening at SourceForge. I don't know that this is really problematic - we do have projects using github as the main portion of the contribution workflow, but it does give me pause. I also see http://sf.net/p/allura - which bears a SF logo, and which doesn't note the fact that the project is at the incubator until 1/2 down the page. And nowhere on the page is it referred to as Apache Allura. From a standpoint of the project which is supposed to be policing its brand, this leaves me a bit worried - this page shows an update to that page recently; and appears at least to the outside world to be the nexus for the project and maintained by members of the PPMC. (first return on Google is the sourceforge link.) To be clear other projects have listings at Sourceforge, so aside from the brand and trademark policing that needs to happen, I am not sure the existence of the page is much to be concerned about. There's a notice on the page that reads: Some project information is still at SourceForge during this transition period. and indeed, there's http://allura.sourceforge.net/docs/ which looks surprisingly good when compared with http://incubator.apache.org/allura which doesn't have a working bug tracker link, and steps listed for building Allura consists of 'TODO'. All of the content from the allure source forge site appears to be in the Apache Allura git repo, so I am curious why it isn't published at the ASF. And again, we have projects who host documentation at ReadTheDocs, so I am not sure that documentation living elsewhere is an inherent problem, but it gives me pause. Individually I don't know that any of these are problematic; but I am curious what the mentors take on it is. --David And it's just dawned on me what's happening. The project is using http://forge-allura.apache.org/p/allura as it's home page instead of http://incubator.apache.org/allura which appears to have all of the appropriate content (according to a google cache) but is down right now. It's making more sense; is the intention to make that the project home page? (e.g. allura.apache.org) You got it! (And bad timing that it was down for several hours today - its back up now). Roman and sebb had similar comments to yours, so I'll respond in a single email. We are self-hosting at http://forge-allura.apache.org/p/allura so that is really our home
Re: [VOTE] Graduation of Apache Allura from the Incubator
Ok, I think we've addressed all of the issues. Namely: * The status page (http://incubator.staging.apache.org/projects/allura.html) has been updated, and now the correct canonical project web page (namely https://forge-allura.apache.org/p/allura/), as well as having an improved project description, links to the docs, and updated news items * The aforementioned docs are now hosted at https://forge-allura.apache.org/docs/ (which is also linked to from the main project page at https://forge-allura.apache.org/p/allura/) * The footer on https://forge-allura.apache.org/p/allura/ has been fixed with the correct trademark and copyright information and links * All Apache Allura (incubating) references have been corrected on http://incubator.staging.apache.org/projects/allura.html, https://forge-allura.apache.org/p/allura/, and https://sourceforge.net/projects/allura/ Additionally, the unused page at http://incubator.apache.org/allura/ has been updated to automatically redirect to the main project page at https://forge-allura.apache.org/p/allura/, and its associated (unused) download page has been updated with a link to the releases repository, so that they are useful for people who may have bookmarked them previously, even though they are no longer linked to from anywhere. This should cover all of the concerns that have been raised thus far, save for the location of the issue tracker which, as previously mentioned, is a difficult undertaking that will be addressed in the future (and the status page indicates this). With these changes, we are hopeful that we can proceed with and pass the graduation vote. On Fri, Mar 14, 2014 at 8:18 AM, sebb seb...@gmail.com wrote: If the home page really is [1] http://forge-allura.apache.org/p/allura then why does the status page [2] http://incubator.apache.org/projects/allura.html point to [3] http://incubator.apache.org/allura/ ? The host [1] is described on the status page [2] as being the Wiki, which is normally separate from the project page. There seems to be very little on [3] that is not on [1] so it could probably be dropped. However the Wiki [1] does not have the correct footer, it only says: This project is powered by Allura. That should be Apache Allura. And the pages also need the standard trademark attributions. The site [3] does have the following: Copyright © 2011 The Apache Software Foundation, Licensed under the Apache License, Version 2.0. Apache and the Apache feather logo are trademarks of The Apache Software Foundation. However that fails to mention Apache Allura and Allura as being trademarks of the ASF. On 14 March 2014 04:32, Dave Brondsema d...@brondsema.net wrote: On 03/13/2014 10:00 PM, David Nalley wrote: On Thu, Mar 13, 2014 at 9:54 PM, David Nalley da...@gnsa.us wrote: On Thu, Mar 13, 2014 at 1:29 PM, Roman Shaposhnik r...@apache.org wrote: After looking at it for some time, my optimistic outlook on the project would be +0 vote at best. On the plus side, the community seems to be really active and reasonably diverse. But if feels, like ASF has not yet become a true home for the project. Here's what I'm talking about: as a casual bystander who was trying to view Allura as an ASF project -- I had difficult time. First of all, I couldn't even get to the releases easily enough: https://incubator.apache.org/allura/downloads.html When I managed to get there the first thing that the README instructed me to do is to go to https://forge-allura.apache.org/ What is that? How does it relate to the project? In fact, from the dev list it feels like there may be yet another canonical place for the Allura -- over at sourceforge: http://mail-archives.apache.org/mod_mbox/incubator-allura-dev/201402.mbox/%3C52F80CA5.8060209%40brondsema.net%3E I am not quite sure if penalizing the project with a failed graduation vote is the right thing to do, but the state of the outwards facing project assets doesn't inspire a feel of a strong ASF community in me Just my 2c worth of feedback. The projects bug tracker also seems to be at sourceforge.net, which means you need a sf.net account to participate in the project. Based on a quick perusal most of the dev@ traffic seems to be bug tracker - which means most of this is happening at SourceForge. I don't know that this is really problematic - we do have projects using github as the main portion of the contribution workflow, but it does give me pause. I also see http://sf.net/p/allura - which bears a SF logo, and which doesn't note the fact that the project is at the incubator until 1/2 down the page. And nowhere on the page is it referred to as Apache Allura. From a standpoint of the project which is supposed to be policing its brand, this leaves me a bit worried - this page shows an update to that page recently; and appears at least to the outside world to be the nexus for the project and
Re: [VOTE] Graduation of Apache Allura from the Incubator
On 14 March 2014 20:16, Cory Johns john...@gmail.com wrote: Ok, I think we've addressed all of the issues. Namely: * The status page (http://incubator.staging.apache.org/projects/allura.html) has been updated, and now the correct canonical project web page (namely https://forge-allura.apache.org/p/allura/), as well as having an improved project description, links to the docs, and updated news items * The aforementioned docs are now hosted at https://forge-allura.apache.org/docs/ (which is also linked to from the main project page at https://forge-allura.apache.org/p/allura/) * The footer on https://forge-allura.apache.org/p/allura/ has been fixed with the correct trademark and copyright information and links * All Apache Allura (incubating) references have been corrected on http://incubator.staging.apache.org/projects/allura.html, https://forge-allura.apache.org/p/allura/, and https://sourceforge.net/projects/allura/ Additionally, the unused page at http://incubator.apache.org/allura/ has been updated to automatically redirect to the main project page at https://forge-allura.apache.org/p/allura/, and its associated (unused) download page has been updated with a link to the releases repository, so that they are useful for people who may have bookmarked them previously, even though they are no longer linked to from anywhere. This should cover all of the concerns that have been raised thus far, save for the location of the issue tracker which, as previously mentioned, is a difficult undertaking that will be addressed in the future (and the status page indicates this). Well, there is still the issue of the download page. There does not seem to be any way to find it from the new site. Also there are some branding requirements that are missing from the site. See http://www.apache.org/foundation/marks/pmcs.html In particular http://www.apache.org/foundation/marks/pmcs.html#navigation With these changes, we are hopeful that we can proceed with and pass the graduation vote. On Fri, Mar 14, 2014 at 8:18 AM, sebb seb...@gmail.com wrote: If the home page really is [1] http://forge-allura.apache.org/p/allura then why does the status page [2] http://incubator.apache.org/projects/allura.html point to [3] http://incubator.apache.org/allura/ ? The host [1] is described on the status page [2] as being the Wiki, which is normally separate from the project page. There seems to be very little on [3] that is not on [1] so it could probably be dropped. However the Wiki [1] does not have the correct footer, it only says: This project is powered by Allura. That should be Apache Allura. And the pages also need the standard trademark attributions. The site [3] does have the following: Copyright © 2011 The Apache Software Foundation, Licensed under the Apache License, Version 2.0. Apache and the Apache feather logo are trademarks of The Apache Software Foundation. However that fails to mention Apache Allura and Allura as being trademarks of the ASF. On 14 March 2014 04:32, Dave Brondsema d...@brondsema.net wrote: On 03/13/2014 10:00 PM, David Nalley wrote: On Thu, Mar 13, 2014 at 9:54 PM, David Nalley da...@gnsa.us wrote: On Thu, Mar 13, 2014 at 1:29 PM, Roman Shaposhnik r...@apache.org wrote: After looking at it for some time, my optimistic outlook on the project would be +0 vote at best. On the plus side, the community seems to be really active and reasonably diverse. But if feels, like ASF has not yet become a true home for the project. Here's what I'm talking about: as a casual bystander who was trying to view Allura as an ASF project -- I had difficult time. First of all, I couldn't even get to the releases easily enough: https://incubator.apache.org/allura/downloads.html When I managed to get there the first thing that the README instructed me to do is to go to https://forge-allura.apache.org/ What is that? How does it relate to the project? In fact, from the dev list it feels like there may be yet another canonical place for the Allura -- over at sourceforge: http://mail-archives.apache.org/mod_mbox/incubator-allura-dev/201402.mbox/%3C52F80CA5.8060209%40brondsema.net%3E I am not quite sure if penalizing the project with a failed graduation vote is the right thing to do, but the state of the outwards facing project assets doesn't inspire a feel of a strong ASF community in me Just my 2c worth of feedback. The projects bug tracker also seems to be at sourceforge.net, which means you need a sf.net account to participate in the project. Based on a quick perusal most of the dev@ traffic seems to be bug tracker - which means most of this is happening at SourceForge. I don't know that this is really problematic - we do have projects using github as the main portion of the contribution workflow, but it does give me pause. I also see http://sf.net/p/allura - which bears a SF
Re: [VOTE] Graduation of Apache Allura from the Incubator
On Mar 7, 2014, at 3:16 PM, Dave Brondsema d...@brondsema.net wrote: Please VOTE below on the graduation of Apache Allura from the Incubator. The graduation resolution is pasted below. The VOTE will be open for at least 72 hours: [X] +1 Graduate Apache Allura from the Incubator. [ ] +0 Don't care. [ ] -1 Don't graduate Apache Allura from the Incubator because - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Apache Allura from the Incubator
After looking at it for some time, my optimistic outlook on the project would be +0 vote at best. On the plus side, the community seems to be really active and reasonably diverse. But if feels, like ASF has not yet become a true home for the project. Here's what I'm talking about: as a casual bystander who was trying to view Allura as an ASF project -- I had difficult time. First of all, I couldn't even get to the releases easily enough: https://incubator.apache.org/allura/downloads.html When I managed to get there the first thing that the README instructed me to do is to go to https://forge-allura.apache.org/ What is that? How does it relate to the project? In fact, from the dev list it feels like there may be yet another canonical place for the Allura -- over at sourceforge: http://mail-archives.apache.org/mod_mbox/incubator-allura-dev/201402.mbox/%3C52F80CA5.8060209%40brondsema.net%3E I am not quite sure if penalizing the project with a failed graduation vote is the right thing to do, but the state of the outwards facing project assets doesn't inspire a feel of a strong ASF community in me Just my 2c worth of feedback. Thanks, Roman. On Wed, Mar 12, 2014 at 11:30 AM, Roman Shaposhnik r...@apache.org wrote: I think what would help to make it into a stronger vote would be a few more IPMC folks looking into the status of the Allura community. I can volunteer to take a closer look at the community today to shape up my own opinion and cast the vote appropriately. If there's anybody else on IPMC who can do that -- that'll be appreciated. Thanks, Roman. On Wed, Mar 12, 2014 at 10:48 AM, Rich Bowen rbo...@rcbowen.com wrote: So where do we go from here? Four +1 votes, but only one of them from outside of the project membership. What does it signify? Did we pass? --Rich On 03/07/2014 03:16 PM, Dave Brondsema wrote: Hi everyone, The Apache Allura podling has discussed and voted to graduate from the incubator. We've made two releases, added several PPMC members, have been working with Infra to set up forge-allura.a.o, etc. We would now like the IPMC to vote. Discuss thread: http://markmail.org/message/wdddve3kxceqvgj5 Vote thread: http://markmail.org/message/4g54fcxwb4xxys5l Community results: +1 Roberto Galoppini Wayne Witzel III Cory Johns Dave Brondsema (IPMC) Rich Bowen (IPMC) Simone Gatti Stefano Invernizzi Alvaro del Castillo Jim Jagielski (IPMC) Tim Van Steenburgh +0 (none) -1 (none) Please VOTE below on the graduation of Apache Allura from the Incubator. The graduation resolution is pasted below. The VOTE will be open for at least 72 hours: [ ] +1 Graduate Apache Allura from the Incubator. [ ] +0 Don't care. [ ] -1 Don't graduate Apache Allura from the Incubator because X. Establish the Apache Allura Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to a software development infrastructure platform commonly known as a forge. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Allura Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Allura Project be and hereby is responsible for the creation and maintenance of software related to a software development infrastructure platform commonly known as a forge; and be it further RESOLVED, that the office of Vice President, Apache Allura be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Allura Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Allura Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Allura Project: * Tim Van Steenburgh tvansteenbu...@apache.org * Wayne Witzel III wwitz...@apache.org * Cory Johns john...@apache.org * Dave Brondsema brond...@apache.org * Roberto Galoppini galopp...@apache.org * Alvaro del Castilloa...@apache.org * Stefano Invernizzi stefano.inverni...@apache.org * Simone Gatti simonega...@apache.org * Jim Jagielski j...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Dave Brondsema be appointed to the office of Vice President,
Re: [VOTE] Graduation of Apache Allura from the Incubator
The Allura website does not appear to follow the branding guidelines. The page footer does not mention Apache Allura and Allura as trademarks Also the footer date is still 2011 The License link must point to http://www.apache.org/licenses/ - not to a local copy of the license. The intro. paragraph starts: The Allura Project is forge software This does not make sense - a project is not software. The bug tracker link on the main page is broken. The page https://incubator.apache.org/allura/contributors.html has at least one incorrect Apache id, and one missing id As noted elsethread, there don't appear to be any download links. The source code page only includes a git: scheme URL. It ought to be possible to browse the source without needing to install Git. The website needs plenty of TLC... As such, I don't think it's ready to become a TLP. On 7 March 2014 20:16, Dave Brondsema d...@brondsema.net wrote: Hi everyone, The Apache Allura podling has discussed and voted to graduate from the incubator. We've made two releases, added several PPMC members, have been working with Infra to set up forge-allura.a.o, etc. We would now like the IPMC to vote. Discuss thread: http://markmail.org/message/wdddve3kxceqvgj5 Vote thread: http://markmail.org/message/4g54fcxwb4xxys5l Community results: +1 Roberto Galoppini Wayne Witzel III Cory Johns Dave Brondsema (IPMC) Rich Bowen (IPMC) Simone Gatti Stefano Invernizzi Alvaro del Castillo Jim Jagielski (IPMC) Tim Van Steenburgh +0 (none) -1 (none) Please VOTE below on the graduation of Apache Allura from the Incubator. The graduation resolution is pasted below. The VOTE will be open for at least 72 hours: [ ] +1 Graduate Apache Allura from the Incubator. [ ] +0 Don't care. [ ] -1 Don't graduate Apache Allura from the Incubator because X. Establish the Apache Allura Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to a software development infrastructure platform commonly known as a forge. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Allura Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Allura Project be and hereby is responsible for the creation and maintenance of software related to a software development infrastructure platform commonly known as a forge; and be it further RESOLVED, that the office of Vice President, Apache Allura be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Allura Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Allura Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Allura Project: * Tim Van Steenburgh tvansteenbu...@apache.org * Wayne Witzel III wwitz...@apache.org * Cory Johns john...@apache.org * Dave Brondsema brond...@apache.org * Roberto Galoppini galopp...@apache.org * Alvaro del Castilloa...@apache.org * Stefano Invernizzi stefano.inverni...@apache.org * Simone Gatti simonega...@apache.org * Jim Jagielski j...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Dave Brondsema be appointed to the office of Vice President, Apache Allura, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Allura PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Allura Project; and be it further RESOLVED, that the Apache Allura Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Allura podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Allura podling encumbered upon the Apache Incubator Project are hereafter discharged. -- Dave Brondsema : d...@brondsema.net http://www.brondsema.net :
Re: [VOTE] Graduation of Apache Allura from the Incubator
Also, the podling status page is not complete. On 13 March 2014 18:34, sebb seb...@gmail.com wrote: The Allura website does not appear to follow the branding guidelines. The page footer does not mention Apache Allura and Allura as trademarks Also the footer date is still 2011 The License link must point to http://www.apache.org/licenses/ - not to a local copy of the license. The intro. paragraph starts: The Allura Project is forge software This does not make sense - a project is not software. The bug tracker link on the main page is broken. The page https://incubator.apache.org/allura/contributors.html has at least one incorrect Apache id, and one missing id As noted elsethread, there don't appear to be any download links. The source code page only includes a git: scheme URL. It ought to be possible to browse the source without needing to install Git. The website needs plenty of TLC... As such, I don't think it's ready to become a TLP. On 7 March 2014 20:16, Dave Brondsema d...@brondsema.net wrote: Hi everyone, The Apache Allura podling has discussed and voted to graduate from the incubator. We've made two releases, added several PPMC members, have been working with Infra to set up forge-allura.a.o, etc. We would now like the IPMC to vote. Discuss thread: http://markmail.org/message/wdddve3kxceqvgj5 Vote thread: http://markmail.org/message/4g54fcxwb4xxys5l Community results: +1 Roberto Galoppini Wayne Witzel III Cory Johns Dave Brondsema (IPMC) Rich Bowen (IPMC) Simone Gatti Stefano Invernizzi Alvaro del Castillo Jim Jagielski (IPMC) Tim Van Steenburgh +0 (none) -1 (none) Please VOTE below on the graduation of Apache Allura from the Incubator. The graduation resolution is pasted below. The VOTE will be open for at least 72 hours: [ ] +1 Graduate Apache Allura from the Incubator. [ ] +0 Don't care. [ ] -1 Don't graduate Apache Allura from the Incubator because X. Establish the Apache Allura Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to a software development infrastructure platform commonly known as a forge. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Allura Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Allura Project be and hereby is responsible for the creation and maintenance of software related to a software development infrastructure platform commonly known as a forge; and be it further RESOLVED, that the office of Vice President, Apache Allura be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Allura Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Allura Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Allura Project: * Tim Van Steenburgh tvansteenbu...@apache.org * Wayne Witzel III wwitz...@apache.org * Cory Johns john...@apache.org * Dave Brondsema brond...@apache.org * Roberto Galoppini galopp...@apache.org * Alvaro del Castilloa...@apache.org * Stefano Invernizzi stefano.inverni...@apache.org * Simone Gatti simonega...@apache.org * Jim Jagielski j...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Dave Brondsema be appointed to the office of Vice President, Apache Allura, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Allura PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Allura Project; and be it further RESOLVED, that the Apache Allura Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Allura podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Allura podling encumbered upon the Apache
Re: [VOTE] Graduation of Apache Allura from the Incubator
To be clear, are you voting -1 on this? I feel like most of these are cosmetic issues that could be addressed in a weekend. The Allura software is a software development forge and as such it makes sense for it to be self hosted. This may result in some metaphors that are a little unfamiliar on the website As to the project being forge software, rather than being a projecy which develops forge software, that feels like semantic pickiness, but we will address that immediately. -- Rich Bowen, mobile edition rbo...@rcbowen.com Please forgive top posting. On Mar 13, 2014 2:35 PM, sebb seb...@gmail.com wrote: The Allura website does not appear to follow the branding guidelines. The page footer does not mention Apache Allura and Allura as trademarks Also the footer date is still 2011 The License link must point to http://www.apache.org/licenses/ - not to a local copy of the license. The intro. paragraph starts: The Allura Project is forge software This does not make sense - a project is not software. The bug tracker link on the main page is broken. The page https://incubator.apache.org/allura/contributors.html has at least one incorrect Apache id, and one missing id As noted elsethread, there don't appear to be any download links. The source code page only includes a git: scheme URL. It ought to be possible to browse the source without needing to install Git. The website needs plenty of TLC... As such, I don't think it's ready to become a TLP. On 7 March 2014 20:16, Dave Brondsema d...@brondsema.net wrote: Hi everyone, The Apache Allura podling has discussed and voted to graduate from the incubator. We've made two releases, added several PPMC members, have been working with Infra to set up forge-allura.a.o, etc. We would now like the IPMC to vote. Discuss thread: http://markmail.org/message/wdddve3kxceqvgj5 Vote thread: http://markmail.org/message/4g54fcxwb4xxys5l Community results: +1 Roberto Galoppini Wayne Witzel III Cory Johns Dave Brondsema (IPMC) Rich Bowen (IPMC) Simone Gatti Stefano Invernizzi Alvaro del Castillo Jim Jagielski (IPMC) Tim Van Steenburgh +0 (none) -1 (none) Please VOTE below on the graduation of Apache Allura from the Incubator. The graduation resolution is pasted below. The VOTE will be open for at least 72 hours: [ ] +1 Graduate Apache Allura from the Incubator. [ ] +0 Don't care. [ ] -1 Don't graduate Apache Allura from the Incubator because X. Establish the Apache Allura Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to a software development infrastructure platform commonly known as a forge. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Allura Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Allura Project be and hereby is responsible for the creation and maintenance of software related to a software development infrastructure platform commonly known as a forge; and be it further RESOLVED, that the office of Vice President, Apache Allura be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Allura Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Allura Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Allura Project: * Tim Van Steenburgh tvansteenbu...@apache.org * Wayne Witzel III wwitz...@apache.org * Cory Johns john...@apache.org * Dave Brondsema brond...@apache.org * Roberto Galoppini galopp...@apache.org * Alvaro del Castilloa...@apache.org * Stefano Invernizzi stefano.inverni...@apache.org * Simone Gatti simonega...@apache.org * Jim Jagielski j...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Dave Brondsema be appointed to the office of Vice President, Apache Allura, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is
Re: [VOTE] Graduation of Apache Allura from the Incubator
On 13 March 2014 22:10, Rich Bowen rbo...@rcbowen.com wrote: To be clear, are you voting -1 on this? I feel like most of these are cosmetic issues that could be addressed in a weekend. I imagine the issues could be addressed in a weekend. However I don't regard them as cosmetic issues. So until this is done, I don't think the podling is ready to graduate. The Allura software is a software development forge and as such it makes sense for it to be self hosted. This may result in some metaphors that are a little unfamiliar on the website No idea what you mean by that paragraph. As to the project being forge software, rather than being a projecy which develops forge software, that feels like semantic pickiness, but we will address that immediately. AIUI this is an important part of the branding. Unless the Allura brand is clearly associated with a particular type of software, it may be difficult to defend Allura as a trademark of the ASF. -- Rich Bowen, mobile edition rbo...@rcbowen.com Please forgive top posting. On Mar 13, 2014 2:35 PM, sebb seb...@gmail.com wrote: The Allura website does not appear to follow the branding guidelines. The page footer does not mention Apache Allura and Allura as trademarks Also the footer date is still 2011 The License link must point to http://www.apache.org/licenses/ - not to a local copy of the license. The intro. paragraph starts: The Allura Project is forge software This does not make sense - a project is not software. The bug tracker link on the main page is broken. The page https://incubator.apache.org/allura/contributors.html has at least one incorrect Apache id, and one missing id As noted elsethread, there don't appear to be any download links. The source code page only includes a git: scheme URL. It ought to be possible to browse the source without needing to install Git. The website needs plenty of TLC... As such, I don't think it's ready to become a TLP. On 7 March 2014 20:16, Dave Brondsema d...@brondsema.net wrote: Hi everyone, The Apache Allura podling has discussed and voted to graduate from the incubator. We've made two releases, added several PPMC members, have been working with Infra to set up forge-allura.a.o, etc. We would now like the IPMC to vote. Discuss thread: http://markmail.org/message/wdddve3kxceqvgj5 Vote thread: http://markmail.org/message/4g54fcxwb4xxys5l Community results: +1 Roberto Galoppini Wayne Witzel III Cory Johns Dave Brondsema (IPMC) Rich Bowen (IPMC) Simone Gatti Stefano Invernizzi Alvaro del Castillo Jim Jagielski (IPMC) Tim Van Steenburgh +0 (none) -1 (none) Please VOTE below on the graduation of Apache Allura from the Incubator. The graduation resolution is pasted below. The VOTE will be open for at least 72 hours: [ ] +1 Graduate Apache Allura from the Incubator. [ ] +0 Don't care. [ ] -1 Don't graduate Apache Allura from the Incubator because X. Establish the Apache Allura Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to a software development infrastructure platform commonly known as a forge. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Allura Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Allura Project be and hereby is responsible for the creation and maintenance of software related to a software development infrastructure platform commonly known as a forge; and be it further RESOLVED, that the office of Vice President, Apache Allura be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Allura Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Allura Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Allura Project: * Tim Van Steenburgh tvansteenbu...@apache.org * Wayne Witzel III wwitz...@apache.org * Cory Johns john...@apache.org * Dave Brondsema brond...@apache.org * Roberto Galoppini galopp...@apache.org * Alvaro del Castilloa...@apache.org * Stefano Invernizzi stefano.inverni...@apache.org *
Re: [VOTE] Graduation of Apache Allura from the Incubator
On Thu, Mar 13, 2014 at 1:29 PM, Roman Shaposhnik r...@apache.org wrote: After looking at it for some time, my optimistic outlook on the project would be +0 vote at best. On the plus side, the community seems to be really active and reasonably diverse. But if feels, like ASF has not yet become a true home for the project. Here's what I'm talking about: as a casual bystander who was trying to view Allura as an ASF project -- I had difficult time. First of all, I couldn't even get to the releases easily enough: https://incubator.apache.org/allura/downloads.html When I managed to get there the first thing that the README instructed me to do is to go to https://forge-allura.apache.org/ What is that? How does it relate to the project? In fact, from the dev list it feels like there may be yet another canonical place for the Allura -- over at sourceforge: http://mail-archives.apache.org/mod_mbox/incubator-allura-dev/201402.mbox/%3C52F80CA5.8060209%40brondsema.net%3E I am not quite sure if penalizing the project with a failed graduation vote is the right thing to do, but the state of the outwards facing project assets doesn't inspire a feel of a strong ASF community in me Just my 2c worth of feedback. The projects bug tracker also seems to be at sourceforge.net, which means you need a sf.net account to participate in the project. Based on a quick perusal most of the dev@ traffic seems to be bug tracker - which means most of this is happening at SourceForge. I don't know that this is really problematic - we do have projects using github as the main portion of the contribution workflow, but it does give me pause. I also see http://sf.net/p/allura - which bears a SF logo, and which doesn't note the fact that the project is at the incubator until 1/2 down the page. And nowhere on the page is it referred to as Apache Allura. From a standpoint of the project which is supposed to be policing its brand, this leaves me a bit worried - this page shows an update to that page recently; and appears at least to the outside world to be the nexus for the project and maintained by members of the PPMC. (first return on Google is the sourceforge link.) To be clear other projects have listings at Sourceforge, so aside from the brand and trademark policing that needs to happen, I am not sure the existence of the page is much to be concerned about. There's a notice on the page that reads: Some project information is still at SourceForge during this transition period. and indeed, there's http://allura.sourceforge.net/docs/ which looks surprisingly good when compared with http://incubator.apache.org/allura which doesn't have a working bug tracker link, and steps listed for building Allura consists of 'TODO'. All of the content from the allure source forge site appears to be in the Apache Allura git repo, so I am curious why it isn't published at the ASF. And again, we have projects who host documentation at ReadTheDocs, so I am not sure that documentation living elsewhere is an inherent problem, but it gives me pause. Individually I don't know that any of these are problematic; but I am curious what the mentors take on it is. --David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Apache Allura from the Incubator
On Thu, Mar 13, 2014 at 9:54 PM, David Nalley da...@gnsa.us wrote: On Thu, Mar 13, 2014 at 1:29 PM, Roman Shaposhnik r...@apache.org wrote: After looking at it for some time, my optimistic outlook on the project would be +0 vote at best. On the plus side, the community seems to be really active and reasonably diverse. But if feels, like ASF has not yet become a true home for the project. Here's what I'm talking about: as a casual bystander who was trying to view Allura as an ASF project -- I had difficult time. First of all, I couldn't even get to the releases easily enough: https://incubator.apache.org/allura/downloads.html When I managed to get there the first thing that the README instructed me to do is to go to https://forge-allura.apache.org/ What is that? How does it relate to the project? In fact, from the dev list it feels like there may be yet another canonical place for the Allura -- over at sourceforge: http://mail-archives.apache.org/mod_mbox/incubator-allura-dev/201402.mbox/%3C52F80CA5.8060209%40brondsema.net%3E I am not quite sure if penalizing the project with a failed graduation vote is the right thing to do, but the state of the outwards facing project assets doesn't inspire a feel of a strong ASF community in me Just my 2c worth of feedback. The projects bug tracker also seems to be at sourceforge.net, which means you need a sf.net account to participate in the project. Based on a quick perusal most of the dev@ traffic seems to be bug tracker - which means most of this is happening at SourceForge. I don't know that this is really problematic - we do have projects using github as the main portion of the contribution workflow, but it does give me pause. I also see http://sf.net/p/allura - which bears a SF logo, and which doesn't note the fact that the project is at the incubator until 1/2 down the page. And nowhere on the page is it referred to as Apache Allura. From a standpoint of the project which is supposed to be policing its brand, this leaves me a bit worried - this page shows an update to that page recently; and appears at least to the outside world to be the nexus for the project and maintained by members of the PPMC. (first return on Google is the sourceforge link.) To be clear other projects have listings at Sourceforge, so aside from the brand and trademark policing that needs to happen, I am not sure the existence of the page is much to be concerned about. There's a notice on the page that reads: Some project information is still at SourceForge during this transition period. and indeed, there's http://allura.sourceforge.net/docs/ which looks surprisingly good when compared with http://incubator.apache.org/allura which doesn't have a working bug tracker link, and steps listed for building Allura consists of 'TODO'. All of the content from the allure source forge site appears to be in the Apache Allura git repo, so I am curious why it isn't published at the ASF. And again, we have projects who host documentation at ReadTheDocs, so I am not sure that documentation living elsewhere is an inherent problem, but it gives me pause. Individually I don't know that any of these are problematic; but I am curious what the mentors take on it is. --David And it's just dawned on me what's happening. The project is using http://forge-allura.apache.org/p/allura as it's home page instead of http://incubator.apache.org/allura which appears to have all of the appropriate content (according to a google cache) but is down right now. It's making more sense; is the intention to make that the project home page? (e.g. allura.apache.org) --David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Apache Allura from the Incubator
On 03/13/2014 10:00 PM, David Nalley wrote: On Thu, Mar 13, 2014 at 9:54 PM, David Nalley da...@gnsa.us wrote: On Thu, Mar 13, 2014 at 1:29 PM, Roman Shaposhnik r...@apache.org wrote: After looking at it for some time, my optimistic outlook on the project would be +0 vote at best. On the plus side, the community seems to be really active and reasonably diverse. But if feels, like ASF has not yet become a true home for the project. Here's what I'm talking about: as a casual bystander who was trying to view Allura as an ASF project -- I had difficult time. First of all, I couldn't even get to the releases easily enough: https://incubator.apache.org/allura/downloads.html When I managed to get there the first thing that the README instructed me to do is to go to https://forge-allura.apache.org/ What is that? How does it relate to the project? In fact, from the dev list it feels like there may be yet another canonical place for the Allura -- over at sourceforge: http://mail-archives.apache.org/mod_mbox/incubator-allura-dev/201402.mbox/%3C52F80CA5.8060209%40brondsema.net%3E I am not quite sure if penalizing the project with a failed graduation vote is the right thing to do, but the state of the outwards facing project assets doesn't inspire a feel of a strong ASF community in me Just my 2c worth of feedback. The projects bug tracker also seems to be at sourceforge.net, which means you need a sf.net account to participate in the project. Based on a quick perusal most of the dev@ traffic seems to be bug tracker - which means most of this is happening at SourceForge. I don't know that this is really problematic - we do have projects using github as the main portion of the contribution workflow, but it does give me pause. I also see http://sf.net/p/allura - which bears a SF logo, and which doesn't note the fact that the project is at the incubator until 1/2 down the page. And nowhere on the page is it referred to as Apache Allura. From a standpoint of the project which is supposed to be policing its brand, this leaves me a bit worried - this page shows an update to that page recently; and appears at least to the outside world to be the nexus for the project and maintained by members of the PPMC. (first return on Google is the sourceforge link.) To be clear other projects have listings at Sourceforge, so aside from the brand and trademark policing that needs to happen, I am not sure the existence of the page is much to be concerned about. There's a notice on the page that reads: Some project information is still at SourceForge during this transition period. and indeed, there's http://allura.sourceforge.net/docs/ which looks surprisingly good when compared with http://incubator.apache.org/allura which doesn't have a working bug tracker link, and steps listed for building Allura consists of 'TODO'. All of the content from the allure source forge site appears to be in the Apache Allura git repo, so I am curious why it isn't published at the ASF. And again, we have projects who host documentation at ReadTheDocs, so I am not sure that documentation living elsewhere is an inherent problem, but it gives me pause. Individually I don't know that any of these are problematic; but I am curious what the mentors take on it is. --David And it's just dawned on me what's happening. The project is using http://forge-allura.apache.org/p/allura as it's home page instead of http://incubator.apache.org/allura which appears to have all of the appropriate content (according to a google cache) but is down right now. It's making more sense; is the intention to make that the project home page? (e.g. allura.apache.org) You got it! (And bad timing that it was down for several hours today - its back up now). Roman and sebb had similar comments to yours, so I'll respond in a single email. We are self-hosting at http://forge-allura.apache.org/p/allura so that is really our home page. It has a clear download link, and git browse link, and the text doesn't equate the project == the software. But it is missing a link to http://www.apache.org/licenses/LICENSE-2.0. (Note this domain forge-allura.a.o also has the future potential to be a project hosting platform for other interested Apache projects besides Allura itself) http://incubator.apache.org/allura is not maintained as is obvious. That should just go away or be redirected to forge-allura.apache.org/p/allura Similarly when we're a TLP, allura.apache.org can just redirect there. We should update http://sf.net/p/allura to remove the SF logo, and clearly identify it as Apache Allura and incubating, so it adheres with Apache branding guidelines. The docs at http://allura.sourceforge.net/docs/ could be moved to live at a URL like http://forge-allura.apache.org/p/allura/docs with a little work. No reason not to. Tickets are the other item still on SourceForge. We do want to move them over to the
Re: [VOTE] Graduation of Apache Allura from the Incubator
So where do we go from here? Four +1 votes, but only one of them from outside of the project membership. What does it signify? Did we pass? --Rich On 03/07/2014 03:16 PM, Dave Brondsema wrote: Hi everyone, The Apache Allura podling has discussed and voted to graduate from the incubator. We've made two releases, added several PPMC members, have been working with Infra to set up forge-allura.a.o, etc. We would now like the IPMC to vote. Discuss thread: http://markmail.org/message/wdddve3kxceqvgj5 Vote thread: http://markmail.org/message/4g54fcxwb4xxys5l Community results: +1 Roberto Galoppini Wayne Witzel III Cory Johns Dave Brondsema (IPMC) Rich Bowen (IPMC) Simone Gatti Stefano Invernizzi Alvaro del Castillo Jim Jagielski (IPMC) Tim Van Steenburgh +0 (none) -1 (none) Please VOTE below on the graduation of Apache Allura from the Incubator. The graduation resolution is pasted below. The VOTE will be open for at least 72 hours: [ ] +1 Graduate Apache Allura from the Incubator. [ ] +0 Don't care. [ ] -1 Don't graduate Apache Allura from the Incubator because X. Establish the Apache Allura Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to a software development infrastructure platform commonly known as a forge. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Allura Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Allura Project be and hereby is responsible for the creation and maintenance of software related to a software development infrastructure platform commonly known as a forge; and be it further RESOLVED, that the office of Vice President, Apache Allura be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Allura Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Allura Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Allura Project: * Tim Van Steenburgh tvansteenbu...@apache.org * Wayne Witzel III wwitz...@apache.org * Cory Johns john...@apache.org * Dave Brondsema brond...@apache.org * Roberto Galoppini galopp...@apache.org * Alvaro del Castilloa...@apache.org * Stefano Invernizzi stefano.inverni...@apache.org * Simone Gatti simonega...@apache.org * Jim Jagielski j...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Dave Brondsema be appointed to the office of Vice President, Apache Allura, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Allura PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Allura Project; and be it further RESOLVED, that the Apache Allura Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Allura podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Allura podling encumbered upon the Apache Incubator Project are hereafter discharged. -- Rich Bowen - rbo...@rcbowen.com - @rbowen http://apachecon.com/ - @apachecon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Apache Allura from the Incubator
On Wed, Mar 12, 2014 at 10:48 AM, Rich Bowen rbo...@rcbowen.com wrote: So where do we go from here? Four +1 votes, but only one of them from outside of the project membership. What does it signify? Did we pass? Votes from the Mentors of a podling are more meaningful than votes from unaffiliated IPMC members who do not follow the podling closely. Call the vote and celebrate! Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Apache Allura from the Incubator
I think what would help to make it into a stronger vote would be a few more IPMC folks looking into the status of the Allura community. I can volunteer to take a closer look at the community today to shape up my own opinion and cast the vote appropriately. If there's anybody else on IPMC who can do that -- that'll be appreciated. Thanks, Roman. On Wed, Mar 12, 2014 at 10:48 AM, Rich Bowen rbo...@rcbowen.com wrote: So where do we go from here? Four +1 votes, but only one of them from outside of the project membership. What does it signify? Did we pass? --Rich On 03/07/2014 03:16 PM, Dave Brondsema wrote: Hi everyone, The Apache Allura podling has discussed and voted to graduate from the incubator. We've made two releases, added several PPMC members, have been working with Infra to set up forge-allura.a.o, etc. We would now like the IPMC to vote. Discuss thread: http://markmail.org/message/wdddve3kxceqvgj5 Vote thread: http://markmail.org/message/4g54fcxwb4xxys5l Community results: +1 Roberto Galoppini Wayne Witzel III Cory Johns Dave Brondsema (IPMC) Rich Bowen (IPMC) Simone Gatti Stefano Invernizzi Alvaro del Castillo Jim Jagielski (IPMC) Tim Van Steenburgh +0 (none) -1 (none) Please VOTE below on the graduation of Apache Allura from the Incubator. The graduation resolution is pasted below. The VOTE will be open for at least 72 hours: [ ] +1 Graduate Apache Allura from the Incubator. [ ] +0 Don't care. [ ] -1 Don't graduate Apache Allura from the Incubator because X. Establish the Apache Allura Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to a software development infrastructure platform commonly known as a forge. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Allura Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Allura Project be and hereby is responsible for the creation and maintenance of software related to a software development infrastructure platform commonly known as a forge; and be it further RESOLVED, that the office of Vice President, Apache Allura be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Allura Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Allura Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Allura Project: * Tim Van Steenburgh tvansteenbu...@apache.org * Wayne Witzel III wwitz...@apache.org * Cory Johns john...@apache.org * Dave Brondsema brond...@apache.org * Roberto Galoppini galopp...@apache.org * Alvaro del Castilloa...@apache.org * Stefano Invernizzi stefano.inverni...@apache.org * Simone Gatti simonega...@apache.org * Jim Jagielski j...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Dave Brondsema be appointed to the office of Vice President, Apache Allura, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Allura PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Allura Project; and be it further RESOLVED, that the Apache Allura Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Allura podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Allura podling encumbered upon the Apache Incubator Project are hereafter discharged. -- Rich Bowen - rbo...@rcbowen.com - @rbowen http://apachecon.com/ - @apachecon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Apache Allura from the Incubator
Yup, it's stefanoinve. Here's my explicit +1 And a bump. We're getting close to 72 hours already. We don't want to rush the vote, but if it is possible to get it done before the board meeting on Wed, then we could graduate before ApacheCon which would be very nice. Thanks On 3/7/14 8:09 PM, Craig L Russell wrote: On Mar 7, 2014, at 3:56 PM, sebb wrote: * Stefano Invernizzi stefano.inverni...@apache.org That's not the correct e-mail AFAICT I don't think any ASF ids have a . character in them. Try stefanoinve Craig Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Dave Brondsema : d...@brondsema.net http://www.brondsema.net : personal http://www.splike.com : programming - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Apache Allura from the Incubator
The board meeting is *next* Wednesday... :) On Mar 10, 2014, at 10:57 AM, Dave Brondsema d...@brondsema.net wrote: Yup, it's stefanoinve. Here's my explicit +1 And a bump. We're getting close to 72 hours already. We don't want to rush the vote, but if it is possible to get it done before the board meeting on Wed, then we could graduate before ApacheCon which would be very nice. Thanks On 3/7/14 8:09 PM, Craig L Russell wrote: On Mar 7, 2014, at 3:56 PM, sebb wrote: * Stefano Invernizzi stefano.inverni...@apache.org That's not the correct e-mail AFAICT I don't think any ASF ids have a . character in them. Try stefanoinve Craig Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Dave Brondsema : d...@brondsema.net http://www.brondsema.net : personal http://www.splike.com : programming - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Apache Allura from the Incubator
On Mar 7, 2014, at 3:16 PM, Dave Brondsema d...@brondsema.net wrote: Please VOTE below on the graduation of Apache Allura from the Incubator. The graduation resolution is pasted below. The VOTE will be open for at least 72 hours: [X] +1 Graduate Apache Allura from the Incubator. [ ] +0 Don't care. [ ] -1 Don't graduate Apache Allura from the Incubator because - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Apache Allura from the Incubator
With fixing of Apache ID for Stefano Invernizzi in the website and incubator report page: +1 (binding) Good luck guys! - Henry On Fri, Mar 7, 2014 at 12:16 PM, Dave Brondsema d...@brondsema.net wrote: Hi everyone, The Apache Allura podling has discussed and voted to graduate from the incubator. We've made two releases, added several PPMC members, have been working with Infra to set up forge-allura.a.o, etc. We would now like the IPMC to vote. Discuss thread: http://markmail.org/message/wdddve3kxceqvgj5 Vote thread: http://markmail.org/message/4g54fcxwb4xxys5l Community results: +1 Roberto Galoppini Wayne Witzel III Cory Johns Dave Brondsema (IPMC) Rich Bowen (IPMC) Simone Gatti Stefano Invernizzi Alvaro del Castillo Jim Jagielski (IPMC) Tim Van Steenburgh +0 (none) -1 (none) Please VOTE below on the graduation of Apache Allura from the Incubator. The graduation resolution is pasted below. The VOTE will be open for at least 72 hours: [ ] +1 Graduate Apache Allura from the Incubator. [ ] +0 Don't care. [ ] -1 Don't graduate Apache Allura from the Incubator because X. Establish the Apache Allura Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to a software development infrastructure platform commonly known as a forge. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Allura Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Allura Project be and hereby is responsible for the creation and maintenance of software related to a software development infrastructure platform commonly known as a forge; and be it further RESOLVED, that the office of Vice President, Apache Allura be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Allura Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Allura Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Allura Project: * Tim Van Steenburgh tvansteenbu...@apache.org * Wayne Witzel III wwitz...@apache.org * Cory Johns john...@apache.org * Dave Brondsema brond...@apache.org * Roberto Galoppini galopp...@apache.org * Alvaro del Castilloa...@apache.org * Stefano Invernizzi stefano.inverni...@apache.org * Simone Gatti simonega...@apache.org * Jim Jagielski j...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Dave Brondsema be appointed to the office of Vice President, Apache Allura, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Allura PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Allura Project; and be it further RESOLVED, that the Apache Allura Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Allura podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Allura podling encumbered upon the Apache Incubator Project are hereafter discharged. -- Dave Brondsema : d...@brondsema.net http://www.brondsema.net : personal http://www.splike.com : programming - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Apache Allura from the Incubator
On 03/07/2014 03:16 PM, Dave Brondsema wrote: Please VOTE below on the graduation of Apache Allura from the Incubator. The graduation resolution is pasted below. The VOTE will be open for at least 72 hours: [x] +1 Graduate Apache Allura from the Incubator. [ ] +0 Don't care. [ ] -1 Don't graduate Apache Allura from the Incubator because +1 -- Rich Bowen - rbo...@rcbowen.com - @rbowen http://apachecon.com/ - @apachecon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Apache Allura from the Incubator
On 7 March 2014 20:16, Dave Brondsema d...@brondsema.net wrote: Hi everyone, The Apache Allura podling has discussed and voted to graduate from the incubator. We've made two releases, added several PPMC members, have been working with Infra to set up forge-allura.a.o, etc. We would now like the IPMC to vote. Discuss thread: http://markmail.org/message/wdddve3kxceqvgj5 Vote thread: http://markmail.org/message/4g54fcxwb4xxys5l Community results: +1 Roberto Galoppini Wayne Witzel III Cory Johns Dave Brondsema (IPMC) Rich Bowen (IPMC) Simone Gatti Stefano Invernizzi Alvaro del Castillo Jim Jagielski (IPMC) Tim Van Steenburgh +0 (none) -1 (none) Please VOTE below on the graduation of Apache Allura from the Incubator. The graduation resolution is pasted below. The VOTE will be open for at least 72 hours: [ ] +1 Graduate Apache Allura from the Incubator. [ ] +0 Don't care. [ ] -1 Don't graduate Apache Allura from the Incubator because X. Establish the Apache Allura Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to a software development infrastructure platform commonly known as a forge. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Allura Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Allura Project be and hereby is responsible for the creation and maintenance of software related to a software development infrastructure platform commonly known as a forge; and be it further RESOLVED, that the office of Vice President, Apache Allura be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Allura Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Allura Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Allura Project: * Tim Van Steenburgh tvansteenbu...@apache.org * Wayne Witzel III wwitz...@apache.org * Cory Johns john...@apache.org * Dave Brondsema brond...@apache.org * Roberto Galoppini galopp...@apache.org * Alvaro del Castilloa...@apache.org * Stefano Invernizzi stefano.inverni...@apache.org That's not the correct e-mail AFAICT I don't think any ASF ids have a . character in them. * Simone Gatti simonega...@apache.org * Jim Jagielski j...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Dave Brondsema be appointed to the office of Vice President, Apache Allura, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Allura PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Allura Project; and be it further RESOLVED, that the Apache Allura Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Allura podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Allura podling encumbered upon the Apache Incubator Project are hereafter discharged. -- Dave Brondsema : d...@brondsema.net http://www.brondsema.net : personal http://www.splike.com : programming - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Apache Allura from the Incubator
On Mar 7, 2014, at 3:56 PM, sebb wrote: * Stefano Invernizzi stefano.inverni...@apache.org That's not the correct e-mail AFAICT I don't think any ASF ids have a . character in them. Try stefanoinve Craig Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
