Re: projects.apache.org overhaul proposal
On 1/15/15, 9:46 AM, Ross Gardler (MS OPEN TECH) ross.gard...@microsoft.com wrote: Where are you seeing discouragement of pilot projects? In the tone and content of the responses on this thread, including this one where it feels to me you are again using the maintenance and training costs to make it seem highly unlikely that any pilot program would ever be accepted. I understand we are using money from donors and have to be somewhat conservative, but I don’t know if it really serves the mission of the ASF to be one of the more conservative customers our projects will encounter. IMO, it would be much more encouraging to say “I don’t know much about OFBiz but if you can find volunteers to put together a pilot program and show us that it is easy to learn and use and will save us time and money, we’ll give you an Azure VM to get started.” How easy something is to learn is often biased by whether that person is incentivized to learn or not. -Alex
Re: projects.apache.org overhaul proposal
On 1/15/15, 6:35 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Thu, Jan 15, 2015 at 3:24 PM, Rich Bowen rbo...@rcbowen.com wrote: ...*historically*, when this kind of thing has happened (project implements, thing becomes critical), gradually it becomes the responsibility of Infra, not of the project, to do ongoing maintenance Yes, this is why I'm reluctant to encourage any initiative that requires our infrastructure team to support new tools. And I suspect infra shares that reluctance ;-) That being said, it's always a question of benefits vs. costs - but if a simple thing using technologies that every web developer is supposed to know works the choice is a no-brainer for me. IMO, that reluctance is the challenge faced by any ASF project that isn’t yet on the list of what everyone is “supposed to know”. AIUI, Infra is also staffed by volunteers so project folks can volunteer to be Infra for their project’s usage at the ASF. And if it isn’t “easy” for non-project Infra folks to grok how the project’s technology works, that is just another challenge for the project. One would suspect that they’ll face the same battle acquiring new customers anyway. I’d guess that most ASF projects are not yet a standard and want to be the new standard. Getting that first testimonial is often key to becoming the new standard. It seems wrong for the ASF to discourage establishment of pilot implementations until the project establishes a track record on some other set of customers. IMO, the ability to get an Azure VM is game changing in this regard. The project’s committers can take full responsibility for the pilot program. All Infra might need to do is establish one-way or two-way database or file mirrors so the pilot can’t mess up what works until it is deemed ready. I’d bet that most of a project’s customers would do that anyway. Infra should be encouraged to learn new things if the ROI is established by the pilot program and includes the cost of training non-project Infra folks, and those folks should ask for support like any other customer on that project’s list, and if they don’t get timely and helpful support, reject the product just like any other customer would. In summary, the ASF should be a slightly more willing customer for any of its projects. Azure VM’s seem to provide a way to do that without adding more load to Infra. -Alex
RE: projects.apache.org overhaul proposal
Where are you seeing discouragement of pilot projects? Any volunteer can step up and deliver any pilot for the foundation on a voluntary basis. We are set up to do that. However, if a service stood up by a volunteer becomes a core part of the ASF then that must be maintained in an ongoing basis. This has budget and resource constraints. Yes we have volunteers, but we don't give volunteers pagers, we have a paid team of contractors who take that kind of responsibility. We can't tell volunteers what to do with their time and we expect our contractors to make decisions that mean they can deliver on our expectations as expressed by VP Infra. It would be wrong of the foundation to say sure go implement that wonderful sounding solution without also saying but be aware there is no guarantee that the foundation would actually use it. I'm pretty sure any volunteer would feel abused by such an approach. Nobody has said to Daniel go get infra backing because his proposal does not change current core processes (it pulls data from those processes but does not write to that data). Furthermore the results of his work, while beneficial to the foundation, are not core to the foundation. If projects.apache.org were down it would be an inconvenience. Waiting for a volunteer to fix it would not be a concern. However, if the system we use for creating and managing core data (as per the OfBiz proposal) were down it would be a significant problem and we would not want to wait for volunteers. Because of this the foundation would look to VP Infra to provide an SLA for that service and VP Infra would say fine, but for that SLA it will cost $x. In a perfect world VP Infra will be able to mobilize volunteers and would not draw on that budget line, but we have to plan for the circumstances in which volunteers are not able to react in a timely way. Add to this that historically we know that volunteers often disappear (as is their right). In short, the foundation cannot rely on volunteers for core services. What we can, and should, do is rely on volunteers to reduce the costs of those core services. With 170+ projects to consider it's arguably the responsibility of those volunteers to actively seek out ways in which they can help reduce those costs (this is one of my own criteria for member candidates). Pierre, for his part, is now following up with the appropriate people (thanks Pierre). Ross -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Thursday, January 15, 2015 9:22 AM To: dev Subject: Re: projects.apache.org overhaul proposal On 1/15/15, 6:35 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Thu, Jan 15, 2015 at 3:24 PM, Rich Bowen rbo...@rcbowen.com wrote: ...*historically*, when this kind of thing has happened (project implements, thing becomes critical), gradually it becomes the responsibility of Infra, not of the project, to do ongoing maintenance Yes, this is why I'm reluctant to encourage any initiative that requires our infrastructure team to support new tools. And I suspect infra shares that reluctance ;-) That being said, it's always a question of benefits vs. costs - but if a simple thing using technologies that every web developer is supposed to know works the choice is a no-brainer for me. IMO, that reluctance is the challenge faced by any ASF project that isn’t yet on the list of what everyone is “supposed to know”. AIUI, Infra is also staffed by volunteers so project folks can volunteer to be Infra for their project’s usage at the ASF. And if it isn’t “easy” for non-project Infra folks to grok how the project’s technology works, that is just another challenge for the project. One would suspect that they’ll face the same battle acquiring new customers anyway. I’d guess that most ASF projects are not yet a standard and want to be the new standard. Getting that first testimonial is often key to becoming the new standard. It seems wrong for the ASF to discourage establishment of pilot implementations until the project establishes a track record on some other set of customers. IMO, the ability to get an Azure VM is game changing in this regard. The project’s committers can take full responsibility for the pilot program. All Infra might need to do is establish one-way or two-way database or file mirrors so the pilot can’t mess up what works until it is deemed ready. I’d bet that most of a project’s customers would do that anyway. Infra should be encouraged to learn new things if the ROI is established by the pilot program and includes the cost of training non-project Infra folks, and those folks should ask for support like any other customer on that project’s list, and if they don’t get timely and helpful support, reject the product just like any other customer would. In summary, the ASF should be a slightly more willing customer for any of its projects. Azure VM’s seem to provide a way to do
Re: projects.apache.org overhaul proposal
On Thu, Jan 15, 2015 at 6:21 PM, Alex Harui aha...@adobe.com wrote: ...Infra should be encouraged to learn new things if the ROI is established by the pilot program... Of course, but when you have to maintain systems for years the investment is huge...so the return has to be huge as well. -Bertrand
Re: projects.apache.org overhaul proposal
To put that last sentence in a more positive manner: The future looks bright and is multi-coloured! But it is shrouded in layers of mists. Unfortunately, so is the future influx of funds. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Thu, Jan 15, 2015 at 4:22 PM, Pierre Smits pierre.sm...@gmail.com wrote: Maybe we should considering changing the subject as this seems bigger than just an overhaul of one of the front ends of the ASF? Yes, it all has to do with the ROI (the benefits at large vs the costs) for the ASF. And such need to be determined regarding the future, not the present day or the past. The time that the ASF was a one project endeavour has past, and the importance of the foundation in the umfeld is growing day by day. People are turning more and more to the ASF with requests to host their open source projects. This all leads to more demand on solutions and services provided by INFRA. But also on our offices. More people/projects involved means more work on the heads in Brand Management, Legal, Communications, Secretary, etc. And these offices also use solutions/services of INFRA and/or third parties. Thus, any decision of this kind is should be taken must be weighed with the future - the 5 year view - of the ASF and its offices in mind. So, what are the future demands on our offices? And how does that impact the solutions and services rendered by INFRA, and/or third parties? To what budget requirements will the availability of those (future) solutions and services lead, with the use of current setup? Can costs be saved by rethinking that setup and replacing it by something else, and do the projected savings outweigh the projected cost of change? Such questions must be considered regularly, because there is no guarantee that current influx of funds will be the same or even increase equally with the increase of needs/wants and pleasures of offices and projects and inherently the cost associated to all that. And then we can make the proper decisions. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Thu, Jan 15, 2015 at 3:35 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Thu, Jan 15, 2015 at 3:24 PM, Rich Bowen rbo...@rcbowen.com wrote: ...*historically*, when this kind of thing has happened (project implements, thing becomes critical), gradually it becomes the responsibility of Infra, not of the project, to do ongoing maintenance Yes, this is why I'm reluctant to encourage any initiative that requires our infrastructure team to support new tools. And I suspect infra shares that reluctance ;-) That being said, it's always a question of benefits vs. costs - but if a simple thing using technologies that every web developer is supposed to know works the choice is a no-brainer for me. -Bertrand
Re: New ComDev VM
+1 On Jan 15, 2015, at 10:54 AM, Ross Gardler (MS OPEN TECH) ross.gard...@microsoft.com wrote: Site dev is just a convenience list. There is no committee backing it. ComDev is the right place. Sent from my Windows Phone From: Daniel Grunomailto:humbed...@apache.org Sent: 1/15/2015 7:49 AM To: dev@community.apache.orgmailto:dev@community.apache.org Subject: Re: New ComDev VM Hi Louis, Yes, I have discussed with my VP, and he does not have any interest whatsoever in infra maintaining the projects site, which is why I instead turned to comdev as a sponsor. projects.apache.org is just as much about getting new people to participate in our community (by finding projects they can join) as it is about showing what we've got, so it felt only natural to ask the community development project to take over. site-dev may be listed as one option, but it is hardly used anymore, sadly. With regards, Daniel. On 2015-01-15 16:42, Louis Suárez-Potts wrote: Daniel, One thing—Apache’s Infra page lists site-dev@ for overhauls that seem to be like what you are proposing. See site-dev@ The site-dev list was formed to allow for discussion of every aspect of the small number of websites that are centrally managed by the ASF (e.g. /dev/) and for co-ordination of infrastructure needs and publishing methods for all ASF project websites. Participation in these lists is NOT limited to committers, but rather to any committer or interested party invited by a committer (please would the committer send email to site-dev-owner). The list is normally low volume and aims to discsuss all aspects of the websites, from creation tools through to look and feel.” at http://apache.org/dev/infra-mail.html. Doubtless, you’ve already gone over this… louis On 15 Jan 2015, at 03:07, Daniel Gruno humbed...@apache.org wrote: Hiya folks, as part of trying out the new projects site, I have set up a VM inside our infrastructure for us to use. the VM is called projects-vm.apache.org and is tied to LDAP much like people.apache.org is these days, thus you will need to have your public ssh key in your LDAP profile in order to gain access. If you do have that set up, and would like to access to the machine (some of you already have access, others don't), just send me a line and I'll open up access for you. The projects VM is set up to serve content via httpd, but only to the TLS-terminator nyx-ssl.apache.org (thus you will get a 403 Denied if you visit the VM's web site directly). To get to the test site, use https://projects-new.apache.org/ . Similar, to try out the (very simple) editing features, use https://projects-new.apache.org/edit/ (requires your LDAP username+password and allows you to edit data for those projects where you are on the PMC). If you try out the editing features, do not that every edit you do will generate an email with the new project data and send it to dev@community.a.o, as a review measure. I hope this will make it easier for people to jump in and help with creating the site :) With regards, Daniel. On 2015-01-14 18:53, Ross Gardler (MS OPEN TECH) wrote: Daniel, There is no assuming just do it :-) You have a number of ComDev PMC members saying +1, and you are a PMC member yourself. Let's have the code where we can start working on it and let's get it to feature parity with projects.apache.org ASAP. I agree with Rich that there is value in this already. This is not to exclude the much broader OfBiz proposal, but it looks to me like this solution is close to being ready to go as a replacement for projects.apache.org and I already see some simple improvements I can make in a coffee break at work :-) Ross -Original Message- From: Daniel Gruno [mailto:humbed...@apache.org] Sent: Wednesday, January 14, 2015 9:43 AM To: dev@community.apache.org Subject: Re: projects.apache.org overhaul proposal On 2015-01-14 18:37, Jacques Le Roux wrote: Just as a note for the sake of truth, OFBiz has Content component http://projects.apache.pw/projects.html?category#content http://ofbiz.apache.org/doap_OFBiz.rdf disagrees ;-) but, assuming this gets accepted into comdev, you needn't worry about doap files any longer, as you will be able to edit it online instead. With regards, Daniel. I very like what I saw, kudos! Jacques Le 14/01/2015 12:48, Daniel Gruno a écrit : Hi folks, I was having a conversation with Rich (Bowen) some weeks ago, and the sentiment was that our projects page ( projects.apache.org http://projects.apache.org ) could use a big overhaul. It's outdated, not very user friendly, doesn't really compile the data into anything useful (mostly just displays raw data) and it's difficult to navigate (no search abilities, no actual overviews). Therefore, I propose that the community development project takes over this project
RE: New ComDev VM
I was thinking of putting the data in a JQuery DataTable, this will make it searchable and sortable. Maybe someone else will beat me to it. Sent from my Windows Phone From: jan imailto:j...@apache.org Sent: 1/15/2015 3:29 AM To: dev@community.apache.orgmailto:dev@community.apache.org Subject: Re: New ComDev VM Hi Very nice site, a little idea, sort the projects on https://projects-new.apache.org/projects.html?language#C, that makes it easier to look at. rgds jan i On 15 January 2015 at 12:14, Daniel Gruno humbed...@apache.org wrote: Just a note/reminder: Whatever you push to svn goes public within 3 seconds, so feel free to use the site for your tests if you like. With regards, Daniel. On 2015-01-15 09:07, Daniel Gruno wrote: Hiya folks, as part of trying out the new projects site, I have set up a VM inside our infrastructure for us to use. the VM is called projects-vm.apache.org and is tied to LDAP much like people.apache.org is these days, thus you will need to have your public ssh key in your LDAP profile in order to gain access. If you do have that set up, and would like to access to the machine (some of you already have access, others don't), just send me a line and I'll open up access for you. The projects VM is set up to serve content via httpd, but only to the TLS-terminator nyx-ssl.apache.org (thus you will get a 403 Denied if you visit the VM's web site directly). To get to the test site, use https://projects-new.apache.org/ . Similar, to try out the (very simple) editing features, use https://projects-new.apache.org/edit/ (requires your LDAP username+password and allows you to edit data for those projects where you are on the PMC). If you try out the editing features, do not that every edit you do will generate an email with the new project data and send it to dev@community.a.o, as a review measure. I hope this will make it easier for people to jump in and help with creating the site :) With regards, Daniel. On 2015-01-14 18:53, Ross Gardler (MS OPEN TECH) wrote: Daniel, There is no assuming just do it :-) You have a number of ComDev PMC members saying +1, and you are a PMC member yourself. Let's have the code where we can start working on it and let's get it to feature parity with projects.apache.org ASAP. I agree with Rich that there is value in this already. This is not to exclude the much broader OfBiz proposal, but it looks to me like this solution is close to being ready to go as a replacement for projects.apache.org and I already see some simple improvements I can make in a coffee break at work :-) Ross -Original Message- From: Daniel Gruno [mailto:humbed...@apache.org] Sent: Wednesday, January 14, 2015 9:43 AM To: dev@community.apache.org Subject: Re: projects.apache.org overhaul proposal On 2015-01-14 18:37, Jacques Le Roux wrote: Just as a note for the sake of truth, OFBiz has Content component http://projects.apache.pw/projects.html?category#content http://ofbiz.apache.org/doap_OFBiz.rdf disagrees ;-) but, assuming this gets accepted into comdev, you needn't worry about doap files any longer, as you will be able to edit it online instead. With regards, Daniel. I very like what I saw, kudos! Jacques Le 14/01/2015 12:48, Daniel Gruno a écrit : Hi folks, I was having a conversation with Rich (Bowen) some weeks ago, and the sentiment was that our projects page ( projects.apache.org http://projects.apache.org ) could use a big overhaul. It's outdated, not very user friendly, doesn't really compile the data into anything useful (mostly just displays raw data) and it's difficult to navigate (no search abilities, no actual overviews). Therefore, I propose that the community development project takes over this project from Infra, which has no interest in continuing/maintaining it, and revamps it with both a new site design and a new LDAP/JSON-based information system which would enable people to edit their project details online without having to upload/change RDF files when something happens. This would also mean that everything could be rendered in the browser instead of relying on daily cron jobs to compile the page, and also allow us to add some inspiring/interesting graphical charts and overviews/timelines. I have been working on a proposal that follows these ideas, which is available for preview at http://projects.apache.pw/ for those interested. Only the first two tabs in the menu currently work (and the extensive search feature), but that is still most of what the old site has and then some. I am pondering on moving some of the front page stuff to the 'Timelines' tab instead, feedback is appreciated on this. So, comments, feedback, questions, anything is most welcome, especially comments on whether you: 1) think comdev should be responsible for the projects directory 2) think the proposal looks good/swell/nifty/whatever. A
RE: New ComDev VM
Site dev is just a convenience list. There is no committee backing it. ComDev is the right place. Sent from my Windows Phone From: Daniel Grunomailto:humbed...@apache.org Sent: 1/15/2015 7:49 AM To: dev@community.apache.orgmailto:dev@community.apache.org Subject: Re: New ComDev VM Hi Louis, Yes, I have discussed with my VP, and he does not have any interest whatsoever in infra maintaining the projects site, which is why I instead turned to comdev as a sponsor. projects.apache.org is just as much about getting new people to participate in our community (by finding projects they can join) as it is about showing what we've got, so it felt only natural to ask the community development project to take over. site-dev may be listed as one option, but it is hardly used anymore, sadly. With regards, Daniel. On 2015-01-15 16:42, Louis Suárez-Potts wrote: Daniel, One thing—Apache’s Infra page lists site-dev@ for overhauls that seem to be like what you are proposing. See site-dev@ The site-dev list was formed to allow for discussion of every aspect of the small number of websites that are centrally managed by the ASF (e.g. /dev/) and for co-ordination of infrastructure needs and publishing methods for all ASF project websites. Participation in these lists is NOT limited to committers, but rather to any committer or interested party invited by a committer (please would the committer send email to site-dev-owner). The list is normally low volume and aims to discsuss all aspects of the websites, from creation tools through to look and feel.” at http://apache.org/dev/infra-mail.html. Doubtless, you’ve already gone over this… louis On 15 Jan 2015, at 03:07, Daniel Gruno humbed...@apache.org wrote: Hiya folks, as part of trying out the new projects site, I have set up a VM inside our infrastructure for us to use. the VM is called projects-vm.apache.org and is tied to LDAP much like people.apache.org is these days, thus you will need to have your public ssh key in your LDAP profile in order to gain access. If you do have that set up, and would like to access to the machine (some of you already have access, others don't), just send me a line and I'll open up access for you. The projects VM is set up to serve content via httpd, but only to the TLS-terminator nyx-ssl.apache.org (thus you will get a 403 Denied if you visit the VM's web site directly). To get to the test site, use https://projects-new.apache.org/ . Similar, to try out the (very simple) editing features, use https://projects-new.apache.org/edit/ (requires your LDAP username+password and allows you to edit data for those projects where you are on the PMC). If you try out the editing features, do not that every edit you do will generate an email with the new project data and send it to dev@community.a.o, as a review measure. I hope this will make it easier for people to jump in and help with creating the site :) With regards, Daniel. On 2015-01-14 18:53, Ross Gardler (MS OPEN TECH) wrote: Daniel, There is no assuming just do it :-) You have a number of ComDev PMC members saying +1, and you are a PMC member yourself. Let's have the code where we can start working on it and let's get it to feature parity with projects.apache.org ASAP. I agree with Rich that there is value in this already. This is not to exclude the much broader OfBiz proposal, but it looks to me like this solution is close to being ready to go as a replacement for projects.apache.org and I already see some simple improvements I can make in a coffee break at work :-) Ross -Original Message- From: Daniel Gruno [mailto:humbed...@apache.org] Sent: Wednesday, January 14, 2015 9:43 AM To: dev@community.apache.org Subject: Re: projects.apache.org overhaul proposal On 2015-01-14 18:37, Jacques Le Roux wrote: Just as a note for the sake of truth, OFBiz has Content component http://projects.apache.pw/projects.html?category#content http://ofbiz.apache.org/doap_OFBiz.rdf disagrees ;-) but, assuming this gets accepted into comdev, you needn't worry about doap files any longer, as you will be able to edit it online instead. With regards, Daniel. I very like what I saw, kudos! Jacques Le 14/01/2015 12:48, Daniel Gruno a écrit : Hi folks, I was having a conversation with Rich (Bowen) some weeks ago, and the sentiment was that our projects page ( projects.apache.org http://projects.apache.org ) could use a big overhaul. It's outdated, not very user friendly, doesn't really compile the data into anything useful (mostly just displays raw data) and it's difficult to navigate (no search abilities, no actual overviews). Therefore, I propose that the community development project takes over this project from Infra, which has no interest in continuing/maintaining it, and revamps it with both a new site design and a new LDAP/JSON-based information
Re: projects.apache.org overhaul proposal
Maybe we should considering changing the subject as this seems bigger than just an overhaul of one of the front ends of the ASF? Yes, it all has to do with the ROI (the benefits at large vs the costs) for the ASF. And such need to be determined regarding the future, not the present day or the past. The time that the ASF was a one project endeavour has past, and the importance of the foundation in the umfeld is growing day by day. People are turning more and more to the ASF with requests to host their open source projects. This all leads to more demand on solutions and services provided by INFRA. But also on our offices. More people/projects involved means more work on the heads in Brand Management, Legal, Communications, Secretary, etc. And these offices also use solutions/services of INFRA and/or third parties. Thus, any decision of this kind is should be taken must be weighed with the future - the 5 year view - of the ASF and its offices in mind. So, what are the future demands on our offices? And how does that impact the solutions and services rendered by INFRA, and/or third parties? To what budget requirements will the availability of those (future) solutions and services lead, with the use of current setup? Can costs be saved by rethinking that setup and replacing it by something else, and do the projected savings outweigh the projected cost of change? Such questions must be considered regularly, because there is no guarantee that current influx of funds will be the same or even increase equally with the increase of needs/wants and pleasures of offices and projects and inherently the cost associated to all that. And then we can make the proper decisions. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Thu, Jan 15, 2015 at 3:35 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Thu, Jan 15, 2015 at 3:24 PM, Rich Bowen rbo...@rcbowen.com wrote: ...*historically*, when this kind of thing has happened (project implements, thing becomes critical), gradually it becomes the responsibility of Infra, not of the project, to do ongoing maintenance Yes, this is why I'm reluctant to encourage any initiative that requires our infrastructure team to support new tools. And I suspect infra shares that reluctance ;-) That being said, it's always a question of benefits vs. costs - but if a simple thing using technologies that every web developer is supposed to know works the choice is a no-brainer for me. -Bertrand
Project base data change for project 'ant-ivy'
Hello,
The following new base data was set for ant-ivy by antoine:
{
category: build-management,
GitRepository: https://git-wip-us.apache.org/repos/asf/ant-ivy.git;,
bug-database: https://issues.apache.org/jira/browse/IVY;,
description: Apache Ivy is a very powerful dependency manager oriented
toward Java dependency management, even though it could be used to manage
dependencies of any kind.,
mailing-list: http://ant.apache.org/ivy/mailing-lists.html;,
programming-language: Java,
file: ant-ivy,
pmc: ant,
shortdesc: Apache Ivy is a very powerful dependency manager oriented
toward Java dependency management, even though it could be used to manage
dependencies of any kind.,
download-page: http://ant.apache.org/ivy/download.cgi;,
homepage: http://ant.apache.org/ivy/;,
SVNRepository: ,
name: Apache Ivy
}
With regards,
projects.apache.org
Re: A maturity model for Apache projects
On 1/15/15 3:39 AM, Bertrand Delacretaz wrote: On Wed, Jan 14, 2015 at 8:29 PM, Phil Steitz phil.ste...@gmail.com wrote: ...Missing Q or C thing: The project is not dead. Bugs do not sit forever with no response. Questions get answered on user lists... Thanks - I have reorganized Antoine's suggestions about this to be QU50 The project strives to process documented bug reports in a timely manner. CO70 The project strives to answer user questions in a timely manner. Yes, it actually is Q and C. Thanks! Phil -Bertrand .
Project base data change for project 'ant-apacheeasyant'
Hello,
The following new base data was set for ant-apacheeasyant by antoine:
{
category: build-management,
GitRepository:
https://git-wip-us.apache.org/repos/asf/ant-easyant-tasks.git;,
bug-database: http://issues.apache.org/jira/browse/EASYANT;,
description: Apache EasyAnt is a toolbox focusing on easing project
build processes.\r\nIt's based on Apache Ant and Apache Ivy, and allows for
maximum flexibily, improved integration in existing build systems and provides
conventions and guidelines.\r\n,
mailing-list: http://ant.apache.org/easyant/Mailinglist.html;,
programming-language: java,
file: ant-apacheeasyant,
pmc: ant,
shortdesc: Apache EasyAnt is a toolbox focusing on easing project build
processes.,
download-page: http://ant.apache.org/easyant/download.cgi;,
homepage: http://ant.apache.org/easyant/;,
SVNRepository: ,
name: Apache EasyAnt
}
With regards,
projects.apache.org
Re: A maturity model for Apache projects
On 01/15/2015 02:47 AM, Bertrand Delacretaz wrote: On Wed, Jan 14, 2015 at 8:29 PM, Phil Steitz phil.ste...@gmail.com wrote: ...QO30 - do we really want individual projects to have / advertise their own ways to take security reports?... We do not want that, agreed, but as I want the model to be usable by non-Apache projects as well I'm trying to focus on the core principles in the model, and leave the Apache specifics to footnotes. I have added a footnote to QU30 that points to http://www.apache.org/security/ as the default, does that work for you? Sling for example has http://sling.apache.org/project-information/security.html which is a bit more Sling-specific and also points to http://www.apache.org/security/ -Bertrand LC20 needs a lot more expansion. There are so many open source licenses. Depending on the complexity of the given ASF project, it's a challenge to evaluate LC20. -- - MzK There's a bit of magic in everything, and some loss to even things out. -- Lou Reed
Project base data change for project 'ant'
Hello,
The following new base data was set for ant by antoine:
{
category: build-management,
GitRepository: https://git-wip-us.apache.org/repos/asf/ant.git;,
bug-database:
http://issues.apache.org/bugzilla/buglist.cgi?product=Ant;,
description: Apache Ant is a Java-based build tool.,
mailing-list: http://ant.apache.org/mail.html;,
programming-language: Java,
file: ant,
pmc: ant,
shortdesc: Java-based build tool,
download-page: http://ant.apache.org/bindownload.cgi;,
homepage: http://ant.apache.org;,
SVNRepository: ,
name: Apache Ant
}
With regards,
projects.apache.org
Project base data change for project 'ant-ivy'
Hello,
The following new base data was set for ant-ivy by antoine:
{
category: build-management,
GitRepository: ttps://git-wip-us.apache.org/repos/asf/ant-ivy.git,
bug-database: https://issues.apache.org/jira/browse/IVY;,
description: Apache Ivy is a very powerful dependency manager oriented
toward Java dependency management, even though it could be used to manage
dependencies of any kind.,
mailing-list: http://ant.apache.org/ivy/mailing-lists.html;,
programming-language: Java,
file: ant-ivy,
pmc: ant,
shortdesc: Apache Ivy is a very powerful dependency manager oriented
toward Java dependency management, even though it could be used to manage
dependencies of any kind.,
download-page: http://ant.apache.org/ivy/download.cgi;,
homepage: http://ant.apache.org/ivy/;,
SVNRepository: ,
name: Apache Ivy
}
With regards,
projects.apache.org
Re: A maturity model for Apache projects
On 1/15/15 3:47 AM, Bertrand Delacretaz wrote: On Wed, Jan 14, 2015 at 8:29 PM, Phil Steitz phil.ste...@gmail.com wrote: ...QO30 - do we really want individual projects to have / advertise their own ways to take security reports?... We do not want that, agreed, but as I want the model to be usable by non-Apache projects as well I'm trying to focus on the core principles in the model, and leave the Apache specifics to footnotes. Oh, sorry I missed that. I have added a footnote to QU30 that points to http://www.apache.org/security/ as the default, does that work for you? Sling for example has http://sling.apache.org/project-information/security.html which is a bit more Sling-specific and also points to http://www.apache.org/security/ Yes that is fine. Thanks! Phil -Bertrand
Re: A maturity model for Apache projects
Hi, Some (very) minor things. CD10 - distributed at no charge to the public. while this may be true at Apache it doesn't have to be the case. 3rd parties wanting to this model may find this a stumbling block. CD40 - Perhaps a footnote? for code donated to Apache the history before Apache may or may not exists. LC30 - Add compatible with the Apache License just to make it clear that some OS licences are not compatible with Apache? RE30 - Perhaps remove and/or as we would want both right? OCXX - Do we need add something about merit once given doesn't expire? CO50 Perhaps change granted more rights to granted more responsibility? INXX - Add something about multiple roles/multiple hats? Thanks, Justin
Project base data change for project 'ant-props-ant-library'
Hello,
The following new base data was set for ant-props-ant-library by antoine:
{
category: build-management,
GitRepository:
https://git-wip-us.apache.org/repos/asf/ant-antlibs-props.git;,
bug-database:
http://issues.apache.org/bugzilla/buglist.cgi?product=Ant;,
description: The Apache Props Antlib is a library of supplementary
handlers for Apache Ant properties resolution.\r\n\r\nThe types provided are
instances of org.apache.tools.ant.PropertyHelper.Delegate and can be invoked
using the propertyhelper task provided in Ant 1.8.0.,
mailing-list: http://ant.apache.org/mail.html;,
programming-language: Java,
file: ant-props-ant-library,
pmc: ant,
shortdesc: The Apache Props Antlib is a library of supplementary
handlers for Apache Ant properties resolution.,
download-page: http://ant.apache.org/antlibs/bindownload.cgi;,
homepage: http://ant.apache.org/antlibs/props/;,
SVNRepository: ,
name: Apache Props Ant Library
}
With regards,
projects.apache.org
Re: New ComDev VM
Hmmm, maybe someone can look at https://jquery-datatables-row-grouping.googlecode.com/svn/trunk/collapsibleGroups.html and work out something nifty? On 2015-01-15 20:24, Daniel Gruno wrote: On 2015-01-15 17:00, Ross Gardler (MS OPEN TECH) wrote: I was thinking of putting the data in a JQuery DataTable, this will make it searchable and sortable. Not a terrible idea you have there :) I have committed a test for this, available at https://projects-new.apache.org/datatables.html now. However, it does leave a few problems, specifically on how to sort by programming language and categories, which I can't quite work out - ideas/suggestions are most welcome!! With regards, Daniel. Maybe someone else will beat me to it. Sent from my Windows Phone From: jan imailto:j...@apache.org Sent: 1/15/2015 3:29 AM To: dev@community.apache.orgmailto:dev@community.apache.org Subject: Re: New ComDev VM Hi Very nice site, a little idea, sort the projects on https://projects-new.apache.org/projects.html?language#C, that makes it easier to look at. rgds jan i On 15 January 2015 at 12:14, Daniel Gruno humbed...@apache.org wrote: Just a note/reminder: Whatever you push to svn goes public within 3 seconds, so feel free to use the site for your tests if you like. With regards, Daniel. On 2015-01-15 09:07, Daniel Gruno wrote: Hiya folks, as part of trying out the new projects site, I have set up a VM inside our infrastructure for us to use. the VM is called projects-vm.apache.org and is tied to LDAP much like people.apache.org is these days, thus you will need to have your public ssh key in your LDAP profile in order to gain access. If you do have that set up, and would like to access to the machine (some of you already have access, others don't), just send me a line and I'll open up access for you. The projects VM is set up to serve content via httpd, but only to the TLS-terminator nyx-ssl.apache.org (thus you will get a 403 Denied if you visit the VM's web site directly). To get to the test site, use https://projects-new.apache.org/ . Similar, to try out the (very simple) editing features, use https://projects-new.apache.org/edit/ (requires your LDAP username+password and allows you to edit data for those projects where you are on the PMC). If you try out the editing features, do not that every edit you do will generate an email with the new project data and send it to dev@community.a.o, as a review measure. I hope this will make it easier for people to jump in and help with creating the site :) With regards, Daniel. On 2015-01-14 18:53, Ross Gardler (MS OPEN TECH) wrote: Daniel, There is no assuming just do it :-) You have a number of ComDev PMC members saying +1, and you are a PMC member yourself. Let's have the code where we can start working on it and let's get it to feature parity with projects.apache.org ASAP. I agree with Rich that there is value in this already. This is not to exclude the much broader OfBiz proposal, but it looks to me like this solution is close to being ready to go as a replacement for projects.apache.org and I already see some simple improvements I can make in a coffee break at work :-) Ross -Original Message- From: Daniel Gruno [mailto:humbed...@apache.org] Sent: Wednesday, January 14, 2015 9:43 AM To: dev@community.apache.org Subject: Re: projects.apache.org overhaul proposal On 2015-01-14 18:37, Jacques Le Roux wrote: Just as a note for the sake of truth, OFBiz has Content component http://projects.apache.pw/projects.html?category#content http://ofbiz.apache.org/doap_OFBiz.rdf disagrees ;-) but, assuming this gets accepted into comdev, you needn't worry about doap files any longer, as you will be able to edit it online instead. With regards, Daniel. I very like what I saw, kudos! Jacques Le 14/01/2015 12:48, Daniel Gruno a écrit : Hi folks, I was having a conversation with Rich (Bowen) some weeks ago, and the sentiment was that our projects page ( projects.apache.org http://projects.apache.org ) could use a big overhaul. It's outdated, not very user friendly, doesn't really compile the data into anything useful (mostly just displays raw data) and it's difficult to navigate (no search abilities, no actual overviews). Therefore, I propose that the community development project takes over this project from Infra, which has no interest in continuing/maintaining it, and revamps it with both a new site design and a new LDAP/JSON-based information system which would enable people to edit their project details online without having to upload/change RDF files when something happens. This would also mean that everything could be rendered in the browser instead of relying on daily cron jobs to compile the page, and also allow us to add some inspiring/interesting graphical charts and overviews/timelines. I have been working on a proposal that follows these ideas, which is available for
New ComDev VM (was: Re: projects.apache.org overhaul proposal)
Hiya folks, as part of trying out the new projects site, I have set up a VM inside our infrastructure for us to use. the VM is called projects-vm.apache.org and is tied to LDAP much like people.apache.org is these days, thus you will need to have your public ssh key in your LDAP profile in order to gain access. If you do have that set up, and would like to access to the machine (some of you already have access, others don't), just send me a line and I'll open up access for you. The projects VM is set up to serve content via httpd, but only to the TLS-terminator nyx-ssl.apache.org (thus you will get a 403 Denied if you visit the VM's web site directly). To get to the test site, use https://projects-new.apache.org/ . Similar, to try out the (very simple) editing features, use https://projects-new.apache.org/edit/ (requires your LDAP username+password and allows you to edit data for those projects where you are on the PMC). If you try out the editing features, do not that every edit you do will generate an email with the new project data and send it to dev@community.a.o, as a review measure. I hope this will make it easier for people to jump in and help with creating the site :) With regards, Daniel. On 2015-01-14 18:53, Ross Gardler (MS OPEN TECH) wrote: Daniel, There is no assuming just do it :-) You have a number of ComDev PMC members saying +1, and you are a PMC member yourself. Let's have the code where we can start working on it and let's get it to feature parity with projects.apache.org ASAP. I agree with Rich that there is value in this already. This is not to exclude the much broader OfBiz proposal, but it looks to me like this solution is close to being ready to go as a replacement for projects.apache.org and I already see some simple improvements I can make in a coffee break at work :-) Ross -Original Message- From: Daniel Gruno [mailto:humbed...@apache.org] Sent: Wednesday, January 14, 2015 9:43 AM To: dev@community.apache.org Subject: Re: projects.apache.org overhaul proposal On 2015-01-14 18:37, Jacques Le Roux wrote: Just as a note for the sake of truth, OFBiz has Content component http://projects.apache.pw/projects.html?category#content http://ofbiz.apache.org/doap_OFBiz.rdf disagrees ;-) but, assuming this gets accepted into comdev, you needn't worry about doap files any longer, as you will be able to edit it online instead. With regards, Daniel. I very like what I saw, kudos! Jacques Le 14/01/2015 12:48, Daniel Gruno a écrit : Hi folks, I was having a conversation with Rich (Bowen) some weeks ago, and the sentiment was that our projects page ( projects.apache.org http://projects.apache.org ) could use a big overhaul. It's outdated, not very user friendly, doesn't really compile the data into anything useful (mostly just displays raw data) and it's difficult to navigate (no search abilities, no actual overviews). Therefore, I propose that the community development project takes over this project from Infra, which has no interest in continuing/maintaining it, and revamps it with both a new site design and a new LDAP/JSON-based information system which would enable people to edit their project details online without having to upload/change RDF files when something happens. This would also mean that everything could be rendered in the browser instead of relying on daily cron jobs to compile the page, and also allow us to add some inspiring/interesting graphical charts and overviews/timelines. I have been working on a proposal that follows these ideas, which is available for preview at http://projects.apache.pw/ for those interested. Only the first two tabs in the menu currently work (and the extensive search feature), but that is still most of what the old site has and then some. I am pondering on moving some of the front page stuff to the 'Timelines' tab instead, feedback is appreciated on this. So, comments, feedback, questions, anything is most welcome, especially comments on whether you: 1) think comdev should be responsible for the projects directory 2) think the proposal looks good/swell/nifty/whatever. A few notes on the search feature: - You can search for virtually anything within a project, types, languages, descriptions, bug-trackers etc - Try typing your committer ID or Apache ID into the box, and it will show all projects you are a part of If there is consensus for moving this into comdev framework and collaborating on this, I will commit the proposal to a sub-folder in the comdev svn repository and ask infra for a VM where we can set this up. With regards, Daniel.
Re: projects.apache.org overhaul proposal
See inline. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Thu, Jan 15, 2015 at 12:42 AM, Alex Harui aha...@adobe.com wrote: I was probing the notion that it might be to the advantage of the OFBiz community to just volunteer something instead of being asked. To the best of my knowledge, the persons in the OFBiz community are volunteering. Maybe the folks on this list know the other Apache projects better than I do, but I wouldn’t even know what to ask for. Asking the first thing that comes to your mind will get you answers. Might not be the right ones, though. ;-) The project I’m involved in, Apache Flex, might also have the technology to improve a lot of things at the ASF. Once the code I’m working on gets to a certain point, if I need more customers and want to test out the “eat your own dog food” principle, I may start offering replacements to some of the web experiences we have at the ASF. I tend to agree. But you have the operators wrong. You are talking about yourself testing the 'eat your own dogfood' principle. That is different to 'having someone else eat/test your dogfood'. That means you have to solicit the willingness of others. And when there is no willingness offered and you keep trying to push it down the throat of the other, the result you get is not something you want. In the case of the works of an ASF project for the ASF (the other), you'll need - beside the willingness of the other - assistance/support from the third party (INFRA, or someone else) regarding the provisioning of hardware, etc . Unless you have unlimited resources yourself in that area. Here in The Netherlands we have this saying 'The road to hell is paved with good intentions'. I surmise, we can all recant the stories of the good intentions abandoned and the effort these required to clean up the left overs. How that eats into the areas with constraints (money, time, etc). So it is better to investigate the potential success rate before endorsing the resources you have control over. If I can run a live PoC, it will make it much easier to sell and focus the conversation and maybe even garner more contributors. And even if the ASF rejects it, I will have learned something in the process. For sure, I will meter the effort I put into it accordingly so it isn’t a huge deal if it doesn’t get adopted. Apart from the exchange of theoretical deliberations in this thread, there are connections established between offices of the ASF and (a) third party(ies) providing OFBiz services regarding exploration whether OFBiz can be utilised with respect to some of the processes of those offices. And OFBiz volunteers have offered their assistance.
Re: A maturity model for Apache projects
On Wed, Jan 14, 2015 at 8:29 PM, Phil Steitz phil.ste...@gmail.com wrote: ...Missing Q or C thing: The project is not dead. Bugs do not sit forever with no response. Questions get answered on user lists... Thanks - I have reorganized Antoine's suggestions about this to be QU50 The project strives to process documented bug reports in a timely manner. CO70 The project strives to answer user questions in a timely manner. -Bertrand
Re: Some maturity model comments
Oh, duh, it's the maturity model. Well, in context I found it confusing. -- Lefty On Thu, Jan 15, 2015 at 2:22 AM, Lefty Leverenz leftylever...@gmail.com wrote: In CO10, what does according to this model mean? *CO10* The project has a well-known homepage that points to all the information required to operate according to this model. If it means the Apache model, do most project home pages currently point to information about Apache operations? -- Lefty Leverenz On Wed, Jan 14, 2015 at 8:51 AM, Benson Margulies bimargul...@gmail.com wrote: On Wed, Jan 14, 2015 at 11:46 AM, Rob Vesse rve...@dotnetrdf.org wrote: LC50: I think the LC50 is actually correct but could perhaps be phrased better My understanding was that the ASF owns the copyright for the collective work of the project I.e. releases. As Benson notes contributors retain copyright on their contributions but grant the ASF a perpetual license to their contributions I think that the wording should be expanded to mention both aspects. QU30: Agreed, some projects may not do anything that is attack prone or are likely only to be run such that any security is provided by whatever runtime they use and the security of that runtime is well beyond the purview of the project. Consensus building: Should there be a CS60 about the rare need for private discussions CS60: In rare situations (typically security, brand enforcement, legal and personnel discussions) the project may need to first reach consensus in private in which case the project should use their official private communications channel such that these rare private discussions are privately archived. The outcomes of such consensus should where possible be discussed in public as soon as it is appropriate to do so. That isn't great wording but hopefully you get what I am trying to convey - projects should rarely discuss in private and any discussions should become public as soon as it is possible to do so Rob On 14/01/2015 15:33, Benson Margulies bimargul...@gmail.com wrote: CD40: perhaps change 'previous version' to 'released version' CD50: the committer is not necessarily the author; someone might read this and not understand what it implies for committers committing contributions via all of the channels allowed for by the AL. One patch would be 'immediate provenance', another would be some more lengthier language about the process. LC20: do we need to explain what we mean by 'dependencies'? This has been a point of friction. Expand or footnote to the distinctions between essential and optional? LC50: the footnote seems wrong; the ASF does not own copyright, rather, the author retains, and grants the license. RE40: do you want to add an explicit statement that legal responsibility falls upon the head of the person who happened to run the build? QU20: Maybe we need to expands on 'secure'? Maybe this is too strong? What's wrong with building a product that is explicitly not intended for use attack-prone environments. QU40: Not all communities might agree. Some communities might see themselves as building fast-moving products. Some communities may lack the level of volunteer effort required to satisfy this. Does this make them immature, or just a group of volunteers with different priorities? IN10: I fear that a more detailed definition of independence is going to be called for here to avoid controversy.
Re: Project base data change for project 'bloodhound'
On Thu, Jan 15, 2015 at 2:10 AM, Daniel Gruno humbed...@apache.org wrote: You can virtually put anything you like as a category, the system will adapt to whatever you enter. If you want a new category called bugtracking, just append it to the categories field; content, bugtracking and it will (eventually) show up as a new category when your browse projects :) With regards, Daniel. Thanks, I was hesitant to break out of what appeared to be a concise list of categories that may have been carefully chosen. I'll discuss the best category with the other committers.
Re: New ComDev VM
Just a note/reminder: Whatever you push to svn goes public within 3 seconds, so feel free to use the site for your tests if you like. With regards, Daniel. On 2015-01-15 09:07, Daniel Gruno wrote: Hiya folks, as part of trying out the new projects site, I have set up a VM inside our infrastructure for us to use. the VM is called projects-vm.apache.org and is tied to LDAP much like people.apache.org is these days, thus you will need to have your public ssh key in your LDAP profile in order to gain access. If you do have that set up, and would like to access to the machine (some of you already have access, others don't), just send me a line and I'll open up access for you. The projects VM is set up to serve content via httpd, but only to the TLS-terminator nyx-ssl.apache.org (thus you will get a 403 Denied if you visit the VM's web site directly). To get to the test site, use https://projects-new.apache.org/ . Similar, to try out the (very simple) editing features, use https://projects-new.apache.org/edit/ (requires your LDAP username+password and allows you to edit data for those projects where you are on the PMC). If you try out the editing features, do not that every edit you do will generate an email with the new project data and send it to dev@community.a.o, as a review measure. I hope this will make it easier for people to jump in and help with creating the site :) With regards, Daniel. On 2015-01-14 18:53, Ross Gardler (MS OPEN TECH) wrote: Daniel, There is no assuming just do it :-) You have a number of ComDev PMC members saying +1, and you are a PMC member yourself. Let's have the code where we can start working on it and let's get it to feature parity with projects.apache.org ASAP. I agree with Rich that there is value in this already. This is not to exclude the much broader OfBiz proposal, but it looks to me like this solution is close to being ready to go as a replacement for projects.apache.org and I already see some simple improvements I can make in a coffee break at work :-) Ross -Original Message- From: Daniel Gruno [mailto:humbed...@apache.org] Sent: Wednesday, January 14, 2015 9:43 AM To: dev@community.apache.org Subject: Re: projects.apache.org overhaul proposal On 2015-01-14 18:37, Jacques Le Roux wrote: Just as a note for the sake of truth, OFBiz has Content component http://projects.apache.pw/projects.html?category#content http://ofbiz.apache.org/doap_OFBiz.rdf disagrees ;-) but, assuming this gets accepted into comdev, you needn't worry about doap files any longer, as you will be able to edit it online instead. With regards, Daniel. I very like what I saw, kudos! Jacques Le 14/01/2015 12:48, Daniel Gruno a écrit : Hi folks, I was having a conversation with Rich (Bowen) some weeks ago, and the sentiment was that our projects page ( projects.apache.org http://projects.apache.org ) could use a big overhaul. It's outdated, not very user friendly, doesn't really compile the data into anything useful (mostly just displays raw data) and it's difficult to navigate (no search abilities, no actual overviews). Therefore, I propose that the community development project takes over this project from Infra, which has no interest in continuing/maintaining it, and revamps it with both a new site design and a new LDAP/JSON-based information system which would enable people to edit their project details online without having to upload/change RDF files when something happens. This would also mean that everything could be rendered in the browser instead of relying on daily cron jobs to compile the page, and also allow us to add some inspiring/interesting graphical charts and overviews/timelines. I have been working on a proposal that follows these ideas, which is available for preview at http://projects.apache.pw/ for those interested. Only the first two tabs in the menu currently work (and the extensive search feature), but that is still most of what the old site has and then some. I am pondering on moving some of the front page stuff to the 'Timelines' tab instead, feedback is appreciated on this. So, comments, feedback, questions, anything is most welcome, especially comments on whether you: 1) think comdev should be responsible for the projects directory 2) think the proposal looks good/swell/nifty/whatever. A few notes on the search feature: - You can search for virtually anything within a project, types, languages, descriptions, bug-trackers etc - Try typing your committer ID or Apache ID into the box, and it will show all projects you are a part of If there is consensus for moving this into comdev framework and collaborating on this, I will commit the proposal to a sub-folder in the comdev svn repository and ask infra for a VM where we can set this up. With regards, Daniel.
Project base data change for project 'corinthia'
Hello,
The following new base data was set for corinthia by jani:
{
category: library,
GitRepository:
https://git-wip-us.apache.org/repos/asf/incubator-corinthia.git;,
bug-database: https://issues.apache.org/jira/browse/COR;,
description: Corinthia is a toolkit/application for converting between
and editing common office file formats, with an initial focus on word
processing. It is designed to cater for multiple classes of platforms -
desktop, web, and mobile - and relies heavily on web technologies such as HTML,
CSS, and JavaScript for representing and manipulating documents. The toolkit is
small, portable, and flexible, with minimal dependencies. The target audience
is developers wishing to include office viewing, conversion, and editing
functionality into their applications.,
mailing-list: d...@corinthia.incubator.apache.org,
programming-language: C,
file: corinthia,
pmc: incubator,
shortdesc: Corinthia edits/converts between office file formats,
download-page: ,
homepage: http://corinthia.incubator.apache.org/;,
SVNRepository: ,
name: Apache Corinthia (Incubating)
}
With regards,
projects.apache.org
Re: A maturity model for Apache projects
On Wed, Jan 14, 2015 at 8:29 PM, Phil Steitz phil.ste...@gmail.com wrote: ...QO30 - do we really want individual projects to have / advertise their own ways to take security reports?... We do not want that, agreed, but as I want the model to be usable by non-Apache projects as well I'm trying to focus on the core principles in the model, and leave the Apache specifics to footnotes. I have added a footnote to QU30 that points to http://www.apache.org/security/ as the default, does that work for you? Sling for example has http://sling.apache.org/project-information/security.html which is a bit more Sling-specific and also points to http://www.apache.org/security/ -Bertrand
Project base data change for project 'corinthia'
Hello,
The following new base data was set for corinthia by humbedooh:
{
category: library,
GitRepository:
https://git-wip-us.apache.org/repos/asf/incubator-corinthia.git;,
bug-database: ,
description: Corinthia is a toolkit/application for converting between
and editing common office file formats, with an initial focus on word
processing. It is designed to cater for multiple classes of platforms -
desktop, web, and mobile - and relies heavily on web technologies such as HTML,
CSS, and JavaScript for representing and manipulating documents. The toolkit is
small, portable, and flexible, with minimal dependencies. The target audience
is developers wishing to include office viewing, conversion, and editing
functionality into their applications.,
mailing-list: ,
programming-language: C,
file: corinthia,
pmc: incubator,
shortdesc: ,
download-page: ,
homepage: http://corinthia.incubator.apache.org/;,
SVNRepository: ,
name: Apache Corinthia (Incubating)
}
With regards,
projects.apache.org
Re: Some maturity model comments
Hi, Thanks for the comments in this thread, I (think I) have incorporated them in revision 14 of https://wiki.apache.org/incubator/ApacheProjectMaturityModel On Wed, Jan 14, 2015 at 4:33 PM, Benson Margulies bimargul...@gmail.com wrote: CD40: perhaps change 'previous version' to 'released version' done CD50: the committer is not necessarily the author;... Added something about thirdy-party contributions LC20: do we need to explain what we mean by 'dependencies'?... Left that as a TODO for now, it might be good but I don't know what to write :-/ LC50: the footnote seems wrong; the ASF does not own copyright, rather, the author retains, and grants the license. Fixed as per Rob's suggestion ...RE40: do you want to add an explicit statement that legal responsibility falls upon the head of the person who happened to run the build?... Chickened out on that one for now - do we have that info somewhere else that I could point to? QU20: Maybe we need to expands on 'secure'?... Added a footnote QU40: Not all communities might agree Let's discuss in a separate thread ...IN10: I fear that a more detailed definition of independence is going to be called for here to avoid controversy Added a footnote. Thanks for the comments, do those changes work for you guys? -Bertrand
Re: Some maturity model comments
On Wed, Jan 14, 2015 at 5:46 PM, Rob Vesse rve...@dotnetrdf.org wrote: ... I think the LC50 is actually correct but could perhaps be phrased better... I've used your suggestion, thanks! QU30: Agreed, some projects may not do anything that is attack prone... Added a footnote ...Should there be a CS60 about the rare need for private discussions... I have added a mention of that in CS50 with a footnote, does that work for you? -Bertrand
Re: Some maturity model comments
On Thu, Jan 15, 2015 at 12:05 PM, Lefty Leverenz leftylever...@gmail.com wrote: Oh, duh, it's the maturity model. Well, in context I found it confusing Indeed - I have changed CO10 to read ...according to this maturity model. Thanks! -Bertrand
Project base data change for project 'bloodhound'
Hello,
The following new base data was set for bloodhound by rjollos:
{
category: content,
GitRepository: ,
bug-database: http://issues.apache.org/bloodhound/;,
description: Apache Bloodhound is an open source collaboration tool to
track the progress of and help distribute tasks within a project. With a
particular focus on software development, it includes integration with popular
source control software including Apache Subversion, Git and Mercurial.,
mailing-list:
https://issues.apache.org/bloodhound/wiki/BloodhoundContactInfo;,
programming-language: Python,
file: bloodhound,
pmc: bloodhound,
shortdesc: Apache Bloodhound is a software development collaboration
tool, including issue tracking, wiki and repository browsing,
download-page: http://bloodhound.apache.org/;,
homepage: http://bloodhound.apache.org/;,
SVNRepository: http://svn.apache.org/repos/asf/bloodhound/trunk;,
name: Apache Bloodhound
}
With regards,
projects.apache.org
Project base data change for project 'httpd'
Hello,
The following new base data was set for httpd by humbedooh:
{
category: network-server, http, httpd-module,
GitRepository: ,
bug-database: http://httpd.apache.org/bug_report.html;,
description: The Apache HTTP Server is an open-source HTTP server for
modern operating systems including UNIX, Microsoft Windows, Mac OS/X and
Netware.\r\n\r\nThe goal of this project is to provide a secure, efficient and
extensible server that provides HTTP services observing the current HTTP
standards. Apache has been the most popular web server on the Internet since
April of 1996.\r\n,
mailing-list: http://httpd.apache.org/lists.html;,
programming-language: C,
file: httpd,
pmc: httpd,
shortdesc: The Apache HTTP Server application, 'httpd'.,
download-page: http://httpd.apache.org/download.cgi;,
homepage: http://httpd.apache.org/;,
SVNRepository: http://svn.apache.org/repos/asf/httpd/httpd/;,
name: Apache HTTP Server
}
With regards,
projects.apache.org
Re: Project base data change for project 'bloodhound'
2015-01-15 9:19 GMT+01:00 no-re...@projects.apache.org:
Hello,
The following new base data was set for bloodhound by rjollos:
{
category: content,
GitRepository: ,
bug-database: http://issues.apache.org/bloodhound/;,
description: Apache Bloodhound is an open source collaboration tool
to track the progress of and help distribute tasks within a project. With a
particular focus on software development, it includes integration with
popular source control software including Apache Subversion, Git and
Mercurial.,
mailing-list:
https://issues.apache.org/bloodhound/wiki/BloodhoundContactInfo;,
programming-language: Python,
file: bloodhound,
pmc: bloodhound,
shortdesc: Apache Bloodhound is a software development
collaboration tool, including issue tracking, wiki and repository browsing,
download-page: http://bloodhound.apache.org/;,
homepage: http://bloodhound.apache.org/;,
SVNRepository: http://svn.apache.org/repos/asf/bloodhound/trunk;,
Shouldn't this be http://svn.apache.org/repos/asf/bloodhound/ ?
Benedikt
name: Apache Bloodhound
}
With regards,
projects.apache.org
--
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter
Re: Project base data change for project 'bloodhound'
You can virtually put anything you like as a category, the system will
adapt to whatever you enter.
If you want a new category called bugtracking, just append it to the
categories field; content, bugtracking and it will (eventually) show
up as a new category when your browse projects :)
With regards,
Daniel.
On 2015-01-15 11:04, Ryan Ollos wrote:
On Thu, Jan 15, 2015 at 1:57 AM, Benedikt Ritter brit...@apache.org wrote:
2015-01-15 9:19 GMT+01:00 no-re...@projects.apache.org:
Hello,
The following new base data was set for bloodhound by rjollos:
{
category: content,
GitRepository: ,
bug-database: http://issues.apache.org/bloodhound/;,
description: Apache Bloodhound is an open source collaboration
tool
to track the progress of and help distribute tasks within a project.
With a
particular focus on software development, it includes integration with
popular source control software including Apache Subversion, Git and
Mercurial.,
mailing-list:
https://issues.apache.org/bloodhound/wiki/BloodhoundContactInfo;,
programming-language: Python,
file: bloodhound,
pmc: bloodhound,
shortdesc: Apache Bloodhound is a software development
collaboration tool, including issue tracking, wiki and repository
browsing,
download-page: http://bloodhound.apache.org/;,
homepage: http://bloodhound.apache.org/;,
SVNRepository: http://svn.apache.org/repos/asf/bloodhound/trunk;,
Shouldn't this be http://svn.apache.org/repos/asf/bloodhound/ ?
Benedikt
I think you are probably right about that, thanks for noticing.
One other thing, the category was build-management. That didn't seem
quite right to me, but given the presence of subversion in that category
maybe it should be interpreted more broadly to include
configuration-management tools. Bloodhound is a project management tool
with an issue tracker as a primary component. We are very similar to Apache
Allura, which is in the content category. I assumed Allura was better
categorized when making the change.
- Ryan
Re: Some maturity model comments
On 15/01/2015 11:33, Bertrand Delacretaz bdelacre...@apache.org wrote: On Wed, Jan 14, 2015 at 5:46 PM, Rob Vesse rve...@dotnetrdf.org wrote: ... I think the LC50 is actually correct but could perhaps be phrased better... I've used your suggestion, thanks! Great QU30: Agreed, some projects may not do anything that is attack prone... Added a footnote ...Should there be a CS60 about the rare need for private discussions... I have added a mention of that in CS50 with a footnote, does that work for you? Yes I think that is much nicer wording and I agree that it best belongs in a footnote Rob -Bertrand
Re: projects.apache.org overhaul proposal
On 01/14/2015 06:42 PM, Alex Harui wrote: I was probing the notion that it might be to the advantage of the OFBiz community to just volunteer something instead of being asked. Maybe the folks on this list know the other Apache projects better than I do, but I wouldn’t even know what to ask for. Yep. This. I've done some reading about OFBiz, but having never actually used it, I wouldn't know where to start. The other consideration is that once we had a mature thing based on OFBiz, and once it became a critical service for the ASF, Infra would be called upon to support it. This would require funding, expertise, and time. Those can come from a variety of places, such as from the OFBiz community, but *historically*, when this kind of thing has happened (project implements, thing becomes critical), gradually it becomes the responsibility of Infra, not of the project, to do ongoing maintenance. Hence the need for a 5 year view rather than a let's get this feature working view. Why is this different from what Daniel has done? Because this is a nice to have, rather than a critical service. (Although that's a dangerous thing to say, because something like this could easily *become* a critical service.) --Rich The project I’m involved in, Apache Flex, might also have the technology to improve a lot of things at the ASF. Once the code I’m working on gets to a certain point, if I need more customers and want to test out the “eat your own dog food” principle, I may start offering replacements to some of the web experiences we have at the ASF. If I can run a live PoC, it will make it much easier to sell and focus the conversation and maybe even garner more contributors. And even if the ASF rejects it, I will have learned something in the process. For sure, I will meter the effort I put into it accordingly so it isn’t a huge deal if it doesn’t get adopted. -Alex On 1/14/15, 2:09 PM, Pierre Smits pierre.sm...@gmail.com wrote: Like some have expressed in earlier messages in this thread this endeavour could take up some time. Especially when requirements are not clear. And let's not forget, the OFBiz community volunteers their effort to get to a better OFBiz product. They have the tools in place for that. If the ASF wants something on top of that from the OFBIz community it needs to be asked there (their mailing lists). Not here. Even if it is assistance with prototyping a Proof of Concept. Apart from that, as the building blocks of OFBiz don't use exotic constructs (it is java, xml, ftl, groovy, when talking languages) I surmise an ASF Azure box can suffice. If concessions regarding data storage are acceptable (integrated derby in stead of external RDBMS) for such a PoC.. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Wed, Jan 14, 2015 at 10:30 PM, Alex Harui aha...@adobe.com wrote: I’m way outside my area of knowledge, but is there anything stopping the OFBiz community from getting an ASF Azure box and trying to prototype something? -Alex On 1/14/15, 10:46 AM, Pierre Smits pierre.sm...@gmail.com wrote: You are correct. And I am aware that budgets are limitied. But I don't what the budget will be nor decide where the money of the ASF flows. I can only ask for some of it regarding a project. And even then, I won't consider doing so for something that could be perceived as a pet project of Pierre Smits. If ASF offices do want an OFBiz implementation to work with, maybe they should go ahead and involve both INFRA and the OFBiz community. I understand the concerns. I myself have them as well when dealing with volunteer organisations. But - and apparently - the ASF has this solved regarding the INFRA office. The same could be worked out for the other solutions and/or services it needs to have in place. You just need to ask the right questions to the right people. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Wed, Jan 14, 2015 at 5:34 PM, Ross Gardler (MS OPEN TECH) ross.gard...@microsoft.com wrote: Maintaining servers costs money. Money has to come from somewhere and has to be budgeted. We can't just drop a new demand on infra without discussing it with them and ensuring they have the capacity. In terms of maintenance of the result Im thinking who makes the changes we need as requirements change over time? Somebody needs to be responsible for that and we need to be sure it is sustainable. The easier it is to maintain the easier it is to find someone willing to do it. As for my suggestion for OfBiz to be applied to operational area of the foundation I said currently unstructured that is the information is in ad-hoc spreadsheets and mailing lists. OfBiz is, as far as I'm aware, designed for
[maturity] QU40 - backwards compatibility, change or remove?
Hi, There were several comments about QU40 in the https://wiki.apache.org/incubator/ApacheProjectMaturityModel draft, which currently reads QU40 The project puts a high priority on backwards compatibility and aims to document any incompatible changes and provide tools and documentation to help users transition to new features. Thinking about it, this is probably too much for the kind of generic maturity model that we are after. Shall we remove it, or do people have a better idea? Maybe something more generic such as the project's quality goals (for example in terms of backwards compatibility, platform independence and automated test coverage) are clearly documented? I'd like to include something about our general goal of producing quality software, without being too specific. -Bertrand
Re: projects.apache.org overhaul proposal
On Thu, Jan 15, 2015 at 3:24 PM, Rich Bowen rbo...@rcbowen.com wrote: ...*historically*, when this kind of thing has happened (project implements, thing becomes critical), gradually it becomes the responsibility of Infra, not of the project, to do ongoing maintenance Yes, this is why I'm reluctant to encourage any initiative that requires our infrastructure team to support new tools. And I suspect infra shares that reluctance ;-) That being said, it's always a question of benefits vs. costs - but if a simple thing using technologies that every web developer is supposed to know works the choice is a no-brainer for me. -Bertrand
