Re: [ DISCUSS ] Pre-Attic banner in the project website

t; Looks like there is discussion on livy[1] for retirement, any chance to try > there..? > > > 1. https://lists.apache.org/thread/mvf80qhh81lkqrmy8vm8ggsbgjwj05b1 > > On Tue, Jul 5, 2022 at 10:35 PM Hervé BOUTEMY wrote: > > Good idea: such banners could help projects

Re: [ DISCUSS ] Pre-Attic banner in the project website

Good idea: such banners could help projects needing help to make noise beyond mailing lists, hoping to get some new contributors. I suppose this is a service the Attic could provide to help projects avoid getting to the Attic :) Currently, when such a banner is added it points to an Attic

Re: removing the Attic banner from Ambari: help needed

From Attic point of view, the work is near completed: I'm just keeping our > > page up https://attic.apache.org/projects/ambari.html while you're > > reopening item by item, and once you tell me you're ready, I'll remove > > the page and close https://issues.apache.org/jir

Re: removing the Attic banner from Ambari: help needed

> > > >>> On Sat, 18 Jun 2022 at 12:03, sebb wrote: > > > >>> > > > >>> > > > >>> Try clearing the browser cache or a different browser. > > > >>> > > > >>> However the Wiki banner is still showing for me

removing the Attic banner from Ambari: help needed

I removed the flag source in xdocs, then in docs because our usual CI commands did not expect the removal of content but only addition/modification but it seems there is still something preventing the banner from disappearing from Ambari site https://ambari.apache.org/ Any idea why? Is the

Re: Question about fork an attic project

Hi Brama, Can you confirm I understood your idea: ideally, you'd like to revive Ambari at ASF, keeping Ambari name and everything else: you'd be forming a new PMC to revive the community around it (users, contributors, maintainers). If keeping the name is not ok, your plan would be to fork and

[HELP WANTED] volunteers for testing our instructions to retire a project

Hi, In the last month, we simplified a lot our retirement process: it is now streamlined, and even simplified by a few scripts: http://attic.apache.org/process.html After the board meeting from yesterday, we have 2 projects to retire: it would be nice to have volunteers to test the process as

Re: reviewing our detailed process instructions

Le vendredi 14 mai 2021, 13:59:22 CEST sebb a écrit : > On Fri, 14 May 2021 at 06:34, Hervé BOUTEMY wrote: > > Hi all, > > > > I just finished Trafodion's move to Attic: it was a lot easier than 1 year > > ago, being helped by 2 nice scripts. But the process docume

reviewing our detailed process instructions

Hi all, I just finished Trafodion's move to Attic: it was a lot easier than 1 year ago, being helped by 2 nice scripts. But the process documentation did not mention these scripts, then showed previous complexity. I updated the documentation to take these scripts into account. Please review

Re: Renaming of Git repos when moving to Attic

Le vendredi 2 avril 2021, 02:11:24 CEST sebb a écrit : > On Thu, 1 Apr 2021 at 22:24, Hervé BOUTEMY wrote: > > Le jeudi 1 avril 2021, 12:21:20 CEST sebb a écrit : > > > Are we all agreed that: > > > - projects which are moved to the Attic should not have their

Re: Renaming of Git repos when moving to Attic

Le jeudi 1 avril 2021, 12:21:20 CEST sebb a écrit : > Are we all agreed that: > - projects which are moved to the Attic should not have their > repositories renamed > - repositories should instead be made read-only and marked as such (as per > [4]) yes, agree > > If so, I will raise an INFRA

Re: Renaming of Git repos when moving to Attic

Le jeudi 1 avril 2021, 20:45:27 CEST Mads Toftum a écrit : > On Thu, Apr 01, 2021 at 11:21:20AM +0100, sebb wrote: > > Are we all agreed that: > > - projects which are moved to the Attic should not have their > > repositories renamed > > - repositories should instead be made read-only and marked

Re: Renaming of Git repos when moving to Attic

looking at Falcon retirement [1], which has a Git repo: - current Gitbox repo is attic-falcon.git [2] - but GitHub (where everybody is looking at) is still falcon.git [3] And on GitHub, a clear sign of retirement for users exists, that has not been activated on this falcon.git: that is

Re: Renaming of Git repos when moving to Attic

yes, many improvements in the process were done in recent years to avoid requiring write access (because this was the step in the process that was the most time/energy consuming between Attic members and infra) now that requiring write access means not only cumbersome efforts but also breaking

Re: svn commit: r1876973 - /attic/site/xdocs/tracking.xml

for next board meeting @Greg, this was not really what you were expecting from contacting Attic PMC, but can you advise, please? Regards, Hervé Le samedi 25 avril 2020, 15:41:33 CEST Hervé BOUTEMY a écrit : > let's investigate first, we'll see after what has to be done: rollback or >

Re: svn commit: r1876973 - /attic/site/xdocs/tracking.xml

ether the PMC had > been correctly terminated. > I guess I should revert the changes for now? > > On Sat, 25 Apr 2020 at 13:26, Hervé BOUTEMY wrote: > > Hi Sebb, > > > > It seems you marked Chewka as moved to the Attic [1] > > But I don't see any associated boa

Re: svn commit: r1876973 - /attic/site/xdocs/tracking.xml

Hi Sebb, It seems you marked Chewka as moved to the Attic [1] But I don't see any associated board resolution: how did you go to this conclusion? Should really Attic work on Chewka retirement? Regards, Hervé [1]

Re: DOAP files for retired projects

nice job done: https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk/data/projects-override/ thank you Sebb Le mardi 3 mars 2020, 15:12:15 CET sebb a écrit : > On Thu, 13 Feb 2020 at 21:53, Hervé BOUTEMY wrote: > > Le jeudi 13 février 2020, 00:57:26 CET Mads Toftu

Re: DOAP files for retired projects

Le jeudi 13 février 2020, 00:57:26 CET Mads Toftum a écrit : > On Wed, Feb 12, 2020 at 03:21:04PM -0800, Hen wrote: > > Sounds good to me. I doubt folk are looking at the DOAP file for status > > instead of checking the updated site. > > Aren't these doap files used for building some of >

[REPORT] Board report 2019-01-16/Attic

Hi, FYI ; I submitted the following Board Report : https://whimsy.apache.org/board/agenda/2019-01-16/Attic ## Description: PMC Attic is responsible for the oversight of projects which otherwise would not have oversight. ## Issues: There are no issues requiring board attention at this

Re: no projects in the Attic

Hi, Le dimanche 22 juillet 2018, 08:21:38 CEST Henk P. Penning a écrit : > On Sat, 21 Jul 2018, Hervé BOUTEMY wrote: > > Date: Sat, 21 Jul 2018 19:17:03 +0200 > > From: Hervé BOUTEMY > > To: general@attic.apache.org > > Subject: Re: no projects in the A

Re: no projects in the Attic

I like that there is no project in the Attic: there is only static codebases (and other types of assets like mailing lists or sites), with nobody to make them evolve, then no project (project means evolution) IMHO, recreating frozen projects is not a good idea it's a question of wording to

Re: Clarifying the process for PMCs adopting codebases from the Attic

+1 to most parts the only part that I'd prefer to keep simple is the Board vote vs Attic vote: this is exactly the type of vote we tried to get from Board when digging into XMLBeans details and got as answer "just do it" Which is sufficient to me: we don't create any new project (= a new

Re: [jira] [Commented] (ATTIC-169) give XMLBeans to POI PMC

Infrastructure at: > us...@infra.apache.org > > > give XMLBeans to POI PMC > > > > > > Key: ATTIC-169 > > URL: https://issues.apache.org/jira/browse/ATTIC-169 > > > >

Re: svn commit: r1832298 - in /xmlbeans/trunk: ./ external/lib/ samples/AbstractTypes/ samples/Any/ samples/DateTime/ samples/MixedContent/ samples/OrderMatters/ samples/SampleTemplate/ samples/Schema

IIUC, that means that we should remove XMLBeans from Attic and switch its ownership to POI? then for example remove the banner on http://xmlbeans.apache.org/? Regards, Hervé Le dimanche 27 mai 2018, 11:07:46 CEST fannin...@apache.org a écrit : > Hi Mads,The Apache POI team are taking over

Re: GitBox attic-test PoC now working on BuildBot

great, thank you Sebb! the last question is: do we try to import Attic svn history (which may be complex, as seen with projects.apache.org [1]) or do we just get the current state? For Attic, history does not seem absolutely necessary Do we launch Git + separate branch for output with just the

Re: getting a svn2git mirror Git repository (read-only for now)

Le dimanche 6 mai 2018, 12:11:52 CEST Jan Iversen a écrit : > > El 6 may 2018, a las 12:01, Hervé BOUTEMY <herve.bout...@free.fr> > > escribió: > > > > I'd like to prepare a Git mirror of our Attic site svn repo: that would be > > useful as a general cont

getting a svn2git mirror Git repository (read-only for now)

I'd like to prepare a Git mirror of our Attic site svn repo: that would be useful as a general contribution helper for people more used to Git than svn (which happens more and more these times) and this would prepare an eventual future switch to Git as read-write canonical repo from

Re: Proposal to fix oltu.[.us|.eu].apache.org banner prefixing

Le samedi 5 mai 2018, 17:38:21 CEST Hervé BOUTEMY a écrit : > Le samedi 5 mai 2018, 17:24:09 CEST sebb a écrit : > > On 5 May 2018 at 16:15, Hervé BOUTEMY <herve.bout...@free.fr> wrote: > > > Honestly, who knows or uses the .us and .eu DNS names? > > > the requirem

Re: Proposal to fix oltu.[.us|.eu].apache.org banner prefixing

Le samedi 5 mai 2018, 17:24:09 CEST sebb a écrit : > On 5 May 2018 at 16:15, Hervé BOUTEMY <herve.bout...@free.fr> wrote: > > Honestly, who knows or uses the .us and .eu DNS names? > > the requirement seems quite theoretical to me: is not worth making site > > mainte

Re: Proposal to fix oltu.[.us|.eu].apache.org banner prefixing

Honestly, who knows or uses the .us and .eu DNS names? the requirement seems quite theoretical to me: is not worth making site maintenance harder but I had a little idea on the flag file creation that could do the job, while even simplifying site maintenance = what it is more about since what

Re: idea for site maintenance simplification

Le samedi 5 mai 2018, 13:10:37 CEST sebb a écrit : > On 5 May 2018 at 11:48, Hervé BOUTEMY <herve.bout...@free.fr> wrote: > > Le samedi 5 mai 2018, 12:00:49 CEST sebb a écrit : > >> On 5 May 2018 at 05:25, Hervé BOUTEMY <herve.bout...@free.fr> wrote: > >> &

Re: idea for site maintenance simplification

Le samedi 5 mai 2018, 13:01:34 CEST Jan Iversen a écrit : [...] > > You need to figure out now if you want to continue to work with us as PMC > > member and committer... > > As above, I have no problem filing board reports, not even retiring a > project now and then (provided I have good tools,

Re: idea for site maintenance simplification

Le samedi 5 mai 2018, 12:00:49 CEST sebb a écrit : > On 5 May 2018 at 05:25, Hervé BOUTEMY <herve.bout...@free.fr> wrote: > > Hi, > > > > I took time to read the whole discussions from april and understand what > > was the common objective, and what were solut

Re: idea for site maintenance simplification

Le samedi 5 mai 2018, 07:39:02 CEST Jan Iversen a écrit : > Sent from my iPad > > > On 5 May 2018, at 06:25, Hervé BOUTEMY <herve.bout...@free.fr> wrote: > > > > Hi, > > > > I took time to read the whole discussions from april and understand what &

idea for site maintenance simplification

Hi, I took time to read the whole discussions from april and understand what was the common objective, and what were solutions envisioned and discussed and partly done and partly with consensus yet to be found. AFAIK, we have a common objective: simplifying attic site maintenance. The

Re: attic-test.git created

Le lundi 30 avril 2018, 22:43:12 CEST Jan Iversen a écrit : > Sent from my iPad > > > On 30 Apr 2018, at 22:28, Hervé BOUTEMY <herve.bout...@free.fr> wrote: > > > > Le lundi 30 avril 2018, 21:03:24 CEST Jan Iversen a écrit : > >> Sent from my iPad >

Re: Separate branch for site (was: Move attic to git,)

Le lundi 30 avril 2018, 20:47:47 CEST sebb a écrit : > On 30 April 2018 at 19:24, Hervé BOUTEMY <herve.bout...@free.fr> wrote: > > Le lundi 30 avril 2018, 12:46:09 CEST sebb a écrit : > >> On 30 April 2018 at 06:56, Hervé BOUTEMY <herve.bout...@free.fr> wrote: > &

Re: attic-test.git created

I don't get what's the issue with creating a test Git repo, that is independent from anything else, and that was discussed on the ML I did the exact same at GitHub just because it was outside Apache then was even more clear that it was a side test to have chance to get common tests instead of

Re: Separate branch for site (was: Move attic to git,)

Le lundi 30 avril 2018, 12:46:09 CEST sebb a écrit : > On 30 April 2018 at 06:56, Hervé BOUTEMY <herve.bout...@free.fr> wrote: > > Le lundi 30 avril 2018, 03:19:20 CEST sebb a écrit : > >> On 29 April 2018 at 22:11, Hervé BOUTEMY <herve.bout...@free.fr> wrote: &

Re: discussion/vote new site (again, but last time from me)

Le lundi 30 avril 2018, 03:10:46 CEST sebb a écrit : > On 29 April 2018 at 18:53, Jan Iversen wrote: > > Hi. > > > > Based on a suggestion from Henk, I hereby once again try to start a > > discussion/vote on the new site. > > > > We need to select either lua-site or

Re: Separate branch for site (was: Move attic to git,)

Le lundi 30 avril 2018, 03:19:20 CEST sebb a écrit : > On 29 April 2018 at 22:11, Hervé BOUTEMY <herve.bout...@free.fr> wrote: > > better than a discussion: a demo > > > > here is the website: > > https://asf-attic.github.io/ > > > > its source: htt

Re: Separate branch for site (was: Move attic to git,)

to checkout the output branch and update content after rebuild But what is done here with GitHub GitPubSub equivalent can be done exactly the same way at Apache Software Foundation Regards, Hervé Le dimanche 29 avril 2018, 19:13:43 CEST Hervé BOUTEMY a écrit : > Le dimanche 29 avril 2018, 14

Re: svn commit: r1830424 - /attic/site/xdocs/process.xml

Le samedi 28 avril 2018, 19:44:45 CEST Jan Iversen a écrit : > Sent from my iPad > > > On 28 Apr 2018, at 18:10, Hervé BOUTEMY <herve.bout...@free.fr> wrote: > > > > Le samedi 28 avril 2018, 15:07:34 CEST Jan Iversen a écrit : > >> Sent from my iPad >

Re: svn commit: r1830452 - /attic/site/xdocs/process.xml

+1 completely agree on the 2 use cases: being able to build locally is useful for complex cases, but avoiding to require it is useful for normal use this will be one of my expectations when we'll change the build engine: being able to build locally without too much hassle when I want to test

Re: svn commit: r1830424 - /attic/site/xdocs/process.xml

rom my iPad > >> > >>>> On 28 Apr 2018, at 14:28, sebb <seb...@gmail.com> wrote: > >>>> > >>>> On 28 April 2018 at 13:06, Jan Iversen <j...@apache.org> wrote: > >>>> > >>>> > >>>> Sent

Re: svn commit: r1830437 - /attic/site/xdocs/flagged/

ah sorry, I missed that one do you prefer me to just fix (add the "x") to the procedure? or revert? (I don't know how to proceed now to propose little changes: GitHub PRs in the future will probably help on proposing concrete little changes to discuss before merging or not...) notice that the

Re: Use svn.apache.org URLs for Subversion source

viewvc is for human to look at: IMHO useful for people to have more human readable info I can uderstand that my personal habit of doing: url of effective svn can be confusing If you prefer having strict equality between link text and link href, I'd like to add "(viewvc)" additional text for

Re: Request GitBox access for Attic?

Le samedi 28 avril 2018, 12:30:46 CEST sebb a écrit : > On 28 April 2018 at 11:15, Hervé BOUTEMY <herve.bout...@free.fr> wrote: > > creating a GitBox/GitHub test repository is easy: it's self service [1] > > I looked at that, and one can only create empty repos for projects

Re: Move attic to git,

Le samedi 28 avril 2018, 13:17:03 CEST sebb a écrit : > On 28 April 2018 at 11:52, Hervé BOUTEMY <herve.bout...@free.fr> wrote: > > ok for me > > > > IIUC, the Buildbot configuration that Sebb started can work from Git > > source as well as from svn: that's great

Re: svn commit: r1830424 - /attic/site/xdocs/process.xml

oh, I was just trying to document, not change anything: - the svnwcsub part is what works for years but was not well known outside infra team - the buildbot job *for the current build.sh* (in/repos/asf/attic/site/) which is just a way to not require to do the build locally this does not include

Re: Move attic to git,

ok for me IIUC, the Buildbot configuration that Sebb started can work from Git source as well as from svn: that's great one thing that we should do IMHO would be to better separate source from generated output: only source should go to Git, and generated html should be elsewhere this means

Re: Buildbot now working, but checkin not enabled

great news: thank you Sebb I just tried to add a link to this Buildbot job in our documentation, but it seems the job did not manage to commit the change in generated html: - my commit: http://svn.apache.org/r1830424 - the Buildbot run: https://ci.apache.org/builders/attic-site/builds/45 - but

Re: Request GitBox access for Attic?

creating a GitBox/GitHub test repository is easy: it's self service [1] You'll get an empty Git repository that is read/write both from GitBox and GitHub: you'll be able to do the tests you want. The only little issue is that future delete of this test repo won't be self service...

Re: WARN: project in Attic but not in 'retired' category: http://svn.apache.org/repos/asf/zest/site/content/doap.rdf

should be ok now: - pointing to the new Polygene project DOAP file (not to be confused with committee DOAP file) [1] - removed Zest from retired committees json file (had been added automatically) [2] Regards, Hervé [1] http://svn.apache.org/r1778745 & http://svn.apache.org/r1778746 [2]

Re: Onami/Rave first step

ers@ is a clear indication. :) > > On Sun, Jan 24, 2016 at 9:58 AM, Hervé BOUTEMY <herve.bout...@free.fr> > > wrote: > > First step is to check Board Resolution: minutes will be published only in > > one > > month > > > > Do we wait for the effective mi

Re: Onami/Rave first step

First step is to check Board Resolution: minutes will be published only in one month Do we wait for the effective minutes publication before doing real work on moving to Attic? Or do we start now (more than documenting what remains to be done and how)? Regards, Hervé Le samedi 23 janvier

Re: Karma to close JIRA issues

yes, it's ok now thank you Le samedi 22 août 2015 10:50:22 Henri Yandell a écrit : Try again. I think I missed hitting update *blush*. On Thu, Aug 20, 2015 at 11:21 PM, Hervé BOUTEMY herve.bout...@free.fr wrote: Hi, It's not ok for me: I still can't close ATTIC Jira issues

Re: Karma to close JIRA issues

Hi, It's not ok for me: I still can't close ATTIC Jira issues Regards, Hervé Le jeudi 20 août 2015 10:39:14 sebb a écrit : Thanks, I now see the extra buttons On 20 August 2015 at 03:43, Henri Yandell bay...@apache.org wrote: Added. I also added Hérve. On Wed, Aug 19, 2015 at 11:29

Re: Project list on www.apache.org?

last time I wanted to update that list (for consistency with committee- info.txt), I had the same problems and my investigations let me find that the list from front page is currently in http://svn.apache.org/repos/asf/infrastructure/site/trunk/templates/index.html Seems like it was done during