Re: Search results for retired projects seem active

Hi Shane, I agree that this is something we Attickers should look into. > On Jan 14, 2017, at 7:08 AM, Shane Curcuru wrote: > > For example: Googling for "Continuum software", the second hit for me is > continuum.apache.org, and the description for the site shown is: > > > Feb 2, 2015 - O

Re: new PMC for xmlbeans

A project is not just code. In addition to the community (duh), there are web pages, mail lists, reporting requirements, issue management, build/release tooling, and various infra bits that need to be maintained. I agree with Jan that if POI is the only project that (currently) uses Xmlbeans, i

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

I suggest to revert the changes, including put Chukwa back into the project list.Then someone can use Whimsy agenda tool to create a resolution for the board for next month to retire the project "by the board for inactivity". I could find no vote or consensus searching the chukwa mail lists for

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

Hi Greg, > On Apr 25, 2020, at 3:53 PM, Greg Stein wrote: > > I suggest that we move forward with a Board resolution for the May meeting. > Bertrand has an Action Item to place this into the agenda. Presumably, the > Board the resolution, and then the Attic can finish the necessary steps for > C

Re: Renaming of Git repos when moving to Attic

I don't see a need for Attic to have write access to the repos. No further code development will be done. I trust Sebb's judgement, since he is the one who has the most recent experience with handling project retirement. So his comments on the damage that is caused by the rename are compelling.

Re: Renaming of Git repos when moving to Attic

Hi Sebb, > On Apr 1, 2021, at 3:21 AM, 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 as such (as per > [4]) > > If so, I will raise an INFRA JIRA to get

Re: Patch for "How to avoid moving to the Attic"

I believe that dev/pmc.html is a good place to put whatever information we want to make available. Putting information on the attic site is like posting a notice on the train station saying "You might want to look at going to the airport". I'd recommend having a section in dev/pmc.html like "H

Re: removing the Attic banner from Ambari: help needed

I loaded the page and the banner shows. Just to be sure we're talking about: The link refers to the live page https://attic.apache.org/projects/ambari.html As far as I know I have never loaded the page before, so it's not a caching issue... Cra

Re: crimson, xml - hit a dead end

Hi Reed, Sorry but this is not the right place to ask. Apache Attic is a project where projects are not actively developed. I don't know where to advise you, since I don't recognize any of the concepts or issues you are trying to solve. Warm regards, Craig > On Apr 3, 2023, at 06:29, Reed Sca

[jira] Updated: (ATTIC-56) Inform Beehive users of move to the Attic

[ https://issues.apache.org/jira/browse/ATTIC-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell updated ATTIC-56: --- Summary: Inform Beehive users of move to the Attic (was: Inform users of move to the Attic) > Inf

[jira] Updated: (ATTIC-57) Update Beehive website with Attic notice

[ https://issues.apache.org/jira/browse/ATTIC-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell updated ATTIC-57: --- Summary: Update Beehive website with Attic notice (was: Update website with Attic notice) > Upd

[jira] Updated: (ATTIC-61) Turn off Beehive automated builds

[ https://issues.apache.org/jira/browse/ATTIC-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell updated ATTIC-61: --- Summary: Turn off Beehive automated builds (was: Turn off automated builds) > Turn off Beeh

[jira] Updated: (ATTIC-58) Update HEADER.html in Beehive downloads

[ https://issues.apache.org/jira/browse/ATTIC-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell updated ATTIC-58: --- Summary: Update HEADER.html in Beehive downloads (was: Update HEADER.html in downloads) > Upd

[jira] Updated: (ATTIC-60) Create Beehive page on Attic site

[ https://issues.apache.org/jira/browse/ATTIC-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell updated ATTIC-60: --- Summary: Create Beehive page on Attic site (was: Create page on Attic site) > Create Beehive page

[jira] Updated: (ATTIC-59) Make Beehive SVN + JIRA/Bugzilla read-only

[ https://issues.apache.org/jira/browse/ATTIC-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell updated ATTIC-59: --- Summary: Make Beehive SVN + JIRA/Bugzilla read-only (was: Make SVN + JIRA/Bugzilla read-only) > M

[jira] Updated: (ATTIC-64) Announce Beehive on announce at apache.org

[ https://issues.apache.org/jira/browse/ATTIC-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell updated ATTIC-64: --- Summary: Announce Beehive on announce at apache.org (was: Announce on announce at apache.org

[jira] Updated: (ATTIC-62) Remove Beehive from www.apache.org navigation

[ https://issues.apache.org/jira/browse/ATTIC-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell updated ATTIC-62: --- Summary: Remove Beehive from www.apache.org navigation (was: Remove from www.apache.org navigation