Re: Fw: Is https://projects-new.apache.org/ ready for prime time?
no need for COMDEV Jira issue: it's Hadoop DOAP that requires to be improved, that is under Hadoop project responsibility in Hadoop svn: http://hadoop.apache.org/doap.rdf Regards, Hervé Le mercredi 15 juillet 2015 13:24:55 Ajoy Bhatia a écrit : > Just read this page: https://projects.apache.org/about.html > > I'll create a COMDEV ticket and try to fix it myself. This would be my > first contribution to the Apache community. :-) > > - Ajoy > > On Wed, Jul 15, 2015 at 1:19 PM, Ajoy Bhatia wrote: > > Hi all, > > > > On https://projects.apache.org/projects.html?category, the only 2 > > occurrences of "hadoop" are the link to the Apache Hadoop > > <https://projects.apache.org/project.html?hadoop> project page in the > > *database* <https://projects.apache.org/projects.html?category#database> > > category, and as the *hadoop* > > <https://projects.apache.org/projects.html?category#hadoop> category > > itself. > > > > I think that Apache Hadoop should also be listed in the *big-data* > > <https://projects.apache.org/projects.html?category#big-data> category, > > as well as in the eponymous *hadoop* > > <https://projects.apache.org/projects.html?category#hadoop> category. > > Don't you agree? > > > > Thanks... > > - Ajoy > > > > > > > > On Tue, Jul 14, 2015 at 4:33 PM, Daniel Gruno > > > > wrote: > >> Fixed in r1691109, thanks for spotting this. > >> > >> With regards, > >> Daniel. > >> > >> On 2015-07-15 01:21, Ted Dunning wrote: > >>> The label on the second pie graph is broken. It refers to language (cut > >>> and paste from the first caption, I think). > >>> > >>> On Tue, Jul 14, 2015 at 10:40 AM, Sally Khudairi wrote: > >>> So ...we've had a tweet from Roman last month, and now JimJag (bcc'd) > >>> > >>>> has > >>>> done so as well > >>>> > >>>> https://twitter.com/jimjag/status/620940463558782976 > >>>> > >>>> > >>>> Are we officially live yet? > >>>> > >>>> If not, please let me know when I can promote. > >>>> > >>>> Cheers, > >>>> Sally > >>>> > >>>> > >>>> From: Sally Khudairi > >>>> To: jan i ; "dev@community.apache.org" < > >>>> dev@community.apache.org> > >>>> Cc: David Crossley ; Sally Khudairi >>>> > >>>> Sent: Saturday, 20 June 2015, 6:53 > >>>> Subject: Re: Fw: Is https://projects-new.apache.org/ ready for prime > >>>> time? > >>>> > >>>> > >>>> > >>>> Aha! > >>>> > >>>> OK --that's exactly it. I didn't realize that it was going to replace > >>>> the > >>>> old link. > >>>> > >>>> So yes, you are correct, Jan, we don't want to do that. > >>>> > >>>> As such, I'll be standing by to hear when you (collectively) are ready. > >>>> > >>>> Thanks again, > >>>> > >>>> Sally > >>>> > >>>> [From the mobile; please excuse top-posting, spelling/spacing errors, > >>>> and > >>>> brevity] > >>>> > >>>> > >>>> > >>>> - Reply message - > >>>> From: "jan i" > >>>> To: "dev@community.apache.org" > >>>> Cc: "David Crossley" , "Sally Khudairi" < > >>>> s...@apache.org> > >>>> Subject: Fw: Is https://projects-new.apache.org/ ready for prime time? > >>>> Date: Sat, Jun 20, 2015 06:39 > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> On 20 June 2015 at 12:34, Sally Khudairi >>>> .invalid> > >>>> wrote: > >>>> > >>>> Thanks, David! > >>>> > >>>>> I noticed that Roman tweeted the link yesterday, so I guess the cat is > >>>> > >>>> out of the bag, as the saying goes. > >>>> > >>>>> As such, barring any objections, I'll start spreading the word. > >>>>> > >>>
Re: Fw: Is https://projects-new.apache.org/ ready for prime time?
Just read this page: https://projects.apache.org/about.html I'll create a COMDEV ticket and try to fix it myself. This would be my first contribution to the Apache community. :-) - Ajoy On Wed, Jul 15, 2015 at 1:19 PM, Ajoy Bhatia wrote: > Hi all, > > On https://projects.apache.org/projects.html?category, the only 2 > occurrences of "hadoop" are the link to the Apache Hadoop > <https://projects.apache.org/project.html?hadoop> project page in the > *database* <https://projects.apache.org/projects.html?category#database> > category, and as the *hadoop* > <https://projects.apache.org/projects.html?category#hadoop> category > itself. > > I think that Apache Hadoop should also be listed in the *big-data* > <https://projects.apache.org/projects.html?category#big-data> category, > as well as in the eponymous *hadoop* > <https://projects.apache.org/projects.html?category#hadoop> category. > Don't you agree? > > Thanks... > - Ajoy > > > > On Tue, Jul 14, 2015 at 4:33 PM, Daniel Gruno > wrote: > >> Fixed in r1691109, thanks for spotting this. >> >> With regards, >> Daniel. >> >> >> On 2015-07-15 01:21, Ted Dunning wrote: >> >>> The label on the second pie graph is broken. It refers to language (cut >>> and paste from the first caption, I think). >>> >>> >>> >>> On Tue, Jul 14, 2015 at 10:40 AM, Sally Khudairi wrote: >>> >>> So ...we've had a tweet from Roman last month, and now JimJag (bcc'd) >>>> has >>>> done so as well >>>> >>>> https://twitter.com/jimjag/status/620940463558782976 >>>> >>>> >>>> Are we officially live yet? >>>> >>>> If not, please let me know when I can promote. >>>> >>>> Cheers, >>>> Sally >>>> >>>> >>>> From: Sally Khudairi >>>> To: jan i ; "dev@community.apache.org" < >>>> dev@community.apache.org> >>>> Cc: David Crossley ; Sally Khudairi >>> > >>>> Sent: Saturday, 20 June 2015, 6:53 >>>> Subject: Re: Fw: Is https://projects-new.apache.org/ ready for prime >>>> time? >>>> >>>> >>>> >>>> Aha! >>>> >>>> OK --that's exactly it. I didn't realize that it was going to replace >>>> the >>>> old link. >>>> >>>> So yes, you are correct, Jan, we don't want to do that. >>>> >>>> As such, I'll be standing by to hear when you (collectively) are ready. >>>> >>>> Thanks again, >>>> Sally >>>> >>>> >>>> [From the mobile; please excuse top-posting, spelling/spacing errors, >>>> and >>>> brevity] >>>> >>>> >>>> >>>> - Reply message - >>>> From: "jan i" >>>> To: "dev@community.apache.org" >>>> Cc: "David Crossley" , "Sally Khudairi" < >>>> s...@apache.org> >>>> Subject: Fw: Is https://projects-new.apache.org/ ready for prime time? >>>> Date: Sat, Jun 20, 2015 06:39 >>>> >>>> >>>> >>>> >>>> >>>> On 20 June 2015 at 12:34, Sally Khudairi >>> .invalid> >>>> wrote: >>>> >>>> Thanks, David! >>>> >>>>> I noticed that Roman tweeted the link yesterday, so I guess the cat is >>>>> >>>> out of the bag, as the saying goes. >>>> >>>>> As such, barring any objections, I'll start spreading the word. >>>>> >>>>> Do we really want to do marketing on the temporary URL ? >>>> >>>> >>>> In my opinion, we should do some renaming so the current one is called >>>> -old and the new one replaces the current one. >>>> >>>> >>>> rgds >>>> >>>> jan i. >>>> >>>> >>>> Are there plans in place to link this from the apache.org homepage? >>>>> >>>>> Thanks again, >>>>> Sally >>>>> >>>>> >>>>> [From the mobile; please excuse top-posting, spelling/spacing errors, >>>>> and >>>>> >>>> brevity] >>>> >>>>> - Rep
Re: Fw: Is https://projects-new.apache.org/ ready for prime time?
Hi all, On https://projects.apache.org/projects.html?category, the only 2 occurrences of "hadoop" are the link to the Apache Hadoop <https://projects.apache.org/project.html?hadoop> project page in the *database* <https://projects.apache.org/projects.html?category#database> category, and as the *hadoop* <https://projects.apache.org/projects.html?category#hadoop> category itself. I think that Apache Hadoop should also be listed in the *big-data* <https://projects.apache.org/projects.html?category#big-data> category, as well as in the eponymous *hadoop* <https://projects.apache.org/projects.html?category#hadoop> category. Don't you agree? Thanks... - Ajoy On Tue, Jul 14, 2015 at 4:33 PM, Daniel Gruno wrote: > Fixed in r1691109, thanks for spotting this. > > With regards, > Daniel. > > > On 2015-07-15 01:21, Ted Dunning wrote: > >> The label on the second pie graph is broken. It refers to language (cut >> and paste from the first caption, I think). >> >> >> >> On Tue, Jul 14, 2015 at 10:40 AM, Sally Khudairi wrote: >> >> So ...we've had a tweet from Roman last month, and now JimJag (bcc'd) has >>> done so as well >>> >>> https://twitter.com/jimjag/status/620940463558782976 >>> >>> >>> Are we officially live yet? >>> >>> If not, please let me know when I can promote. >>> >>> Cheers, >>> Sally >>> >>> ________ >>> From: Sally Khudairi >>> To: jan i ; "dev@community.apache.org" < >>> dev@community.apache.org> >>> Cc: David Crossley ; Sally Khudairi >>> Sent: Saturday, 20 June 2015, 6:53 >>> Subject: Re: Fw: Is https://projects-new.apache.org/ ready for prime >>> time? >>> >>> >>> >>> Aha! >>> >>> OK --that's exactly it. I didn't realize that it was going to replace the >>> old link. >>> >>> So yes, you are correct, Jan, we don't want to do that. >>> >>> As such, I'll be standing by to hear when you (collectively) are ready. >>> >>> Thanks again, >>> Sally >>> >>> >>> [From the mobile; please excuse top-posting, spelling/spacing errors, and >>> brevity] >>> >>> >>> >>> - Reply message - >>> From: "jan i" >>> To: "dev@community.apache.org" >>> Cc: "David Crossley" , "Sally Khudairi" < >>> s...@apache.org> >>> Subject: Fw: Is https://projects-new.apache.org/ ready for prime time? >>> Date: Sat, Jun 20, 2015 06:39 >>> >>> >>> >>> >>> >>> On 20 June 2015 at 12:34, Sally Khudairi >> .invalid> >>> wrote: >>> >>> Thanks, David! >>> >>>> I noticed that Roman tweeted the link yesterday, so I guess the cat is >>>> >>> out of the bag, as the saying goes. >>> >>>> As such, barring any objections, I'll start spreading the word. >>>> >>>> Do we really want to do marketing on the temporary URL ? >>> >>> >>> In my opinion, we should do some renaming so the current one is called >>> -old and the new one replaces the current one. >>> >>> >>> rgds >>> >>> jan i. >>> >>> >>> Are there plans in place to link this from the apache.org homepage? >>>> >>>> Thanks again, >>>> Sally >>>> >>>> >>>> [From the mobile; please excuse top-posting, spelling/spacing errors, >>>> and >>>> >>> brevity] >>> >>>> - Reply message - >>>> >>>> From: "David Crossley" >>>> To: , "Sally Khudairi" >>>> Subject: Fw: Is https://projects-new.apache.org/ ready for prime time? >>>> Date: Sat, Jun 20, 2015 03:03 >>>> >>>> Previous discussion here was about how to maintain the >>>> actual project data. >>>> Also various items listed here: >>>> https://projects-new.apache.org/about.html >>>> >>>> ~David >>>> >>>> On Fri, Jun 19, 2015 at 08:55:52PM +, Sally Khudairi wrote: >>>> >>>>> Hello Uli and the Apache ComDev team --I hope this message finds you >>>>> >>>> well. >>> >>>> Per below, I'm interes
Re: Fw: Is https://projects-new.apache.org/ ready for prime time?
Fixed in r1691109, thanks for spotting this. With regards, Daniel. On 2015-07-15 01:21, Ted Dunning wrote: The label on the second pie graph is broken. It refers to language (cut and paste from the first caption, I think). On Tue, Jul 14, 2015 at 10:40 AM, Sally Khudairi wrote: So ...we've had a tweet from Roman last month, and now JimJag (bcc'd) has done so as well https://twitter.com/jimjag/status/620940463558782976 Are we officially live yet? If not, please let me know when I can promote. Cheers, Sally From: Sally Khudairi To: jan i ; "dev@community.apache.org" < dev@community.apache.org> Cc: David Crossley ; Sally Khudairi Sent: Saturday, 20 June 2015, 6:53 Subject: Re: Fw: Is https://projects-new.apache.org/ ready for prime time? Aha! OK --that's exactly it. I didn't realize that it was going to replace the old link. So yes, you are correct, Jan, we don't want to do that. As such, I'll be standing by to hear when you (collectively) are ready. Thanks again, Sally [From the mobile; please excuse top-posting, spelling/spacing errors, and brevity] - Reply message - From: "jan i" To: "dev@community.apache.org" Cc: "David Crossley" , "Sally Khudairi" < s...@apache.org> Subject: Fw: Is https://projects-new.apache.org/ ready for prime time? Date: Sat, Jun 20, 2015 06:39 On 20 June 2015 at 12:34, Sally Khudairi wrote: Thanks, David! I noticed that Roman tweeted the link yesterday, so I guess the cat is out of the bag, as the saying goes. As such, barring any objections, I'll start spreading the word. Do we really want to do marketing on the temporary URL ? In my opinion, we should do some renaming so the current one is called -old and the new one replaces the current one. rgds jan i. Are there plans in place to link this from the apache.org homepage? Thanks again, Sally [From the mobile; please excuse top-posting, spelling/spacing errors, and brevity] ----- Reply message - From: "David Crossley" To: , "Sally Khudairi" Subject: Fw: Is https://projects-new.apache.org/ ready for prime time? Date: Sat, Jun 20, 2015 03:03 Previous discussion here was about how to maintain the actual project data. Also various items listed here: https://projects-new.apache.org/about.html ~David On Fri, Jun 19, 2015 at 08:55:52PM +, Sally Khudairi wrote: Hello Uli and the Apache ComDev team --I hope this message finds you well. Per below, I'm interested in promoting the new Projects page. Can you please let me know if/when we're ready to do so? Thanks so much, Sally - Forwarded Message - From: David Nalley To: Sally Khudairi Cc: Daniel Gruno ; ASF Infrastructure < infrastruct...@apache.org> Sent: Friday, June 19, 2015 11:50 AM Subject: Re: Is https://projects-new.apache.org/ ready for prime time? Hi Sally: projects-new.apache.org is a ComDev managed resource, not an infrastructure managed resource. I think the PMC has had a discussion or two about when to migrate projects-new to projects.a.o --David On Fri, Jun 19, 2015 at 11:30 AM, Sally Khudairi wrote: Hello Daniel and David --I hope you are both well. I was wondering if the new Projects page at https://projects-new.apache.org/ was ready to be publicly deployed/announced/promoted. There's so much great information there and it's an incredible resource (I use it every week for the News Round-ups and we relied on it for the Annual Report), if there's no reason why it should still be in stealth mode, I'd like to shout out about it from the rooftops. Just let me know if we're good to go and if there are any disclaimers/caveats we should be aware of. Warm thanks, Sally = = = = = vox +1 617 921 8656 off2 +1 646 583 3362 skype sallykhudairi
Re: Fw: Is https://projects-new.apache.org/ ready for prime time?
The label on the second pie graph is broken. It refers to language (cut and paste from the first caption, I think). On Tue, Jul 14, 2015 at 10:40 AM, Sally Khudairi wrote: > So ...we've had a tweet from Roman last month, and now JimJag (bcc'd) has > done so as well > > https://twitter.com/jimjag/status/620940463558782976 > > > Are we officially live yet? > > If not, please let me know when I can promote. > > Cheers, > Sally > > > From: Sally Khudairi > To: jan i ; "dev@community.apache.org" < > dev@community.apache.org> > Cc: David Crossley ; Sally Khudairi > Sent: Saturday, 20 June 2015, 6:53 > Subject: Re: Fw: Is https://projects-new.apache.org/ ready for prime time? > > > > Aha! > > OK --that's exactly it. I didn't realize that it was going to replace the > old link. > > So yes, you are correct, Jan, we don't want to do that. > > As such, I'll be standing by to hear when you (collectively) are ready. > > Thanks again, > Sally > > > [From the mobile; please excuse top-posting, spelling/spacing errors, and > brevity] > > > > ----- Reply message - > From: "jan i" > To: "dev@community.apache.org" > Cc: "David Crossley" , "Sally Khudairi" < > s...@apache.org> > Subject: Fw: Is https://projects-new.apache.org/ ready for prime time? > Date: Sat, Jun 20, 2015 06:39 > > > > > > On 20 June 2015 at 12:34, Sally Khudairi > wrote: > > Thanks, David! > > > >I noticed that Roman tweeted the link yesterday, so I guess the cat is > out of the bag, as the saying goes. > > > >As such, barring any objections, I'll start spreading the word. > > > Do we really want to do marketing on the temporary URL ? > > > In my opinion, we should do some renaming so the current one is called > -old and the new one replaces the current one. > > > rgds > > jan i. > > > >Are there plans in place to link this from the apache.org homepage? > > > >Thanks again, > >Sally > > > > > >[From the mobile; please excuse top-posting, spelling/spacing errors, and > brevity] > > > >- Reply message - > > > >From: "David Crossley" > >To: , "Sally Khudairi" > >Subject: Fw: Is https://projects-new.apache.org/ ready for prime time? > >Date: Sat, Jun 20, 2015 03:03 > > > >Previous discussion here was about how to maintain the > >actual project data. > >Also various items listed here: > >https://projects-new.apache.org/about.html > > > >~David > > > >On Fri, Jun 19, 2015 at 08:55:52PM +, Sally Khudairi wrote: > >> Hello Uli and the Apache ComDev team --I hope this message finds you > well. > >> Per below, I'm interested in promoting the new Projects page. > >> Can you please let me know if/when we're ready to do so? > >> Thanks so much, > >> Sally > >> > >> - Forwarded Message - > >> From: David Nalley > >> To: Sally Khudairi > >> Cc: Daniel Gruno ; ASF Infrastructure < > infrastruct...@apache.org> > >> Sent: Friday, June 19, 2015 11:50 AM > >> Subject: Re: Is https://projects-new.apache.org/ ready for prime time? > >> > >> Hi Sally: > >> > >> projects-new.apache.org is a ComDev managed resource, not an > >> infrastructure managed resource. I think the PMC has had a discussion > >> or two about when to migrate projects-new to projects.a.o > >> > >> --David > >> > >> > >> > >> On Fri, Jun 19, 2015 at 11:30 AM, Sally Khudairi > >> wrote: > >> > Hello Daniel and David --I hope you are both well. > >> > > >> > > >> > I was wondering if the new Projects page at > >> > > >> > https://projects-new.apache.org/ > >> > > >> > was ready to be publicly deployed/announced/promoted. > >> > > >> > There's so much great information there and it's an incredible > resource (I use it every week for the News Round-ups and we relied on it > for the Annual Report), if there's no reason why it should still be in > stealth mode, I'd like to shout out about it from the rooftops. > >> > > >> > Just let me know if we're good to go and if there are any > disclaimers/caveats we should be aware of. > >> > > >> > Warm thanks, > >> > Sally > >> > > >> > > >> > = = = = = > >> > vox +1 617 921 8656 > >> > off2 +1 646 583 3362 > >> > skype sallykhudairi > >> > >> >
Re: Fw: Is https://projects-new.apache.org/ ready for prime time?
Tweeted! https://twitter.com/TheASF/status/621022893405806593 This will also be included in the Apache Weekly News Round-ups as well. Cheers, Sally - Original Message - From: Sally Khudairi To: Hervé BOUTEMY ; "dev@community.apache.org" Cc: Sally Khudairi ; jan i ; David Crossley ; "ro...@shaposhnik.org" Sent: Tuesday, 14 July 2015, 14:23 Subject: Re: Fw: Is https://projects-new.apache.org/ ready for prime time? Thanks for the confirmation, Hervé! Salut, Sally - Original Message - From: Hervé BOUTEMY To: dev@community.apache.org Cc: Sally Khudairi ; Sally Khudairi ; jan i ; David Crossley ; "ro...@shaposhnik.org" Sent: Tuesday, 14 July 2015, 14:09 Subject: Re: Fw: Is https://projects-new.apache.org/ ready for prime time? yes, we are officially live since sunday night https://projects.apache.org/ Regards, Hervé Le mardi 14 juillet 2015 17:40:02 Sally Khudairi a écrit : > So ...we've had a tweet from Roman last month, and now JimJag (bcc'd) has > done so as well > > https://twitter.com/jimjag/status/620940463558782976 > > > Are we officially live yet? > > If not, please let me know when I can promote. > > Cheers, > Sally > > > From: Sally Khudairi > To: jan i ; "dev@community.apache.org" > Cc: David Crossley ; Sally > Khudairi Sent: Saturday, 20 June 2015, 6:53 > Subject: Re: Fw: Is https://projects-new.apache.org/ ready for prime time? > > > > Aha! > > OK --that's exactly it. I didn't realize that it was going to replace the > old link. > > So yes, you are correct, Jan, we don't want to do that. > > As such, I'll be standing by to hear when you (collectively) are ready. > > Thanks again, > Sally > > > [From the mobile; please excuse top-posting, spelling/spacing errors, and > brevity] > > > > - Reply message - > From: "jan i" > To: "dev@community.apache.org" > Cc: "David Crossley" , "Sally Khudairi" > Subject: Fw: Is https://projects-new.apache.org/ ready for prime time? > Date: Sat, Jun 20, 2015 06:39 > > > > > > On 20 June 2015 at 12:34, Sally Khudairi > wrote: > > Thanks, David! > > >I noticed that Roman tweeted the link yesterday, so I guess the cat is out > >of the bag, as the saying goes. > > > >As such, barring any objections, I'll start spreading the word. > > Do we really want to do marketing on the temporary URL ? > > > In my opinion, we should do some renaming so the current one is called -old > and the new one replaces the current one. > > > rgds > > jan i. > > >Are there plans in place to link this from the apache.org homepage? > > > >Thanks again, > >Sally > > > > > >[From the mobile; please excuse top-posting, spelling/spacing errors, and > >brevity] > > > >- Reply message - > > > >From: "David Crossley" > >To: , "Sally Khudairi" > >Subject: Fw: Is https://projects-new.apache.org/ ready for prime time? > >Date: Sat, Jun 20, 2015 03:03 > > > >Previous discussion here was about how to maintain the > >actual project data. > >Also various items listed here: > >https://projects-new.apache.org/about.html > > > >~David > > > >On Fri, Jun 19, 2015 at 08:55:52PM +, Sally Khudairi wrote: > >> Hello Uli and the Apache ComDev team --I hope this message finds you > >> well. > >> Per below, I'm interested in promoting the new Projects page. > >> Can you please let me know if/when we're ready to do so? > >> Thanks so much, > >> Sally > >> > >> - Forwarded Message - > >> > >> From: David Nalley > >> > >> To: Sally Khudairi > >> > >> Cc: Daniel Gruno ; ASF Infrastructure > >> >> > >> Sent: Friday, June 19, 2015 11:50 AM > >> Subject: Re: Is https://projects-new.apache.org/ ready for prime time? > >> > >> Hi Sally: > >> > >> projects-new.apache.org is a ComDev managed resource, not an > >> infrastructure managed resource. I think the PMC has had a discussion > >> or two about when to migrate projects-new to projects.a.o > >> > >> --David > >> > >> > >> > >> On Fri, Jun 19, 2015 at 11:30 AM, Sally Khudairi > >> > >> wrote: > >> > Hello Daniel and David --I hope you are both well. > >> > > >> > > >> > I was wondering if the new Projects page at > >> > > >> > https://projects-new.apache.org/ > >> > > >> > was ready to be publicly deployed/announced/promoted. > >> > > >> > There's so much great information there and it's an incredible resource > >> > (I use it every week for the News Round-ups and we relied on it for > >> > the Annual Report), if there's no reason why it should still be in > >> > stealth mode, I'd like to shout out about it from the rooftops. > >> > > >> > Just let me know if we're good to go and if there are any > >> > disclaimers/caveats we should be aware of. > >> > > >> > Warm thanks, > >> > Sally > >> > > >> > > >> > = = = = = > >> > vox +1 617 921 8656 > >> > off2 +1 646 583 3362 > >> > skype sallykhudairi
Re: Fw: Is https://projects-new.apache.org/ ready for prime time?
Thanks for the confirmation, Hervé! Salut, Sally - Original Message - From: Hervé BOUTEMY To: dev@community.apache.org Cc: Sally Khudairi ; Sally Khudairi ; jan i ; David Crossley ; "ro...@shaposhnik.org" Sent: Tuesday, 14 July 2015, 14:09 Subject: Re: Fw: Is https://projects-new.apache.org/ ready for prime time? yes, we are officially live since sunday night https://projects.apache.org/ Regards, Hervé Le mardi 14 juillet 2015 17:40:02 Sally Khudairi a écrit : > So ...we've had a tweet from Roman last month, and now JimJag (bcc'd) has > done so as well > > https://twitter.com/jimjag/status/620940463558782976 > > > Are we officially live yet? > > If not, please let me know when I can promote. > > Cheers, > Sally > > > From: Sally Khudairi > To: jan i ; "dev@community.apache.org" > Cc: David Crossley ; Sally > Khudairi Sent: Saturday, 20 June 2015, 6:53 > Subject: Re: Fw: Is https://projects-new.apache.org/ ready for prime time? > > > > Aha! > > OK --that's exactly it. I didn't realize that it was going to replace the > old link. > > So yes, you are correct, Jan, we don't want to do that. > > As such, I'll be standing by to hear when you (collectively) are ready. > > Thanks again, > Sally > > > [From the mobile; please excuse top-posting, spelling/spacing errors, and > brevity] > > > > - Reply message - > From: "jan i" > To: "dev@community.apache.org" > Cc: "David Crossley" , "Sally Khudairi" > Subject: Fw: Is https://projects-new.apache.org/ ready for prime time? > Date: Sat, Jun 20, 2015 06:39 > > > > > > On 20 June 2015 at 12:34, Sally Khudairi > wrote: > > Thanks, David! > > >I noticed that Roman tweeted the link yesterday, so I guess the cat is out > >of the bag, as the saying goes. > > > >As such, barring any objections, I'll start spreading the word. > > Do we really want to do marketing on the temporary URL ? > > > In my opinion, we should do some renaming so the current one is called -old > and the new one replaces the current one. > > > rgds > > jan i. > > >Are there plans in place to link this from the apache.org homepage? > > > >Thanks again, > >Sally > > > > > >[From the mobile; please excuse top-posting, spelling/spacing errors, and > >brevity] > > > >- Reply message - > > > >From: "David Crossley" > >To: , "Sally Khudairi" > >Subject: Fw: Is https://projects-new.apache.org/ ready for prime time? > >Date: Sat, Jun 20, 2015 03:03 > > > >Previous discussion here was about how to maintain the > >actual project data. > >Also various items listed here: > >https://projects-new.apache.org/about.html > > > >~David > > > >On Fri, Jun 19, 2015 at 08:55:52PM +, Sally Khudairi wrote: > >> Hello Uli and the Apache ComDev team --I hope this message finds you > >> well. > >> Per below, I'm interested in promoting the new Projects page. > >> Can you please let me know if/when we're ready to do so? > >> Thanks so much, > >> Sally > >> > >> - Forwarded Message - > >> > >> From: David Nalley > >> > >> To: Sally Khudairi > >> > >> Cc: Daniel Gruno ; ASF Infrastructure > >> >> > >> Sent: Friday, June 19, 2015 11:50 AM > >> Subject: Re: Is https://projects-new.apache.org/ ready for prime time? > >> > >> Hi Sally: > >> > >> projects-new.apache.org is a ComDev managed resource, not an > >> infrastructure managed resource. I think the PMC has had a discussion > >> or two about when to migrate projects-new to projects.a.o > >> > >> --David > >> > >> > >> > >> On Fri, Jun 19, 2015 at 11:30 AM, Sally Khudairi > >> > >> wrote: > >> > Hello Daniel and David --I hope you are both well. > >> > > >> > > >> > I was wondering if the new Projects page at > >> > > >> > https://projects-new.apache.org/ > >> > > >> > was ready to be publicly deployed/announced/promoted. > >> > > >> > There's so much great information there and it's an incredible resource > >> > (I use it every week for the News Round-ups and we relied on it for > >> > the Annual Report), if there's no reason why it should still be in > >> > stealth mode, I'd like to shout out about it from the rooftops. > >> > > >> > Just let me know if we're good to go and if there are any > >> > disclaimers/caveats we should be aware of. > >> > > >> > Warm thanks, > >> > Sally > >> > > >> > > >> > = = = = = > >> > vox +1 617 921 8656 > >> > off2 +1 646 583 3362 > >> > skype sallykhudairi
Re: Fw: Is https://projects-new.apache.org/ ready for prime time?
yes, we are officially live since sunday night https://projects.apache.org/ Regards, Hervé Le mardi 14 juillet 2015 17:40:02 Sally Khudairi a écrit : > So ...we've had a tweet from Roman last month, and now JimJag (bcc'd) has > done so as well > > https://twitter.com/jimjag/status/620940463558782976 > > > Are we officially live yet? > > If not, please let me know when I can promote. > > Cheers, > Sally > > > From: Sally Khudairi > To: jan i ; "dev@community.apache.org" > Cc: David Crossley ; Sally > Khudairi Sent: Saturday, 20 June 2015, 6:53 > Subject: Re: Fw: Is https://projects-new.apache.org/ ready for prime time? > > > > Aha! > > OK --that's exactly it. I didn't realize that it was going to replace the > old link. > > So yes, you are correct, Jan, we don't want to do that. > > As such, I'll be standing by to hear when you (collectively) are ready. > > Thanks again, > Sally > > > [From the mobile; please excuse top-posting, spelling/spacing errors, and > brevity] > > > > - Reply message - > From: "jan i" > To: "dev@community.apache.org" > Cc: "David Crossley" , "Sally Khudairi" > Subject: Fw: Is https://projects-new.apache.org/ ready for prime time? > Date: Sat, Jun 20, 2015 06:39 > > > > > > On 20 June 2015 at 12:34, Sally Khudairi > wrote: > > Thanks, David! > > >I noticed that Roman tweeted the link yesterday, so I guess the cat is out > >of the bag, as the saying goes. > > > >As such, barring any objections, I'll start spreading the word. > > Do we really want to do marketing on the temporary URL ? > > > In my opinion, we should do some renaming so the current one is called -old > and the new one replaces the current one. > > > rgds > > jan i. > > >Are there plans in place to link this from the apache.org homepage? > > > >Thanks again, > >Sally > > > > > >[From the mobile; please excuse top-posting, spelling/spacing errors, and > >brevity] > > > >- Reply message - > > > >From: "David Crossley" > >To: , "Sally Khudairi" > >Subject: Fw: Is https://projects-new.apache.org/ ready for prime time? > >Date: Sat, Jun 20, 2015 03:03 > > > >Previous discussion here was about how to maintain the > >actual project data. > >Also various items listed here: > >https://projects-new.apache.org/about.html > > > >~David > > > >On Fri, Jun 19, 2015 at 08:55:52PM +, Sally Khudairi wrote: > >> Hello Uli and the Apache ComDev team --I hope this message finds you > >> well. > >> Per below, I'm interested in promoting the new Projects page. > >> Can you please let me know if/when we're ready to do so? > >> Thanks so much, > >> Sally > >> > >> - Forwarded Message - > >> > >> From: David Nalley > >> > >> To: Sally Khudairi > >> > >> Cc: Daniel Gruno ; ASF Infrastructure > >> >> > >> Sent: Friday, June 19, 2015 11:50 AM > >> Subject: Re: Is https://projects-new.apache.org/ ready for prime time? > >> > >> Hi Sally: > >> > >> projects-new.apache.org is a ComDev managed resource, not an > >> infrastructure managed resource. I think the PMC has had a discussion > >> or two about when to migrate projects-new to projects.a.o > >> > >> --David > >> > >> > >> > >> On Fri, Jun 19, 2015 at 11:30 AM, Sally Khudairi > >> > >> wrote: > >> > Hello Daniel and David --I hope you are both well. > >> > > >> > > >> > I was wondering if the new Projects page at > >> > > >> > https://projects-new.apache.org/ > >> > > >> > was ready to be publicly deployed/announced/promoted. > >> > > >> > There's so much great information there and it's an incredible resource > >> > (I use it every week for the News Round-ups and we relied on it for > >> > the Annual Report), if there's no reason why it should still be in > >> > stealth mode, I'd like to shout out about it from the rooftops. > >> > > >> > Just let me know if we're good to go and if there are any > >> > disclaimers/caveats we should be aware of. > >> > > >> > Warm thanks, > >> > Sally > >> > > >> > > >> > = = = = = > >> > vox +1 617 921 8656 > >> > off2 +1 646 583 3362 > >> > skype sallykhudairi
Re: Fw: Is https://projects-new.apache.org/ ready for prime time?
So ...we've had a tweet from Roman last month, and now JimJag (bcc'd) has done so as well https://twitter.com/jimjag/status/620940463558782976 Are we officially live yet? If not, please let me know when I can promote. Cheers, Sally From: Sally Khudairi To: jan i ; "dev@community.apache.org" Cc: David Crossley ; Sally Khudairi Sent: Saturday, 20 June 2015, 6:53 Subject: Re: Fw: Is https://projects-new.apache.org/ ready for prime time? Aha! OK --that's exactly it. I didn't realize that it was going to replace the old link. So yes, you are correct, Jan, we don't want to do that. As such, I'll be standing by to hear when you (collectively) are ready. Thanks again, Sally [From the mobile; please excuse top-posting, spelling/spacing errors, and brevity] - Reply message - From: "jan i" To: "dev@community.apache.org" Cc: "David Crossley" , "Sally Khudairi" Subject: Fw: Is https://projects-new.apache.org/ ready for prime time? Date: Sat, Jun 20, 2015 06:39 On 20 June 2015 at 12:34, Sally Khudairi wrote: Thanks, David! > >I noticed that Roman tweeted the link yesterday, so I guess the cat is out of >the bag, as the saying goes. > >As such, barring any objections, I'll start spreading the word. > Do we really want to do marketing on the temporary URL ? In my opinion, we should do some renaming so the current one is called -old and the new one replaces the current one. rgds jan i. >Are there plans in place to link this from the apache.org homepage? > >Thanks again, >Sally > > >[From the mobile; please excuse top-posting, spelling/spacing errors, and >brevity] > >- Reply message - > >From: "David Crossley" >To: , "Sally Khudairi" >Subject: Fw: Is https://projects-new.apache.org/ ready for prime time? >Date: Sat, Jun 20, 2015 03:03 > >Previous discussion here was about how to maintain the >actual project data. >Also various items listed here: >https://projects-new.apache.org/about.html > >~David > >On Fri, Jun 19, 2015 at 08:55:52PM +, Sally Khudairi wrote: >> Hello Uli and the Apache ComDev team --I hope this message finds you well. >> Per below, I'm interested in promoting the new Projects page. >> Can you please let me know if/when we're ready to do so? >> Thanks so much, >> Sally >> >> - Forwarded Message - >> From: David Nalley >> To: Sally Khudairi >> Cc: Daniel Gruno ; ASF Infrastructure >> >> Sent: Friday, June 19, 2015 11:50 AM >> Subject: Re: Is https://projects-new.apache.org/ ready for prime time? >> >> Hi Sally: >> >> projects-new.apache.org is a ComDev managed resource, not an >> infrastructure managed resource. I think the PMC has had a discussion >> or two about when to migrate projects-new to projects.a.o >> >> --David >> >> >> >> On Fri, Jun 19, 2015 at 11:30 AM, Sally Khudairi >> wrote: >> > Hello Daniel and David --I hope you are both well. >> > >> > >> > I was wondering if the new Projects page at >> > >> > https://projects-new.apache.org/ >> > >> > was ready to be publicly deployed/announced/promoted. >> > >> > There's so much great information there and it's an incredible resource (I >> > use it every week for the News Round-ups and we relied on it for the >> > Annual Report), if there's no reason why it should still be in stealth >> > mode, I'd like to shout out about it from the rooftops. >> > >> > Just let me know if we're good to go and if there are any >> > disclaimers/caveats we should be aware of. >> > >> > Warm thanks, >> > Sally >> > >> > >> > = = = = = >> > vox +1 617 921 8656 >> > off2 +1 646 583 3362 >> > skype sallykhudairi >> >>
Re: Is https://projects-new.apache.org/ ready for prime time?
Le vendredi 26 juin 2015 17:46:55 sebb a écrit : > On 26 June 2015 at 07:12, Hervé BOUTEMY wrote: > > that's why I want to switch projects to projects-old and projects-new to > > projects: be able to work on extracting documentation from projects-old > > and > > updating it to match the new location > > That will break the existing links. > > If you want do the switch ahead of fixing the documentation, then one > way to do it is to ensure that projects-old is set up to point to the > current projects.a.o. > > Then change projects-new to link to projects-old instead of projects - > that should be trivial to do. > > Then projects-new can replace projects.a.o. > > Documentation can then be migrated to the new code in the old URL. yes, of course, these are the exact steps: I just summarised > > > I proposed http://svn.apache.org/viewvc/comdev/projects.apache.org/data/ > > as > > the new location of DOAP files lists (both PMC and projects) but got no > > answer > Did not see that. > > That will break projects-old, so -1 until projects-old has been > retired unless you can find a way to keep projects-old working with > the new location. the idea is to let old data in the old location and not update it any more: this won't break anything, just make projects-old less accurate over time that's not an issue IMHO, since we expect to migrate the doc and shutdown projects-old after that, in a few monthes notice that I think the cron job that updates projects-old should be switched off to avoid issues > > AFAIK it's not necessary to move the location. ? previously, you told having projects-new depending on projects-old was an issue and you were right! and IMHO, it's an issue just because data in projects-old is hard to find for someone not expert in the whole system I'll start to add comments in projects-old data to point to projects-new to start the transition then we'll have to agree on when to really switch (and find who can do it) Regards, Hervé > > > if we're ok with that new location, the next step is to stop modifying > > equivalent files in > > http://svn.apache.org/viewvc/infrastructure/site-tools/trunk/projects/ > > (or even remove them) but point to the new location > > > > Of course, if ok with the new location, we can immediately add > > committees.xml and projects.xml pointers to > > https://projects-new.apache.org/about.html IMHO the simple file names and > > location in about.html would make things very clear before diggin into > > more details on DOAP format and conventions (which could be in the Wiki > > for ease of editing) > > > > > > can we agree: > > 1. on the new data location and content: > > http://svn.apache.org/viewvc/comdev/projects.apache.org/data/ > > No, see above. > > > 2. on the switch then update of everything to match the new location (and > > stop updating projects-old) > > Not entirely, see above. > > > Regards, > > > > Hervé > > > > Le jeudi 25 juin 2015 09:17:32 vous avez écrit : > >> On 25 June 2015 at 06:53, Hervé BOUTEMY wrote: > >> > Sebb, > >> > > >> > as main maintainer of current http://projects.apache.org/ (AFAIK), are > >> > you > >> > ok with switching the url to the new service and renaming current > >> > service > >> > to projects-old (to let use time to continue content migration withotu > >> > loosing anything)? Do you see any show stopper? > >> > >> The main item missing from projects-new is documentation - it > >> currently points to projects. > >> It's not immediately obvious how to provide data for the site. > >> I think the main page needs to provide more of an overview. > >> > >> I think the first step needs to be to improve the projects-new > >> documentation so it does not rely on the current project pages. > >> > >> Also I notice that it seems p-new relies on parsing > >> http://people.apache.org/committer-index.html > >> which in turn parses other data sources. > >> > >> That needs to be fixed. > >> > >> > Of course, I'm interested in your help to maintain the new projects > >> > site: > >> > don't hesitate to comment on or change the code. > >> > > >> > Regards, > >> > > >> > Hervé > >> > > >> > Le dimanche 21 juin 2015 17:16:07 jan i a écrit : > >> >> +1 switch as soon as possible, and then continue working on the data > >
Re: Is https://projects-new.apache.org/ ready for prime time?
On 26 June 2015 at 07:12, Hervé BOUTEMY wrote: > that's why I want to switch projects to projects-old and projects-new to > projects: be able to work on extracting documentation from projects-old and > updating it to match the new location That will break the existing links. If you want do the switch ahead of fixing the documentation, then one way to do it is to ensure that projects-old is set up to point to the current projects.a.o. Then change projects-new to link to projects-old instead of projects - that should be trivial to do. Then projects-new can replace projects.a.o. Documentation can then be migrated to the new code in the old URL. > I proposed http://svn.apache.org/viewvc/comdev/projects.apache.org/data/ as > the new location of DOAP files lists (both PMC and projects) but got no answer Did not see that. That will break projects-old, so -1 until projects-old has been retired unless you can find a way to keep projects-old working with the new location. AFAIK it's not necessary to move the location. > if we're ok with that new location, the next step is to stop modifying > equivalent files in > http://svn.apache.org/viewvc/infrastructure/site-tools/trunk/projects/ (or > even remove them) but point to the new location > > Of course, if ok with the new location, we can immediately add committees.xml > and projects.xml pointers to https://projects-new.apache.org/about.html > IMHO the simple file names and location in about.html would make things very > clear before diggin into more details on DOAP format and conventions (which > could be in the Wiki for ease of editing) > > > can we agree: > 1. on the new data location and content: > http://svn.apache.org/viewvc/comdev/projects.apache.org/data/ No, see above. > 2. on the switch then update of everything to match the new location (and stop > updating projects-old) Not entirely, see above. > Regards, > > Hervé > > Le jeudi 25 juin 2015 09:17:32 vous avez écrit : >> On 25 June 2015 at 06:53, Hervé BOUTEMY wrote: >> > Sebb, >> > >> > as main maintainer of current http://projects.apache.org/ (AFAIK), are you >> > ok with switching the url to the new service and renaming current service >> > to projects-old (to let use time to continue content migration withotu >> > loosing anything)? Do you see any show stopper? >> >> The main item missing from projects-new is documentation - it >> currently points to projects. >> It's not immediately obvious how to provide data for the site. >> I think the main page needs to provide more of an overview. >> >> I think the first step needs to be to improve the projects-new >> documentation so it does not rely on the current project pages. >> >> Also I notice that it seems p-new relies on parsing >> http://people.apache.org/committer-index.html >> which in turn parses other data sources. >> >> That needs to be fixed. >> >> > Of course, I'm interested in your help to maintain the new projects site: >> > don't hesitate to comment on or change the code. >> > >> > Regards, >> > >> > Hervé >> > >> > Le dimanche 21 juin 2015 17:16:07 jan i a écrit : >> >> +1 switch as soon as possible, and then continue working on the data end. >> >> >> >> rgds >> >> jan i >> >> >> >> On Sunday, June 21, 2015, Hervé BOUTEMY wrote: >> >> > Le dimanche 21 juin 2015 15:54:29 jan i a écrit : >> >> > > On 21 June 2015 at 15:48, Daniel Gruno > >> > >> >> > > wrote: >> >> > > > On 2015-06-21 02:45, Hervé BOUTEMY wrote: >> >> > > >> for me, the new site is ready: there is of course room for >> >> > >> >> > improvements, >> >> > >> >> > > >> but >> >> > > >> it is stable and maintainable, waiting for contributions >> >> > > >> >> >> > > >> notice: I changed the wording to stop using "TLP", but use >> >> > > >> "Committee" >> >> > > >> instead, since TLP cause issues when trying to describe each >> >> > > >> projects >> >> > > >> (the >> >> > > >> software) as TLP or sub-projects >> >> > > >> >> >> > > >> >> >> > > >> when doing the switch, we'll need to rename current site as >> >> > > >> projects- >> >> > > >> old.apa
Re: Is https://projects-new.apache.org/ ready for prime time?
On 26 June 2015 at 08:12, Hervé BOUTEMY wrote: > that's why I want to switch projects to projects-old and projects-new to > projects: be able to work on extracting documentation from projects-old and > updating it to match the new location > If we wait too long, too many people start using projects-new. I do not think it is possible to make the perfect site, especially not in advance. > > I proposed http://svn.apache.org/viewvc/comdev/projects.apache.org/data/ > as > the new location of DOAP files lists (both PMC and projects) but got no > answer > ups, I did not see it as a question, but as a decision to which I had no objections. > > if we're ok with that new location, the next step is to stop modifying > equivalent files in > http://svn.apache.org/viewvc/infrastructure/site-tools/trunk/projects/ > (or even remove them) but point to the new location > > Of course, if ok with the new location, we can immediately add > committees.xml > and projects.xml pointers to https://projects-new.apache.org/about.html > IMHO the simple file names and location in about.html would make things > very > clear before diggin into more details on DOAP format and conventions (which > could be in the Wiki for ease of editing) > > > can we agree: > 1. on the new data location and content: > http://svn.apache.org/viewvc/comdev/projects.apache.org/data/ > +1 > > 2. on the switch then update of everything to match the new location (and > stop > updating projects-old) > +1 I do not have a lot of spare cycles due to apacheCON, but I am always availble if you need a bit of testing. rgds jan i. > > Regards, > > Hervé > > Le jeudi 25 juin 2015 09:17:32 vous avez écrit : > > On 25 June 2015 at 06:53, Hervé BOUTEMY wrote: > > > Sebb, > > > > > > as main maintainer of current http://projects.apache.org/ (AFAIK), > are you > > > ok with switching the url to the new service and renaming current > service > > > to projects-old (to let use time to continue content migration withotu > > > loosing anything)? Do you see any show stopper? > > > > The main item missing from projects-new is documentation - it > > currently points to projects. > > It's not immediately obvious how to provide data for the site. > > I think the main page needs to provide more of an overview. > > > > I think the first step needs to be to improve the projects-new > > documentation so it does not rely on the current project pages. > > > > Also I notice that it seems p-new relies on parsing > > http://people.apache.org/committer-index.html > > which in turn parses other data sources. > > > > That needs to be fixed. > > > > > Of course, I'm interested in your help to maintain the new projects > site: > > > don't hesitate to comment on or change the code. > > > > > > Regards, > > > > > > Hervé > > > > > > Le dimanche 21 juin 2015 17:16:07 jan i a écrit : > > >> +1 switch as soon as possible, and then continue working on the data > end. > > >> > > >> rgds > > >> jan i > > >> > > >> On Sunday, June 21, 2015, Hervé BOUTEMY > wrote: > > >> > Le dimanche 21 juin 2015 15:54:29 jan i a écrit : > > >> > > On 21 June 2015 at 15:48, Daniel Gruno > >> > > > >> > > wrote: > > >> > > > On 2015-06-21 02:45, Hervé BOUTEMY wrote: > > >> > > >> for me, the new site is ready: there is of course room for > > >> > > > >> > improvements, > > >> > > > >> > > >> but > > >> > > >> it is stable and maintainable, waiting for contributions > > >> > > >> > > >> > > >> notice: I changed the wording to stop using "TLP", but use > > >> > > >> "Committee" > > >> > > >> instead, since TLP cause issues when trying to describe each > > >> > > >> projects > > >> > > >> (the > > >> > > >> software) as TLP or sub-projects > > >> > > >> > > >> > > >> > > >> > > >> when doing the switch, we'll need to rename current site as > > >> > > >> projects- > > >> > > >> old.apache.org: there is some content to migrate (DOAP, > > >> > > > >> > documentation) > > >> > > > >> > > >
Re: Is https://projects-new.apache.org/ ready for prime time?
that's why I want to switch projects to projects-old and projects-new to projects: be able to work on extracting documentation from projects-old and updating it to match the new location I proposed http://svn.apache.org/viewvc/comdev/projects.apache.org/data/ as the new location of DOAP files lists (both PMC and projects) but got no answer if we're ok with that new location, the next step is to stop modifying equivalent files in http://svn.apache.org/viewvc/infrastructure/site-tools/trunk/projects/ (or even remove them) but point to the new location Of course, if ok with the new location, we can immediately add committees.xml and projects.xml pointers to https://projects-new.apache.org/about.html IMHO the simple file names and location in about.html would make things very clear before diggin into more details on DOAP format and conventions (which could be in the Wiki for ease of editing) can we agree: 1. on the new data location and content: http://svn.apache.org/viewvc/comdev/projects.apache.org/data/ 2. on the switch then update of everything to match the new location (and stop updating projects-old) Regards, Hervé Le jeudi 25 juin 2015 09:17:32 vous avez écrit : > On 25 June 2015 at 06:53, Hervé BOUTEMY wrote: > > Sebb, > > > > as main maintainer of current http://projects.apache.org/ (AFAIK), are you > > ok with switching the url to the new service and renaming current service > > to projects-old (to let use time to continue content migration withotu > > loosing anything)? Do you see any show stopper? > > The main item missing from projects-new is documentation - it > currently points to projects. > It's not immediately obvious how to provide data for the site. > I think the main page needs to provide more of an overview. > > I think the first step needs to be to improve the projects-new > documentation so it does not rely on the current project pages. > > Also I notice that it seems p-new relies on parsing > http://people.apache.org/committer-index.html > which in turn parses other data sources. > > That needs to be fixed. > > > Of course, I'm interested in your help to maintain the new projects site: > > don't hesitate to comment on or change the code. > > > > Regards, > > > > Hervé > > > > Le dimanche 21 juin 2015 17:16:07 jan i a écrit : > >> +1 switch as soon as possible, and then continue working on the data end. > >> > >> rgds > >> jan i > >> > >> On Sunday, June 21, 2015, Hervé BOUTEMY wrote: > >> > Le dimanche 21 juin 2015 15:54:29 jan i a écrit : > >> > > On 21 June 2015 at 15:48, Daniel Gruno >> > > >> > > wrote: > >> > > > On 2015-06-21 02:45, Hervé BOUTEMY wrote: > >> > > >> for me, the new site is ready: there is of course room for > >> > > >> > improvements, > >> > > >> > > >> but > >> > > >> it is stable and maintainable, waiting for contributions > >> > > >> > >> > > >> notice: I changed the wording to stop using "TLP", but use > >> > > >> "Committee" > >> > > >> instead, since TLP cause issues when trying to describe each > >> > > >> projects > >> > > >> (the > >> > > >> software) as TLP or sub-projects > >> > > >> > >> > > >> > >> > > >> when doing the switch, we'll need to rename current site as > >> > > >> projects- > >> > > >> old.apache.org: there is some content to migrate (DOAP, > >> > > >> > documentation) > >> > > >> > > >> associated to communication with projects on the changes that has > >> > > >> to > >> > > >> > be > >> > > >> > > >> decoupled from public vizualisation. I'll continue working on it. > >> > > >> > >> > > >> There one choice to do: continue serving the pages from current VM > >> > > >> or > >> > > >> serve > >> > > >> through standard resilient httpds. The VM is useful for cron jobs, > >> > > >> > but is > >> > > >> > > >> not > >> > > >> absolutely necessary for serving content since I removed online > >> > > >> > content > >> > > >> > > >> editing that caused the VM requirement for conte
Re: Is https://projects-new.apache.org/ ready for prime time?
oice). >> > >> > step by step, please: this will avoid confusion between independant topics >> > >> > switching without disturbing current conventions/knowledge is something >> > that >> > already takes a long time and energy: I know it because I put a lot of >> > energy >> > on it for a few monthes now! >> > >> > We started a discussion on this source format topic during april, and >> > AFAIK >> > nobody worked on it. >> > >> > What I'd like now is to switch: we can discuss later on what we want to >> > change >> > (and communication to every comittees this requires). >> > With the new site, we'll be able to change formats if we want, the only >> > requirement is to have json files for the visualization >> > >> > >> > >> > >> > Regards, >> > >> > Hervé >> > >> > > rgds >> > > jan i. >> > > >> > > > With regards, >> > > > Daniel. >> > > > >> > > >> but definitely, the site is ready for the switch >> > > >> >> > > >> Regards, >> > > >> >> > > >> Hervé >> > > >> >> > > >> Le vendredi 19 juin 2015 20:55:52 Sally Khudairi a écrit : >> > > >>> Hello Uli and the Apache ComDev team --I hope this message finds you >> > > >>> well. >> > > >>> Per below, I'm interested in promoting the new Projects page. >> > > >>> Can you please let me know if/when we're ready to do so? >> > > >>> Thanks so much, >> > > >>> Sally >> > > >>> >> > > >>> - Forwarded Message - >> > > >>> >> > > >>>From: David Nalley > >> > > >>> >> > > >>> To: Sally Khudairi > >> > > >>> >> > > >>> Cc: Daniel Gruno >; ASF >> > >> > Infrastructure >> > >> > > >>> > Sent: Friday, June 19, >> > >> > 2015 11:50 AM >> > >> > > >>> Subject: Re: Is https://projects-new.apache.org/ ready for prime >> > >> > time? >> > >> > > >>> Hi Sally: >> > > >>> >> > > >>> projects-new.apache.org is a ComDev managed resource, not an >> > > >>> infrastructure managed resource. I think the PMC has had a >> > > >>> discussion >> > > >>> or two about when to migrate projects-new to projects.a.o >> > > >>> >> > > >>> --David >> > > >>> >> > > >>> >> > > >>> >> > > >>> On Fri, Jun 19, 2015 at 11:30 AM, Sally Khudairi >> > > >>> >> > > >>> > wrote: >> > > >>>> Hello Daniel and David --I hope you are both well. >> > > >>>> >> > > >>>> >> > > >>>> I was wondering if the new Projects page at >> > > >>>> >> > > >>>> https://projects-new.apache.org/ >> > > >>>> >> > > >>>> was ready to be publicly deployed/announced/promoted. >> > > >>>> >> > > >>>> There's so much great information there and it's an incredible >> > >> > resource >> > >> > > >>>> (I >> > > >>>> use it every week for the News Round-ups and we relied on it for >> > > >>>> the >> > > >>>> Annual Report), if there's no reason why it should still be in >> > >> > stealth >> > >> > > >>>> mode, I'd like to shout out about it from the rooftops. >> > > >>>> >> > > >>>> Just let me know if we're good to go and if there are any >> > > >>>> disclaimers/caveats we should be aware of. >> > > >>>> >> > > >>>> Warm thanks, >> > > >>>> Sally >> > > >>>> >> > > >>>> >> > > >>>> = = = = = >> > > >>>> vox +1 617 921 8656 >> > > >>>> off2 +1 646 583 3362 >> > > >>>> skype sallykhudairi >
Re: Is https://projects-new.apache.org/ ready for prime time?
Sebb, as main maintainer of current http://projects.apache.org/ (AFAIK), are you ok with switching the url to the new service and renaming current service to projects-old (to let use time to continue content migration withotu loosing anything)? Do you see any show stopper? Of course, I'm interested in your help to maintain the new projects site: don't hesitate to comment on or change the code. Regards, Hervé Le dimanche 21 juin 2015 17:16:07 jan i a écrit : > +1 switch as soon as possible, and then continue working on the data end. > > rgds > jan i > > On Sunday, June 21, 2015, Hervé BOUTEMY wrote: > > Le dimanche 21 juin 2015 15:54:29 jan i a écrit : > > > On 21 June 2015 at 15:48, Daniel Gruno > > > > wrote: > > > > On 2015-06-21 02:45, Hervé BOUTEMY wrote: > > > >> for me, the new site is ready: there is of course room for > > > > improvements, > > > > > >> but > > > >> it is stable and maintainable, waiting for contributions > > > >> > > > >> notice: I changed the wording to stop using "TLP", but use > > > >> "Committee" > > > >> instead, since TLP cause issues when trying to describe each projects > > > >> (the > > > >> software) as TLP or sub-projects > > > >> > > > >> > > > >> when doing the switch, we'll need to rename current site as projects- > > > >> old.apache.org: there is some content to migrate (DOAP, > > > > documentation) > > > > > >> associated to communication with projects on the changes that has to > > > > be > > > > > >> decoupled from public vizualisation. I'll continue working on it. > > > >> > > > >> There one choice to do: continue serving the pages from current VM or > > > >> serve > > > >> through standard resilient httpds. The VM is useful for cron jobs, > > > > but is > > > > > >> not > > > >> absolutely necessary for serving content since I removed online > > > > content > > > > > >> editing that caused the VM requirement for content serving AFAIK. > > > > Using > > > > > >> standard httpd will avoid SPOF or eventual load issue. > > > > > > > > What do you mean by 'standard httpd'? It already uses...standard httpd > > > > for > > > > > > serving the site. > > > > The cron jobs are needed for updating various statistics and data on > > > > the > > > > > > site, they can't just be shut off - they also power > > > > reporter.apache.org. > > > > > Maybe I misunderstood something, I understood that we are using httpd, > > > > but > > > > > in our own vm. In my opinion it would be nicer to use the www.a.o httpd > > > (sorry > > > vms have been changing lately so I am not sure where it runs), since > > > that > > > would put httpd maintenance on infra instead of comdev. > > > > +1 > > that was what I mean by "standard httpd" (ie not the binary but the > > machines > > where it runs) > > > > > > I think the site is ready for a more prominent role, but I find this > > > > discussion confusing, and I find it somewhat sad that we're gonna > > > > stick > > > > with something as arcane as DOAP. > > > > > > +100 !! > > > > > > DOAP == Dead On Arrival Permanently :-) JSON == Jump Simply On New > > > (but I know I am only 1 voice). > > > > step by step, please: this will avoid confusion between independant topics > > > > switching without disturbing current conventions/knowledge is something > > that > > already takes a long time and energy: I know it because I put a lot of > > energy > > on it for a few monthes now! > > > > We started a discussion on this source format topic during april, and > > AFAIK > > nobody worked on it. > > > > What I'd like now is to switch: we can discuss later on what we want to > > change > > (and communication to every comittees this requires). > > With the new site, we'll be able to change formats if we want, the only > > requirement is to have json files for the visualization > > > > > > > > > > Regards, > > > > Hervé > > > > > rgds > > > j
Re: Format for project data: DOAP/JSON/other (was: Is https://projects-new.apache.org/ ready for prime time?)
from my experience when working on the topic, what was very confusing was PMC descriptors vs projects DOAP files, and the fact that everything was mixed in code [1] Then I just copied content in projects-new data directory and renamed things to be clear about these 2 types of descriptors [2]: IMHO, this will already help a lot Another thing I did is that Python scripts that parse descriptors (projects and committees) to generate json files also copy .rdf files in /doap/{committeeId} [3] Last thing at the moment: once again, I'm not a DOAP expert, and there seem to be semantic web experts in ASF who should help others better understand how to use that. But at the moment, the format seems really not well understood by a vast majority of people, even if some advanced rdf files [4] show what can be done Regards, Hervé [1] http://svn.apache.org/viewvc/infrastructure/site-tools/trunk/projects/ [2] http://svn.apache.org/viewvc/comdev/projects.apache.org/data/ [3] https://projects-new.apache.org/doap/ http://svn.apache.org/viewvc/comdev/projects.apache.org/site/doap/ [4] http://svn.apache.org/repos/asf/oltu/site/doap_org.apache.oltu.parent.rdf Le dimanche 21 juin 2015 16:29:19 sebb a écrit : > [Starting thread with new subject] > > On 21 June 2015 at 16:03, Hervé BOUTEMY wrote: > > Le dimanche 21 juin 2015 15:54:29 jan i a écrit : > >> On 21 June 2015 at 15:48, Daniel Gruno wrote: > >> > I think the site is ready for a more prominent role, but I find this > >> > discussion confusing, and I find it somewhat sad that we're gonna stick > >> > with something as arcane as DOAP. > >> > >> +100 !! > >> > >> DOAP == Dead On Arrival Permanently :-) JSON == Jump Simply On New > >> (but I know I am only 1 voice). > > > > step by step, please: this will avoid confusion between independant topics > > > > switching without disturbing current conventions/knowledge is something > > that already takes a long time and energy: I know it because I put a lot > > of energy on it for a few monthes now! > > > > We started a discussion on this source format topic during april, and > > AFAIK > > nobody worked on it. > > > > What I'd like now is to switch: we can discuss later on what we want to > > change (and communication to every comittees this requires). > > With the new site, we'll be able to change formats if we want, the only > > requirement is to have json files for the visualization > > Some PMCs are very responsive to requests to maintain DOAP files; > others take months and multiple reminders even for a simple fix. This > does not directly affect the format used to hold the data. However it > does mean that changing to a new format is likely to take a lot of > time and involve a lot of work. Meanwhile the code will need to > continue to support the old format. > > It would however be an opportunity to make some improvements. For example: > - we could be more specific about the data that really needs to be > maintained by PMCs > - we could require that the files are stored in a well-known place, > rather than requiring an index file to find them.
Re: Fw: Is https://projects-new.apache.org/ ready for prime time?
:-D OK --glad we're cool. [From the mobile; please excuse top-posting, spelling/spacing errors, and brevity] - Reply message - From: "Roman Shaposhnik" To: "ComDev" , "Sally Khudairi" Cc: "David Crossley" Subject: Fw: Is https://projects-new.apache.org/ ready for prime time? Date: Sun, Jun 21, 2015 16:37 On Sun, Jun 21, 2015 at 1:24 PM, Sally Khudairi wrote: > Thanks, Roman. > To be clear, my statement was not intended to be an attack of any kind! I really didn't read it like that! Just felt like clarifying, I guess ;-) Thanks, Roman.
Re: Is https://projects-new.apache.org/ ready for prime time?
For example, Which species or type of animal, where it is native to, the various nests, mating seasons, colors. Through an interactive viewing ai similar to the window zoomed in on the animal. Aaron D. Gordon Jr. > On Jun 21, 2015, at 1:37 PM, Roman Shaposhnik wrote: > >> On Sun, Jun 21, 2015 at 1:24 PM, Sally Khudairi wrote: >> Thanks, Roman. >> To be clear, my statement was not intended to be an attack of any kind! > > I really didn't read it like that! Just felt like clarifying, I guess ;-) > > Thanks, > Roman.
Re: Fw: Is https://projects-new.apache.org/ ready for prime time?
On Sun, Jun 21, 2015 at 1:24 PM, Sally Khudairi wrote: > Thanks, Roman. > To be clear, my statement was not intended to be an attack of any kind! I really didn't read it like that! Just felt like clarifying, I guess ;-) Thanks, Roman.
Re: Is https://projects-new.apache.org/ ready for prime time?
That would auto inform photographs, text, words..yeah. Aaron D. Gordon Jr. > On Jun 21, 2015, at 1:25 PM, Aaron Gordon Jr. wrote: > > What about a native informative app? > > Aaron D. Gordon Jr. > >> On Jun 21, 2015, at 1:24 PM, Sally Khudairi wrote: >> >> Thanks, Roman. >> To be clear, my statement was not intended to be an attack of any kind! Just >> stating what had come across @TheASF "notifications" thread on Twitter. >> Cheers,Sally >> >> From: Roman Shaposhnik >> To: ComDev >> Cc: David Crossley ; Sally Khudairi >> Sent: Sunday, June 21, 2015 4:20 PM >> Subject: Re: Fw: Is https://projects-new.apache.org/ ready for prime time? >> >> On Sat, Jun 20, 2015 at 3:34 AM, Sally Khudairi >> wrote: >>> Thanks, David! >>> >>> I noticed that Roman tweeted the link yesterday, so I guess the cat is out >>> of the bag, as the saying goes. >> >> Btw, the reason I tweeted a 'beta' URL is to get feedback. >> >> Thanks, >> Roman. >> >>
Re: Format for project data: DOAP/JSON/other (was: Is https://projects-new.apache.org/ ready for prime time?)
On Sun, Jun 21, 2015 at 11:29 AM, sebb wrote: > [Starting thread with new subject] > > On 21 June 2015 at 16:03, Hervé BOUTEMY wrote: >> Le dimanche 21 juin 2015 15:54:29 jan i a écrit : >>> On 21 June 2015 at 15:48, Daniel Gruno wrote: >>> > I think the site is ready for a more prominent role, but I find this >>> > discussion confusing, and I find it somewhat sad that we're gonna stick >>> > with something as arcane as DOAP. >>> >>> +100 !! >>> >>> DOAP == Dead On Arrival Permanently :-) JSON == Jump Simply On New >>> (but I know I am only 1 voice). >> step by step, please: this will avoid confusion between independant topics >> >> switching without disturbing current conventions/knowledge is something that >> already takes a long time and energy: I know it because I put a lot of energy >> on it for a few monthes now! >> >> We started a discussion on this source format topic during april, and AFAIK >> nobody worked on it. >> >> What I'd like now is to switch: we can discuss later on what we want to >> change >> (and communication to every comittees this requires). >> With the new site, we'll be able to change formats if we want, the only >> requirement is to have json files for the visualization > > Some PMCs are very responsive to requests to maintain DOAP files; > others take months and multiple reminders even for a simple fix. This > does not directly affect the format used to hold the data. However it > does mean that changing to a new format is likely to take a lot of > time and involve a lot of work. Meanwhile the code will need to > continue to support the old format. > > It would however be an opportunity to make some improvements. For example: > - we could be more specific about the data that really needs to be > maintained by PMCs > - we could require that the files are stored in a well-known place, > rather than requiring an index file to find them. Personally, I'd like to see a nice web interface for a project's "profile", akin to social media profiles or one's personal profile at nearly every site on the web. Whatever file format is used behind the scenes shouldn't matter for PMCs. I think projects-new started us off in the right direction, essentially doing this for release information, but really everything about a project could be contained in a profile managed by a web interface of this type. I don't think adding requirements to these files (like a well-known location) are going to make them more maintainable for PMCs. It's just going to be one more thing for them to remember to get right for something which is relatively rarely edited. It'd be much easier to make projects.apache.org be for projects what id.apache.org is for committers. For comparison, Fedora seems to do a decent job of providing a consistent web view of all aspects of a project: https://apps.fedoraproject.org/packages/java-1.8.0-openjdk . There's actually several different views, but in general, there's links to contributors, upstream project page, builds, bug tracker, "updates" (analogous to releases), source, etc. I realize Apache projects aren't as homogeneous as package management in Fedora, which makes things a bit difficult for us, but I do think there's probably some lessons to be gained. For one, most of those web views are auto-generated, based on maintainer and user actions (like triggering an update, filing a bug, applying a patch, or retiring a package). As such, these interfaces tend not to be editable. However, one can pretty easily imagine similar project profile pages which are editable by a PMC. However, I'm not really all that familiar with the historical need for DOAP files, what tools actually use them, or the historical preferences for maintaining them. So, I admittedly may not fully grasp the scope of the problem/changes being discussed. I'm just thinking that if we can get rid of the requirement for PMCs to maintain them (in favor of a web-interface way for PMCs to describe all aspects of their projects), then I'd like that. -- Christopher L Tubbs II http://gravatar.com/ctubbsii
Re: Is https://projects-new.apache.org/ ready for prime time?
What about a native informative app? Aaron D. Gordon Jr. > On Jun 21, 2015, at 1:24 PM, Sally Khudairi wrote: > > Thanks, Roman. > To be clear, my statement was not intended to be an attack of any kind! Just > stating what had come across @TheASF "notifications" thread on Twitter. > Cheers,Sally > > From: Roman Shaposhnik > To: ComDev > Cc: David Crossley ; Sally Khudairi > Sent: Sunday, June 21, 2015 4:20 PM > Subject: Re: Fw: Is https://projects-new.apache.org/ ready for prime time? > > On Sat, Jun 20, 2015 at 3:34 AM, Sally Khudairi > wrote: >> Thanks, David! >> >> I noticed that Roman tweeted the link yesterday, so I guess the cat is out >> of the bag, as the saying goes. > > Btw, the reason I tweeted a 'beta' URL is to get feedback. > > Thanks, > Roman. > >
Re: Fw: Is https://projects-new.apache.org/ ready for prime time?
Thanks, Roman. To be clear, my statement was not intended to be an attack of any kind! Just stating what had come across @TheASF "notifications" thread on Twitter. Cheers,Sally From: Roman Shaposhnik To: ComDev Cc: David Crossley ; Sally Khudairi Sent: Sunday, June 21, 2015 4:20 PM Subject: Re: Fw: Is https://projects-new.apache.org/ ready for prime time? On Sat, Jun 20, 2015 at 3:34 AM, Sally Khudairi wrote: > Thanks, David! > > I noticed that Roman tweeted the link yesterday, so I guess the cat is out of > the bag, as the saying goes. Btw, the reason I tweeted a 'beta' URL is to get feedback. Thanks, Roman.
Re: Fw: Is https://projects-new.apache.org/ ready for prime time?
On Sat, Jun 20, 2015 at 3:34 AM, Sally Khudairi wrote: > Thanks, David! > > I noticed that Roman tweeted the link yesterday, so I guess the cat is out of > the bag, as the saying goes. Btw, the reason I tweeted a 'beta' URL is to get feedback. Thanks, Roman.
Format for project data: DOAP/JSON/other (was: Is https://projects-new.apache.org/ ready for prime time?)
[Starting thread with new subject] On 21 June 2015 at 16:03, Hervé BOUTEMY wrote: > Le dimanche 21 juin 2015 15:54:29 jan i a écrit : >> On 21 June 2015 at 15:48, Daniel Gruno wrote: >> > I think the site is ready for a more prominent role, but I find this >> > discussion confusing, and I find it somewhat sad that we're gonna stick >> > with something as arcane as DOAP. >> >> +100 !! >> >> DOAP == Dead On Arrival Permanently :-) JSON == Jump Simply On New >> (but I know I am only 1 voice). > step by step, please: this will avoid confusion between independant topics > > switching without disturbing current conventions/knowledge is something that > already takes a long time and energy: I know it because I put a lot of energy > on it for a few monthes now! > > We started a discussion on this source format topic during april, and AFAIK > nobody worked on it. > > What I'd like now is to switch: we can discuss later on what we want to change > (and communication to every comittees this requires). > With the new site, we'll be able to change formats if we want, the only > requirement is to have json files for the visualization Some PMCs are very responsive to requests to maintain DOAP files; others take months and multiple reminders even for a simple fix. This does not directly affect the format used to hold the data. However it does mean that changing to a new format is likely to take a lot of time and involve a lot of work. Meanwhile the code will need to continue to support the old format. It would however be an opportunity to make some improvements. For example: - we could be more specific about the data that really needs to be maintained by PMCs - we could require that the files are stored in a well-known place, rather than requiring an index file to find them.
Re: Is https://projects-new.apache.org/ ready for prime time?
+1 switch as soon as possible, and then continue working on the data end. rgds jan i On Sunday, June 21, 2015, Hervé BOUTEMY wrote: > Le dimanche 21 juin 2015 15:54:29 jan i a écrit : > > On 21 June 2015 at 15:48, Daniel Gruno > wrote: > > > On 2015-06-21 02:45, Hervé BOUTEMY wrote: > > >> for me, the new site is ready: there is of course room for > improvements, > > >> but > > >> it is stable and maintainable, waiting for contributions > > >> > > >> notice: I changed the wording to stop using "TLP", but use "Committee" > > >> instead, since TLP cause issues when trying to describe each projects > > >> (the > > >> software) as TLP or sub-projects > > >> > > >> > > >> when doing the switch, we'll need to rename current site as projects- > > >> old.apache.org: there is some content to migrate (DOAP, > documentation) > > >> associated to communication with projects on the changes that has to > be > > >> decoupled from public vizualisation. I'll continue working on it. > > >> > > >> There one choice to do: continue serving the pages from current VM or > > >> serve > > >> through standard resilient httpds. The VM is useful for cron jobs, > but is > > >> not > > >> absolutely necessary for serving content since I removed online > content > > >> editing that caused the VM requirement for content serving AFAIK. > Using > > >> standard httpd will avoid SPOF or eventual load issue. > > > > > > What do you mean by 'standard httpd'? It already uses...standard httpd > for > > > serving the site. > > > The cron jobs are needed for updating various statistics and data on > the > > > site, they can't just be shut off - they also power > reporter.apache.org. > > > > Maybe I misunderstood something, I understood that we are using httpd, > but > > in our own vm. In my opinion it would be nicer to use the www.a.o httpd > > (sorry > > vms have been changing lately so I am not sure where it runs), since that > > would put httpd maintenance on infra instead of comdev. > +1 > that was what I mean by "standard httpd" (ie not the binary but the > machines > where it runs) > > > > > > > I think the site is ready for a more prominent role, but I find this > > > discussion confusing, and I find it somewhat sad that we're gonna stick > > > with something as arcane as DOAP. > > > > +100 !! > > > > DOAP == Dead On Arrival Permanently :-) JSON == Jump Simply On New > > (but I know I am only 1 voice). > step by step, please: this will avoid confusion between independant topics > > switching without disturbing current conventions/knowledge is something > that > already takes a long time and energy: I know it because I put a lot of > energy > on it for a few monthes now! > > We started a discussion on this source format topic during april, and AFAIK > nobody worked on it. > > What I'd like now is to switch: we can discuss later on what we want to > change > (and communication to every comittees this requires). > With the new site, we'll be able to change formats if we want, the only > requirement is to have json files for the visualization > > > Regards, > > Hervé > > > > > rgds > > jan i. > > > > > With regards, > > > Daniel. > > > > > >> but definitely, the site is ready for the switch > > >> > > >> Regards, > > >> > > >> Hervé > > >> > > >> Le vendredi 19 juin 2015 20:55:52 Sally Khudairi a écrit : > > >>> Hello Uli and the Apache ComDev team --I hope this message finds you > > >>> well. > > >>> Per below, I'm interested in promoting the new Projects page. > > >>> Can you please let me know if/when we're ready to do so? > > >>> Thanks so much, > > >>> Sally > > >>> > > >>> - Forwarded Message - > > >>> > > >>>From: David Nalley > > > >>> > > >>> To: Sally Khudairi > > > >>> > > >>> Cc: Daniel Gruno >; ASF > Infrastructure > > >>> > Sent: Friday, June 19, > 2015 11:50 AM > > >>> > > >>> Subject: Re: Is https://projects-new.apache.org/ ready for prime > time? > > >>> > >
Re: Fw: Is https://projects-new.apache.org/ ready for prime time?
Le dimanche 21 juin 2015 15:54:29 jan i a écrit : > On 21 June 2015 at 15:48, Daniel Gruno wrote: > > On 2015-06-21 02:45, Hervé BOUTEMY wrote: > >> for me, the new site is ready: there is of course room for improvements, > >> but > >> it is stable and maintainable, waiting for contributions > >> > >> notice: I changed the wording to stop using "TLP", but use "Committee" > >> instead, since TLP cause issues when trying to describe each projects > >> (the > >> software) as TLP or sub-projects > >> > >> > >> when doing the switch, we'll need to rename current site as projects- > >> old.apache.org: there is some content to migrate (DOAP, documentation) > >> associated to communication with projects on the changes that has to be > >> decoupled from public vizualisation. I'll continue working on it. > >> > >> There one choice to do: continue serving the pages from current VM or > >> serve > >> through standard resilient httpds. The VM is useful for cron jobs, but is > >> not > >> absolutely necessary for serving content since I removed online content > >> editing that caused the VM requirement for content serving AFAIK. Using > >> standard httpd will avoid SPOF or eventual load issue. > > > > What do you mean by 'standard httpd'? It already uses...standard httpd for > > serving the site. > > The cron jobs are needed for updating various statistics and data on the > > site, they can't just be shut off - they also power reporter.apache.org. > > Maybe I misunderstood something, I understood that we are using httpd, but > in our own vm. In my opinion it would be nicer to use the www.a.o httpd > (sorry > vms have been changing lately so I am not sure where it runs), since that > would put httpd maintenance on infra instead of comdev. +1 that was what I mean by "standard httpd" (ie not the binary but the machines where it runs) > > > I think the site is ready for a more prominent role, but I find this > > discussion confusing, and I find it somewhat sad that we're gonna stick > > with something as arcane as DOAP. > > +100 !! > > DOAP == Dead On Arrival Permanently :-) JSON == Jump Simply On New > (but I know I am only 1 voice). step by step, please: this will avoid confusion between independant topics switching without disturbing current conventions/knowledge is something that already takes a long time and energy: I know it because I put a lot of energy on it for a few monthes now! We started a discussion on this source format topic during april, and AFAIK nobody worked on it. What I'd like now is to switch: we can discuss later on what we want to change (and communication to every comittees this requires). With the new site, we'll be able to change formats if we want, the only requirement is to have json files for the visualization Regards, Hervé > > rgds > jan i. > > > With regards, > > Daniel. > > > >> but definitely, the site is ready for the switch > >> > >> Regards, > >> > >> Hervé > >> > >> Le vendredi 19 juin 2015 20:55:52 Sally Khudairi a écrit : > >>> Hello Uli and the Apache ComDev team --I hope this message finds you > >>> well. > >>> Per below, I'm interested in promoting the new Projects page. > >>> Can you please let me know if/when we're ready to do so? > >>> Thanks so much, > >>> Sally > >>> > >>> - Forwarded Message - > >>> > >>>From: David Nalley > >>> > >>> To: Sally Khudairi > >>> > >>> Cc: Daniel Gruno ; ASF Infrastructure > >>> Sent: Friday, June 19, 2015 11:50 AM > >>> > >>> Subject: Re: Is https://projects-new.apache.org/ ready for prime time? > >>> > >>> Hi Sally: > >>> > >>> projects-new.apache.org is a ComDev managed resource, not an > >>> infrastructure managed resource. I think the PMC has had a discussion > >>> or two about when to migrate projects-new to projects.a.o > >>> > >>> --David > >>> > >>> > >>> > >>> On Fri, Jun 19, 2015 at 11:30 AM, Sally Khudairi > >>> > >>> wrote: > >>>> Hello Daniel and David --I hope you are both well. > >>>> > >>>> > >>>> I was wondering if the new Projects page at > >>>> > >>>> https://projects-new.apache.org/ > >>>> > >>>> was ready to be publicly deployed/announced/promoted. > >>>> > >>>> There's so much great information there and it's an incredible resource > >>>> (I > >>>> use it every week for the News Round-ups and we relied on it for the > >>>> Annual Report), if there's no reason why it should still be in stealth > >>>> mode, I'd like to shout out about it from the rooftops. > >>>> > >>>> Just let me know if we're good to go and if there are any > >>>> disclaimers/caveats we should be aware of. > >>>> > >>>> Warm thanks, > >>>> Sally > >>>> > >>>> > >>>> = = = = = > >>>> vox +1 617 921 8656 > >>>> off2 +1 646 583 3362 > >>>> skype sallykhudairi
Re: Fw: Is https://projects-new.apache.org/ ready for prime time?
On 21 June 2015 at 15:48, Daniel Gruno wrote: > > > On 2015-06-21 02:45, Hervé BOUTEMY wrote: > >> for me, the new site is ready: there is of course room for improvements, >> but >> it is stable and maintainable, waiting for contributions >> >> notice: I changed the wording to stop using "TLP", but use "Committee" >> instead, since TLP cause issues when trying to describe each projects (the >> software) as TLP or sub-projects >> >> >> when doing the switch, we'll need to rename current site as projects- >> old.apache.org: there is some content to migrate (DOAP, documentation) >> associated to communication with projects on the changes that has to be >> decoupled from public vizualisation. I'll continue working on it. >> >> There one choice to do: continue serving the pages from current VM or >> serve >> through standard resilient httpds. The VM is useful for cron jobs, but is >> not >> absolutely necessary for serving content since I removed online content >> editing that caused the VM requirement for content serving AFAIK. Using >> standard httpd will avoid SPOF or eventual load issue. >> > What do you mean by 'standard httpd'? It already uses...standard httpd for > serving the site. > The cron jobs are needed for updating various statistics and data on the > site, they can't just be shut off - they also power reporter.apache.org. > Maybe I misunderstood something, I understood that we are using httpd, but in our own vm. In my opinion it would be nicer to use the www.a.o httpd (sorry vms have been changing lately so I am not sure where it runs), since that would put httpd maintenance on infra instead of comdev. > > I think the site is ready for a more prominent role, but I find this > discussion confusing, and I find it somewhat sad that we're gonna stick > with something as arcane as DOAP. > +100 !! DOAP == Dead On Arrival Permanently :-) JSON == Jump Simply On New (but I know I am only 1 voice). rgds jan i. > > With regards, > Daniel. > > >> >> but definitely, the site is ready for the switch >> >> Regards, >> >> Hervé >> >> Le vendredi 19 juin 2015 20:55:52 Sally Khudairi a écrit : >> >>> Hello Uli and the Apache ComDev team --I hope this message finds you >>> well. >>> Per below, I'm interested in promoting the new Projects page. >>> Can you please let me know if/when we're ready to do so? >>> Thanks so much, >>> Sally >>> >>> - Forwarded Message - >>>From: David Nalley >>> To: Sally Khudairi >>> Cc: Daniel Gruno ; ASF Infrastructure >>> Sent: Friday, June 19, 2015 11:50 AM >>> Subject: Re: Is https://projects-new.apache.org/ ready for prime time? >>> >>> Hi Sally: >>> >>> projects-new.apache.org is a ComDev managed resource, not an >>> infrastructure managed resource. I think the PMC has had a discussion >>> or two about when to migrate projects-new to projects.a.o >>> >>> --David >>> >>> >>> >>> On Fri, Jun 19, 2015 at 11:30 AM, Sally Khudairi >>> >>> wrote: >>> >>>> Hello Daniel and David --I hope you are both well. >>>> >>>> >>>> I was wondering if the new Projects page at >>>> >>>> https://projects-new.apache.org/ >>>> >>>> was ready to be publicly deployed/announced/promoted. >>>> >>>> There's so much great information there and it's an incredible resource >>>> (I >>>> use it every week for the News Round-ups and we relied on it for the >>>> Annual Report), if there's no reason why it should still be in stealth >>>> mode, I'd like to shout out about it from the rooftops. >>>> >>>> Just let me know if we're good to go and if there are any >>>> disclaimers/caveats we should be aware of. >>>> >>>> Warm thanks, >>>> Sally >>>> >>>> >>>> = = = = = >>>> vox +1 617 921 8656 >>>> off2 +1 646 583 3362 >>>> skype sallykhudairi >>>> >>> >
Re: Fw: Is https://projects-new.apache.org/ ready for prime time?
On 2015-06-21 02:45, Hervé BOUTEMY wrote: for me, the new site is ready: there is of course room for improvements, but it is stable and maintainable, waiting for contributions notice: I changed the wording to stop using "TLP", but use "Committee" instead, since TLP cause issues when trying to describe each projects (the software) as TLP or sub-projects when doing the switch, we'll need to rename current site as projects- old.apache.org: there is some content to migrate (DOAP, documentation) associated to communication with projects on the changes that has to be decoupled from public vizualisation. I'll continue working on it. There one choice to do: continue serving the pages from current VM or serve through standard resilient httpds. The VM is useful for cron jobs, but is not absolutely necessary for serving content since I removed online content editing that caused the VM requirement for content serving AFAIK. Using standard httpd will avoid SPOF or eventual load issue. What do you mean by 'standard httpd'? It already uses...standard httpd for serving the site. The cron jobs are needed for updating various statistics and data on the site, they can't just be shut off - they also power reporter.apache.org. I think the site is ready for a more prominent role, but I find this discussion confusing, and I find it somewhat sad that we're gonna stick with something as arcane as DOAP. With regards, Daniel. but definitely, the site is ready for the switch Regards, Hervé Le vendredi 19 juin 2015 20:55:52 Sally Khudairi a écrit : Hello Uli and the Apache ComDev team --I hope this message finds you well. Per below, I'm interested in promoting the new Projects page. Can you please let me know if/when we're ready to do so? Thanks so much, Sally - Forwarded Message - From: David Nalley To: Sally Khudairi Cc: Daniel Gruno ; ASF Infrastructure Sent: Friday, June 19, 2015 11:50 AM Subject: Re: Is https://projects-new.apache.org/ ready for prime time? Hi Sally: projects-new.apache.org is a ComDev managed resource, not an infrastructure managed resource. I think the PMC has had a discussion or two about when to migrate projects-new to projects.a.o --David On Fri, Jun 19, 2015 at 11:30 AM, Sally Khudairi wrote: Hello Daniel and David --I hope you are both well. I was wondering if the new Projects page at https://projects-new.apache.org/ was ready to be publicly deployed/announced/promoted. There's so much great information there and it's an incredible resource (I use it every week for the News Round-ups and we relied on it for the Annual Report), if there's no reason why it should still be in stealth mode, I'd like to shout out about it from the rooftops. Just let me know if we're good to go and if there are any disclaimers/caveats we should be aware of. Warm thanks, Sally = = = = = vox +1 617 921 8656 off2 +1 646 583 3362 skype sallykhudairi
Re: Is https://projects-new.apache.org/ ready for prime time?
On Sunday, June 21, 2015, Hervé BOUTEMY wrote: > for me, the new site is ready: there is of course room for improvements, > but > it is stable and maintainable, waiting for contributions > > notice: I changed the wording to stop using "TLP", but use "Committee" > instead, since TLP cause issues when trying to describe each projects (the > software) as TLP or sub-projects > > > when doing the switch, we'll need to rename current site as projects- > old.apache.org: there is some content to migrate (DOAP, documentation) > associated to communication with projects on the changes that has to be > decoupled from public vizualisation. I'll continue working on it. > > There one choice to do: continue serving the pages from current VM or serve > through standard resilient httpds. The VM is useful for cron jobs, but is > not > absolutely necessary for serving content since I removed online content > editing that caused the VM requirement for content serving AFAIK. Using > standard httpd will avoid SPOF or eventual load issue. +1 to move to standard httpd instead of the vm. rgds jan i > > > but definitely, the site is ready for the switch > > Regards, > > Hervé > > Le vendredi 19 juin 2015 20:55:52 Sally Khudairi a écrit : > > Hello Uli and the Apache ComDev team --I hope this message finds you > well. > > Per below, I'm interested in promoting the new Projects page. > > Can you please let me know if/when we're ready to do so? > > Thanks so much, > > Sally > > > > - Forwarded Message - > > From: David Nalley > > > To: Sally Khudairi > > > Cc: Daniel Gruno >; ASF > Infrastructure > > > Sent: Friday, June 19, 2015 > 11:50 AM > > Subject: Re: Is https://projects-new.apache.org/ ready for prime time? > > > > Hi Sally: > > > > projects-new.apache.org is a ComDev managed resource, not an > > infrastructure managed resource. I think the PMC has had a discussion > > or two about when to migrate projects-new to projects.a.o > > > > --David > > > > > > > > On Fri, Jun 19, 2015 at 11:30 AM, Sally Khudairi > > > > > wrote: > > > Hello Daniel and David --I hope you are both well. > > > > > > > > > I was wondering if the new Projects page at > > > > > > https://projects-new.apache.org/ > > > > > > was ready to be publicly deployed/announced/promoted. > > > > > > There's so much great information there and it's an incredible > resource (I > > > use it every week for the News Round-ups and we relied on it for the > > > Annual Report), if there's no reason why it should still be in stealth > > > mode, I'd like to shout out about it from the rooftops. > > > > > > Just let me know if we're good to go and if there are any > > > disclaimers/caveats we should be aware of. > > > > > > Warm thanks, > > > Sally > > > > > > > > > = = = = = > > > vox +1 617 921 8656 > > > off2 +1 646 583 3362 > > > skype sallykhudairi > > -- Sent from My iPad, sorry for any misspellings.
Re: Fw: Is https://projects-new.apache.org/ ready for prime time?
for me, the new site is ready: there is of course room for improvements, but it is stable and maintainable, waiting for contributions notice: I changed the wording to stop using "TLP", but use "Committee" instead, since TLP cause issues when trying to describe each projects (the software) as TLP or sub-projects when doing the switch, we'll need to rename current site as projects- old.apache.org: there is some content to migrate (DOAP, documentation) associated to communication with projects on the changes that has to be decoupled from public vizualisation. I'll continue working on it. There one choice to do: continue serving the pages from current VM or serve through standard resilient httpds. The VM is useful for cron jobs, but is not absolutely necessary for serving content since I removed online content editing that caused the VM requirement for content serving AFAIK. Using standard httpd will avoid SPOF or eventual load issue. but definitely, the site is ready for the switch Regards, Hervé Le vendredi 19 juin 2015 20:55:52 Sally Khudairi a écrit : > Hello Uli and the Apache ComDev team --I hope this message finds you well. > Per below, I'm interested in promoting the new Projects page. > Can you please let me know if/when we're ready to do so? > Thanks so much, > Sally > > - Forwarded Message - > From: David Nalley > To: Sally Khudairi > Cc: Daniel Gruno ; ASF Infrastructure > Sent: Friday, June 19, 2015 11:50 AM > Subject: Re: Is https://projects-new.apache.org/ ready for prime time? > > Hi Sally: > > projects-new.apache.org is a ComDev managed resource, not an > infrastructure managed resource. I think the PMC has had a discussion > or two about when to migrate projects-new to projects.a.o > > --David > > > > On Fri, Jun 19, 2015 at 11:30 AM, Sally Khudairi > > wrote: > > Hello Daniel and David --I hope you are both well. > > > > > > I was wondering if the new Projects page at > > > > https://projects-new.apache.org/ > > > > was ready to be publicly deployed/announced/promoted. > > > > There's so much great information there and it's an incredible resource (I > > use it every week for the News Round-ups and we relied on it for the > > Annual Report), if there's no reason why it should still be in stealth > > mode, I'd like to shout out about it from the rooftops. > > > > Just let me know if we're good to go and if there are any > > disclaimers/caveats we should be aware of. > > > > Warm thanks, > > Sally > > > > > > = = = = = > > vox +1 617 921 8656 > > off2 +1 646 583 3362 > > skype sallykhudairi
Re: Fw: Is https://projects-new.apache.org/ ready for prime time?
sallykhuda...@yahoo.com On Jun 20, 2015 8:23 AM, "Sally Khudairi" wrote: > > Fab! Thanks so much, Roman. > > Bon weekend, > Sally > > > [From the mobile; please excuse top-posting, spelling/spacing errors, and brevity] > > - Reply message - > From: "Roman Shaposhnik" > To: "ComDev" > Cc: "Sally Khudairi" , "Ulrich Stärk" > Subject: Fw: Is https://projects-new.apache.org/ ready for prime time? > Date: Fri, Jun 19, 2015 19:47 > > On Fri, Jun 19, 2015 at 2:42 PM, jan i wrote: > > On 19 June 2015 at 22:55, Sally Khudairi wrote: > > > >> Hello Uli and the Apache ComDev team --I hope this message finds you well. > >> Per below, I'm interested in promoting the new Projects page. > >> Can you please let me know if/when we're ready to do so? > >> > > > > I have followed it for a while now, and seen from my pow, we should change > > that to be > > the live site now, but that is of course just my opinion. > > FWIW: you've got my +1
Re: Fw: Is https://projects-new.apache.org/ ready for prime time?
sallykhuda...@yahoo.com On Jun 20, 2015 8:23 AM, "Sally Khudairi" wrote: > Fab! Thanks so much, Roman. > > Bon weekend, > Sally > > > [From the mobile; please excuse top-posting, spelling/spacing errors, and > brevity] > > - Reply message - > From: "Roman Shaposhnik" > To: "ComDev" > Cc: "Sally Khudairi" , "Ulrich Stärk" > Subject: Fw: Is https://projects-new.apache.org/ ready for prime time? > Date: Fri, Jun 19, 2015 19:47 > > On Fri, Jun 19, 2015 at 2:42 PM, jan i wrote: > > On 19 June 2015 at 22:55, Sally Khudairi wrote: > > > >> Hello Uli and the Apache ComDev team --I hope this message finds you > well. > >> Per below, I'm interested in promoting the new Projects page. > >> Can you please let me know if/when we're ready to do so? > >> > > > > I have followed it for a while now, and seen from my pow, we should > change > > that to be > > the live site now, but that is of course just my opinion. > > FWIW: you've got my +1
Re: Fw: Is https://projects-new.apache.org/ ready for prime time?
Aha! OK --that's exactly it. I didn't realize that it was going to replace the old link. So yes, you are correct, Jan, we don't want to do that. As such, I'll be standing by to hear when you (collectively) are ready. Thanks again, Sally [From the mobile; please excuse top-posting, spelling/spacing errors, and brevity] - Reply message - From: "jan i" To: "dev@community.apache.org" Cc: "David Crossley" , "Sally Khudairi" Subject: Fw: Is https://projects-new.apache.org/ ready for prime time? Date: Sat, Jun 20, 2015 06:39 On 20 June 2015 at 12:34, Sally Khudairi wrote: Thanks, David! I noticed that Roman tweeted the link yesterday, so I guess the cat is out of the bag, as the saying goes. As such, barring any objections, I'll start spreading the word. Do we really want to do marketing on the temporary URL ? In my opinion, we should do some renaming so the current one is called -old and the new one replaces the current one. rgds jan i. Are there plans in place to link this from the apache.org homepage? Thanks again, Sally [From the mobile; please excuse top-posting, spelling/spacing errors, and brevity] - Reply message - From: "David Crossley" To: , "Sally Khudairi" Subject: Fw: Is https://projects-new.apache.org/ ready for prime time? Date: Sat, Jun 20, 2015 03:03 Previous discussion here was about how to maintain the actual project data. Also various items listed here: https://projects-new.apache.org/about.html ~David On Fri, Jun 19, 2015 at 08:55:52PM +, Sally Khudairi wrote: > Hello Uli and the Apache ComDev team --I hope this message finds you well. > Per below, I'm interested in promoting the new Projects page. > Can you please let me know if/when we're ready to do so? > Thanks so much, > Sally > > - Forwarded Message - > From: David Nalley > To: Sally Khudairi > Cc: Daniel Gruno ; ASF Infrastructure > > Sent: Friday, June 19, 2015 11:50 AM > Subject: Re: Is https://projects-new.apache.org/ ready for prime time? > > Hi Sally: > > projects-new.apache.org is a ComDev managed resource, not an > infrastructure managed resource. I think the PMC has had a discussion > or two about when to migrate projects-new to projects.a.o > > --David > > > > On Fri, Jun 19, 2015 at 11:30 AM, Sally Khudairi > wrote: > > Hello Daniel and David --I hope you are both well. > > > > > > I was wondering if the new Projects page at > > > > https://projects-new.apache.org/ > > > > was ready to be publicly deployed/announced/promoted. > > > > There's so much great information there and it's an incredible resource (I > > use it every week for the News Round-ups and we relied on it for the Annual > > Report), if there's no reason why it should still be in stealth mode, I'd > > like to shout out about it from the rooftops. > > > > Just let me know if we're good to go and if there are any > > disclaimers/caveats we should be aware of. > > > > Warm thanks, > > Sally > > > > > > = = = = = > > vox +1 617 921 8656 > > off2 +1 646 583 3362 > > skype sallykhudairi > >
Re: Fw: Is https://projects-new.apache.org/ ready for prime time?
On 20 June 2015 at 12:34, Sally Khudairi wrote: > Thanks, David! > > I noticed that Roman tweeted the link yesterday, so I guess the cat is out > of the bag, as the saying goes. > > As such, barring any objections, I'll start spreading the word. > Do we really want to do marketing on the temporary URL ? In my opinion, we should do some renaming so the current one is called -old and the new one replaces the current one. rgds jan i. > > Are there plans in place to link this from the apache.org homepage? > > Thanks again, > Sally > > > [From the mobile; please excuse top-posting, spelling/spacing errors, and > brevity] > > - Reply message - > From: "David Crossley" > To: , "Sally Khudairi" > Subject: Fw: Is https://projects-new.apache.org/ ready for prime time? > Date: Sat, Jun 20, 2015 03:03 > > Previous discussion here was about how to maintain the > actual project data. > Also various items listed here: > https://projects-new.apache.org/about.html > > ~David > > On Fri, Jun 19, 2015 at 08:55:52PM +, Sally Khudairi wrote: > > Hello Uli and the Apache ComDev team --I hope this message finds you > well. > > Per below, I'm interested in promoting the new Projects page. > > Can you please let me know if/when we're ready to do so? > > Thanks so much, > > Sally > > > > - Forwarded Message - > > From: David Nalley > > To: Sally Khudairi > > Cc: Daniel Gruno ; ASF Infrastructure < > infrastruct...@apache.org> > > Sent: Friday, June 19, 2015 11:50 AM > > Subject: Re: Is https://projects-new.apache.org/ ready for prime time? > > > > Hi Sally: > > > > projects-new.apache.org is a ComDev managed resource, not an > > infrastructure managed resource. I think the PMC has had a discussion > > or two about when to migrate projects-new to projects.a.o > > > > --David > > > > > > > > On Fri, Jun 19, 2015 at 11:30 AM, Sally Khudairi > > wrote: > > > Hello Daniel and David --I hope you are both well. > > > > > > > > > I was wondering if the new Projects page at > > > > > > https://projects-new.apache.org/ > > > > > > was ready to be publicly deployed/announced/promoted. > > > > > > There's so much great information there and it's an incredible > resource (I use it every week for the News Round-ups and we relied on it > for the Annual Report), if there's no reason why it should still be in > stealth mode, I'd like to shout out about it from the rooftops. > > > > > > Just let me know if we're good to go and if there are any > disclaimers/caveats we should be aware of. > > > > > > Warm thanks, > > > Sally > > > > > > > > > = = = = = > > > vox +1 617 921 8656 > > > off2 +1 646 583 3362 > > > skype sallykhudairi > > > > >
Re: Fw: Is https://projects-new.apache.org/ ready for prime time?
Thanks, David! I noticed that Roman tweeted the link yesterday, so I guess the cat is out of the bag, as the saying goes. As such, barring any objections, I'll start spreading the word. Are there plans in place to link this from the apache.org homepage? Thanks again, Sally [From the mobile; please excuse top-posting, spelling/spacing errors, and brevity] - Reply message - From: "David Crossley" To: , "Sally Khudairi" Subject: Fw: Is https://projects-new.apache.org/ ready for prime time? Date: Sat, Jun 20, 2015 03:03 Previous discussion here was about how to maintain the actual project data. Also various items listed here: https://projects-new.apache.org/about.html ~David On Fri, Jun 19, 2015 at 08:55:52PM +, Sally Khudairi wrote: > Hello Uli and the Apache ComDev team --I hope this message finds you well. > Per below, I'm interested in promoting the new Projects page. > Can you please let me know if/when we're ready to do so? > Thanks so much, > Sally > > - Forwarded Message - > From: David Nalley > To: Sally Khudairi > Cc: Daniel Gruno ; ASF Infrastructure > > Sent: Friday, June 19, 2015 11:50 AM > Subject: Re: Is https://projects-new.apache.org/ ready for prime time? > > Hi Sally: > > projects-new.apache.org is a ComDev managed resource, not an > infrastructure managed resource. I think the PMC has had a discussion > or two about when to migrate projects-new to projects.a.o > > --David > > > > On Fri, Jun 19, 2015 at 11:30 AM, Sally Khudairi > wrote: > > Hello Daniel and David --I hope you are both well. > > > > > > I was wondering if the new Projects page at > > > > https://projects-new.apache.org/ > > > > was ready to be publicly deployed/announced/promoted. > > > > There's so much great information there and it's an incredible resource (I > > use it every week for the News Round-ups and we relied on it for the Annual > > Report), if there's no reason why it should still be in stealth mode, I'd > > like to shout out about it from the rooftops. > > > > Just let me know if we're good to go and if there are any > > disclaimers/caveats we should be aware of. > > > > Warm thanks, > > Sally > > > > > > = = = = = > > vox +1 617 921 8656 > > off2 +1 646 583 3362 > > skype sallykhudairi > >
Re: Fw: Is https://projects-new.apache.org/ ready for prime time?
Previous discussion here was about how to maintain the actual project data. Also various items listed here: https://projects-new.apache.org/about.html ~David On Fri, Jun 19, 2015 at 08:55:52PM +, Sally Khudairi wrote: > Hello Uli and the Apache ComDev team --I hope this message finds you well. > Per below, I'm interested in promoting the new Projects page. > Can you please let me know if/when we're ready to do so? > Thanks so much, > Sally > > - Forwarded Message - > From: David Nalley > To: Sally Khudairi > Cc: Daniel Gruno ; ASF Infrastructure > > Sent: Friday, June 19, 2015 11:50 AM > Subject: Re: Is https://projects-new.apache.org/ ready for prime time? > > Hi Sally: > > projects-new.apache.org is a ComDev managed resource, not an > infrastructure managed resource. I think the PMC has had a discussion > or two about when to migrate projects-new to projects.a.o > > --David > > > > On Fri, Jun 19, 2015 at 11:30 AM, Sally Khudairi > wrote: > > Hello Daniel and David --I hope you are both well. > > > > > > I was wondering if the new Projects page at > > > > https://projects-new.apache.org/ > > > > was ready to be publicly deployed/announced/promoted. > > > > There's so much great information there and it's an incredible resource (I > > use it every week for the News Round-ups and we relied on it for the Annual > > Report), if there's no reason why it should still be in stealth mode, I'd > > like to shout out about it from the rooftops. > > > > Just let me know if we're good to go and if there are any > > disclaimers/caveats we should be aware of. > > > > Warm thanks, > > Sally > > > > > > = = = = = > > vox +1 617 921 8656 > > off2 +1 646 583 3362 > > skype sallykhudairi > >
Re: Fw: Is https://projects-new.apache.org/ ready for prime time?
Fab! Thanks so much, Roman. Bon weekend, Sally [From the mobile; please excuse top-posting, spelling/spacing errors, and brevity] - Reply message - From: "Roman Shaposhnik" To: "ComDev" Cc: "Sally Khudairi" , "Ulrich Stärk" Subject: Fw: Is https://projects-new.apache.org/ ready for prime time? Date: Fri, Jun 19, 2015 19:47 On Fri, Jun 19, 2015 at 2:42 PM, jan i wrote: > On 19 June 2015 at 22:55, Sally Khudairi wrote: > >> Hello Uli and the Apache ComDev team --I hope this message finds you well. >> Per below, I'm interested in promoting the new Projects page. >> Can you please let me know if/when we're ready to do so? >> > > I have followed it for a while now, and seen from my pow, we should change > that to be > the live site now, but that is of course just my opinion. FWIW: you've got my +1
Re: Fw: Is https://projects-new.apache.org/ ready for prime time?
On Fri, Jun 19, 2015 at 2:42 PM, jan i wrote: > On 19 June 2015 at 22:55, Sally Khudairi wrote: > >> Hello Uli and the Apache ComDev team --I hope this message finds you well. >> Per below, I'm interested in promoting the new Projects page. >> Can you please let me know if/when we're ready to do so? >> > > I have followed it for a while now, and seen from my pow, we should change > that to be > the live site now, but that is of course just my opinion. FWIW: you've got my +1
Re: Fw: Is https://projects-new.apache.org/ ready for prime time?
Excellent. Thanks, Jan. I think the site is great and look forward to our community at-large enjoying it as well! Bon weekend, Sally [From the mobile; please excuse top-posting, spelling/spacing errors, and brevity] - Reply message - From: "jan i" To: "dev@community.apache.org" , "Sally Khudairi" Cc: "Ulrich Stärk" Subject: Fw: Is https://projects-new.apache.org/ ready for prime time? Date: Fri, Jun 19, 2015 17:42 On 19 June 2015 at 22:55, Sally Khudairi wrote: Hello Uli and the Apache ComDev team --I hope this message finds you well. Per below, I'm interested in promoting the new Projects page. Can you please let me know if/when we're ready to do so? I have followed it for a while now, and seen from my pow, we should change that to be the live site now, but that is of course just my opinion. rgds jan I. Thanks so much, Sally - Forwarded Message - From: David Nalley To: Sally Khudairi Cc: Daniel Gruno ; ASF Infrastructure Sent: Friday, June 19, 2015 11:50 AM Subject: Re: Is https://projects-new.apache.org/ ready for prime time? Hi Sally: projects-new.apache.org is a ComDev managed resource, not an infrastructure managed resource. I think the PMC has had a discussion or two about when to migrate projects-new to projects.a.o --David On Fri, Jun 19, 2015 at 11:30 AM, Sally Khudairi wrote: > Hello Daniel and David --I hope you are both well. > > > I was wondering if the new Projects page at > > https://projects-new.apache.org/ > > was ready to be publicly deployed/announced/promoted. > > There's so much great information there and it's an incredible resource (I > use it every week for the News Round-ups and we relied on it for the Annual > Report), if there's no reason why it should still be in stealth mode, I'd > like to shout out about it from the rooftops. > > Just let me know if we're good to go and if there are any disclaimers/caveats > we should be aware of. > > Warm thanks, > Sally > > > = = = = = > vox +1 617 921 8656 > off2 +1 646 583 3362 > skype sallykhudairi
Re: Fw: Is https://projects-new.apache.org/ ready for prime time?
On 19 June 2015 at 22:55, Sally Khudairi wrote: > Hello Uli and the Apache ComDev team --I hope this message finds you well. > Per below, I'm interested in promoting the new Projects page. > Can you please let me know if/when we're ready to do so? > I have followed it for a while now, and seen from my pow, we should change that to be the live site now, but that is of course just my opinion. rgds jan I. > Thanks so much, > Sally > > - Forwarded Message - > From: David Nalley > To: Sally Khudairi > Cc: Daniel Gruno ; ASF Infrastructure < > infrastruct...@apache.org> > Sent: Friday, June 19, 2015 11:50 AM > Subject: Re: Is https://projects-new.apache.org/ ready for prime time? > > Hi Sally: > > projects-new.apache.org is a ComDev managed resource, not an > infrastructure managed resource. I think the PMC has had a discussion > or two about when to migrate projects-new to projects.a.o > > --David > > > > On Fri, Jun 19, 2015 at 11:30 AM, Sally Khudairi > wrote: > > Hello Daniel and David --I hope you are both well. > > > > > > I was wondering if the new Projects page at > > > > https://projects-new.apache.org/ > > > > was ready to be publicly deployed/announced/promoted. > > > > There's so much great information there and it's an incredible resource > (I use it every week for the News Round-ups and we relied on it for the > Annual Report), if there's no reason why it should still be in stealth > mode, I'd like to shout out about it from the rooftops. > > > > Just let me know if we're good to go and if there are any > disclaimers/caveats we should be aware of. > > > > Warm thanks, > > Sally > > > > > > = = = = = > > vox +1 617 921 8656 > > off2 +1 646 583 3362 > > skype sallykhudairi > > >
Fw: Is https://projects-new.apache.org/ ready for prime time?
Hello Uli and the Apache ComDev team --I hope this message finds you well. Per below, I'm interested in promoting the new Projects page. Can you please let me know if/when we're ready to do so? Thanks so much, Sally - Forwarded Message - From: David Nalley To: Sally Khudairi Cc: Daniel Gruno ; ASF Infrastructure Sent: Friday, June 19, 2015 11:50 AM Subject: Re: Is https://projects-new.apache.org/ ready for prime time? Hi Sally: projects-new.apache.org is a ComDev managed resource, not an infrastructure managed resource. I think the PMC has had a discussion or two about when to migrate projects-new to projects.a.o --David On Fri, Jun 19, 2015 at 11:30 AM, Sally Khudairi wrote: > Hello Daniel and David --I hope you are both well. > > > I was wondering if the new Projects page at > > https://projects-new.apache.org/ > > was ready to be publicly deployed/announced/promoted. > > There's so much great information there and it's an incredible resource (I > use it every week for the News Round-ups and we relied on it for the Annual > Report), if there's no reason why it should still be in stealth mode, I'd > like to shout out about it from the rooftops. > > Just let me know if we're good to go and if there are any disclaimers/caveats > we should be aware of. > > Warm thanks, > Sally > > > = = = = = > vox +1 617 921 8656 > off2 +1 646 583 3362 > skype sallykhudairi
Re: projects-new.apache.org
I have found that chrome is not so good at expiring the cache on https pages On 13 April 2015 at 23:59, David Crossley wrote: > Hervé BOUTEMY wrote: > > ok, I added forrest to projects.json and it is now visible in projects > list > > https://projects-new.apache.org/projects.html > > Beaut, thanks. > > > notice there may be issues with browser cache: json content doesn't seem > to be > > refreshed when reloading page, I had to directly browse the json file and > > reload it > > in the future, we may eed to do something to improve such refresh for > end- > > users who won't be able to do such tricks > > I reloaded that page just before you sent this message, and it > was okay without such a trick. > > -David > > > Regards, > > > > Hervé > > > > Le lundi 13 avril 2015 08:09:40 Hervé BOUTEMY a écrit : > > > great: I generated the json file [1] > > > > > > now you are live! > > > https://projects-new.apache.org/project.html?forrest > > > > > > you still don't appear in the projects list: I need to investigate, > will do > > > tonight (Paris time). > > > > > > Regards, > > > > > > Hervé > > > > > > [1] https://projects-new.apache.org/json/projects/forrest.json >
Re: disabling edit feature in https://projects-new.apache.org/
while working on missing Forrest info, I'm now completely convinced we should not edit json but completely generate them from existing DOAP and project.a.o contents then I'll immediately disable the edit feature: this can easily be reverted later And I'll add a link to existing information on how to add a new TLP Regards, Hervé Le dimanche 12 avril 2015 18:39:57 Hervé BOUTEMY a écrit : > Hi, > > I'm working on https://projects-new.apache.org/ , trying to figure out the > whole information flow for informations about our projects: I like this new > site, but IMHO we can't switch until we're clear on that. > > > And it seems the edit feature currently cause inconsistencies since it edits > site's svn simplified json content, instead of DOAP which is AFAIK the > current project description standard [1] > > > There are only few projects that used the feature, then it's not too late to > fix the issue before it gets worse and people are lost. > > > IMHO, adding a link to this DOAP page in projects-new's about page would do > the job = explain people how to add their project (perhaps some additionnal > instructions are required, I'm not sure) > > WDYT? > > Regards, > > Hervé > > [1] http://projects.apache.org/doap.html
Re: projects-new.apache.org
Hervé BOUTEMY wrote: > ok, I added forrest to projects.json and it is now visible in projects list > https://projects-new.apache.org/projects.html Beaut, thanks. > notice there may be issues with browser cache: json content doesn't seem to > be > refreshed when reloading page, I had to directly browse the json file and > reload it > in the future, we may eed to do something to improve such refresh for end- > users who won't be able to do such tricks I reloaded that page just before you sent this message, and it was okay without such a trick. -David > Regards, > > Hervé > > Le lundi 13 avril 2015 08:09:40 Hervé BOUTEMY a écrit : > > great: I generated the json file [1] > > > > now you are live! > > https://projects-new.apache.org/project.html?forrest > > > > you still don't appear in the projects list: I need to investigate, will do > > tonight (Paris time). > > > > Regards, > > > > Hervé > > > > [1] https://projects-new.apache.org/json/projects/forrest.json
Re: projects-new.apache.org
ok, I added forrest to projects.json and it is now visible in projects list https://projects-new.apache.org/projects.html notice there may be issues with browser cache: json content doesn't seem to be refreshed when reloading page, I had to directly browse the json file and reload it in the future, we may eed to do something to improve such refresh for end- users who won't be able to do such tricks Regards, Hervé Le lundi 13 avril 2015 08:09:40 Hervé BOUTEMY a écrit : > great: I generated the json file [1] > > now you are live! > https://projects-new.apache.org/project.html?forrest > > you still don't appear in the projects list: I need to investigate, will do > tonight (Paris time). > > Regards, > > Hervé > > [1] https://projects-new.apache.org/json/projects/forrest.json > > Le lundi 13 avril 2015 14:41:07 David Crossley a écrit : > > Hervé BOUTEMY wrote: > > > I had a look at Forrest doap file[1]: it's not a doap file, it's a feed > > > containing a doap entry > > > > > > you should IMHO simplify it to match a simple doap file, like [2], for > > > example > > > > Ah, many thanks. I have now published that, and also updated the > > reference in files.xml at the old projects.apache.org > > http://svn.apache.org/r1673100 > > > > -David > > > > > Regards, > > > > > > Hervé > > > > > > [1] http://forrest.apache.org/doap.xml > > > > > > [2] > > > http://svn.apache.org/repos/asf/geronimo/site/trunk/doap_Geronimo.rdf > > > > > > Le lundi 13 avril 2015 04:58:05 Hervé BOUTEMY a écrit : > > > > if you run parserdf.py, you'll see that forrest is one of the few rdf > > > > that > > > > makes the script choke: > > > > > > > > Error when reading None's doap file > > > > http://forrest.apache.org/doap.xml: > > > > > > > > > > > > Traceback (most recent call last): > > > > File "rdfparse.py", line 59, in > > > > > > > > if pjson['homepage']: > > > > KeyError: 'homepage' > > > > > > > > > > > > > > > > I still didn't have time to investigate this one, and report (did it > > > > for > > > > lucy and uima: opened Jira issues on each project) > > > > > > > > Regards, > > > > > > > > Hervé > > > > > > > > Le lundi 13 avril 2015 12:32:49 David Crossley a écrit : > > > > > Apache Forrest is also missing from projects-new.a.o > > > > > but was one of the early adopters at projects.a.o > > > > > > > > > > I cannot determine why. Would someone else please try. > > > > > > > > > > -David > > > > > > > > > > On Sun, Apr 12, 2015 at 07:27:18PM +0200, Hervé BOUTEMY wrote: > > > > > > I finally found time to investigate: > > > > > > > > > > > > this is because ofbiz is not in pmcs reference list [1] used by > > > > > > the > > > > > > site > > > > > > to > > > > > > create pmcs.json [2] > > > > > > > > > > > > it seems one step was missed during OFBiz TLP creation [3] > > > > > > > > > > > > As PMC Chair and/or member, you should be able to fix it [4] > > > > > > > > > > > > Once done, just tell and I'll regenerate the pmcs.json file > > > > > > > > > > > > Regards, > > > > > > > > > > > > Hervé > > > > > > > > > > > > > > > > > > [1] > > > > > > https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/p > > > > > > ro > > > > > > ject > > > > > > s > > > > > > /data_files/ > > > > > > > > > > > > [2] https://projects-new.apache.org/json/foundation/pmcs.json > > > > > > > > > > > > [3] > > > > > > https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/p > > > > > > ro > > > > > > ject > > > > > > s > > > > > > /data_files/aareadme.txt > > > > > > > > > > > > [4] http://projects.apache.org/create.html#submit > > > > > > > > > > > > Le lundi 30 mars 2015 08:54:46 Pierre Smits a écrit : > > > > > > > Hi. I don't see Apache OFBiz when looking at the 'Projects by > > > > > > > PMC' > > > > > > > overview. > > > > > > > > > > > > > > Best regards, > > > > > > > > > > > > > > Pierre Smits
Re: projects-new.apache.org
great: I generated the json file [1] now you are live! https://projects-new.apache.org/project.html?forrest you still don't appear in the projects list: I need to investigate, will do tonight (Paris time). Regards, Hervé [1] https://projects-new.apache.org/json/projects/forrest.json Le lundi 13 avril 2015 14:41:07 David Crossley a écrit : > Hervé BOUTEMY wrote: > > I had a look at Forrest doap file[1]: it's not a doap file, it's a feed > > containing a doap entry > > > > you should IMHO simplify it to match a simple doap file, like [2], for > > example > Ah, many thanks. I have now published that, and also updated the > reference in files.xml at the old projects.apache.org > http://svn.apache.org/r1673100 > > -David > > > Regards, > > > > Hervé > > > > [1] http://forrest.apache.org/doap.xml > > > > [2] http://svn.apache.org/repos/asf/geronimo/site/trunk/doap_Geronimo.rdf > > > > Le lundi 13 avril 2015 04:58:05 Hervé BOUTEMY a écrit : > > > if you run parserdf.py, you'll see that forrest is one of the few rdf > > > that > > > makes the script choke: > > > > > > Error when reading None's doap file http://forrest.apache.org/doap.xml: > > > > > > > > > Traceback (most recent call last): > > > File "rdfparse.py", line 59, in > > > > > > if pjson['homepage']: > > > KeyError: 'homepage' > > > > > > > > > > > > I still didn't have time to investigate this one, and report (did it for > > > lucy and uima: opened Jira issues on each project) > > > > > > Regards, > > > > > > Hervé > > > > > > Le lundi 13 avril 2015 12:32:49 David Crossley a écrit : > > > > Apache Forrest is also missing from projects-new.a.o > > > > but was one of the early adopters at projects.a.o > > > > > > > > I cannot determine why. Would someone else please try. > > > > > > > > -David > > > > > > > > On Sun, Apr 12, 2015 at 07:27:18PM +0200, Hervé BOUTEMY wrote: > > > > > I finally found time to investigate: > > > > > > > > > > this is because ofbiz is not in pmcs reference list [1] used by the > > > > > site > > > > > to > > > > > create pmcs.json [2] > > > > > > > > > > it seems one step was missed during OFBiz TLP creation [3] > > > > > > > > > > As PMC Chair and/or member, you should be able to fix it [4] > > > > > > > > > > Once done, just tell and I'll regenerate the pmcs.json file > > > > > > > > > > Regards, > > > > > > > > > > Hervé > > > > > > > > > > > > > > > [1] > > > > > https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/pro > > > > > ject > > > > > s > > > > > /data_files/ > > > > > > > > > > [2] https://projects-new.apache.org/json/foundation/pmcs.json > > > > > > > > > > [3] > > > > > https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/pro > > > > > ject > > > > > s > > > > > /data_files/aareadme.txt > > > > > > > > > > [4] http://projects.apache.org/create.html#submit > > > > > > > > > > Le lundi 30 mars 2015 08:54:46 Pierre Smits a écrit : > > > > > > Hi. I don't see Apache OFBiz when looking at the 'Projects by PMC' > > > > > > overview. > > > > > > > > > > > > Best regards, > > > > > > > > > > > > Pierre Smits
Re: projects-new.apache.org
Hervé BOUTEMY wrote: > I had a look at Forrest doap file[1]: it's not a doap file, it's a feed > containing a doap entry > > you should IMHO simplify it to match a simple doap file, like [2], for example Ah, many thanks. I have now published that, and also updated the reference in files.xml at the old projects.apache.org http://svn.apache.org/r1673100 -David > Regards, > > Hervé > > [1] http://forrest.apache.org/doap.xml > > [2] http://svn.apache.org/repos/asf/geronimo/site/trunk/doap_Geronimo.rdf > > Le lundi 13 avril 2015 04:58:05 Hervé BOUTEMY a écrit : > > if you run parserdf.py, you'll see that forrest is one of the few rdf that > > makes the script choke: > > > > Error when reading None's doap file http://forrest.apache.org/doap.xml: > > > > Traceback (most recent call last): > > File "rdfparse.py", line 59, in > > if pjson['homepage']: > > KeyError: 'homepage' > > > > > > > > I still didn't have time to investigate this one, and report (did it for > > lucy and uima: opened Jira issues on each project) > > > > Regards, > > > > Hervé > > > > Le lundi 13 avril 2015 12:32:49 David Crossley a écrit : > > > Apache Forrest is also missing from projects-new.a.o > > > but was one of the early adopters at projects.a.o > > > > > > I cannot determine why. Would someone else please try. > > > > > > -David > > > > > > On Sun, Apr 12, 2015 at 07:27:18PM +0200, Hervé BOUTEMY wrote: > > > > I finally found time to investigate: > > > > > > > > this is because ofbiz is not in pmcs reference list [1] used by the site > > > > to > > > > create pmcs.json [2] > > > > > > > > it seems one step was missed during OFBiz TLP creation [3] > > > > > > > > As PMC Chair and/or member, you should be able to fix it [4] > > > > > > > > Once done, just tell and I'll regenerate the pmcs.json file > > > > > > > > Regards, > > > > > > > > Hervé > > > > > > > > > > > > [1] > > > > https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/project > > > > s > > > > /data_files/ > > > > > > > > [2] https://projects-new.apache.org/json/foundation/pmcs.json > > > > > > > > [3] > > > > https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/project > > > > s > > > > /data_files/aareadme.txt > > > > > > > > [4] http://projects.apache.org/create.html#submit > > > > > > > > Le lundi 30 mars 2015 08:54:46 Pierre Smits a écrit : > > > > > Hi. I don't see Apache OFBiz when looking at the 'Projects by PMC' > > > > > overview. > > > > > > > > > > Best regards, > > > > > > > > > > Pierre Smits >
Re: projects-new.apache.org
I had a look at Forrest doap file[1]: it's not a doap file, it's a feed containing a doap entry you should IMHO simplify it to match a simple doap file, like [2], for example Regards, Hervé [1] http://forrest.apache.org/doap.xml [2] http://svn.apache.org/repos/asf/geronimo/site/trunk/doap_Geronimo.rdf Le lundi 13 avril 2015 04:58:05 Hervé BOUTEMY a écrit : > if you run parserdf.py, you'll see that forrest is one of the few rdf that > makes the script choke: > > Error when reading None's doap file http://forrest.apache.org/doap.xml: > > Traceback (most recent call last): > File "rdfparse.py", line 59, in > if pjson['homepage']: > KeyError: 'homepage' > > > > I still didn't have time to investigate this one, and report (did it for > lucy and uima: opened Jira issues on each project) > > Regards, > > Hervé > > Le lundi 13 avril 2015 12:32:49 David Crossley a écrit : > > Apache Forrest is also missing from projects-new.a.o > > but was one of the early adopters at projects.a.o > > > > I cannot determine why. Would someone else please try. > > > > -David > > > > On Sun, Apr 12, 2015 at 07:27:18PM +0200, Hervé BOUTEMY wrote: > > > I finally found time to investigate: > > > > > > this is because ofbiz is not in pmcs reference list [1] used by the site > > > to > > > create pmcs.json [2] > > > > > > it seems one step was missed during OFBiz TLP creation [3] > > > > > > As PMC Chair and/or member, you should be able to fix it [4] > > > > > > Once done, just tell and I'll regenerate the pmcs.json file > > > > > > Regards, > > > > > > Hervé > > > > > > > > > [1] > > > https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/project > > > s > > > /data_files/ > > > > > > [2] https://projects-new.apache.org/json/foundation/pmcs.json > > > > > > [3] > > > https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/project > > > s > > > /data_files/aareadme.txt > > > > > > [4] http://projects.apache.org/create.html#submit > > > > > > Le lundi 30 mars 2015 08:54:46 Pierre Smits a écrit : > > > > Hi. I don't see Apache OFBiz when looking at the 'Projects by PMC' > > > > overview. > > > > > > > > Best regards, > > > > > > > > Pierre Smits
Re: projects-new.apache.org
if you run parserdf.py, you'll see that forrest is one of the few rdf that makes the script choke: Error when reading None's doap file http://forrest.apache.org/doap.xml: Traceback (most recent call last): File "rdfparse.py", line 59, in if pjson['homepage']: KeyError: 'homepage' I still didn't have time to investigate this one, and report (did it for lucy and uima: opened Jira issues on each project) Regards, Hervé Le lundi 13 avril 2015 12:32:49 David Crossley a écrit : > Apache Forrest is also missing from projects-new.a.o > but was one of the early adopters at projects.a.o > > I cannot determine why. Would someone else please try. > > -David > > On Sun, Apr 12, 2015 at 07:27:18PM +0200, Hervé BOUTEMY wrote: > > I finally found time to investigate: > > > > this is because ofbiz is not in pmcs reference list [1] used by the site > > to > > create pmcs.json [2] > > > > it seems one step was missed during OFBiz TLP creation [3] > > > > As PMC Chair and/or member, you should be able to fix it [4] > > > > Once done, just tell and I'll regenerate the pmcs.json file > > > > Regards, > > > > Hervé > > > > > > [1] > > https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects > > /data_files/ > > > > [2] https://projects-new.apache.org/json/foundation/pmcs.json > > > > [3] > > https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects > > /data_files/aareadme.txt > > > > [4] http://projects.apache.org/create.html#submit > > > > Le lundi 30 mars 2015 08:54:46 Pierre Smits a écrit : > > > Hi. I don't see Apache OFBiz when looking at the 'Projects by PMC' > > > overview. > > > > > > Best regards, > > > > > > Pierre Smits
Re: projects-new.apache.org
Apache Forrest is also missing from projects-new.a.o but was one of the early adopters at projects.a.o I cannot determine why. Would someone else please try. -David On Sun, Apr 12, 2015 at 07:27:18PM +0200, Hervé BOUTEMY wrote: > I finally found time to investigate: > > this is because ofbiz is not in pmcs reference list [1] used by the site to > create pmcs.json [2] > > it seems one step was missed during OFBiz TLP creation [3] > > As PMC Chair and/or member, you should be able to fix it [4] > > Once done, just tell and I'll regenerate the pmcs.json file > > Regards, > > Hervé > > > [1] > https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/data_files/ > > [2] https://projects-new.apache.org/json/foundation/pmcs.json > > [3] > https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/data_files/aareadme.txt > > [4] http://projects.apache.org/create.html#submit > > Le lundi 30 mars 2015 08:54:46 Pierre Smits a écrit : > > Hi. I don't see Apache OFBiz when looking at the 'Projects by PMC' overview. > > > > Best regards, > > > > Pierre Smits
Re: projects-new.apache.org
I finally found time to investigate: this is because ofbiz is not in pmcs reference list [1] used by the site to create pmcs.json [2] it seems one step was missed during OFBiz TLP creation [3] As PMC Chair and/or member, you should be able to fix it [4] Once done, just tell and I'll regenerate the pmcs.json file Regards, Hervé [1] https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/data_files/ [2] https://projects-new.apache.org/json/foundation/pmcs.json [3] https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/data_files/aareadme.txt [4] http://projects.apache.org/create.html#submit Le lundi 30 mars 2015 08:54:46 Pierre Smits a écrit : > Hi. I don't see Apache OFBiz when looking at the 'Projects by PMC' overview. > > 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 Mon, Mar 30, 2015 at 8:23 AM, Hervé BOUTEMY > > wrote: > > Now that every committer has commit privs, I continued my improvements > > (about > > Attic, whimsy, categories) and added an About page: > > https://projects-new.apache.org/about.html > > > > It is pretty basic at the moment, but tells important things to > > contribute. > > The format is quite simple, but since it's handwritten html... > > > > Now what remains to do before we can switch projects.a.o to projects-new > > content? > > I made a list of "TbD" in the About page listing content that exists in > > previous site that should be somthing like imported IMHO > > > > WDYT? > > > > > > Notice that the Comdev PMC does not have any DOAP file, then no page to > > describe its structure. Same applies to special comittees (Infrastructure, > > Travel Assistance, Security Team, Legal Affairs and Brand Management). > > Don't > > you think we should list these PMCs like any other? > > > > Regards, > > > > Hervé
disabling edit feature in https://projects-new.apache.org/
Hi, I'm working on https://projects-new.apache.org/ , trying to figure out the whole information flow for informations about our projects: I like this new site, but IMHO we can't switch until we're clear on that. And it seems the edit feature currently cause inconsistencies since it edits site's svn simplified json content, instead of DOAP which is AFAIK the current project description standard [1] There are only few projects that used the feature, then it's not too late to fix the issue before it gets worse and people are lost. IMHO, adding a link to this DOAP page in projects-new's about page would do the job = explain people how to add their project (perhaps some additionnal instructions are required, I'm not sure) WDYT? Regards, Hervé [1] http://projects.apache.org/doap.html
Re: projects-new.apache.org
On 03/30/2015 02:23 AM, Hervé BOUTEMY wrote: Notice that the Comdev PMC does not have any DOAP file, then no page to describe its structure. Same applies to special comittees (Infrastructure, Travel Assistance, Security Team, Legal Affairs and Brand Management). Don't you think we should list these PMCs like any other? Sure. Just need someone to make it happen. -- Rich Bowen - rbo...@rcbowen.com - @rbowen http://apachecon.com/ - @apachecon
Re: projects-new.apache.org
Hi. I don't see Apache OFBiz when looking at the 'Projects by PMC' overview. 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 Mon, Mar 30, 2015 at 8:23 AM, Hervé BOUTEMY wrote: > Now that every committer has commit privs, I continued my improvements > (about > Attic, whimsy, categories) and added an About page: > https://projects-new.apache.org/about.html > > It is pretty basic at the moment, but tells important things to contribute. > The format is quite simple, but since it's handwritten html... > > Now what remains to do before we can switch projects.a.o to projects-new > content? > I made a list of "TbD" in the About page listing content that exists in > previous site that should be somthing like imported IMHO > > WDYT? > > > Notice that the Comdev PMC does not have any DOAP file, then no page to > describe its structure. Same applies to special comittees (Infrastructure, > Travel Assistance, Security Team, Legal Affairs and Brand Management). > Don't > you think we should list these PMCs like any other? > > Regards, > > Hervé >
projects-new.apache.org
Now that every committer has commit privs, I continued my improvements (about Attic, whimsy, categories) and added an About page: https://projects-new.apache.org/about.html It is pretty basic at the moment, but tells important things to contribute. The format is quite simple, but since it's handwritten html... Now what remains to do before we can switch projects.a.o to projects-new content? I made a list of "TbD" in the About page listing content that exists in previous site that should be somthing like imported IMHO WDYT? Notice that the Comdev PMC does not have any DOAP file, then no page to describe its structure. Same applies to special comittees (Infrastructure, Travel Assistance, Security Team, Legal Affairs and Brand Management). Don't you think we should list these PMCs like any other? Regards, Hervé
Re: first little patch for projects-new.apache.org
Le jeudi 19 mars 2015 12:20:08 Rich Bowen a écrit : > Thanks, Herve. I've applied all of your patches. Sorry for the long > delay. Thanks so much for helping out. thank you Rich I'll wait for the permission opening to continue improvements (I already know a few little steps to do) then, before switching, we'll need to discuss about: - project's DOAP future - previous site with site-dev@ Regards, Hervé > > On 03/08/2015 12:56 PM, Hervé BOUTEMY wrote: > > avoid copy paste for TLP vs sub-project icon and put the icon on the > > left to have full alignment
Re: first little patch for projects-new.apache.org
On 03/09/2015 06:46 AM, Daniel Gruno wrote: Can someone apply Hervé's patches, so it's not just me doing all the commits on this project? :) Thanks! Done. Sorry for the delay. With regards, Daniel. On 2015-03-08 18:01, Hervé BOUTEMY wrote: IMHO, icons for incubating and Attic projects should be different than standard sub-project (no idea about rendering of such icons) Regards, Hervé Le dimanche 8 mars 2015 17:56:52 Hervé BOUTEMY a écrit : next: avoid copy paste for TLP vs sub-project icon and put the icon on the left to have full alignment Regards, Hervé Le dimanche 8 mars 2015 17:43:49 Hervé BOUTEMY a écrit : and a third one: just white background instead of black Regards, Hervé Le dimanche 8 mars 2015 17:29:56 Hervé BOUTEMY a écrit : another one, with simple instructions to make local tests Regards, Hervé Le dimanche 8 mars 2015 17:23:36 Hervé BOUTEMY a écrit : Hi, As promise, here is a first little patch: this is simply to add a link to our license, per our policy :) Regards, Hervé -- Rich Bowen - rbo...@rcbowen.com - @rbowen http://apachecon.com/ - @apachecon
Re: first little patch for projects-new.apache.org
Thanks, Herve. I've applied all of your patches. Sorry for the long delay. Thanks so much for helping out. On 03/08/2015 12:56 PM, Hervé BOUTEMY wrote: avoid copy paste for TLP vs sub-project icon and put the icon on the left to have full alignment -- Rich Bowen - rbo...@rcbowen.com - @rbowen http://apachecon.com/ - @apachecon
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
Kinda strange that none of this involves site-dev@ which was the genesis of the original site. Sent from my iPhone > On Mar 13, 2015, at 3:44 AM, Daniel Gruno wrote: > > > If someone other than me could apply those patches, that'd sure be swell. > This is (the future) projects.apache.org, not humbedooh.apache.org :( > > > As for keeping the old site around for a while, I suppose that's an option, > just don't expect infra to maintain it if it keels over ;) > With regards, > Daniel. > >> On 2015-03-13 08:40, Hervé BOUTEMY wrote: >> ping? >> >> Le mercredi 11 mars 2015 08:49:23 Hervé BOUTEMY a écrit : >>> Le mardi 10 mars 2015 13:32:26 Rich Bowen a écrit : >>>> On 03/06/2015 11:52 AM, Rich Bowen wrote: >>>>> I'd like for us to go ahead and replace projects.apache.org with >>>>> projects-new.apache.org. It now has all the functionality that >>>>> projects.a.o has, and much more, and there's no reason to have two sites >>>>> up. If you object to moving forward with this, please say so. >>>>> >>>>> [ ] +1, do it >>>>> [ ] +0, whatevs >>>>> [ ] -1, No (and say why, so we can address the problem) >>>> I'm going to call this a "yes" vote overall, with a few nits >>> +1 >>> >>> one more thing: when we switch projects-new to projects, it would be useful >>> to have old projects switched to projects-old, since there are still parts >>> that are useful or to be integrated to the new site (see Feeds, DOAP Files >>> and Documentation sections) >>> >>>> that have been addressed. >>> -1 I sent patches but they were not applied >>> >>>> Thank you all for your thoughts. Thanks, Daniel, for >>>> your work on this. And with all the folks that have said they'll get >>>> checkouts and hack on it, we should have much wonderment real soon. >>> Can I get commit access (without being PMC member)? >>> >>> I'd like to add an "about" folder equivalent to >>> https://projects.apache.org/references.html, and with a reference to >>> http://people.apache.org/committers-by-project.html#comdev >>> >>> Notice: shouldn't comdev be added to projects-new as 6th "special >>> committee"? >>> >>> Regards, >>> >>> Hervé >>> >>>> --Rich >
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
Le vendredi 13 mars 2015 08:44:05 Daniel Gruno a écrit : > > If someone other than me could apply those patches, that'd sure be swell. > This is (the future) projects.apache.org, not humbedooh.apache.org :( > +1 that's why I proposed to even join (and not only stay outside) > > As for keeping the old site around for a while, I suppose that's an > option, just don't expect infra to maintain it if it keels over ;) how is it related to infra? I supposed projects-new was like projects, ie a comdev site, with comdev community? if that's not the casae, I understand now that the change from projects to projects-new is also a switch from infra responsibility to comdev = an organisational change, not only technical Perhaps the organisational part wasn't expected. Regards, Hervé > With regards, > Daniel. > > On 2015-03-13 08:40, Hervé BOUTEMY wrote: > > ping? > > > > Le mercredi 11 mars 2015 08:49:23 Hervé BOUTEMY a écrit : > >> Le mardi 10 mars 2015 13:32:26 Rich Bowen a écrit : > >>> On 03/06/2015 11:52 AM, Rich Bowen wrote: > >>>> I'd like for us to go ahead and replace projects.apache.org with > >>>> projects-new.apache.org. It now has all the functionality that > >>>> projects.a.o has, and much more, and there's no reason to have two > >>>> sites > >>>> up. If you object to moving forward with this, please say so. > >>>> > >>>> [ ] +1, do it > >>>> [ ] +0, whatevs > >>>> [ ] -1, No (and say why, so we can address the problem) > >>> > >>> I'm going to call this a "yes" vote overall, with a few nits > >> > >> +1 > >> > >> one more thing: when we switch projects-new to projects, it would be > >> useful > >> to have old projects switched to projects-old, since there are still > >> parts > >> that are useful or to be integrated to the new site (see Feeds, DOAP > >> Files > >> and Documentation sections) > >> > >>> that have been addressed. > >> > >> -1 I sent patches but they were not applied > >> > >>> Thank you all for your thoughts. Thanks, Daniel, for > >>> your work on this. And with all the folks that have said they'll get > >>> checkouts and hack on it, we should have much wonderment real soon. > >> > >> Can I get commit access (without being PMC member)? > >> > >> I'd like to add an "about" folder equivalent to > >> https://projects.apache.org/references.html, and with a reference to > >> http://people.apache.org/committers-by-project.html#comdev > >> > >> Notice: shouldn't comdev be added to projects-new as 6th "special > >> committee"? > >> > >> Regards, > >> > >> Hervé > >> > >>> --Rich
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
If someone other than me could apply those patches, that'd sure be swell. This is (the future) projects.apache.org, not humbedooh.apache.org :( As for keeping the old site around for a while, I suppose that's an option, just don't expect infra to maintain it if it keels over ;) With regards, Daniel. On 2015-03-13 08:40, Hervé BOUTEMY wrote: ping? Le mercredi 11 mars 2015 08:49:23 Hervé BOUTEMY a écrit : Le mardi 10 mars 2015 13:32:26 Rich Bowen a écrit : On 03/06/2015 11:52 AM, Rich Bowen wrote: I'd like for us to go ahead and replace projects.apache.org with projects-new.apache.org. It now has all the functionality that projects.a.o has, and much more, and there's no reason to have two sites up. If you object to moving forward with this, please say so. [ ] +1, do it [ ] +0, whatevs [ ] -1, No (and say why, so we can address the problem) I'm going to call this a "yes" vote overall, with a few nits +1 one more thing: when we switch projects-new to projects, it would be useful to have old projects switched to projects-old, since there are still parts that are useful or to be integrated to the new site (see Feeds, DOAP Files and Documentation sections) that have been addressed. -1 I sent patches but they were not applied Thank you all for your thoughts. Thanks, Daniel, for your work on this. And with all the folks that have said they'll get checkouts and hack on it, we should have much wonderment real soon. Can I get commit access (without being PMC member)? I'd like to add an "about" folder equivalent to https://projects.apache.org/references.html, and with a reference to http://people.apache.org/committers-by-project.html#comdev Notice: shouldn't comdev be added to projects-new as 6th "special committee"? Regards, Hervé --Rich
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
ping? Le mercredi 11 mars 2015 08:49:23 Hervé BOUTEMY a écrit : > Le mardi 10 mars 2015 13:32:26 Rich Bowen a écrit : > > On 03/06/2015 11:52 AM, Rich Bowen wrote: > > > I'd like for us to go ahead and replace projects.apache.org with > > > projects-new.apache.org. It now has all the functionality that > > > projects.a.o has, and much more, and there's no reason to have two sites > > > up. If you object to moving forward with this, please say so. > > > > > > [ ] +1, do it > > > [ ] +0, whatevs > > > [ ] -1, No (and say why, so we can address the problem) > > > > I'm going to call this a "yes" vote overall, with a few nits > > +1 > > one more thing: when we switch projects-new to projects, it would be useful > to have old projects switched to projects-old, since there are still parts > that are useful or to be integrated to the new site (see Feeds, DOAP Files > and Documentation sections) > > > that have been addressed. > > -1 I sent patches but they were not applied > > > Thank you all for your thoughts. Thanks, Daniel, for > > your work on this. And with all the folks that have said they'll get > > checkouts and hack on it, we should have much wonderment real soon. > > Can I get commit access (without being PMC member)? > > I'd like to add an "about" folder equivalent to > https://projects.apache.org/references.html, and with a reference to > http://people.apache.org/committers-by-project.html#comdev > > Notice: shouldn't comdev be added to projects-new as 6th "special > committee"? > > Regards, > > Hervé > > > --Rich
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
Le mardi 10 mars 2015 13:32:26 Rich Bowen a écrit : > On 03/06/2015 11:52 AM, Rich Bowen wrote: > > I'd like for us to go ahead and replace projects.apache.org with > > projects-new.apache.org. It now has all the functionality that > > projects.a.o has, and much more, and there's no reason to have two sites > > up. If you object to moving forward with this, please say so. > > > > [ ] +1, do it > > [ ] +0, whatevs > > [ ] -1, No (and say why, so we can address the problem) > > I'm going to call this a "yes" vote overall, with a few nits +1 one more thing: when we switch projects-new to projects, it would be useful to have old projects switched to projects-old, since there are still parts that are useful or to be integrated to the new site (see Feeds, DOAP Files and Documentation sections) > that have been addressed. -1 I sent patches but they were not applied > Thank you all for your thoughts. Thanks, Daniel, for > your work on this. And with all the folks that have said they'll get > checkouts and hack on it, we should have much wonderment real soon. Can I get commit access (without being PMC member)? I'd like to add an "about" folder equivalent to https://projects.apache.org/references.html, and with a reference to http://people.apache.org/committers-by-project.html#comdev Notice: shouldn't comdev be added to projects-new as 6th "special committee"? Regards, Hervé > > --Rich
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
On 03/06/2015 11:52 AM, Rich Bowen wrote: I'd like for us to go ahead and replace projects.apache.org with projects-new.apache.org. It now has all the functionality that projects.a.o has, and much more, and there's no reason to have two sites up. If you object to moving forward with this, please say so. [ ] +1, do it [ ] +0, whatevs [ ] -1, No (and say why, so we can address the problem) I'm going to call this a "yes" vote overall, with a few nits that have been addressed. Thank you all for your thoughts. Thanks, Daniel, for your work on this. And with all the folks that have said they'll get checkouts and hack on it, we should have much wonderment real soon. --Rich -- Rich Bowen - rbo...@rcbowen.com - @rbowen http://apachecon.com/ - @apachecon
Re: first little patch for projects-new.apache.org
Can someone apply Hervé's patches, so it's not just me doing all the commits on this project? :) Thanks! With regards, Daniel. On 2015-03-08 18:01, Hervé BOUTEMY wrote: IMHO, icons for incubating and Attic projects should be different than standard sub-project (no idea about rendering of such icons) Regards, Hervé Le dimanche 8 mars 2015 17:56:52 Hervé BOUTEMY a écrit : next: avoid copy paste for TLP vs sub-project icon and put the icon on the left to have full alignment Regards, Hervé Le dimanche 8 mars 2015 17:43:49 Hervé BOUTEMY a écrit : and a third one: just white background instead of black Regards, Hervé Le dimanche 8 mars 2015 17:29:56 Hervé BOUTEMY a écrit : another one, with simple instructions to make local tests Regards, Hervé Le dimanche 8 mars 2015 17:23:36 Hervé BOUTEMY a écrit : Hi, As promise, here is a first little patch: this is simply to add a link to our license, per our policy :) Regards, Hervé
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
On 2015-03-08 19:33, Hitesh Shah wrote: Thanks for the info, Daniel. Updated. In terms of keeping project info updated, is this info along with all the release info, etc. being pulled from the project DOAP files? If not, do we still need to maintain them? No, if/when projects.apache.org gets replaced with the new system, you do not need to maintain doap files. As for the data update, I did see you push the save button a few times there ;). Your browser probably caches the json objects for N minutes, which is why you did not notice that the data had indeed been updated. Once we move this to a faster TLS terminator, we can look at updating JSON objects more often within browsers. With regards, Daniel Do I need to do anything additional for it to show up in the listing on https://projects-new.apache.org/projects.html or will something eventually kick in to add it to the index? https://projects-new.apache.org/project.html?tez seems to show my updates. thanks — Hitesh On Mar 7, 2015, at 2:12 AM, Daniel Gruno wrote: Hi Hitesh, log onto https://projects-new.apache.org/edit/ and go to the bottom. Pick 'tez' as the PMC and nothing as the sub-project name, click the button and start typing :) That will create a tez.json file that the site will then use. With regards, Daniel. On 2015-03-07 04:56, Hitesh Shah wrote: Same question for Apache Tez. How do we need to fix the new website to show the Tez project? thanks — Hitesh On Mar 6, 2015, at 1:46 PM, Marshall Schor wrote: I can see the Apache UIMA entry in the "old" page, but it's not listed on the new page. What needs fixing? -Marshall Schor On 3/6/2015 11:52 AM, Rich Bowen wrote: I'd like for us to go ahead and replace projects.apache.org with projects-new.apache.org. It now has all the functionality that projects.a.o has, and much more, and there's no reason to have two sites up. If you object to moving forward with this, please say so. [ ] +1, do it [ ] +0, whatevs [ ] -1, No (and say why, so we can address the problem) --Rich
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
Thanks for the info, Daniel. Updated. In terms of keeping project info updated, is this info along with all the release info, etc. being pulled from the project DOAP files? If not, do we still need to maintain them? Do I need to do anything additional for it to show up in the listing on https://projects-new.apache.org/projects.html or will something eventually kick in to add it to the index? https://projects-new.apache.org/project.html?tez seems to show my updates. thanks — Hitesh On Mar 7, 2015, at 2:12 AM, Daniel Gruno wrote: > Hi Hitesh, > log onto https://projects-new.apache.org/edit/ and go to the bottom. Pick > 'tez' as the PMC and nothing as the sub-project name, click the button and > start typing :) That will create a tez.json file that the site will then use. > > With regards, > Daniel. > > On 2015-03-07 04:56, Hitesh Shah wrote: >> Same question for Apache Tez. How do we need to fix the new website to show >> the Tez project? >> >> thanks >> — Hitesh >> >> On Mar 6, 2015, at 1:46 PM, Marshall Schor wrote: >> >>> I can see the Apache UIMA entry in the "old" page, but it's not listed on >>> the >>> new page. What needs fixing? >>> >>> -Marshall Schor >>> >>> On 3/6/2015 11:52 AM, Rich Bowen wrote: >>>> I'd like for us to go ahead and replace projects.apache.org with >>>> projects-new.apache.org. It now has all the functionality that projects.a.o >>>> has, and much more, and there's no reason to have two sites up. If you >>>> object >>>> to moving forward with this, please say so. >>>> >>>> [ ] +1, do it >>>> [ ] +0, whatevs >>>> [ ] -1, No (and say why, so we can address the problem) >>>> >>>> --Rich >>>> >
Re: first little patch for projects-new.apache.org
IMHO, icons for incubating and Attic projects should be different than standard sub-project (no idea about rendering of such icons) Regards, Hervé Le dimanche 8 mars 2015 17:56:52 Hervé BOUTEMY a écrit : > next: avoid copy paste for TLP vs sub-project icon and put the icon on the > left to have full alignment > > Regards, > > Hervé > > Le dimanche 8 mars 2015 17:43:49 Hervé BOUTEMY a écrit : > > and a third one: just white background instead of black > > > > Regards, > > > > Hervé > > > > Le dimanche 8 mars 2015 17:29:56 Hervé BOUTEMY a écrit : > > > another one, with simple instructions to make local tests > > > > > > Regards, > > > > > > Hervé > > > > > > Le dimanche 8 mars 2015 17:23:36 Hervé BOUTEMY a écrit : > > > > Hi, > > > > > > > > As promise, here is a first little patch: this is simply to add a link > > > > to > > > > our license, per our policy :) > > > > > > > > Regards, > > > > > > > > Hervé
Re: first little patch for projects-new.apache.org
next: avoid copy paste for TLP vs sub-project icon and put the icon on the left to have full alignment Regards, Hervé Le dimanche 8 mars 2015 17:43:49 Hervé BOUTEMY a écrit : > and a third one: just white background instead of black > > Regards, > > Hervé > > Le dimanche 8 mars 2015 17:29:56 Hervé BOUTEMY a écrit : > > another one, with simple instructions to make local tests > > > > Regards, > > > > Hervé > > > > Le dimanche 8 mars 2015 17:23:36 Hervé BOUTEMY a écrit : > > > Hi, > > > > > > As promise, here is a first little patch: this is simply to add a link > > > to > > > our license, per our policy :) > > > > > > Regards, > > > > > > Hervé Index: js/projects.js === --- js/projects.js (révision 1665047) +++ js/projects.js (copie de travail) @@ -475,6 +475,14 @@ return str.replace(/^([a-z])(.+)$/, function(c,a,b) { return a.toUpperCase() + b.toLowerCase() } ); } +function projectIcon(name) { +if (isTLP(name)) { + return "" +} else { + return "" +} +} + function renderProjectsList(cat) { var obj = document.getElementById('contents'); @@ -502,12 +510,7 @@ for (i in arr) { project = arr[i] var li = document.createElement('li'); - li.innerHTML = "" + projects[project].name + ""; - if (isTLP(projects[project].name)) { - li.innerHTML += "" - } else { - li.innerHTML += "" - } + li.innerHTML = projectIcon(projects[project].name) + "" + projects[project].name + ""; ul.appendChild(li) } obj.appendChild(ul); @@ -551,12 +554,7 @@ for (x in a) { if (a[x].toLowerCase() == lang.toLowerCase()) { var cli = document.createElement('li'); - cli.innerHTML = "" + projects[i].name + ""; - if (isTLP(projects[i].name)) { -cli.innerHTML += "" - } else { -cli.innerHTML += "" - } + cli.innerHTML = projectIcon(projects[i].name) + "" + projects[i].name + ""; cul.appendChild(cli) } } @@ -609,12 +607,7 @@ a[x] = a[x].replace("http://projects.apache.org/category/";, "").toLowerCase(); if (a[x] == lang) { var cli = document.createElement('li'); - cli.innerHTML = "" + projects[i].name + ""; - if (isTLP(projects[i].name)) { -cli.innerHTML += "" - } else { -cli.innerHTML += "" - } + cli.innerHTML = projectIcon(projects[i].name) + "" + projects[i].name + ""; cul.appendChild(cli) } } @@ -662,12 +655,7 @@ xdate = committees[projects[i].name] if (xdate == date) { var cli = document.createElement('li'); - cli.innerHTML = "" + projects[i].name + ""; - if (isTLP(projects[i].name)) { - cli.innerHTML += "" - } else { - cli.innerHTML += "" - } + cli.innerHTML = projectIcon(projects[i].name) + "" + projects[i].name + ""; cul.appendChild(cli) } } @@ -712,12 +700,7 @@ var cli = document.createElement('li'); cli.innerHTML = "" + projects[i].name + ": " + len + " committers"; if (unixgroups[i+'-pmc']) { - cli.innerHTML += ", " + unixgroups[i+'-pmc'].length + " PMC members"; - if (isTLP(projects[i].name)) { -cli.innerHTML += "" - } else { -cli.innerHTML += "" - } + cli.innerHTML = projectIcon(projects[i].name) + cli.innerHTML + ", " + unixgroups[i+'-pmc'].length + " PMC members"; } ul.appendChild(cli) } @@ -771,12 +754,7 @@ xlpmc = projects[i].pmc if (xlpmc == lpmc) { var cli = document.createElement('li'); - cli.innerHTML = "" + projects[i].name + ""; - if (isTLP(projects[i].name)) { - cli.innerHTML += "" - } else { - cli.innerHTML += "" - } + cli.innerHTML = projectIcon(projects[i].name) + "" + projects[i].name + ""; cul.appendChild(cli) } }
Re: first little patch for projects-new.apache.org
and a third one: just white background instead of black Regards, Hervé Le dimanche 8 mars 2015 17:29:56 Hervé BOUTEMY a écrit : > another one, with simple instructions to make local tests > > Regards, > > Hervé > > Le dimanche 8 mars 2015 17:23:36 Hervé BOUTEMY a écrit : > > Hi, > > > > As promise, here is a first little patch: this is simply to add a link to > > our license, per our policy :) > > > > Regards, > > > > Hervé Index: styles.css === --- styles.css (révision 1665047) +++ styles.css (copie de travail) @@ -105,7 +105,7 @@ } body { font: 15px/1.5 Helvetica, Arial, 'Liberation Sans', FreeSans, sans-serif; -background-color: #666; +background-color: #fff; } .leftbar { @@ -194,7 +194,6 @@ } #footer { - color: #DDD; font-style: italic; font-size: small; text-align: center;
Re: first little patch for projects-new.apache.org
another one, with simple instructions to make local tests Regards, Hervé Le dimanche 8 mars 2015 17:23:36 Hervé BOUTEMY a écrit : > Hi, > > As promise, here is a first little patch: this is simply to add a link to > our license, per our policy :) > > Regards, > > Hervé Index: STRUCTURE.txt === --- STRUCTURE.txt (révision 1664978) +++ STRUCTURE.txt (copie de travail) @@ -4,20 +4,20 @@ - Contains scripts used for import and maintenance of foundation-wide data, such as committer IDs/names, project VPs, founding dates, reporting cycles etc. - + /site: - Contains the HTML, images and javascript needed to run the site - + /site/json: - Contains the JSON data storage - + /site/json/foundation: - Contains foundation-wide JSON data (committers, chairs, podling evolution etc) - + /site/projects: - Contains project-specific base data. - + Suggested cron setup: scripts/cronjobs/parsechairs.py - daily scripts/cronjobs/parsecomitters.py - daily/hourly (whatever we need/want) @@ -28,4 +28,8 @@ scripts/import/parsecommittees.py - requires committee-info.txt to be present scripts/import/addpmc.py - manual run whenever a new PMC is founded - \ No newline at end of file +Webserver required: +To test the site locally, a webserver is required or you'll get +"Cross origin requests are only supported for HTTP" errors. +An easy setup is: run "python -m SimpleHTTPServer " from site directory +to have site available at http://localhost:/
first little patch for projects-new.apache.org
Hi, As promise, here is a first little patch: this is simply to add a link to our license, per our policy :) Regards, HervéIndex: datatables.html === --- datatables.html (révision 1665047) +++ datatables.html (copie de travail) @@ -52,7 +52,7 @@ - Copyright© 2015, the Apache Software Foundation. Licensed under the Apache License v/2.0 + Copyright© 2015, the Apache Software Foundation. Licensed under the http://www.apache.org/licenses/LICENSE-2.0";>Apache License, Version 2.0 For inquiries, contact dev@community.apache.org. Index: index.html === --- index.html (révision 1665047) +++ index.html (copie de travail) @@ -40,7 +40,7 @@ - Copyright© 2015, the Apache Software Foundation. Licensed under the Apache License v/2.0 + Copyright© 2015, the Apache Software Foundation. Licensed under the http://www.apache.org/licenses/LICENSE-2.0";>Apache License, Version 2.0 For inquiries, contact dev@community.apache.org.
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
Le dimanche 8 mars 2015 13:13:32 Daniel Gruno a écrit : > > CMS has staging, no? > > And perhaps the site is tiny because there is no easy editing: chicken and > > egg. IMHO, this new site has great graphics, but it really requires more > > than graphics. And the CMS could be part of the solution to do that. > > I'm not sure the CMS would add anything but trouble to this, as the site > is tied to svn two-way; It reads data but also commits it back to SVN > when changes occur. only the edit has such effect, and on some data, not on the site itself I'm sure using CMS would help make this site a normal site > Furthermore, I'm not sure the CMS would work for > non-tlp sites...I've never tried that :) Maven has Doxia site which is a sub-site, non-TLP > and it would still be > restricted to comdev in any case. yes, comdev is a TLP like any other: should use CMS, since once again the site should not only have calculated graphics: it should have plain text too, with editorial content > > >>> - the idea of online editing is great, but not knowing what happens > >>> behind > >>> the scene, I fear to add sub-projects: what sub-projects should be > >>> added? > >>> can sub- projects be removed if the addition gives unexpected result? > >> > >> A delete feature would make sense, yes. As for what can be added, that's > >> really up to the project, just as it was with the doap files. If you > >> feel something in your project is a sub project in itself, you can add > >> it. > > > > IIUC, the online editing just updates > > https://svn.apache.org/repos/asf/comdev/projects.apache.org/site/json/proj > > ects/ ? > > Then editing these files is the way to track changes, or do what the > > online > > editing doesn't have any feature to do? > > When you edit a project's JSON file, it triggers an email to this list, > detailing what was edited. > There is also (now) a job on the machine that updates it in SVN. The svn > goes both ways; You can update something online and it will be committed > to svn, or you can edit the json object in svn directly and it will be > checked out on the machine. ok, svnpubsub and svn commit list: really classical > > >>> - what should we do with DOAP? Did I miss some explanations on private@ > >>> or > >>> dev@ ML from a project I'm working on? > >> > >> DOAP will be replaced by the online editing. We haven't contacted > >> projects about this yet, but on the other hand, I don't think we'd just > >> change the DNS without letting folks know what we were doing. It's only > >> been in testing so far. Once it was on the path to becoming something > >> more official, surely projects would be included more. > > > > what is great with DOAP is that there is a schema: is there something > > equivalent with json? > > > >> But it also requires people other than me to chip in - I only have so > >> many hands and feet :) > > > > now that we know where the source code is, I hope people will involve. > > How do we send patches? To you in person? > > No, you send them to this ML :) This is a comdev project, not a > Humbedooh project ;) ok, I'll try tonight with some really simple changes before trying more complex work Regards, Hervé
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
On 2015-03-08 12:47, Hervé BOUTEMY wrote: Le dimanche 8 mars 2015 11:28:22 Daniel Gruno a écrit : - "Whereas the old pages were basic, the new ones have kind of an unusual dark theme to them and look unpolished (vs. just plain as the old one)" (copy/paste of another feedback that perfectly summarised a feeling I could not express better) Heh, not really a technical argument ;-) But if people feel it's too dark, they are more than welcome to submit a patch for something lighter :) yes, I'll try :) - can we have a link to source? how can we submit patches? how can we test for ourselves improvement ideas before submitting patches? This is really a good start, but IMHO, if we don't have community involved in updates, this new site will loose a great opportunity to have contributors (unless it is a choice to avoid contributors) It's under the comdev banner, and as such, is available at https://svn.apache.org/repos/asf/comdev/projects.apache.org/ great, I'll have a look - why doesn't this use the CMS for some classical pages? Should not some parts of the old site be added to the new graphic content? While graphics and generated content are great, I think that some handwritten content would be useful (to explain where data come from, for example, or what happened to DOAP, or how to contribute...) All excellent points. If you check out the source, you can see that all doap files have been converted to JSON instead. you mean that projects should not update DOAP files any more but these json files? I really missed the info (and this means we should perhaps move maven- doap-plugin to the Attic...) As for CMS, I don't see any reason to use the CMS compared to just editing it in svn - it's 4-5 pages, each around 10 lines of html, not a 500+ page behemoth. CMS has staging, no? And perhaps the site is tiny because there is no easy editing: chicken and egg. IMHO, this new site has great graphics, but it really requires more than graphics. And the CMS could be part of the solution to do that. I'm not sure the CMS would add anything but trouble to this, as the site is tied to svn two-way; It reads data but also commits it back to SVN when changes occur. Furthermore, I'm not sure the CMS would work for non-tlp sites...I've never tried that :) and it would still be restricted to comdev in any case. - the idea of online editing is great, but not knowing what happens behind the scene, I fear to add sub-projects: what sub-projects should be added? can sub- projects be removed if the addition gives unexpected result? A delete feature would make sense, yes. As for what can be added, that's really up to the project, just as it was with the doap files. If you feel something in your project is a sub project in itself, you can add it. IIUC, the online editing just updates https://svn.apache.org/repos/asf/comdev/projects.apache.org/site/json/projects/ ? Then editing these files is the way to track changes, or do what the online editing doesn't have any feature to do? When you edit a project's JSON file, it triggers an email to this list, detailing what was edited. There is also (now) a job on the machine that updates it in SVN. The svn goes both ways; You can update something online and it will be committed to svn, or you can edit the json object in svn directly and it will be checked out on the machine. - what should we do with DOAP? Did I miss some explanations on private@ or dev@ ML from a project I'm working on? DOAP will be replaced by the online editing. We haven't contacted projects about this yet, but on the other hand, I don't think we'd just change the DNS without letting folks know what we were doing. It's only been in testing so far. Once it was on the path to becoming something more official, surely projects would be included more. what is great with DOAP is that there is a schema: is there something equivalent with json? But it also requires people other than me to chip in - I only have so many hands and feet :) now that we know where the source code is, I hope people will involve. How do we send patches? To you in person? No, you send them to this ML :) This is a comdev project, not a Humbedooh project ;) Regards, Hervé With regards, Daniel. Please take this feedback as constructive feedback: I really like the new site, just need some little improvements to get out of beta and make a public release :) Regards, Hervé Le vendredi 6 mars 2015 11:52:35 Rich Bowen a écrit : I'd like for us to go ahead and replace projects.apache.org with projects-new.apache.org. It now has all the functionality that projects.a.o has, and much more, and there's no reason to have two sites up. If you object to moving forward with this, please say so. [ ] +1, do it [ ] +0, whatevs [ ] -1, No (and say why, so we can address the problem) --Rich
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
Le dimanche 8 mars 2015 11:28:22 Daniel Gruno a écrit : > > - "Whereas the old pages were basic, the new ones have kind of an unusual > > dark theme to them and look unpolished (vs. just plain as the old one)" > > (copy/paste of another feedback that perfectly summarised a feeling I > > could not express better) > > Heh, not really a technical argument ;-) But if people feel it's too > dark, they are more than welcome to submit a patch for something lighter :) yes, I'll try :) > > > - can we have a link to source? how can we submit patches? how can we test > > for ourselves improvement ideas before submitting patches? This is really > > a good start, but IMHO, if we don't have community involved in updates, > > this new site will loose a great opportunity to have contributors (unless > > it is a choice to avoid contributors) > > It's under the comdev banner, and as such, is available at > https://svn.apache.org/repos/asf/comdev/projects.apache.org/ great, I'll have a look > > > - why doesn't this use the CMS for some classical pages? Should not some > > parts of the old site be added to the new graphic content? While graphics > > and generated content are great, I think that some handwritten content > > would be useful (to explain where data come from, for example, or what > > happened to DOAP, or how to contribute...) > > All excellent points. If you check out the source, you can see that all > doap files have been converted to JSON instead. you mean that projects should not update DOAP files any more but these json files? I really missed the info (and this means we should perhaps move maven- doap-plugin to the Attic...) > As for CMS, I don't see any reason to use the CMS compared to just > editing it in svn - it's 4-5 pages, each around 10 lines of html, not a > 500+ page behemoth. CMS has staging, no? And perhaps the site is tiny because there is no easy editing: chicken and egg. IMHO, this new site has great graphics, but it really requires more than graphics. And the CMS could be part of the solution to do that. > > > - the idea of online editing is great, but not knowing what happens behind > > the scene, I fear to add sub-projects: what sub-projects should be added? > > can sub- projects be removed if the addition gives unexpected result? > > A delete feature would make sense, yes. As for what can be added, that's > really up to the project, just as it was with the doap files. If you > feel something in your project is a sub project in itself, you can add it. IIUC, the online editing just updates https://svn.apache.org/repos/asf/comdev/projects.apache.org/site/json/projects/ ? Then editing these files is the way to track changes, or do what the online editing doesn't have any feature to do? > > > - what should we do with DOAP? Did I miss some explanations on private@ or > > dev@ ML from a project I'm working on? > > DOAP will be replaced by the online editing. We haven't contacted > projects about this yet, but on the other hand, I don't think we'd just > change the DNS without letting folks know what we were doing. It's only > been in testing so far. Once it was on the path to becoming something > more official, surely projects would be included more. what is great with DOAP is that there is a schema: is there something equivalent with json? > > But it also requires people other than me to chip in - I only have so > many hands and feet :) now that we know where the source code is, I hope people will involve. How do we send patches? To you in person? Regards, Hervé > > With regards, > Daniel. > > > Please take this feedback as constructive feedback: I really like the new > > site, just need some little improvements to get out of beta and make a > > public release :) > > > > Regards, > > > > Hervé > > > > Le vendredi 6 mars 2015 11:52:35 Rich Bowen a écrit : > >> I'd like for us to go ahead and replace projects.apache.org with > >> projects-new.apache.org. It now has all the functionality that > >> projects.a.o has, and much more, and there's no reason to have two sites > >> up. If you object to moving forward with this, please say so. > >> > >> [ ] +1, do it > >> [ ] +0, whatevs > >> [ ] -1, No (and say why, so we can address the problem) > >> > >> --Rich
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
El vie., 6 de marzo de 2015 a las 23:40, Daniel Gruno () escribió: > > > On 2015-03-06 23:39, Christopher wrote: > > On Fri, Mar 6, 2015 at 5:35 PM, Shane Curcuru > (...) > >> Similarly, are we still using DOAP files? I could imagine that there > >> are others who were also referring to individual DOAPs or to the > >> projects.a.o/feeds content. > >> > >> These may not be widely used features, but if we're nuking them we > >> should be explicit about that and provide some notice about them being > >> gone. > >> > >> > > +1; it'd be nice to know that we don't have to update them anymore, if > > that's the case. > You don't, you update everything through the site ( currently at > https://projects-new.apache.org/edit ). > > Is there a reasonable audit trail of changes? Before now, the svn log of the DOAP files was effectively an audit trail. Does the project-new system provide something reasonably similar? Regards Santiago > With regards, > Daniel. > >
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
On 2015-03-08 11:12, Hervé BOUTEMY wrote: +0.5 I really like the graphics and general idea: that's for sure the way to go! but before switching, there are some issues to fix, IMHO: - "Whereas the old pages were basic, the new ones have kind of an unusual dark theme to them and look unpolished (vs. just plain as the old one)" (copy/paste of another feedback that perfectly summarised a feeling I could not express better) Heh, not really a technical argument ;-) But if people feel it's too dark, they are more than welcome to submit a patch for something lighter :) - can we have a link to source? how can we submit patches? how can we test for ourselves improvement ideas before submitting patches? This is really a good start, but IMHO, if we don't have community involved in updates, this new site will loose a great opportunity to have contributors (unless it is a choice to avoid contributors) It's under the comdev banner, and as such, is available at https://svn.apache.org/repos/asf/comdev/projects.apache.org/ - why doesn't this use the CMS for some classical pages? Should not some parts of the old site be added to the new graphic content? While graphics and generated content are great, I think that some handwritten content would be useful (to explain where data come from, for example, or what happened to DOAP, or how to contribute...) All excellent points. If you check out the source, you can see that all doap files have been converted to JSON instead. As for CMS, I don't see any reason to use the CMS compared to just editing it in svn - it's 4-5 pages, each around 10 lines of html, not a 500+ page behemoth. - the idea of online editing is great, but not knowing what happens behind the scene, I fear to add sub-projects: what sub-projects should be added? can sub- projects be removed if the addition gives unexpected result? A delete feature would make sense, yes. As for what can be added, that's really up to the project, just as it was with the doap files. If you feel something in your project is a sub project in itself, you can add it. - what should we do with DOAP? Did I miss some explanations on private@ or dev@ ML from a project I'm working on? DOAP will be replaced by the online editing. We haven't contacted projects about this yet, but on the other hand, I don't think we'd just change the DNS without letting folks know what we were doing. It's only been in testing so far. Once it was on the path to becoming something more official, surely projects would be included more. But it also requires people other than me to chip in - I only have so many hands and feet :) With regards, Daniel. Please take this feedback as constructive feedback: I really like the new site, just need some little improvements to get out of beta and make a public release :) Regards, Hervé Le vendredi 6 mars 2015 11:52:35 Rich Bowen a écrit : I'd like for us to go ahead and replace projects.apache.org with projects-new.apache.org. It now has all the functionality that projects.a.o has, and much more, and there's no reason to have two sites up. If you object to moving forward with this, please say so. [ ] +1, do it [ ] +0, whatevs [ ] -1, No (and say why, so we can address the problem) --Rich
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
+0.5 I really like the graphics and general idea: that's for sure the way to go! but before switching, there are some issues to fix, IMHO: - "Whereas the old pages were basic, the new ones have kind of an unusual dark theme to them and look unpolished (vs. just plain as the old one)" (copy/paste of another feedback that perfectly summarised a feeling I could not express better) - can we have a link to source? how can we submit patches? how can we test for ourselves improvement ideas before submitting patches? This is really a good start, but IMHO, if we don't have community involved in updates, this new site will loose a great opportunity to have contributors (unless it is a choice to avoid contributors) - why doesn't this use the CMS for some classical pages? Should not some parts of the old site be added to the new graphic content? While graphics and generated content are great, I think that some handwritten content would be useful (to explain where data come from, for example, or what happened to DOAP, or how to contribute...) - the idea of online editing is great, but not knowing what happens behind the scene, I fear to add sub-projects: what sub-projects should be added? can sub- projects be removed if the addition gives unexpected result? - what should we do with DOAP? Did I miss some explanations on private@ or dev@ ML from a project I'm working on? Please take this feedback as constructive feedback: I really like the new site, just need some little improvements to get out of beta and make a public release :) Regards, Hervé Le vendredi 6 mars 2015 11:52:35 Rich Bowen a écrit : > I'd like for us to go ahead and replace projects.apache.org with > projects-new.apache.org. It now has all the functionality that > projects.a.o has, and much more, and there's no reason to have two sites > up. If you object to moving forward with this, please say so. > > [ ] +1, do it > [ ] +0, whatevs > [ ] -1, No (and say why, so we can address the problem) > > --Rich
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
+1 Antoine On Mar 6, 2015, at 11:52 AM, Rich Bowen wrote: > I'd like for us to go ahead and replace projects.apache.org with > projects-new.apache.org. It now has all the functionality that projects.a.o > has, and much more, and there's no reason to have two sites up. If you object > to moving forward with this, please say so. > > [ ] +1, do it > [ ] +0, whatevs > [ ] -1, No (and say why, so we can address the problem) > > --Rich > > -- > Rich Bowen - rbo...@redhat.com > OpenStack Community Liaison > http://rdoproject.org/
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
On 03/06/2015 06:08 PM, Shane Curcuru wrote: This is really cool stuff, but I want to make sure that our 160++ projects actually understand what's going on (and will take the responsibility to keep their own info updated here), and that various outsiders who come to the site to find our projects get the information they need. we've told them several times. I recognize that's not the same as "projects actually understand". -- Rich Bowen - rbo...@rcbowen.com - @rbowen http://apachecon.com/ - @apachecon
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
Hi Hitesh, log onto https://projects-new.apache.org/edit/ and go to the bottom. Pick 'tez' as the PMC and nothing as the sub-project name, click the button and start typing :) That will create a tez.json file that the site will then use. With regards, Daniel. On 2015-03-07 04:56, Hitesh Shah wrote: Same question for Apache Tez. How do we need to fix the new website to show the Tez project? thanks — Hitesh On Mar 6, 2015, at 1:46 PM, Marshall Schor wrote: I can see the Apache UIMA entry in the "old" page, but it's not listed on the new page. What needs fixing? -Marshall Schor On 3/6/2015 11:52 AM, Rich Bowen wrote: I'd like for us to go ahead and replace projects.apache.org with projects-new.apache.org. It now has all the functionality that projects.a.o has, and much more, and there's no reason to have two sites up. If you object to moving forward with this, please say so. [ ] +1, do it [ ] +0, whatevs [ ] -1, No (and say why, so we can address the problem) --Rich
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
On 2015-03-07 05:20, Pei Chen wrote: This is pretty cool. Just curious- are the *.json automagically updated via a script of some sort? eg https://projects-new.apache.org/json/foundation/people.json We were thinking of reusing the data to pull that and populate our own people.html page dynamically via jQuery. Yeah, that's all updated automatically these days. With regards, Daniel. On Fri, Mar 6, 2015 at 10:43 PM, Mattmann, Chris A (3980) < chris.a.mattm...@jpl.nasa.gov> wrote: +1 please do so :) ++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 168-519, Mailstop: 168-527 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Associate Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ -Original Message- From: Mike Drob Reply-To: "dev@community.apache.org" Date: Friday, March 6, 2015 at 12:50 PM To: "dev@community.apache.org" Subject: Re: [VOTE] Replace projects.apache.org with projects-new.apache.org Minor design nit: the content boxes should either be centered or do a better job of auto filling the available horizontal space. Otherwise, it looks spiffy, despite being fairly tiny on my monitor. Would also like to see the releases page sort by date by default, and show more than 10 entries. This is not a reason to block the switch though. +0.9 in current state, +1 once my comments are addressed. On Fri, Mar 6, 2015 at 2:29 PM, Yann Ylavic wrote: On Fri, Mar 6, 2015 at 5:52 PM, Rich Bowen wrote: I'd like for us to go ahead and replace projects.apache.org with projects-new.apache.org. -0, do we need all these js/css/cookies from google(apis)? I never had to disable noscript for anything than a.o on a.o until then, whitelisting *.gg.c annoys me a bit...
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
+1 Thanks for your work, much more better now! :-) # web: http://www.jgeppert.com twitter: http://twitter.com/jogep 2015-03-07 5:20 GMT+01:00 Pei Chen : > This is pretty cool. > Just curious- are the *.json automagically updated via a script of some > sort? > eg https://projects-new.apache.org/json/foundation/people.json > We were thinking of reusing the data to pull that and populate our own > people.html page dynamically via jQuery. > > > On Fri, Mar 6, 2015 at 10:43 PM, Mattmann, Chris A (3980) < > chris.a.mattm...@jpl.nasa.gov> wrote: > > > +1 please do so :) > > > > ++ > > Chris Mattmann, Ph.D. > > Chief Architect > > Instrument Software and Science Data Systems Section (398) > > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > > Office: 168-519, Mailstop: 168-527 > > Email: chris.a.mattm...@nasa.gov > > WWW: http://sunset.usc.edu/~mattmann/ > > ++ > > Adjunct Associate Professor, Computer Science Department > > University of Southern California, Los Angeles, CA 90089 USA > > ++ > > > > > > > > > > > > > > -Original Message- > > From: Mike Drob > > Reply-To: "dev@community.apache.org" > > Date: Friday, March 6, 2015 at 12:50 PM > > To: "dev@community.apache.org" > > Subject: Re: [VOTE] Replace projects.apache.org with > > projects-new.apache.org > > > > >Minor design nit: the content boxes should either be centered or do a > > >better job of auto filling the available horizontal space. Otherwise, it > > >looks spiffy, despite being fairly tiny on my monitor. > > > > > >Would also like to see the releases page sort by date by default, and > show > > >more than 10 entries. This is not a reason to block the switch though. > > > > > >+0.9 in current state, +1 once my comments are addressed. > > > > > >On Fri, Mar 6, 2015 at 2:29 PM, Yann Ylavic > wrote: > > > > > >> On Fri, Mar 6, 2015 at 5:52 PM, Rich Bowen wrote: > > >> > I'd like for us to go ahead and replace projects.apache.org with > > >> > projects-new.apache.org. > > >> > > >> -0, do we need all these js/css/cookies from google(apis)? > > >> I never had to disable noscript for anything than a.o on a.o until > > >> then, whitelisting *.gg.c annoys me a bit... > > >> > > > > >
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
This is pretty cool. Just curious- are the *.json automagically updated via a script of some sort? eg https://projects-new.apache.org/json/foundation/people.json We were thinking of reusing the data to pull that and populate our own people.html page dynamically via jQuery. On Fri, Mar 6, 2015 at 10:43 PM, Mattmann, Chris A (3980) < chris.a.mattm...@jpl.nasa.gov> wrote: > +1 please do so :) > > ++ > Chris Mattmann, Ph.D. > Chief Architect > Instrument Software and Science Data Systems Section (398) > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > Office: 168-519, Mailstop: 168-527 > Email: chris.a.mattm...@nasa.gov > WWW: http://sunset.usc.edu/~mattmann/ > ++ > Adjunct Associate Professor, Computer Science Department > University of Southern California, Los Angeles, CA 90089 USA > ++ > > > > > > > -Original Message- > From: Mike Drob > Reply-To: "dev@community.apache.org" > Date: Friday, March 6, 2015 at 12:50 PM > To: "dev@community.apache.org" > Subject: Re: [VOTE] Replace projects.apache.org with > projects-new.apache.org > > >Minor design nit: the content boxes should either be centered or do a > >better job of auto filling the available horizontal space. Otherwise, it > >looks spiffy, despite being fairly tiny on my monitor. > > > >Would also like to see the releases page sort by date by default, and show > >more than 10 entries. This is not a reason to block the switch though. > > > >+0.9 in current state, +1 once my comments are addressed. > > > >On Fri, Mar 6, 2015 at 2:29 PM, Yann Ylavic wrote: > > > >> On Fri, Mar 6, 2015 at 5:52 PM, Rich Bowen wrote: > >> > I'd like for us to go ahead and replace projects.apache.org with > >> > projects-new.apache.org. > >> > >> -0, do we need all these js/css/cookies from google(apis)? > >> I never had to disable noscript for anything than a.o on a.o until > >> then, whitelisting *.gg.c annoys me a bit... > >> > >
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
Same question for Apache Tez. How do we need to fix the new website to show the Tez project? thanks — Hitesh On Mar 6, 2015, at 1:46 PM, Marshall Schor wrote: > I can see the Apache UIMA entry in the "old" page, but it's not listed on the > new page. What needs fixing? > > -Marshall Schor > > On 3/6/2015 11:52 AM, Rich Bowen wrote: >> I'd like for us to go ahead and replace projects.apache.org with >> projects-new.apache.org. It now has all the functionality that projects.a.o >> has, and much more, and there's no reason to have two sites up. If you object >> to moving forward with this, please say so. >> >> [ ] +1, do it >> [ ] +0, whatevs >> [ ] -1, No (and say why, so we can address the problem) >> >> --Rich >> >
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
LGTM, but don't forget to update the www.apache.org homepageto base it on the new stuff instead of the DOAP files. On Friday, March 6, 2015 10:47 PM, "Mattmann, Chris A (3980)" wrote: +1 please do so :) ++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 168-519, Mailstop: 168-527 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Associate Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ -Original Message- From: Mike Drob Reply-To: "dev@community.apache.org" Date: Friday, March 6, 2015 at 12:50 PM To: "dev@community.apache.org" Subject: Re: [VOTE] Replace projects.apache.org with projects-new.apache.org >Minor design nit: the content boxes should either be centered or do a >better job of auto filling the available horizontal space. Otherwise, it >looks spiffy, despite being fairly tiny on my monitor. > >Would also like to see the releases page sort by date by default, and show >more than 10 entries. This is not a reason to block the switch though. > >+0.9 in current state, +1 once my comments are addressed. > >On Fri, Mar 6, 2015 at 2:29 PM, Yann Ylavic wrote: > >> On Fri, Mar 6, 2015 at 5:52 PM, Rich Bowen wrote: >> > I'd like for us to go ahead and replace projects.apache.org with >> > projects-new.apache.org. >> >> -0, do we need all these js/css/cookies from google(apis)? >> I never had to disable noscript for anything than a.o on a.o until >> then, whitelisting *.gg.c annoys me a bit... >>
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
+1 please do so :) ++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 168-519, Mailstop: 168-527 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Associate Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ -Original Message- From: Mike Drob Reply-To: "dev@community.apache.org" Date: Friday, March 6, 2015 at 12:50 PM To: "dev@community.apache.org" Subject: Re: [VOTE] Replace projects.apache.org with projects-new.apache.org >Minor design nit: the content boxes should either be centered or do a >better job of auto filling the available horizontal space. Otherwise, it >looks spiffy, despite being fairly tiny on my monitor. > >Would also like to see the releases page sort by date by default, and show >more than 10 entries. This is not a reason to block the switch though. > >+0.9 in current state, +1 once my comments are addressed. > >On Fri, Mar 6, 2015 at 2:29 PM, Yann Ylavic wrote: > >> On Fri, Mar 6, 2015 at 5:52 PM, Rich Bowen wrote: >> > I'd like for us to go ahead and replace projects.apache.org with >> > projects-new.apache.org. >> >> -0, do we need all these js/css/cookies from google(apis)? >> I never had to disable noscript for anything than a.o on a.o until >> then, whitelisting *.gg.c annoys me a bit... >>
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
On 3/6/15 5:40 PM, Daniel Gruno wrote: > > > On 2015-03-06 23:39, Christopher wrote: >> On Fri, Mar 6, 2015 at 5:35 PM, Shane Curcuru >> wrote: >> >>> Question: is there any plan to redirect old URLs? >>> >>> The old projects.a.o certainly is clunky, but there may well be a few >>> people who have linked to various parts of the site. >>> >>> Similarly, are we still using DOAP files? I could imagine that there >>> are others who were also referring to individual DOAPs or to the >>> projects.a.o/feeds content. >>> >>> These may not be widely used features, but if we're nuking them we >>> should be explicit about that and provide some notice about them being >>> gone. >>> >>> >> +1; it'd be nice to know that we don't have to update them anymore, if >> that's the case. > You don't, you update everything through the site ( currently at > https://projects-new.apache.org/edit ). Ah, so this means DOAP files are essentially deprecated, correct? Have we documented how PMCs are supposed to update their project's details, and communicated to pmcs@ the expectation that they must now keep this stuff updated instead of the DOAP files? This is really cool stuff, but I want to make sure that our 160++ projects actually understand what's going on (and will take the responsibility to keep their own info updated here), and that various outsiders who come to the site to find our projects get the information they need. - Shane > > With regards, > Daniel. >
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
On 2015-03-06 23:39, Christopher wrote: On Fri, Mar 6, 2015 at 5:35 PM, Shane Curcuru wrote: Question: is there any plan to redirect old URLs? The old projects.a.o certainly is clunky, but there may well be a few people who have linked to various parts of the site. Similarly, are we still using DOAP files? I could imagine that there are others who were also referring to individual DOAPs or to the projects.a.o/feeds content. These may not be widely used features, but if we're nuking them we should be explicit about that and provide some notice about them being gone. +1; it'd be nice to know that we don't have to update them anymore, if that's the case. You don't, you update everything through the site ( currently at https://projects-new.apache.org/edit ). With regards, Daniel.
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
On Fri, Mar 6, 2015 at 5:35 PM, Shane Curcuru wrote: > Question: is there any plan to redirect old URLs? > > The old projects.a.o certainly is clunky, but there may well be a few > people who have linked to various parts of the site. > > Similarly, are we still using DOAP files? I could imagine that there > are others who were also referring to individual DOAPs or to the > projects.a.o/feeds content. > > These may not be widely used features, but if we're nuking them we > should be explicit about that and provide some notice about them being > gone. > > +1; it'd be nice to know that we don't have to update them anymore, if that's the case.
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
Question: is there any plan to redirect old URLs? The old projects.a.o certainly is clunky, but there may well be a few people who have linked to various parts of the site. Similarly, are we still using DOAP files? I could imagine that there are others who were also referring to individual DOAPs or to the projects.a.o/feeds content. These may not be widely used features, but if we're nuking them we should be explicit about that and provide some notice about them being gone. - Shane P.S. There's some perspective for you on the Releases tab... 5306 software product releases (and those are just ones that the scripts can detect). On 3/6/15 11:52 AM, Rich Bowen wrote: > I'd like for us to go ahead and replace projects.apache.org with > projects-new.apache.org. It now has all the functionality that > projects.a.o has, and much more, and there's no reason to have two sites > up. If you object to moving forward with this, please say so. > > [ ] +1, do it > [ ] +0, whatevs > [ ] -1, No (and say why, so we can address the problem) > > --Rich >
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
I can see the Apache UIMA entry in the "old" page, but it's not listed on the new page. What needs fixing? -Marshall Schor On 3/6/2015 11:52 AM, Rich Bowen wrote: > I'd like for us to go ahead and replace projects.apache.org with > projects-new.apache.org. It now has all the functionality that projects.a.o > has, and much more, and there's no reason to have two sites up. If you object > to moving forward with this, please say so. > > [ ] +1, do it > [ ] +0, whatevs > [ ] -1, No (and say why, so we can address the problem) > > --Rich >
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
Just happened to notice that the new website's header seems to be truncated on mobile. I use Chrome on Android.. http://imgur.com/8gZfu0i On 6 Mar 2015 16:53, "Rich Bowen" wrote: > I'd like for us to go ahead and replace projects.apache.org with > projects-new.apache.org. It now has all the functionality that > projects.a.o has, and much more, and there's no reason to have two sites > up. If you object to moving forward with this, please say so. > > [ ] +1, do it > [ ] +0, whatevs > [ ] -1, No (and say why, so we can address the problem) > > --Rich > > -- > Rich Bowen - rbo...@redhat.com > OpenStack Community Liaison > http://rdoproject.org/ >
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
Minor design nit: the content boxes should either be centered or do a better job of auto filling the available horizontal space. Otherwise, it looks spiffy, despite being fairly tiny on my monitor. Would also like to see the releases page sort by date by default, and show more than 10 entries. This is not a reason to block the switch though. +0.9 in current state, +1 once my comments are addressed. On Fri, Mar 6, 2015 at 2:29 PM, Yann Ylavic wrote: > On Fri, Mar 6, 2015 at 5:52 PM, Rich Bowen wrote: > > I'd like for us to go ahead and replace projects.apache.org with > > projects-new.apache.org. > > -0, do we need all these js/css/cookies from google(apis)? > I never had to disable noscript for anything than a.o on a.o until > then, whitelisting *.gg.c annoys me a bit... >
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
On Fri, Mar 6, 2015 at 5:52 PM, Rich Bowen wrote: > I'd like for us to go ahead and replace projects.apache.org with > projects-new.apache.org. -0, do we need all these js/css/cookies from google(apis)? I never had to disable noscript for anything than a.o on a.o until then, whitelisting *.gg.c annoys me a bit...
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
On Fri, Mar 6, 2015 at 11:52 AM, Rich Bowen wrote: > I'd like for us to go ahead and replace projects.apache.org with > projects-new.apache.org. It now has all the functionality that projects.a.o > has, and much more, and there's no reason to have two sites up. If you > object to moving forward with this, please say so. > > [ ] +1, do it > [ ] +0, whatevs > [ ] -1, No (and say why, so we can address the problem) -0, index on new site took in excess of 20 seconds to load for me in chrome. About 10 seconds trying again in firefox. Whereas the old pages were basic, the new ones have kind of an unusual dark theme to them and look unpolished (vs. just plain as the old one)
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
+1 On 6 Mar 2015 17:53, "Rich Bowen" wrote: > I'd like for us to go ahead and replace projects.apache.org with > projects-new.apache.org. It now has all the functionality that > projects.a.o has, and much more, and there's no reason to have two sites > up. If you object to moving forward with this, please say so. > > [ ] +1, do it > [ ] +0, whatevs > [ ] -1, No (and say why, so we can address the problem) > > --Rich > > -- > Rich Bowen - rbo...@redhat.com > OpenStack Community Liaison > http://rdoproject.org/ >
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
+1 On 2015-03-06 17:52, Rich Bowen wrote: > I'd like for us to go ahead and replace projects.apache.org with > projects-new.apache.org. It now has > all the functionality that projects.a.o has, and much more, and there's no > reason to have two sites > up. If you object to moving forward with this, please say so. > > [ ] +1, do it > [ ] +0, whatevs > [ ] -1, No (and say why, so we can address the problem) > > --Rich >
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
+1, with two comments: 1. the projects page on the new site has a link to "Contributors", which is broken. 2. there's some information linked on the old site about DOAP files and RSS/Atom feeds, which do not exist (or are not obvious) on the new site. -- Christopher L Tubbs II http://gravatar.com/ctubbsii On Fri, Mar 6, 2015 at 11:52 AM, Rich Bowen wrote: > I'd like for us to go ahead and replace projects.apache.org with > projects-new.apache.org. It now has all the functionality that > projects.a.o has, and much more, and there's no reason to have two sites > up. If you object to moving forward with this, please say so. > > [ ] +1, do it > [ ] +0, whatevs > [ ] -1, No (and say why, so we can address the problem) > > --Rich > > -- > Rich Bowen - rbo...@redhat.com > OpenStack Community Liaison > http://rdoproject.org/ >