[REPORT] Board report 2019-04-17/Attic
Hi, FYI ; I submitted the following Board Report : https://whimsy.apache.org/board/agenda/2019-04-17/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 time. ## Activity: Attic finished retiring project Polygene. ## PMC changes: - Currently 20 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Herve Boutemy on Sun Jul 19 2015 ## Committer base changes: - Currently 24 committers. - No new committers added in the last 3 months - Last committer addition was Jan Iversen at Thu Mar 16 2017 ## Releases: - No release can be made in Attic - Regards, HPP _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: Attic projects Moin wikis are going away
On Mon, 25 Mar 2019, Shane Curcuru wrote: Date: Mon, 25 Mar 2019 22:58:29 + From: Shane Curcuru To: general@attic.apache.org Subject: Attic projects Moin wikis are going away Per Infra, the Moin wiki.apache.org system is going away in May. That means a lot of older wikis will be deleted (i.e. gone from our servers). Are there any attic'd projects that had notable content on their old wiki that anyone wants to try to preserve? A partial list of wikis going away (i.e. ones that people cared enough about when created to manually list them on FrontPage) are: https://wiki.apache.org/general/FrontPage In attic I see : site/xdocs/projects/avalon.xml: site/xdocs/projects/devicemap.xml: site/xdocs/projects/harmony.xml: site/xdocs/projects/hivemind.xml: site/xdocs/projects/lucy.xml: site/xdocs/projects/rave.xml: site/xdocs/projects/shale.xml: site/xdocs/projects/stdcxx.xml: [ the ''s generate refs to wiki.apache.org ] It would be easy to dump the HTML-content somewhere with : wget -r -np -l100 http://wiki.apache.org/avalon/ wget -r -np -l100 http://wiki.apache.org/devicemap/ ... wget -r -np -l100 http://wiki.apache.org/stdcxx/ Avalon is only 9 MB ; I haven't tried the others. To show them online would require some work : -- internal refs are like "/avalon/" ; so it would only work in httpd vhost ; -- re-add style sheets etc -- add caveats etc - Shane Regards, HPP ---- _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/ -- Not On The Attic PMC The Apache Software Foundation
[REPORT] Board report 2018-10-17/Attic
Hi, FYI ; I submitted the following Board Report : https://whimsy.apache.org/board/agenda/2018-10-17/Attic ## Description: PMC Attic is responsible for the oversight of projects which otherwise would not have oversight. ## Issues: FYI ; After the transfer of XMLbeans from Attic to Poi, board asked Attic to document the "unattick" policy. On a attic.a.o, under "Process of leaving the Attic again", we have added this : + * [option 4] Transfering to an existing PMC + A receiving PMC must be willing to assume all responsibilities that come + with running a project : maintain code, answer questions, fix bugs, + publish releases etc. + If the Board does not object, PMC Attic will transfer the project's assets + (code-base, TLP website, maven group-id etc) to the receiving PMC. + After the transfer the receiving PMC will report to the Board about the + project's activities, and publish project releases in the PMC's dist area. One point remains ; Attic would like the board's advice on the following. The Board of Directors Meeting Minutes July 17, 2013, section 7.E says : [https://www.apache.org/foundation/records/minutes/2013/board_minutes_2013_07_17.txt] ... RESOLVED, that the Attic PMC be and hereby is tasked with oversight over the software developed by the Apache XMLBeans Project; and be it further ... As far as Attic knows, Attic is still formally tasked with this oversight. This is not correct, because the XMLBeans software is now under the care of PMC Poi. Attic wants to know how this inaccuracy can be formally remedied. ## Activity: Attic retired project Lucy. ## PMC changes: - Currently 20 PMC members. - Jan Iversen left the PMC on Wed May 19 2018 - Last to join the current PMC : Hervé Boutemy, July 2015 ## Committer base changes: - Currently 25 committers. - No new committers added in the last 3 months - Last committer addition was Jan Iversen at Thu Mar 16 2017 - Jan Iversen left the project on Wed May 19 2018 ## Releases: - No release can be made in attic -------- _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
transfer proj to existing PMC
Hi, I've fixed the Attic index page re: "Process of leaving the Attic again", adding "Transfering to an existing PMC". The additional details are not exhaustive but the main points are clear, I think. I think this addition addresess the remarks in "Board feedback on 2018-07-18 Attic report" : https://lists.apache.org/thread.html/51b845f7b54d25f60a858eb39fff1dbfd1be9f05344556f6eafd83d0@%3Cprivate.attic.apache.org%3E Agree ? About the next report : -- activity : lucy was retired Board of Directors Meeting Minutes July 17, 2013, section 7.E says : https://www.apache.org/foundation/records/minutes/2013/board_minutes_2013_07_17.txt RESOLVED, that the Attic PMC be and hereby is tasked with oversight over the software developed by the Apache XMLBeans Project; and be it further ... I think that Attic is formally still tasked with this oversight, where in practice isn't ; only a board resolution can fix that. I don't want to re-open the can of worms again, but I'm tempted to suggest to the board that, in future cases like Poi/Xmlbeans, board officially -- un-tasks Attic and, in the same resolution, -- tasks the receiving PMC [ack'ing that the transfer is ok] What do you think ? [1] the point is not valid [2] the point is valid but don't raise it now [3] raise the point ; just ask for advice Thanks ; regards, Henk Penning ------------ _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/ -- Forwarded message -- Date: Mon, 8 Oct 2018 09:44:09 +0200 From: build...@apache.org To: general@attic.apache.org Subject: svn commit: r1843115 - /attic/site/docs/index.html Author: buildbot Date: Mon Oct 8 07:44:09 2018 New Revision: 1843115 URL: http://svn.apache.org/viewvc?rev=1843115=rev Log: Automatic Site Publish by Buildbot Modified: attic/site/docs/index.html Modified: attic/site/docs/index.html URL: http://svn.apache.org/viewvc/attic/site/docs/index.html?rev=1843115=1843114=1843115=diff == --- attic/site/docs/index.html (original) +++ attic/site/docs/index.html Mon Oct 8 07:44:09 2018 @@ -106,10 +106,23 @@ Options are: -Forking the project - we'll link to any forks which have been created so please let us know +Forking the project - we'll link to any forks which have been + created so please let us know Restarting the community in the Apache Incubator Recreating a PMC for the project +Transfering to an existing PMC + +A receiving PMC must be willing to assume all responsibilities that come +with running a project : maintain code, answer questions, fix bugs, +publish releases etc. + +If the Board does not object, PMC Attic will transfer the project's +assets (code-base, TLP website, maven group-id etc) to the receiving PMC. + +After the transfer the receiving PMC will report to the Board about the +project's activities, and publish project releases in the PMC's dist area. +
Re: Clarifying the process for PMCs adopting codebases from the Attic
On Mon, 23 Jul 2018, Ralph Goers wrote: Date: Mon, 23 Jul 2018 15:24:58 +0200 From: Ralph Goers To: general@attic.apache.org Subject: Re: Clarifying the process for PMCs adopting codebases from the Attic On Jul 23, 2018, at 1:47 AM, Bertrand Delacretaz wrote: As for having a Board decision when reviving a project, that probably makes sense for symmetry with the Board resolution that moved the project to the Attic. But I don't think the Board necessarily needs to be involved in the discussions that lead to that resolution, I think the Attic PMC can simply add a resolution to the Board agenda as needed, and the Board just ratifies it. There is no symmetry. The board terminated the PMC and gave its assets to the attic to manage. The board passed a resolution saying : RESOLVED, that the Attic PMC be and hereby is tasked with oversight over the software developed by the Apache X Project; and My question is : can Attic 'un-task' itself, or is a board resolution required ? If a resolution is required, board might as well (symmetry) task the new PMC with "oversight over ...". Since you (rightly, in my view) broaden "the software" to "all assets", the resolution would effectively move the PROJECT (== all assets) to another PMC. The board is NOT reinstating a PMC or creating a new one. True. Once the attic owns the assets it should be free to assign those assets to any PMC willing to manage them. Ralph Thanks ; regards, Henk Penning ------------ _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: no projects in the Attic
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 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 better represent the semantic behind Attic: project = codebase + community to make it evolve and a PMC to manage the evolution ... now separate PMC and PROJECT -- it is the PMC that has a 'community' (members, committers, developers, users) -- a PROJECT (as an entity on it's own) has no community ; if/when a PROJECT moves from one PMC to another, it happily lives on, cared for by another community evolution : -- when a project enters the Attic, we 'evolve' it to a 'retired' project -- then we wait for it to be revived ; if/when that happens, we 'evolve' the project some more : we 'revive' it in some other PMC. I maintain that this is a consistent world-view. Regards, HPP _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/ we should perhaps rephrase: a project is not Attic'ed, but a former project's codebase (+ site + mailing lists) is Attic'ed because community disappeared Regards, Hervé Le vendredi 20 juillet 2018, 09:45:47 CEST Henk P. Penning a écrit : Hi Attic, FYI ; for the record. Last wednesday I attended the Board meeting ; this is recommended for new chairs ; also, the board would discuss Attic's last report. To my surprise I've learned that formally there are no "projects in the Attic". The reason is that the board resolution that terminates a PMC, also terminates the Project. Because the project does not (formally) exist, it can't be in the Attic ; so, there are no projects in the Attic. This (formal) worldview is at variance with our charter, and it is not how we work, or what we present to the world. So, I took the liberty to ask the board to -- pass a resolution (see below, lines marked with '*') which (formally) re-establishes 'our' projects again, -- in the future, move projects into the Attic, instead of terminating them so we can keep on working as we have upto now. I hope the board will accept this ; it would erase the difference between the 'formal' worldview, and what we do and present to the world. Regards, Henk Penning PS : I hope I didn't violate accepted procedure ; If not, I hope this post will correct that. ---- _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/ -- Forwarded message -- Date: Thu, 19 Jul 2018 21:11:03 +0200 From: Henk P. Penning To: Apache Board Subject: Re: XMLBeans => POI and decision making On Thu, 19 Jul 2018, Jim Jagielski wrote: Date: Thu, 19 Jul 2018 13:05:54 +0200 From: Jim Jagielski To: Apache Board Subject: Re: XMLBeans => POI and decision making As the canonical sources of truth, board resolutions are pretty high on the list. If a board resolution, which was voted on and passed by the board, says that a project was terminated, well, it was terminated. Great ; that's clear. The (formal) 'truth' is that, at the moment, PMC Attic is tasked with "oversight over the software developed by the Apache XMLBeans Project" [Board minutes 17 Jul 2013] https://whimsy.apache.org/board/minutes/XMLBeans.html I think I must ask the board to pass a resolution effectively relieving PMC Attic of this task, because the XMLbeans codebase is now managed by PCM Poi. For convenience referring to Apache Foo as being moved to the Attic or lumping (ex) projects under Apache Attic is simply that... convenience. It is much easier to say "Apache Foo is now in the Attic" (colloquial) than "The Apache Foo project no longer exists but the codebase which comprised the project is now under the official oversight of the Apache Attic and the software can be found there". * The discrepancy 'truth' vs 'colloquial' is ... inconvenient, * and confusing for many people. It can me remedied easily. * I propose that the board passes a resolution which * -- establishes (retired) projects : * -
Re: Clarifying the process for PMCs adopting codebases from the Attic
On Mon, 23 Jul 2018, Bertrand Delacretaz wrote: Date: Mon, 23 Jul 2018 10:47:59 +0200 From: Bertrand Delacretaz To: general@attic.apache.org Subject: Re: Clarifying the process for PMCs adopting codebases from the Attic Hi Bertrand, thanks for the notes. On Fri, Jul 20, 2018 at 6:40 AM Henk P. Penning wrote: ... This name change is exactly what POI wanted to avoid ; XMLbeans users want (maven-name-space) continuity ; not change. The fact that XMLbeans is "under new management" should not be visible to users ; project management stuff is an ASF-internal thing... Ok, I think this is where we see things from a different angle. I agree with you from the user's perspective, a seamless change is useful. From the Foundation's governance point of view however, by default a project found at foo.apache.org is governed by the foo PMC. If that's not the case, like here, I think there should be a clear note like "XMLBeans is managed by the Apache POI PMC" on all pages of http://xmlbeans.apache.org/ . A small thing in the site's footer is good enough IMO. Fine ; maintaining xmlbeans.apache.org is the receiving PMC's (POI)'s business, but we can add it to the list, of course. It looks like "the codebase" and the (Maven-name-space) 'GroupId' are very closely related. Whoever 'owns' "the codebase", has the right to publish releases using the GroupId. Is this something that is always true ? The Board has to manage about 180 PMC and 300 projects if i remember correctly, so it's important to have clarity there. It's a small thing that can be added to the Attic's documentation on how to revive codebases. Clarity is vitally important ; and it is lacking in spades. As for having a Board decision when reviving a project, that probably makes sense for symmetry with the Board resolution that moved the project to the Attic. But I don't think the Board necessarily needs to be involved in the discussions that lead to that resolution, I think the Attic PMC can simply add a resolution to the Board agenda as needed, and the Board just ratifies it. Attic implements board resolutions ; I think it is as simple as that. Before the move, Attic is not involved. In Attic, there is nothing to discuss, or vote upon. It is upto the board to decide if the move is ok ; that's not Attic's business. -Bertrand Groeten, HPP -------- _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: no projects in the Attic
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 Attic
Hi,
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)
I like 'project x is in the attic' (but I won't be stubborn :-).
I like the idea of 'project' as a (separate) object that
-- is created by Incubator ; may die in Incubator
-- can move from PMC to PMC ;
graduation : project -> move ( Incubator, Parent )
retirement : project -> move ( Parent, Attic )
reviving : project -> move ( Attic, Parent )
-- board ok's the moves
A Project has more attributes than (pointer to) 'codebase' ;
like name, description, website, logo, trademark, MavenId (?) etc.
Even "in the attic", a project has more 'presence' than
just 'codebase'.
In fact, an Attic project is just a project without a 'community'.
[ Why do you say "project means evolution" ?
; That is what everybody seems to think :-),
but I don't get it ; hence, I won't stubborn
; Can you please explain that for me ?
]
IMHO, recreating frozen projects is not a good idea
it's a question of wording to better represent the semantic behind Attic:
project = codebase + community to make it evolve and a PMC to manage the
evolution
we should perhaps rephrase: a project is not Attic'ed, but a former project's
codebase (+ site + mailing lists) is Attic'ed because community disappeared
-- I think 'project X' is always the same thing ;
some of it's attributes my change from time to time.
-- PMCs Incubator and Attic are like other PMCs,
except that they have special rules for managing projects.
-- Remember the 'Project' versus 'Product' discussion ?
A 'Product' is just the public facing side of a 'Project' ;
same object, different presentation.
-- When the board kills a product, it is taken of the shelves,
but it is/was still a 'product' ('not available, at the moment').
I think the above is a clean, clear design ; easy to explain,
easy to document, and easy to implement (put in a database).
For a fresh look, please read the above again ;
read 'product' where it says 'project' :-).
Hervé
Groeten,
HPP
-------- _
Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Le vendredi 20 juillet 2018, 09:45:47 CEST Henk P. Penning a écrit :
Hi Attic,
FYI ; for the record.
Last wednesday I attended the Board meeting ;
this is recommended for new chairs ; also,
the board would discuss Attic's last report.
To my surprise I've learned that formally
there are no "projects in the Attic".
The reason is that the board resolution that terminates
a PMC, also terminates the Project. Because the project
does not (formally) exist, it can't be in the Attic ;
so, there are no projects in the Attic.
This (formal) worldview is at variance with our charter,
and it is not how we work, or what we present to the world.
So, I took the liberty to ask the board to
-- pass a resolution (see below, lines marked with '*')
which (formally) re-establishes 'our' projects again,
-- in the future, move projects into the Attic,
instead of terminating them
so we can keep on working as we have upto now.
I hope the board will accept this ; it would erase
the difference between the 'formal' worldview,
and what we do and present to the world.
Regards,
Henk Penning
PS : I hope I didn't violate accepted procedure ;
If not, I hope this post will correct that.
------------ _
Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
-- Forwarded message --
Date: Thu, 19 Jul 2018 21:11:03 +0200
From: Henk P. Penning
To: Apache Board
Subject: Re: XMLBeans => POI and decision making
On Thu, 19 Jul 2018, Jim Jagielski wrote:
Date: Thu, 19 Jul 2018 13:05:54 +0200
From: Jim Jagielski
To: Apache Board
Subject: Re: XMLBeans => POI and decision making
As the canonical sources of truth, board resolutions are pretty high
on the list. If a board resolution, which was voted on and passed by
the board, says that a project was terminated, well, it was terminated.
Great ; that's clear.
The (formal) 'truth' is
no projects in the Attic
Hi Attic, FYI ; for the record. Last wednesday I attended the Board meeting ; this is recommended for new chairs ; also, the board would discuss Attic's last report. To my surprise I've learned that formally there are no "projects in the Attic". The reason is that the board resolution that terminates a PMC, also terminates the Project. Because the project does not (formally) exist, it can't be in the Attic ; so, there are no projects in the Attic. This (formal) worldview is at variance with our charter, and it is not how we work, or what we present to the world. So, I took the liberty to ask the board to -- pass a resolution (see below, lines marked with '*') which (formally) re-establishes 'our' projects again, -- in the future, move projects into the Attic, instead of terminating them so we can keep on working as we have upto now. I hope the board will accept this ; it would erase the difference between the 'formal' worldview, and what we do and present to the world. Regards, Henk Penning PS : I hope I didn't violate accepted procedure ; If not, I hope this post will correct that. ---- _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/ -- Forwarded message -- Date: Thu, 19 Jul 2018 21:11:03 +0200 From: Henk P. Penning To: Apache Board Subject: Re: XMLBeans => POI and decision making On Thu, 19 Jul 2018, Jim Jagielski wrote: Date: Thu, 19 Jul 2018 13:05:54 +0200 From: Jim Jagielski To: Apache Board Subject: Re: XMLBeans => POI and decision making As the canonical sources of truth, board resolutions are pretty high on the list. If a board resolution, which was voted on and passed by the board, says that a project was terminated, well, it was terminated. Great ; that's clear. The (formal) 'truth' is that, at the moment, PMC Attic is tasked with "oversight over the software developed by the Apache XMLBeans Project" [Board minutes 17 Jul 2013] https://whimsy.apache.org/board/minutes/XMLBeans.html I think I must ask the board to pass a resolution effectively relieving PMC Attic of this task, because the XMLbeans codebase is now managed by PCM Poi. For convenience referring to Apache Foo as being moved to the Attic or lumping (ex) projects under Apache Attic is simply that... convenience. It is much easier to say "Apache Foo is now in the Attic" (colloquial) than "The Apache Foo project no longer exists but the codebase which comprised the project is now under the official oversight of the Apache Attic and the software can be found there". * The discrepancy 'truth' vs 'colloquial' is ... inconvenient, * and confusing for many people. It can me remedied easily. * I propose that the board passes a resolution which * -- establishes (retired) projects : * -- "Apache Abdera Project" * -- "Apache ACE Project" * -- "Apache Avalon Project" * -- ... * -- "Apache XML Project" * -- tasks PMC "Apache Attic Project" with the oversight the projects * -- pursuant to bylaws of the Foundation * In the future, the board 'termination' resolution should *-- terminate the PMC XXX [as is usual] *-- terminate the office of "VP, Apache XXX" [as is usual] *-- task PMC Attic with the oversight of Project XXX * Note that this : *... merely sanctions current, established, accepted practice *... cleans up the process, a little *... hopefully avoids some endless, confused discussions in the future Thanks ; regards, Henk Penning _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/ As for the POI stuff, well, IMHO POI lacks the ability and power and authority to "unretire" XMLBeans: XMLBeans was not "retired". It was terminated (https://www.apache.org/foundation/records/minutes/2013/board_minutes_2013_07_17.txt). That was an action by the board. A PMC can not reverse nor overturn that on its own. Also, the binding of a project and a PMC is also something that the bylaws clearly state (Section 6.3)[1] is something that must be done by the board and via a resolution. 1: "Each Project Management Committee shall be responsible for the active management of one or more projects identified by resolution of the Board of Directors"
Re: Clarifying the process for PMCs adopting codebases from the Attic
; (as was done in the POI/XMLbeans case) works well ; I see no problems in the future, should it happen again. Maybe this is how ATTIC-169 has been handled, though the note at http://attic.apache.org/ saying that XMLBeans was "revived" can be understood as the project getting back to life which is not the case IMO - it's only the codebase that's been adopted. Also, I don't see an Attic mention at http://xmlbeans.apache.org/ and I think that's not good as per d) above. -Bertrand Thanks ; regards, Henk Penning _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: Clarifying the process for PMCs adopting codebases from the Attic
by different PMCs c) For this to happen, a positive vote of the Attic PMC is sufficient, on this list, backed by a JIRA ticket to describe the details and actions d) When that happens, the FROM website is updated to indicate that TO adopted the code, saying something like "The TO PMC has now adopted the FROM codebase", indicating exactly which part(s) of the codebase have been adopted. No other change is made to that website, it remains frozen apart from that note. TO can copy the website content under their own to evolve it, but the original FROM.apache.org domain content must stay as it was when FROM moved to the Attic. e) The Attic website is updated with that same information f) TO can release the FROM modules that it adopted, using names like TOO-FROM-module-V1.2.3 to differentiate those artifacts from the older ones that FROM released - adding the TOO prefix to their names, both for release archives and things like Java jars, etc. g) Java package names etc. can remain as they were, for convenience How does this sound? Maybe this is how ATTIC-169 has been handled, though the note at http://attic.apache.org/ saying that XMLBeans was "revived" can be understood as the project getting back to life which is not the case IMO - it's only the codebase that's been adopted. Also, I don't see an Attic mention at http://xmlbeans.apache.org/ and I think that's not good as per d) above. -Bertrand -------- _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: svn commit: r1832298 - in /xmlbeans/trunk: ./ external/lib/ samples/AbstractTypes/ samples/Any/ samples/DateTime/ samples/MixedContent/ samples/OrderMatters/ samples/SampleTemplate/ samples/Schema
On Mon, 28 May 2018, sebb wrote: Date: Mon, 28 May 2018 18:37:25 +0200 From: sebb To: general@attic.apache.org Subject: Re: svn commit: r1832298 - in /xmlbeans/trunk: ./ external/lib/ samples/AbstractTypes/ samples/Any/ samples/DateTime/ samples/MixedContent/ samples/OrderMatters/ samples/SampleTemplate/ samples/SchemaEnum/ samples/SubstitutionGroup/ samples/Validation/ sam... On 28 May 2018 at 12:14, Henk P. Penning wrote: On Mon, 28 May 2018, Mads Toftum wrote: Date: Mon, 28 May 2018 10:25:56 +0200 From: Mads Toftum To: general@attic.apache.org Subject: Re: svn commit: r1832298 - in /xmlbeans/trunk: ./ external/lib/ samples/AbstractTypes/ samples/Any/ samples/DateTime/ samples/MixedContent/ samples/OrderMatters/ samples/SampleTemplate/ samples/SchemaEnum/ samples/SubstitutionGroup/ samples/Validation/ sam... On Mon, May 28, 2018 at 08:36:37AM +0200, Hervé BOUTEMY wrote: IIUC, that means that we should remove XMLBeans from Attic and switch its ownership to POI? I don't think that's right ; PCM XMLBeans is retired ; that PMC can be revived (within the ASF, with board approval) by -- reviving the PMC - unlikely given that the PMC died 5 years ago -- make a restart in the incubator. I do think that -- poi can fork the code and devellop it as a sub-project -- we can add a reference on the XMLBeans attic page to the new fork Agreed. That would be my thinking as well. Development shouldn't be happening in an attic project. If the board has approved "un-retiring", then we should move it first before allowing commits. As far as I know, commits should be impossible ; that is, the codebase should be frozen. Isn't that what 2.6.ii does in http://attic.apache.org/process.html ? AFAICT Infra allowed access following a JIRA: INFRA-16580 Does anyone know a PCM (except incubator and, in some sense attic) that manages more than 1 project ? Commons, MINA, Creadur, Maven (?) Sorry ; with 'project' I meant 'Top-Level-Project' (not 'sub-project'). As in (second paragraph) of https://www.apache.org/foundation/bylaws.html#6.3 Each Project Management Committee shall be responsible for the active management of one or more projects identified by resolution of the Board of Directors ... Are there any PMC's that manage more than one TLP ? It would appear that, for PMC Poi to manage project XMLBeans, a resolution of the Board is required ... Regards, HPP then for example remove the banner on http://xmlbeans.apache.org/? I wonder if it wouldn't make sense to put it somewhere under poi.apache.org unless there's a new xmlbeans pmc being put in place? Mads Toftum Groeten, Henk Penning ---- _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/ ---- _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: svn commit: r1832298 - in /xmlbeans/trunk: ./ external/lib/ samples/AbstractTypes/ samples/Any/ samples/DateTime/ samples/MixedContent/ samples/OrderMatters/ samples/SampleTemplate/ samples/Schema
On Sun, 27 May 2018, fannin...@apache.org wrote: Date: Sun, 27 May 2018 11:07:46 +0200 From: "fannin...@apache.org" <fannin...@apache.org> To: general@attic.apache.org, Mads Toftum <m...@toftum.dk> Subject: Re: svn commit: r1832298 - in /xmlbeans/trunk: ./ external/lib/ samples/AbstractTypes/ samples/Any/ samples/DateTime/ samples/MixedContent/ samples/OrderMatters/ samples/SampleTemplate/ samples/SchemaEnum/ samples/SubstitutionGroup/ samples/Validation/ sam... Hi Mads,The Apache POI team are taking over the XMLBeans library because it is still used by POI libs and we'd like to do a release with some bug fixes.https://issues.apache.org/jira/browse/INFRA-16278 has some of the details. Hi PJ Fanning, just for my information ... ; what is the difficulty with -- importing the existing xmlbeans code -- change some things -- and release (almost as is) ? Thanks ; regards, Henk Penning On Sunday 27 May 2018, 10:02:39 GMT+1, Mads Toftum <m...@toftum.dk> wrote: On Sat, May 26, 2018 at 08:31:15AM -, fannin...@apache.org wrote: Author: fanningpj Date: Sat May 26 08:31:14 2018 New Revision: 1832298 According to http://attic.apache.org/projects/xmlbeans.html xmlbeans has been retired since July 2013 - I'm a bit surprised to see commits. vh Mads Toftum -- http://flickr.com/photos/q42/ -------- _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: svn commit: r1832298 - in /xmlbeans/trunk: ./ external/lib/ samples/AbstractTypes/ samples/Any/ samples/DateTime/ samples/MixedContent/ samples/OrderMatters/ samples/SampleTemplate/ samples/Schema
On Mon, 28 May 2018, Mads Toftum wrote: Date: Mon, 28 May 2018 10:25:56 +0200 From: Mads Toftum <m...@toftum.dk> To: general@attic.apache.org Subject: Re: svn commit: r1832298 - in /xmlbeans/trunk: ./ external/lib/ samples/AbstractTypes/ samples/Any/ samples/DateTime/ samples/MixedContent/ samples/OrderMatters/ samples/SampleTemplate/ samples/SchemaEnum/ samples/SubstitutionGroup/ samples/Validation/ sam... On Mon, May 28, 2018 at 08:36:37AM +0200, Hervé BOUTEMY wrote: IIUC, that means that we should remove XMLBeans from Attic and switch its ownership to POI? I don't think that's right ; PCM XMLBeans is retired ; that PMC can be revived (within the ASF, with board approval) by -- reviving the PMC - unlikely given that the PMC died 5 years ago -- make a restart in the incubator. I do think that -- poi can fork the code and devellop it as a sub-project -- we can add a reference on the XMLBeans attic page to the new fork That would be my thinking as well. Development shouldn't be happening in an attic project. If the board has approved "un-retiring", then we should move it first before allowing commits. As far as I know, commits should be impossible ; that is, the codebase should be frozen. Isn't that what 2.6.ii does in http://attic.apache.org/process.html ? Does anyone know a PCM (except incubator and, in some sense attic) that manages more than 1 project ? then for example remove the banner on http://xmlbeans.apache.org/? I wonder if it wouldn't make sense to put it somewhere under poi.apache.org unless there's a new xmlbeans pmc being put in place? Mads Toftum Groeten, Henk Penning -------- _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: Discussion to select chair candidates followed by a vote starting may 13 2018.
On Tue, 1 May 2018, Jan Iversen wrote: Date: Tue, 1 May 2018 22:46:41 +0200 From: Jan Iversen <j...@apache.org> To: general@attic.apache.org Subject: Discussion to select chair candidates followed by a vote starting may 13 2018. Hi Jan, I thought the plan was to reach consensus, and otherwise vote. Let me try to reach consensus this way : Hi Sebb, Can we agree to just let Jan pick a winner ? and for us to forever hold our peace (regarding the choice)? This is a bike-shed problem ; any simple solution is ok. [ Forgive my ignorance if this is against etiquette. How does a PMC resolve bike-shed problems ? ] Regards, Henk Penning ---- _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/ Hi I am truly sorry having to write this email. I am embarrassed of not being able to keep my promise and stay as a long-term chair, but sometimes you have to ask yourself is it worth the time spent and instead use time where it is makes a difference. Considering we have a very silent community and the current site maintenance was unacceptable to me, I spent a couple of days to make my life easier and asked for opinions from the community before changing the production site, after that our list drowned in emails from 2 pmc members pursuing other solutions. This is not the first time we have a situation like this, a while ago we had long discussion with -1 flowing around, between the same 2 PMC members about rewriting rules etc, where finally (I believe partly due to my intervention) consensus was reached. I volunteered to be chair and was clear it meant I had not only to file board reports but also do the bulk part of retiring projects. I did not volunteer to spend endless hours trying to get consensus or to get simple changes agreed on. I proposed a very simple solution, but have accepted that the other 2 solutions each have advantages, so I might have continued had I believed in the possibility of consensus and an, for me, easy to maintain solution. There are no signs of convergence and a vote on technical solutions are bad, apart from the fact that I am convinced both solutions would receive a -1. Changes are high, that the current deadlock will end with no change at all. I humbly accept my failure to help bring consensus and progress to the attic, so I hereby announce my retirement as chair/pmc/committer. I am hereby starting a discussion on who should be the next chair. The discussion will run until 13 may 2018, where I will start the formal vote. The result of the vote will be added to the agenda for the board June meeting. In case we have no positive result of the vote, the board will be asked to appoint a new chair. The 2 PMC members have each promised to support a future site, so it is natural for me to propose Henkp and Sebb as chair candidates, both have used significant time to implement technical elegant solutions. Ball is rolling, let the community decide. rgds Jan I Sent from my iPad
Re: discussion/vote new site (again, but last time from me)
On Mon, 30 Apr 2018, sebb wrote:
Date: Mon, 30 Apr 2018 14:34:13 +0200
From: sebb <seb...@gmail.com>
To: general@attic.apache.org
Subject: Re: discussion/vote new site (again, but last time from me)
Let's not forget that Jani created the initial JSON file contents.
That was quite a bit of work.
True ; big thanks.
Note that proj-data includes layout in the above list.
Yep, the $proj-data is a (tag->value) html table ;
the script computes a table
[ tag => tag_function ( param, ... )
, ...
]
Then the table is converted to html ; this is straight forward.
-- only 3 substitutions are needed [project-list, title, $proj-data].
Additional substitutions of need to be made to create the proj-data as
that is a mix of variable data with fixed layout.
Don't understand ; the per/proj html == table + 'postlude'.
and can't be understood unless you look at the code too.
In the lua case, the conditional and looping code is buried inside the
Perl script.
I'm not religous about the ModelViewControler stuff ;
I like stuff in one place (file), if the file is small.
At present the code generates a Board entry in the table regardless of
whether it is a sub-project or not. How would you fix that so it
agrees with the existing Attic site?
Ok ; I'll bite ...
If the 'minutes' entry also depends on entry 'subproject'
pass it to function 'minutes_url' ; let 'minutes_url'
return 'n/a' if subproject is not empty ;
sub minutes_url
{ my $p = shift or return $NA ; # == 'n/a'
my $s = shift or return $NA ;
url "https://whimsy.apache.org/board/minutes/$p.html;, 'Minutes'
}
If you mean the line shouldn't be there at al, I would fix function
minutes_url to return undef, and fix the tab-to-table expansion
skip entries with and undefined value ; that is one extra line.
Nevermind ; anything can be easily fixed.
I maintain that the problem is simple,
and using a template system is overkill.
To me, the split is "controler logic" and "view logic"
(as with 'board' example) is confusing and a hindrance.
It's a well-written script, but it is hard to follow - mainly because
it mixes content with presentation.
yea ; that is 6 lines of code ;
it makes I only need 1 very simple template,
that doesn't change when attributes change.
Netto : a big win.
Groeten,
HPP
-------- _
Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: Buildbot fails to build site-lua because it cannot find JSON.pm
On Mon, 30 Apr 2018, sebb wrote: Date: Mon, 30 Apr 2018 15:53:11 +0200 From: sebb <seb...@gmail.com> To: general@attic.apache.org Subject: Buildbot fails to build site-lua because it cannot find JSON.pm I know how to install JSON.pm on my own system. However I don't know how to install it on the Buildbot node(s). @henkp - is this something that can be done in the buildbot script? Or does it have to be done by Infra? https://github.com/apache/infrastructure-puppet/blob/deployment/data/ubuntu/1604.yaml#L542 https://github.com/apache/infrastructure-puppet/blob/deployment/data/ubuntu/1404.yaml#L556 Infra says : those are the 2 files you'd want to make a PR against Looks like the module is called 'libjson-perl' in ubuntu. S. Groeten, HPP ---- _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: discussion/vote new site (again, but last time from me)
On Sun, 29 Apr 2018, Jan Iversen wrote: Date: Sun, 29 Apr 2018 19:53:45 +0200 From: Jan Iversen <j...@apache.org> To: general@attic.apache.org Subject: discussion/vote new site (again, but last time from me) Hi. Based on a suggestion from Henk, I hereby once again try to start a discussion/vote on the new site. Ok ; great ; thanks. We need to select either lua-site or jekyll-site. I strongly believe there are no reasons to polish the sites more before selecting, it is apparent how both sites will work. Let me say first that Sebb did a great job perfecting the config (json/yaml file) ; since it handles all the past retirements, we can be confident that either solution can handle (almost) any future case. The problem at hand is simple : -- there is only one 'base' ; all generated pages look the same. -- there is only one 'template' : base + project-list (on the right) -- there are only 4 (kinds of) pages : -- index.html : template + index.txt -- process.html: template + process.txt -- resolution.html : template + resolution.txt -- $project.html : template + where is generated from the config. -- only 3 substitutions are needed [project-list, title, $proj-data]. [main point] I think using a template system is, at best, unnecessary. Note that the jekyll templates aren't 'easy' (full of if/then/else's), and can't be understood unless you look at the code too. [I know, because I had to follow Sebb, as he added more and more ;-] With the lua stuff, the 'logic' is in one place. -- the jekyll stuff uses ruby, ant and jekyll ; requiring installs. the lua stuff uses only perl and make ; always available, and more widely used/known. -- the lua tree looks simpler than the jekyll tree ... As the problem is simple, a simple solution is sufficient. jan I Regards, Henk Penning ---- _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: svn commit: r1830424 - /attic/site/xdocs/process.xml
On Sun, 29 Apr 2018, Jan Iversen wrote: Date: Sun, 29 Apr 2018 19:31:48 +0200 From: Jan Iversen <j...@apache.org> To: general@attic.apache.org Subject: Re: svn commit: r1830424 - /attic/site/xdocs/process.xml On 29 Apr 2018, at 08:23, Henk P. Penning <penn...@uu.nl> wrote: Hi, Hi Jan, May I ask you (as chair) to set an agenda? to focus everybody's enthousiasm :-) Wearing my chair hat, I need to give a polite note. A chair is just a member of the community like any other PMC, with no special powers (something I highly second). So everybody can start the agenda [...] Sorry about that. Attic is the first 'project' I'm involved in. Re: etiquette, I'm a newbie :-) Regards, HPP ---- _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: Applying banners to ghost.[eu|us].apache.org hosts
On Sun, 29 Apr 2018, sebb wrote: Date: Sun, 29 Apr 2018 11:39:51 +0200 From: sebb <seb...@gmail.com> To: general@attic.apache.org Subject: Re: Applying banners to ghost.[eu|us].apache.org hosts On 29 April 2018 at 10:29, Henk P. Penning <penn...@uu.nl> wrote: Until now Attic has taken responsibility for changing the website which automatically fixes all the hosts. Hardly ; I proposed a solution to infra, and they showed me a better way. With some to-and-fro we got stuff working. The banner solution pushes part of the work onto Infra (at least initially) How will the eu/us hosts get fixed? Does it need an Infra JIRA? To be decided by infra, when the rules get fixed ; and no. I see you already issued a pull-request for a rule change ; please tell infra to wait with this. Does it matter if the extra rules are in place for a while? Yes. For infra these rule changes are spurious ; to judge them infra has to look at attic stuff that isn't even there ; it's just annoying and that not good for Attic. Please stop this before it is too late. HPP ---- _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: Proposed httpd tlp config changes for Attic redirects
On Sun, 29 Apr 2018, sebb wrote: Date: Sun, 29 Apr 2018 09:02:20 +0200 From: sebb <seb...@gmail.com> To: general@attic.apache.org Subject: Re: Proposed httpd tlp config changes for Attic redirects On 29 April 2018 at 06:50, Henk P. Penning <penn...@uu.nl> wrote: On Sat, 28 Apr 2018, sebb wrote: I think we should stop 'fixing' the 'old' site and move to a new site. The HTTPD changes have to be in place *before* any move. Why? The 'new' site should have this, of course : docs/flagged/oltu.apache.org/oltu.apache.org -- that's enough to get oltu bannered -- atm, the /dist/ redirects are triggered by the presence of "projects/TLP.html" and that is unchanged (regards TLP's). Am I missing something here ? Regards, HPP ------------ _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: site-lua buildbot job added
On Sat, 28 Apr 2018, sebb wrote: Date: Sat, 28 Apr 2018 15:43:51 +0200 From: sebb <seb...@gmail.com> To: general@attic.apache.org Subject: Re: site-lua buildbot job added On 28 April 2018 at 14:34, Henk P. Penning <penn...@uu.nl> wrote: On Sat, 28 Apr 2018, sebb wrote: -- The site-lua/docs dir is built from scratch Would this work as 'build.sh' : svn rm docs make svn add docs No need for the SVN commands. So, a local "make ; commit" does something else than the buildbot's "make" ; in that the buildbot's "make" magically adds stuff to the repo. Correct ? Any other differences ? Is it a problem if the 'make' would "svn add stuff" to the repo ? Thanks ; regards, HPP -------- _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: site-lua buildbot job added
On Sat, 28 Apr 2018, sebb wrote: Date: Sat, 28 Apr 2018 14:46:09 +0200 From: sebb <seb...@gmail.com> To: general@attic.apache.org Subject: site-lua buildbot job added I added a site-lua buildbot job. It's on demand only (like the jekyll one). It assumes there is a build.sh script to do the build. This makes it easier to update the build without needing to change the Buildbot job. ... just for my information ... -- The site-lua/docs dir is built from scratch Would this work as 'build.sh' : svn rm docs make svn add docs My concern is this : /if/ the 'make' generates new files, how are they added to a repo, so SvnPubSub/GitPubSub can publish them on the webservers. Groeten, HPP ---- _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: svn commit: r1830424 - /attic/site/xdocs/process.xml
On Sat, 28 Apr 2018, Jan Iversen wrote: Date: Sat, 28 Apr 2018 12:54:40 +0200 From: Jan Iversen <j...@apache.org> To: general@attic.apache.org Subject: Re: svn commit: r1830424 - /attic/site/xdocs/process.xml Isn’t it a bit premature to change the process ? Seen from pow we are experimenting with at least 3 proposals of which 1 does not need a buildbot. I agree ; site maintainance (with svn) can be as simple as -- svn up -- edit data/attic.yaml -- make -- commit I assume the same works after a switch to git. Regards, Henk Penning rgds jan I Sent from my iPad On 28 Apr 2018, at 12:33, hbout...@apache.org wrote: Author: hboutemy Date: Sat Apr 28 10:33:07 2018 New Revision: 1830424 URL: http://svn.apache.org/viewvc?rev=1830424=rev Log: added links to Buildbot job and svnwcsub configuration Modified: attic/site/xdocs/process.xml Modified: attic/site/xdocs/process.xml URL: http://svn.apache.org/viewvc/attic/site/xdocs/process.xml?rev=1830424=1830423=1830424=diff == --- attic/site/xdocs/process.xml (original) +++ attic/site/xdocs/process.xml Sat Apr 28 10:33:07 2018 @@ -76,8 +76,9 @@ The following are usefull svn/https locations: - svn site http://svn.apache.org/repos/asf/attic;>http://svn.apache.org/repos/asf/attic + svn site http://svn.apache.org/viewvc/attic;>http://svn.apache.org/repos/asf/attic: sources in xdocs, generated html in docs site http://attic.apache.org;>http://attic.apache.org + internals: https://ci.apache.org/builders/attic-site;>Buildbot job to build from source and commit generated html, https://github.com/apache/infrastructure-puppet/blob/deployment/modules/svnwcsub/files/svnwcsub.conf#L36;>svnwcsub configuration to update generated html from svn to webserver jira https://issues.apache.org/jira/browse/ATTIC;>https://issues.apache.org/jira/browse/ATTIC committees.xml https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/committees.xml;>https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/committees.xml ------------ _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: svn commit: r1830185 - /attic/site-lua/docs/OUT
On Thu, 26 Apr 2018, sebb wrote: Date: Thu, 26 Apr 2018 15:13:08 +0200 From: sebb <seb...@gmail.com> To: general@attic.apache.org Subject: Re: svn commit: r1830185 - /attic/site-lua/docs/OUT I think postlude should be just a text blob : postlude: |- just a blob Adding structuring is artificial, and a source of errors. It makes checking the generated HTML harder. how so ? the generate HTML is exactly the same as the blob ; See the source of the hardest case : http://mirror-vm80.apache.org/projects/jakarta-taglibs.html compare with : https://svn.apache.org/repos/asf/attic/site-lua/docs/data/attic.yaml Groeten, HPP can you please fix the projects.json ? Avoid the booleans by changing the values of 'nodist' and 'keys' to 1 (instead of 'true'). Why avoid booleans? It is a perl thingy ; a JSON-read accepts true and false, but the resulting data-structure has typed values JSON::XS::Boolean (or some such) that YAML doesn't grok. Using just 0 and 1 makes it a little easier (without loss). Please fix. The Jekyll PoC does not use Perl. It's also ambiguous to use 0 and 1 because their truth values depends on the language. Groeten, HPP ---- _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/ ---- _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: new sites and swarm of commits.
On Fri, 27 Apr 2018, Jan Iversen wrote: Date: Fri, 27 Apr 2018 15:04:50 +0200 From: Jan Iversen <j...@apache.org> To: general@attic.apache.org Subject: Re: new sites and swarm of commits. Hi Jan, --- name: Oltu project: oltu retired: April 2018 mailnames: - dev - user - commits tracker: - JIRA - OLTU scm: svn wiki: https://cwiki.apache.org/confluence/display/oltu/ description: |- Apache Oltu was an OAuth protocol implementation in Java. It also covers others OAuth family related implementations such as JWT, JWS and OpenID Connect --- What is complicated about that ? for one it is, yaml, and I still have not seen any online validator of that. json offers online validation so som faulty commits are avoided (not all I know). Why check ? If there's a yaml error the generator shows exactly where the error occurs ; I think we can catch that. If/when an error occurs, nothing should be committed, of course. secondly I believe having fields like JIRA and svn are wrong un very unflexible, having the url is a lot more generic. how will you retire e.g. AOO that runs its own bugzilla instance. I agree ; just an url is fine ; but 'as is' is easy too. and I have to learn yaml. Copy/paste/edit of the example above should suffice almost always. Just ignore the commits. We'll judge the stuff when dev is done. I think we're mostly done. both of you keep saying thatI still believe that having a volunteer who will actually maintain it is now more important than seeing the final bits. Ok ; I'll volunteer to maintain the site. I would love to see the stuff "at work". jan i Regards, HPP -------- _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: new sites and swarm of commits.
On Fri, 27 Apr 2018, Jan Iversen wrote: Date: Fri, 27 Apr 2018 13:39:16 +0200 From: Jan Iversen <jancasacon...@gmail.com> To: general@attic.apache.org Subject: new sites and swarm of commits. Hi Jan, It is amazing how many commits Henk and Sebb can produce, I have lost track long ago about the status of things Please, just ignore the commits. with one exception I see both proposals having growing complexity (now e.g. both use yaml) most of the complexity seems to arise in order to be to be able to handle situations in the future (by using the past as s valid example) something I strongly believe is a false assumption. Eh, no. To generate the old (even pre-attic) stuff, some optional attributes had to be added. The last project to retire (oltu) is typical for future projects ; this is the config entry : --- name: Oltu project: oltu retired: April 2018 mailnames: - dev - user - commits tracker: - JIRA - OLTU scm: svn wiki: https://cwiki.apache.org/confluence/display/oltu/ description: |- Apache Oltu was an OAuth protocol implementation in Java. It also covers others OAuth family related implementations such as JWT, JWS and OpenID Connect --- What is complicated about that ? To update the site, all you have to do is 'edit' and 'commit' ; that is the goal. My stuff is now 300 lines of simple Perl ; as it was before. Sebb uses more tools, but about the same ones as before. Processing appears to be split between the (ruby) generator, and the jekyll template ; preference is a matter of taste. Sebb is setting up the build stuff ; great ; we'll (something like) that anyway after the git switch, if I'm not mistaken. Just ignore the commits. We'll judge the stuff when dev is done. I think we're mostly done. Sebb, ... are you almost done :-) ? ... using yaml ? The next board report will contain a description of the ongoing activity, but hopefully with a positive conclusion. I'm sure of it. jan i Regards, HPP ---- _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: svn commit: r1830185 - /attic/site-lua/docs/OUT
On Thu, 26 Apr 2018, sebb wrote: Date: Thu, 26 Apr 2018 13:25:49 +0200 From: sebb <seb...@gmail.com> To: general@attic.apache.org Subject: Re: svn commit: r1830185 - /attic/site-lua/docs/OUT I have recently tried using an array for postlude. That has the advantage that the output is still folded. I would like to keep that feature if possible. I will try converting the copy under site-jekyll to YAML and see if there are any issues I think postlude should be just a text blob : postlude: |- just a blob Adding structuring is artificial, and a source of errors. can you please fix the projects.json ? Avoid the booleans by changing the values of 'nodist' and 'keys' to 1 (instead of 'true'). Why avoid booleans? It is a perl thingy ; a JSON-read accepts true and false, but the resulting data-structure has typed values JSON::XS::Boolean (or some such) that YAML doesn't grok. Using just 0 and 1 makes it a little easier (without loss). Please fix. Groeten, HPP ---- _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: svn commit: r1830185 - /attic/site-lua/docs/OUT
On Thu, 26 Apr 2018, Jan Iversen wrote:
Date: Thu, 26 Apr 2018 13:32:31 +0200
From: Jan Iversen <j...@apache.org>
To: general@attic.apache.org
Subject: Re: svn commit: r1830185 - /attic/site-lua/docs/OUT
Why is that? Apart from a couple of old sites data are simple one liners.
For example ACE ; I think this :
---
name: ACE
project: ace
retired: December 2017
mailnames:
- dev
- commits
- users
jira: ACE
scm: svn
wiki: https://cwiki.apache.org/confluence/display/ace/
description: |-
Apache ACE was a software distribution framework that allows you to
centrally manage and distribute software components, configuration
data and other artifacts to target systems. It is built using OSGi and
can be deployed in different topologies. The target systems are
usually also OSGi based, but don't have to be.
---
... is better than :
{
"name":"ACE",
"project": "ace",
"retired": "December 2017",
"scm": "svn",
"jira":"ACE",
"wiki":"https://cwiki.apache.org/confluence/display/ace/;,
"mailnames": ["dev", "commits", "users"],
"description": "Apache ACE was a software distribution framework that allows
you to centrally manage and distribute software components, configuration data and other artifacts
to target systems. It is built using OSGi and can be deployed in different topologies. The target
systems are usually also OSGi based, but don't have to be. "
},
I hate lines much longer than 80 chars.
Jan I
Groeten,
HPP
_
Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: svn commit: r1830185 - /attic/site-lua/docs/OUT
+wiki: https://cwiki.apache.org/confluence/display/wink/ +description: |- + Apache Wink was a simple yet solid framework for building RESTful Web + services. It is comprised of a Server module and a Client module for + developing and consuming RESTful Web services. +--- +name: Wookie +project: wookie +retired: April 2016 +mailnames: + - dev + - user + - commits +jira: WOOKIE +scm: svn +wiki: https://cwiki.apache.org/confluence/display/wookie/ +description: |- + Wookie was a Java server application that allowed you to upload and + deploy W3C/OpenSocial/Google Wave widgets to your applications. +--- +name: WS Muse +project: ws +subproject: muse +stem: muse +retired: January 2013 +mailnames: + - dev + - user + - commits +website: # +description: |- + Muse was a Java-based implementation of the WS-ResourceFramework + (WSRF), WS-BaseNotification (WSN), and WS-DistributedManagement (WSDM) + specifications. +postlude: |- + One fork that has been created is amused, available at http://52north.org/communities/sensorweb/amused/;>http://52north.org/communities/sensorweb/amused. + +--- +name: Xang +project: xml +subproject: xang +retired: December 2009 +mailnames: + - dev + - commits +scm: svn +description: |- + Apache Xang was an XML Web Framework that aggregated multiple data + sources, made that data URL addressable and defined custom methods to + access that data. +--- +name: Xindice +project: xml +subproject: xindice +retired: August 2011 +mailnames: + - dev + - user +bugzilla: Xindice +scm: svn +wiki: http://wiki.apache.org/xindice +description: |- + Apache Xindice was a native XML database. +--- +name: XMLBeans +project: xml +subproject: xmlbeans +retired: July 2013 +mailnames: + - dev + - user + - commits + - cxx-dev +scm: svn +description: |- + Apache XMLBeans was a technology for accessing XML by binding it to + Java types. +postlude: |- + Alternatives are discussed on this StackOverflow question: http://stackoverflow.com/questions/27727546/what-to-use-instead-of-xmlbeans-now-that-it-has-been-retired;>What + to use instead of XMLBeans now that it has been retired? +--- +name: XML +project: xml +retired: April 2012 +mailnames: + - bugs + - announcements + - general + - general-cvs +scm: svn +nokeys: 1 +description: |- + the Apache XML Project housed a diverse set of popular open source XML + solutions. _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: svn commit: r1829959 - /attic/site-jekyll/src/_data/projects.json
On Tue, 24 Apr 2018, Jan Iversen wrote:
Date: Tue, 24 Apr 2018 11:58:10 +0200
From: Jan Iversen <j...@apache.org>
To: general@attic.apache.org
Subject: Re: svn commit: r1829959 - /attic/site-jekyll/src/_data/projects.json
I still argue, we just need something simple, a build script and a
couple of templates (which are easy to read).
I just committed 'mk-stuff' ; 200 lines of perl-code ;
for now, the texts for {index,resolution,process}.html
are in mk-stuff too ; I couldn't decide where to put them.
Prog 'mk-stuff' generates {index,resolution,process}.html
and projects/*.
At work : http://mirror-vm80.apache.org/index.html
Not all (per project) attributes are shown correctly,
but you get the idea.
jan i
Regards,
HPP
---- _
Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: svn commit: r1829888 - in /attic/site-jekyll/src: _data/projects.json _layouts/project.html _plugins/generate_projects.rb
+ "project": "shale",
"retired": "May 2009",
"source code": "http://svn.apache.org/repos/asf/shale;,
"issues": "",
@@ -443,7 +454,7 @@
},
{
"name":"Shindig",
- "website": "http://shindig.apache.org/;,
+ "project": "shindig",
"retired": "November 2015",
"source code": "http://svn.apache.org/repos/asf/shindig;,
"issues": "https://issues.apache.org/jira/projects/SHINDIG;,
@@ -458,7 +469,7 @@
{
"id": "stdcxx",
"name":"Standard C++ Library (STDCXX)",
- "website": "http://stdcxx.apache.org/;,
+ "project": "stdcxx",
"retired": "July 2013",
"source code": "http://svn.apache.org/repos/asf/stdcxx;,
"issues": "https://issues.apache.org/jira/projects/STDCXX;,
@@ -473,7 +484,7 @@
},
{
"name":"Stratos",
- "website": "http://stratos.apache.org/;,
+ "project": "stratos",
"retired": "January 2017",
"source code": "http://svn.apache.org/repos/asf/stratos/;,
"issues": "https://issues.apache.org/jira/projects/STRATOS;,
@@ -485,7 +496,7 @@
},
{
"name":"Tuscany",
- "website": "http://tuscany.apache.org/;,
+ "project": "tuscany",
"retired": "May 2016",
"source code": "http://svn.apache.org/repos/asf/tuscany;,
"issues": "https://issues.apache.org/jira/projects/TUSCANY;,
@@ -499,7 +510,7 @@
},
{
"name":"Whirr",
- "website": "http://whirr.apache.org/;,
+ "project": "whirr",
"retired": "March 2015",
"source code": "http://svn.apache.org/repos/asf/whirr;,
"issues": "https://issues.apache.org/jira/projects/WHIRR;,
@@ -512,7 +523,7 @@
},
{
"name":"Wink",
- "website": "http://wink.apache.org/;,
+ "project": "wink",
"retired": "April 2017",
"source code": "http://svn.apache.org/repos/asf/wink;,
"issues": "https://issues.apache.org/jira/projects/WINK;,
@@ -525,7 +536,7 @@
},
{
"name":"Wookie",
- "website": "http://wookie.apache.org/;,
+ "project": "wookie",
"retired": "April 2016",
"source code": "http://svn.apache.org/repos/asf/wookie;,
"issues": "https://issues.apache.org/jira/projects/WOOKIE;,
@@ -539,7 +550,7 @@
{
"id": "muse",
"name":"WS Muse",
- "website": "",
+ "website": "NONE",
"retired": "January 2013",
"source code": "",
"issues": "",
@@ -553,7 +564,8 @@
},
{
"name":"Xang",
- "website": "http://xml.apache.org/xang;,
+ "project": "xml",
+ "subproject": "xang",
"retired": "December 2009",
"source code": "http://svn.apache.org/repos/asf/xml/xang;,
"issues": "",
@@ -565,7 +577,8 @@
},
{
"name":"Xindice",
- "website": "http://xml.apache.org/xindice;,
+ "project": "xml",
+ "subproject": "xindice",
"retired": "August 2011",
"source code": "http://svn.apache.org/repos/asf/xml/xindice;,
"issues": "https://bz.apache.org/bugzilla/buglist.cgi?product=Xindice;,
@@ -577,7 +590,8 @@
},
{
"name":"XMLBeans",
- "website": "http://xml.apache.org/xmlbeans;,
+ "project": "xml",
+ "subproject": "xmlbeans",
"retired": "July 2013",
"source code": "http://svn.apache.org/repos/asf/xmlbeans;,
"issues": "",
@@ -591,7 +605,7 @@
},
{
"name":"XML",
- "website": "http://xml.apache.org/;,
+ "project": "xml",
"retired": "April 2012",
"source code": "http://svn.apache.org/repos/asf/xml;,
"issues": "",
Modified: attic/site-jekyll/src/_layouts/project.html
URL:
http://svn.apache.org/viewvc/attic/site-jekyll/src/_layouts/project.html?rev=1829888=1829887=1829888=diff
==
--- attic/site-jekyll/src/_layouts/project.html (original)
+++ attic/site-jekyll/src/_layouts/project.html Mon Apr 23 13:51:31 2018
@@ -60,7 +60,7 @@
Website
- {{ page.json.website | replace: "http://",";
}}
+ {{ page.json.website | replace: "http://",";
}}/
Mailing List Archives
Modified: attic/site-jekyll/src/_plugins/generate_projects.rb
URL:
http://svn.apache.org/viewvc/attic/site-jekyll/src/_plugins/generate_projects.rb?rev=1829888=1829887=1829888=diff
==
--- attic/site-jekyll/src/_plugins/generate_projects.rb (original)
+++ attic/site-jekyll/src/_plugins/generate_projects.rb Mon Apr 23 13:51:31 2018
@@ -20,6 +20,14 @@ module Jekyll
end
p['dist'] = id.sub 'jakarta-','jakarta/'
+ unless p['website'] # generate the website unless it is overridden
+# Omit the trailing slash as that is added in the template if needed
+if p['subproject']
+ p['website'] = "http://#{p['project']}.apache.org/#{p['subproject']}"
+else
+ p['website'] = "http://#{p['project']}.apache.org"
+end
+ end
self.data['json'] = p # pass the data to the page processor
end
end
_
Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: Index.lua script (was: svn commit: r1829853 - in /attic/site: docs/projects/oltu.html xdocs/projects/oltu.xml)
On Mon, 23 Apr 2018, sebb AT ASF wrote: Date: Mon, 23 Apr 2018 13:15:34 +0200 From: sebb AT ASF <s...@apache.org> To: Henk P. Penning <penn...@uu.nl> Cc: general@attic.apache.org Subject: Index.lua script (was: svn commit: r1829853 - in /attic/site: docs/projects/oltu.html xdocs/projects/oltu.xml) Sender: seb...@gmail.com AFAICT that has to run on the server, right? right. Does Infra agree to converting the static Attic site into a dynamic one? No, they don't ; so, static pages it is, then. Groeten, HPP ---- _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
svn commit: r1829853 - in /attic/site: docs/projects/oltu.html xdocs/projects/oltu.xml (fwd)
Hi Sebb, I created an 'index.lua' script for attic.a.o ; -- only some 130 lines -- it creates the index and projects/ pages for attic.a.o -- I added one or two 'dist' attributes to attic.json -- still rough ; but ready :-) At work : http://mirror-vm80.apache.org/index.lua Source : http://mirror-vm80.apache.org/index.txt I can do the 'flagged' stuff ; easy. Groeten, HPP _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/ -- Forwarded message -- Date: Mon, 23 Apr 2018 12:21:59 +0200 From: s...@apache.org To: general@attic.apache.org Subject: svn commit: r1829853 - in /attic/site: docs/projects/oltu.html xdocs/projects/oltu.xml Author: sebb Date: Mon Apr 23 10:21:59 2018 New Revision: 1829853 URL: http://svn.apache.org/viewvc?rev=1829853=rev Log: Oltu uses confluence Modified: attic/site/docs/projects/oltu.html attic/site/xdocs/projects/oltu.xml Modified: attic/site/docs/projects/oltu.html URL: http://svn.apache.org/viewvc/attic/site/docs/projects/oltu.html?rev=1829853=1829852=1829853=diff == --- attic/site/docs/projects/oltu.html (original) +++ attic/site/docs/projects/oltu.html Mon Apr 23 10:21:59 2018 @@ -76,7 +76,7 @@ Apache Oltu is an OAuth protocol impleme Wiki - http://wiki.apache.org/oltu/;>wiki.apache.org/oltu/ + https://cwiki.apache.org/confluence/display/oltu/;>cwiki.apache.org: oltu Source Code (Subversion) Modified: attic/site/xdocs/projects/oltu.xml URL: http://svn.apache.org/viewvc/attic/site/xdocs/projects/oltu.xml?rev=1829853=1829852=1829853=diff == --- attic/site/xdocs/projects/oltu.xml (original) +++ attic/site/xdocs/projects/oltu.xml Mon Apr 23 10:21:59 2018 @@ -33,9 +33,9 @@ Apache Oltu is an OAuth protocol impleme - - - + + + As with any project in the Attic - if you should choose to fork Oltu outside of Apache,
Re: New maintenance.
On Sun, 22 Apr 2018, j...@apache.org wrote: Date: Sun, 22 Apr 2018 15:53:52 +0200 From: j...@apache.org To: general@attic.apache.org Subject: New maintenance. Based on site-json I propose the following changes: Change docs/scripts/attic.js to project.json (kept as pure json outside docs). Also, I /really/ would like to have the .json available for 'others', so inside docs/ please. Let's call the .json 'attic.json' ; for 'others' the .json describes what PMC attic has done. Remove xdocs. Ok. Allow a build job to monitor for svn changes and if any active a generation script. The generation script does the following: - generate a sidebar.inc which is included (physically in all files) - Generate a page pr. project in projects, based on a 1 template “project.md” or similar Eh, no ; if the build scripts creates the attic.js (from a template and 'attic.json') we are done ; this is much closer to what we have now. - Generate a flagged directory (if field “flag” is present in the JSON object”) perhaps we should go with 'retired' (as opposed to 'flagged/') after all ; this makes it easier to fix the httpd config as a separate issue ; we'll rm -rf flagged/ later. Ps. I can help to change attic.js, but I am afraid the generate script is for someone else to write. Can we please go for a simple Makefile ? So we can simply do : -- svn up -- edit json -- make -- commit Sebb, I am totally ignorant re: build stuff ; can the build stuff run a make ? Groeten, HPP _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: svn commit: r1829770 - in /attic/site-json: build.props build.sh build.xml docs/projects/ lib/ xdocs/
On Sun, 22 Apr 2018, Jan Iversen wrote: Date: Sun, 22 Apr 2018 14:34:29 +0200 From: Jan Iversen <jancasacon...@gmail.com> To: general@attic.apache.org Subject: Re: svn commit: r1829770 - in /attic/site-json: build.props build.sh build.xml docs/projects/ lib/ xdocs/ The 'name' attribute in the JSON in "attic.js". That is the text for the project list in the RH menu, and is free-format. It's not directly convertible into a dist/ directory name. So I agree that a dist attribute would be needed for at least some entries. That is the reason for the “website” field. If we want to use the name alone, that field could be split in 2. IHMO it is better to derive attribute 'website' (as $dist.apache.org) from a 'dist' attribute, than the other way around ; nevermind. I hope dist names are the same as TLP website names but I've not checked. The field “board” was added where I had problems between the TLP name used in Whimsy and the normal name. I see only two entries with non-empty "board" fields ; the first isn't necessary ; the second isn't helpful in mapping to the right /dist/GHOST tag : "name":"Crimson", "board": "crimson", "name":"Standard C++ Library (STDCXX)", "board": "Cxx_Standard_Library", Let's have a 'dist' attribute for entries that need it. default : lowercase($name). sanity : if $name matches whitespace then $dist must not be empty. Let's remove 'board' in entries where board == ''. Regards, HPP _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: svn commit: r1829770 - in /attic/site-json: build.props build.sh build.xml docs/projects/ lib/ xdocs/
On Sun, 22 Apr 2018, sebb wrote:
Date: Sun, 22 Apr 2018 13:53:15 +0200
From: sebb <seb...@gmail.com>
To: general@attic.apache.org
Subject: Re: svn commit: r1829770 - in /attic/site-json: build.props build.sh
build.xml docs/projects/ lib/ xdocs/
Eh ; just a reminder ; the httpd config for www.a.o uses :
RewriteCond "%%{}{REQUEST_URI}" "^/dist/([-a-zA-Z0-9]+)"
RewriteCond "/var/www/attic.apache.org/projects/%1.html" -f
RewriteRule ".*" "http://attic.apache.org/projects/%1.html; [R=307,L]
In other words : the /dist/GHOST/ redirects are triggered
by the presence of "attic.apache.org/projects/GHOST.html".
The point is that the lookup [-f] has to fast.
In the future we should create a directory (like "flagged/") ;
possibly combine the two, as in :
attic.a.o/retired/
attic.a.o/retired/GHOST/# retired flag
attic.a.o/retired/GHOST/add-banner # banner flag
The dist redirect needs the plain host name, e.g. ace, whereas AFAIK
the banner processing needs FQDN, e.g. ace[.eu|us].apache.org.
So that won't work unless the banner processing can be changed to use
the plain host name.
Right ; if we stay with /flagged/, the dist trigger can changed as :
- RewriteCond "/var/www/attic.apache.org/projects/%1.html" -f
+ RewriteCond "/var/www/attic.apache.org/flagged/%1.apache.org/" -d
... and the banner-trigger :
-
+
But I agree it would be good to reduce the number of files that have
to be created/amended for a new retirement.
Eventually, we should generate the 'flagged' stuff.
Does it make sense to have an (optional) 'dist' attribute,
for sites where "lowercase(name)" is not equal to the
the NAME in /dist/NAME ?
Which 'name' are you referring to here?
The 'name' attribute in the JSON in "attic.js".
Regards,
HPP
_
Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: Discussion on proposed solutions for simplified maintenance.
On Sun, 22 Apr 2018, Jan Iversen wrote: Date: Sun, 22 Apr 2018 11:57:33 +0200 From: Jan Iversen <jancasacon...@gmail.com> To: general@attic.apache.org Subject: Re: Discussion on proposed solutions for simplified maintenance. On 22 Apr 2018, at 11:33, sebb <seb...@gmail.com> wrote: For proper comparison I think we need to see the whole solution. This will obviously have to be done so that it does not impact the live site. I believe the sample I have made with test.html and generation of all project files are sufficient. No need to waste more time on that. Time saving is important to me, and it does not make sense to waste resources on making two complete solutions just to scrap one of them. Right ; I think Jan's stuff is ok ; basicly it doesn't have to be more complicated than that. It is a good starting point for further development. Personally I would separate the (json) data from the program, but that is a minor detail. Regards, Henk Penning ---- _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: Sorry for the noise
On Fri, 13 Apr 2018, Jan Iversen wrote: Date: Fri, 13 Apr 2018 12:22:06 +0200 From: Jan Iversen <jancasacon...@gmail.com> To: general@attic.apache.org Subject: Re: Sorry for the noise If we are going to change the site generation, I suggest we start with a data file containing all the retired project details and use that to generate the pages. Also the data file may be useful for other purposes, so JSON might be a good format. I was not thinking of “generation”, because we have to few projects entering attic that is does not have value. I am thinking of making something that can be plainly edited, which would make life easier, since it can be done directly in a browser without the need of having special software installed. This is of course also true for server side generated html, which could be a second step if we agree on it. You do the work, so you decide. For the long term I think it would be nice to have -- a template file, -- a data (json?) file with per/project attributes -- a simple 'expand' script. Not for now, but perhaps you can keep it in mind ... Jan I. Regards, HPP ---- _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: process
On Fri, 13 Apr 2018, Jan Iversen wrote:
Date: Fri, 13 Apr 2018 08:35:23 +0200
From: Jan Iversen <jancasacon...@gmail.com>
To: Henk P. Penning <penn...@uu.nl>
Cc: general@attic.apache.org
Subject: Re: process
Hi Jan,
Done.
Nice work !
Thanks.
typo : touch docsflagged => docs/flagged
Perhaps change :
Create directory to signal project is moved to Attic
into
Signal that retired banners must be added to ${project}.a.o.
[ because, older retirees already have banners
and shouldn't be 'flagged'.
]
Jan I
Thanks ; regards,
HPP
-------- _
Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
On 13 Apr 2018, at 07:46, Henk P. Penning <penn...@uu.nl> wrote:
Hi Jan,
can you please update the 'process page' ?
-- after 2.5 "Create project page ..." add (as one bullit) :
mkdir flagged/${project}.apache.org ;
touch flagged/${project}.apache.org/${project}.apache.org
-- remove 2.6.i "Update website with Attic notice: ..."
FYI,
-- The layout of the 'flagged' directory is not yet fixed.
-- perhaps we'll use it to augment it with (per project)
meta info, quickly accessible by httpd/lua.
Thanks ; groeten,
HPP
-------- _
Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: svn commit: r1829018 - /attic/site/docs/scripts/attic_filter.lua
On Fri, 13 Apr 2018, s...@apache.org wrote:
Date: Fri, 13 Apr 2018 01:31:26 +0200
From: s...@apache.org
To: general@attic.apache.org
Subject: svn commit: r1829018 - /attic/site/docs/scripts/attic_filter.lua
Sebb,
please DON'T change this stuff ; you just broke it.
HPP
Author: sebb
Date: Thu Apr 12 23:31:26 2018
New Revision: 1829018
URL: http://svn.apache.org/viewvc?rev=1829018=rev
Log:
Prettify
Modified:
attic/site/docs/scripts/attic_filter.lua
Modified: attic/site/docs/scripts/attic_filter.lua
URL:
http://svn.apache.org/viewvc/attic/site/docs/scripts/attic_filter.lua?rev=1829018=1829017=1829018=diff
==
--- attic/site/docs/scripts/attic_filter.lua (original)
+++ attic/site/docs/scripts/attic_filter.lua Thu Apr 12 23:31:26 2018
@@ -17,14 +17,15 @@ function output_filter(r)
-- add header:
local host = r.hostname:match("^([^.]+)") -- get TLP part of hostname
+local name = host:gsub("^%l", string.upper) -- Prettify (TODO: look up
real name)
local sty1 = 'font-size:x-large;padding:15px;color:white;background:red;' ;
local sty2 = 'color:white' ;
coroutine.yield ( ([[
-Project %s is retired. See %s's
+Project %s has retired. For details please refer to its
https://attic.apache.org/projects/%s.html;>
-attic page.
- ]]):format(sty1, host, host, sty2, host) )
+Attic page.
+ ]]):format(sty1, name, sty2, host) )
-- spit out the actual page
while bucket do
coroutine.yield(bucket)
------------ _
Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: attic_filter suggestions
On Thu, 12 Apr 2018, sebb wrote:
Date: Thu, 12 Apr 2018 17:53:42 +0200
From: sebb <seb...@gmail.com>
To: general@attic.apache.org
Subject: attic_filter suggestions
The new filter is great as it makes the Attic's job much simpler.
Yep ; it does ; a bit.
However it looks a bit odd to see the project name only in lower case;
it would be nice if it showed the name in the correct format.
Work is still in progress ; we'll make it nicer, if easy and robust.
For many projects that just means capitalising the first letter.
For others there could be a conversion table.
Also, the marker is currently implemented as a directory containing an
empty file of the same name, e.g.
flagged/oltu.apache.org/oltu.apache.org
That is (for now) a safeguard ; what happened is that the
'show-a-banner' condition :
-d /var/attic.apache.org/flagged/%{HTTP_HOST}
was mangeled by puppet and effectively was
-d /var/attic.apache.org/flagged/
so, for a few minutes /every/ TLP got a banner ...
That seems a bit unnecessary; surely it would be enough to just have a
file under flagged?
... work is still in progress.
We will have to see if this works for all GHOST.apache.org sites ;
As is, some oltu.apache.org pages don't show the banner.
Work will continue in about a week.
Regards,
HPP
---- _
Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
+= scripts/
Hi, I will add a scripts/ directory to the attic-site shortly, for the script that adds a banner to retired TLP sites. Hope that's OK ; regards, Henk Penning _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: [jira] [Created] (ATTIC-168) move oltu to attic
On Sun, 8 Apr 2018, Jan Iversen wrote:
Date: Sun, 8 Apr 2018 16:45:37 +0200
From: Jan Iversen <j...@apache.org>
To: general@attic.apache.org
Subject: Re: [jira] [Created] (ATTIC-168) move oltu to attic
Last task in moving oltu to attic is all yours :-)
Hi Jan,
... thanks ; will work on it, but it depends on coop of infra.
Btw, I see /dist/oltu/ isn't removed (yet).
Did you file a infra-jira ? I can't find it.
I mean the jira mentioned in attic 'process' point 3.
jan i
Thanks ; regards,
Henk Penning
Sent from my iPad
On 1 Apr 2018, at 16:46, Jan Iversen <jancasacon...@gmail.com> wrote:
Ok will (not) do :-)
Jan I
On 1 Apr 2018, at 11:14, Henk P. Penning <penn...@uu.nl> wrote:
On Fri, 23 Mar 2018, jan iversen (JIRA) wrote:
Date: Fri, 23 Mar 2018 20:15:00 +0100
From: "jan iversen (JIRA)" <j...@apache.org>
To: general@attic.apache.org
Subject: [jira] [Created] (ATTIC-168) move oltu to attic
[ top post ]
Hi,
[ just a reminder ]
I developped an idea on how we can 'fix' site oltu.apache.org ;
see http://mirror-vm80.apache.org/sites/oltu/
So please don't touch site oltu.apache.org ...
Thanks ; regards,
Henk Penning
------------ _
Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
jan iversen created ATTIC-168:
-
Summary: move oltu to attic
Key: ATTIC-168
URL: https://issues.apache.org/jira/browse/ATTIC-168
Project: Attic
Issue Type: Task
Reporter: jan iversen
Assignee: jan iversen
Will start after easter
Confirm Board Resolution (if TLP)
Delete from committee-info.txt (if TLP)
Remove VP entry on http://www.apache.org/foundation/ (if TLP)
Inform users of the move to the Attic
Create project page on Attic site:
http://attic.apache.org/projects/${project}.html
Obtain source control karma and point source control mails to general at attic
i. Update website with Attic notice: http://${project}.apache.org/
ii. Update the project DOAP file (if any):
https://projects.apache.org/project.html?${project}
iii. Make source control read-only
Move committee's PMC data file to retired (if TLP)
Remove from http://www.apache.org/#projects-list navigation (if TLP)
Announce on announce at apache.org
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
------------ _
Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: [jira] [Created] (ATTIC-168) move oltu to attic
On Fri, 23 Mar 2018, jan iversen (JIRA) wrote:
Date: Fri, 23 Mar 2018 20:15:00 +0100
From: "jan iversen (JIRA)" <j...@apache.org>
To: general@attic.apache.org
Subject: [jira] [Created] (ATTIC-168) move oltu to attic
[ top post ]
Hi,
[ just a reminder ]
I developped an idea on how we can 'fix' site oltu.apache.org ;
see http://mirror-vm80.apache.org/sites/oltu/
So please don't touch site oltu.apache.org ...
Thanks ; regards,
Henk Penning
-------- _
Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
jan iversen created ATTIC-168:
-
Summary: move oltu to attic
Key: ATTIC-168
URL: https://issues.apache.org/jira/browse/ATTIC-168
Project: Attic
Issue Type: Task
Reporter: jan iversen
Assignee: jan iversen
Will start after easter
Confirm Board Resolution (if TLP)
Delete from committee-info.txt (if TLP)
Remove VP entry on http://www.apache.org/foundation/ (if TLP)
Inform users of the move to the Attic
Create project page on Attic site:
http://attic.apache.org/projects/${project}.html
Obtain source control karma and point source control mails to general at attic
i. Update website with Attic notice: http://${project}.apache.org/
ii. Update the project DOAP file (if any):
https://projects.apache.org/project.html?${project}
iii. Make source control read-only
Move committee's PMC data file to retired (if TLP)
Remove from http://www.apache.org/#projects-list navigation (if TLP)
Announce on announce at apache.org
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Re: Redirects for attic project download directories
On Wed, 28 Feb 2018, sebb wrote:
Date: Wed, 28 Feb 2018 19:48:21 +0100
From: sebb <seb...@gmail.com>
To: general@attic.apache.org
Subject: Re: Redirects for attic project download directories
[ top-post ; further comments in-line ]
Hi,
Five days ago [23-2-2018] I wrote :
> I think it is now safe to remove all /dist/GHOST/ directories.
This was met with "silent consent".
Regards,
Henk Penning
On 28 February 2018 at 18:28, Henk P. Penning <penn...@uu.nl> wrote:
On Fri, 23 Feb 2018, Henk P. Penning wrote:
Date: Fri, 23 Feb 2018 18:09:28 +0100
From: Henk P. Penning <penn...@uu.nl>
To: general@attic.apache.org
Subject: Re: Redirects for attic project download directories
I think it is now safe to remove all /dist/GHOST/ directories.
Hi,
For the record, because INFRA-16034 requires an 'ack',
here's my summary of this thread :
GHOST == retired project ;
The objection to the rm's of the /dist/GHOST/ directories was the loss
of redirects caused by the /dist/GHOST/.htaccess files.
-- On www.a.o this is now fixed with rewrite rules in the config
for "www.a.o/dist/".
-- On GHOST.apache.org, the refs to the mirrors (closer.{cgi,lua})
redirect to attic because closer.lua is now "attic aware".
However, the redirects will no longer work for mirrors, because they
don't see the local redirects.
Right.
For example, this does not redirect:
http://mirror.ox.ac.uk/sites/rsync.apache.org/ace/
Whereas this does:
https://www.apache.org/dist/ace/
Right [ace is/was todo ; it doesn't have a .htaccess]
[note that dist/abdera and dist/wookie are empty :-]
At present, some attic projects do redirect; that is because of the
.htaccess files.
http://mirror.ox.ac.uk/sites/rsync.apache.org/harmony/
It seems to me that this is a big change.
The change is not relevant. The point is that we (the ASF)
don't refer to individual items on specfic mirrors anymore
(because closer.lua is now "attic aware") ; refs like :
http://mirror.ox.ac.uk/sites/rsync.apache.org/harmony/foo/bar
All refs like that on third-party pages, and indeed all refs to
/dist/ items, will eventually die ; that is the nature of /dist/.
And it goes against what you wrote on the following issue:
https://issues.apache.org/jira/browse/INFRA-16122?focusedCommentId=16380672=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16380672
i.e. you still expect mirrors to redirect attic projects.
I don't ; but redirects should work. For examples, see below.
Perhaps we should add a test to dist/zzz/ :-).
-------- _
Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
/dist/thrift/rpm/.htaccess:RedirectMatch permanent (.*)rpm/(.*)
http://dl.bintray.com/apache/thrift/rpm/$2
/dist/thrift/debian/.htaccess:RedirectMatch permanent (.*)thrift/debian/(.*)
http://dl.bintray.com/apache/thrift/debian/$2
/dist/lucene/mahout/.htaccess:RedirectMatch Permanent .*
http://www.apache.org/dyn/closer.cgi/mahout
/dist/lucene/mahout/mahout-collections-1.0/.htaccess:RedirectMatch Permanent .*
http://www.apache.org/dyn/closer.cgi/mahout
/dist/lucene/tika/.htaccess:RedirectMatch Permanent .*
http://www.apache.org/dyn/closer.cgi/tika
/dist/lucene/nutch/.htaccess:RedirectMatch Permanent .*
http://www.apache.org/dyn/closer.cgi/nutch
/dist/apr/.htaccess:RedirectMatch 301 ^(.*)/Announcement\.(.*)
$1/Announcement1.2.$2
/dist/apr/.htaccess:RedirectMatch 301 ^(.*)/Announcement-1\.(.*)
$1/Announcement1.2.$2
/dist/cassandra/debian/.htaccess:RedirectMatch ^/~eevans/debian(.*)
http://wiki.apache.org/cassandra/DebianPackaging
/dist/cassandra/debian/.htaccess:RedirectMatch permanent
(.*)cassandra/debian/(.*) http://dl.bintray.com/apache/cassandra/$2
/dist/httpd/.htaccess:RedirectMatch 301 ^(.*)/Announcement\.(.*)
$1/Announcement1.3.$2
/dist/httpd/.htaccess:RedirectMatch 301 ^(.*)/Announcement2\.([th].*)
$1/Announcement2.0.$2
/dist/httpd/.htaccess:RedirectMatch 301 ^(.*)/Announcement21\.(.*)
$1/Announcement2.1.$2
/dist/sling/.htaccess:Redirect Permanent /dist/sling/KEYS
https://people.apache.org/keys/group/sling.asc
/dist/aurora/debian/.htaccess:RedirectMatch permanent (.*)aurora/debian/(.*)
http://dl.bintray.com/apache/aurora/$2
Re: next project
On Tue, 27 Feb 2018, j...@apache.org wrote: Date: Tue, 27 Feb 2018 13:57:36 +0100 From: j...@apache.org To: general@attic.apache.org Subject: Re: next project the next time a project (say, GHOST) goes into the attic, please don't fix GHOST.apache.org ; Just to be sure, our procedure does not say anything about changing .apache.org <http://apache.org/>, all we do on the site is to insert a text, explaining that the project is moved to the Attic. That's what I meant with "fix GHOST.apache.org". I am not to sure, what should be changed in the procedure, and would be glad for a text that could be added. My request is to not touch GHOST.apache.org, while we establish what works best. Perhaps we can make GHOST.apache.org have a "RETIRED" header as soon as "attic.a.o/projects/GHOST.html" exists. Jan I. Groeten, HPP -------- _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
next project
Hi, the next time a project (say, GHOST) goes into the attic, please don't fix GHOST.apache.org ; perhaps it is not necessary anymore. I've talked to infra ; we would like try something like http://mirror-vm80.apache.org/sites/httpd [ for 'mirror-vm80' read 'attic' ; the box below the read message is an iframe pointing to httpd.apache.org ] More detailed ; if/when project GHOST retires, we simply add to the apache config of GHOST.apache.org : # Accept "__ATTIC__/*" ; redirect everything else RewriteRule "^__ATTIC__/(.*)$" "$1" [L] RewriteRule "^(.*)$" "http://attic.apache.org/sites/$1; [L] The iframe page for "GHOST.apache.org/$PATH" will contain "http://GHOST/__ATTIC__/$PATH;. Groeten, HPP -------- _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: Redirects for attic project download directories
On Thu, 15 Feb 2018, sebb wrote: Date: Thu, 15 Feb 2018 22:22:12 +0100 From: sebb <seb...@gmail.com> To: general@attic.apache.org Subject: Redirects for attic project download directories The original thread got derailed, so here is what I think the issue is. When a project is moved to the attic, its website is updated to show a banner that the project has been retired, with a link to the attic. Also, its release files on www.apache.org/dist are removed, and replaced with an .htaccess redirect to an Attic page with summary details of the project. e.g. http://www.apache.org/dist/harmony redirects to http://attic.apache.org/projects/harmony.html Whilst this redirect works, and is simple to administer, it means there are many directories under www.apache.org/dist/ which only contain an .htaccess file, and scripts may have to be aware of which directories correspond to active projects. It would be useful to be able to tidy this up. FYI ; this now works. The config of www.apache.org redirects www.apache.org/dist/GHOST => attic.apache.org/projects/GHOST.html ... if the latter exists. See : https://dist.apache.org/repos/dist/release/etch/ This dir has no '.htaccess' file ; note the leading '.' ; infra moved .htaccess => htaccess as a final test. Try : https://www.apache.org/dist/etch I think it is now safe to remove all /dist/GHOST/ directories. Groeten, HPP ---- _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: Redirects for attic project download directories
On Tue, 20 Feb 2018, sebb wrote: Date: Tue, 20 Feb 2018 11:37:12 +0100 From: sebb <seb...@gmail.com> To: general@attic.apache.org Subject: Re: Redirects for attic project download directories On 20 February 2018 at 09:21, Henk P. Penning <penn...@uu.nl> wrote: We would map it into attic-space if we could do it elegantly. This still preserves the URL as far as the public are concerned. Which is my point: we preserve ghost.a.o, Of course, but I hope we can add the "retired" top-of-page stuff without touching the content of ghost.a.o. and at present we preserve www.a.o/dist/ghost as a redirect. Of course ; but that is fixable with 3 or 4 rewrite rules in the config of www.apache.org/dist/ ; that is, without the www.a.o/dist/ghost directories. These rules will work for GHOST ; as soon as there is a "attic.a.o/projects/GHOST.html" page, www.a.o will redirect to it. [ on the webserver, the page is in file /x1/www/attic.apache.org/projects/GHOST.html" ] So, there is no need for dist/attic/GHOST ; after attic.a.o/projects/GHOST.html is created, infra can simply svn rm dist/release/GHOST ; I believe that is the usual work-flow. correct me if I'm wrong :-). I think that is worth keeping. Of course. Fixing website GHOST.apache.org is a hassle. It would be nice if we could present it "as is", prefixed with the necessary "RETIRED" head. That's a subject for a separate thread. Agree :-) Ideas (or working examples) welcome ; think "mod_proxy", "mod_sed" etc. Groeten, HPP ---- _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: Redirects for attic project download directories
On Sun, 18 Feb 2018, sebb wrote: Date: Sun, 18 Feb 2018 19:35:40 +0100 From: sebb <seb...@gmail.com> To: general@attic.apache.org Subject: Re: Redirects for attic project download directories On 18 February 2018 at 16:10, Henk P. Penning <penn...@uu.nl> wrote: On retirement we remove GHOSTS from committee-info.txt and navigation [http://www.apache.org/#projects-list], etc. In short, we have pointers to GHOSTs, but not among the living ; and that should also be the case for /dist/ (and the mirrors). But we keep ghost.apache.org. We would map it into attic-space if we could do it elegantly. Fixing website GHOST.apache.org is a hassle. It would be nice if we could present it "as is", prefixed with the necessary "RETIRED" head. Perhaps with something like : https://mirror-vm.apache.org/frames.html At the moment this doesn't work too good ; -- browers don't like http urls on https page -- sites don't like to be included in 's But maybe this can fixed without touching the /content/ of GHOST.a.o ; with config fixes only. Groeten, HPP -------- _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: Redirects for attic project download directories
On Sat, 17 Feb 2018, sebb wrote: Date: Sat, 17 Feb 2018 19:45:56 +0100 From: sebb <seb...@gmail.com> To: general@attic.apache.org Subject: Re: Redirects for attic project download directories On 16 February 2018 at 16:53, Henk P. Penning <penn...@uu.nl> wrote: On Thu, 15 Feb 2018, sebb wrote: It would be useful to be able to tidy this up. Links to mirrors are typically generated by closer.lua ; we can make closer.lua attic-aware (says humbedooh :-). When closer.lua encounters a target in an atticked project, it can redirect to attic.a.o. Good idea as it will stop further generation of useless URLs. This now in test on mirror-vm ; try https://mirror-vm.apache.org/dyn/dev_closer.lua/ https://mirror-vm.apache.org/dyn/dev_closer.lua/beehive/blib/blob Aside: dev_closer.lua is also 'dist' and 'archive' aware ; try https://mirror-vm.apache.org/dyn/dev_closer.lua/FOO/BAR https://mirror-vm.apache.org/dyn/dev_closer.lua/httpd/apache_1.3.0.tar.Z Now, suppose we create dist/attic/ghosts/ https:// dist.apache.org/repos/dist/release/attic/ghosts/ -- on retirement, infra svn moves dist/GHOST/ to dist/attic/ghosts/ ; Pmc Attic can cleanup what was formerly dist/GHOST/ Unless the archive synch job is changed to ignore files under dist/attic/ghosts this will result in creating copies of the release artifacts on archive.a.o That's a detail ; the point is that /we/ can cleanup ; less work for infra ; more control for us. -- closer.lua can check the presence of dist/attic/ghosts/PROJ -- the RewriteRules idem I think this would tidy up /dist/ while keeping the proper Redirects. It won't keep the redirects on the 3rd party mirrors. Such URLs may well have been stored elsewhere. For example [1] points to (e.g.) http://mirror.org/apache/harmony/milestones/5.0/M15/apache-harmony-5.0-jre-r991518-windows-x86-snapshot.zip At present such a URL will redirect back to the attic (try it!) That is the functionality which I think is important to preserve. When the new closer.lua is in place, [1] will point directly to attic.a.o/projects/harmony.html ; Are there any other examples of important pages ? That is not true for 3rd party mirrors ... Any link to a specific file on a specific mirror will stop working sooner or later ; mirrors disappear and /dist/ changes. LIVE-link : http://some.mirror.org/.../httpd/some-old-version.gz GHOST-link : http://some.mirror.org/.../beehive/some-old-version.gz The LIVE-link gives a 404 ; the GHOST-link gives a redirect. Why the difference? On retirement we remove GHOSTS from committee-info.txt and navigation [http://www.apache.org/#projects-list], etc. In short, we have pointers to GHOSTs, but not among the living ; and that should also be the case for /dist/ (and the mirrors). [1] http://harmony.apache.org/download.cgi Groeten, HPP ---- _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: Redirects for attic project download directories
On Thu, 15 Feb 2018, sebb wrote: Date: Thu, 15 Feb 2018 22:22:12 +0100 From: sebb <seb...@gmail.com> To: general@attic.apache.org Subject: Redirects for attic project download directories The original thread got derailed, so here is what I think the issue is. When a project is moved to the attic, its website is updated to show a banner that the project has been retired, with a link to the attic. Also, its release files on www.apache.org/dist are removed, and replaced with an .htaccess redirect to an Attic page with summary details of the project. e.g. http://www.apache.org/dist/harmony redirects to http://attic.apache.org/projects/harmony.html Whilst this redirect works, and is simple to administer, it means there are many directories under www.apache.org/dist/ which only contain an .htaccess file, and scripts may have to be aware of which directories correspond to active projects. It would be useful to be able to tidy this up. Agree ; that's a good summary. However it is important that the redirects are kept as there are likely to be links to the download location in lots of places. We should not break URLs unnecessarily. Note that the redirects also work on mirror links as well as on the ASF hosts. This behaviour should be preserved as historical links will generally use the dynamic mirror system. For example the harmony download page [1] points to the mirrors; externally preserved links are likely to do so as well. Removing the .htaccess files and their parent directories will break all the links, so IMO that is not an option. [ humbedooh == Daniel Gruno ; infra ; initial(?) author of closer.lua ; closer.lua == the script that projects use on their (download) pages to link to "the mirrors" ; GHOST == a retire project ; ASF GHOSTs live in the Attic :-) ] Links to mirrors are typically generated by closer.lua ; we can make closer.lua attic-aware (says humbedooh :-). When closer.lua encounters a target in an atticked project, it can redirect to attic.a.o. Are there any important links to specific files on specific mirrors ? That leaves "www.apache.org/dist/GHOST". It would be easy (again, says humbedooh) to configure www.apache.org with a few (fixed number of) Rewrite rules like (pseudo-code) : # redirect dist/GHOST to attic.a.o/.../GHOST.hmtl RewriteCondition "file path in an atticked dir" RewriteRule .* "Redirect to attic.a.o" Now, suppose we create dist/attic/ghosts/ https:// dist.apache.org/repos/dist/release/attic/ghosts/ -- on retirement, infra svn moves dist/GHOST/ to dist/attic/ghosts/ ; Pmc Attic can cleanup what was formerly dist/GHOST/ -- closer.lua can check the presence of dist/attic/ghosts/PROJ -- the RewriteRules idem I think this would tidy up /dist/ while keeping the proper Redirects. [1] http://harmony.apache.org/download.cgi Regards, Henk Penning ------------ _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: project ACE.
On Wed, 14 Feb 2018, jan iversen wrote: Date: Wed, 14 Feb 2018 13:07:56 +0100 From: jan iversen <jancasacon...@gmail.com> To: general@attic.apache.org Subject: Re: project ACE. On Wed, 14 Feb 2018 at 10:16, Henk P. Penning <penn...@uu.nl> wrote: If there are no objections, I'll ask infra to svn rm https://dist.apache.org/repos/dist/release/XXX for XXX = hivemind shale beehive ibatis excalibur harmony jakarta xml esme stdcxx xmlbeans +1 Thanks. Solely out of curiosity, do you know approx. how much space it will free ? Absolutely nothing :-) These projs only have /dist/XXX/.htaccess I just want to unclutter /dist/ ; and consequently, for instance : https://checker.apache.org/ Jan i Thanks ; regards, HPP ---- _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: project ACE.
On Mon, 12 Feb 2018, Henk P. Penning wrote: I will "roll my own" if there is no wider interest ; that's ok. Here are the dates I gleaned from the attic pages : moved to attic before 2014-02-14 ; 4 years ago : 2009-04-15 hivemind 2009-05-15 shale 2010-01-15 beehive 2010-06-15 ibatis 2010-12-15 excalibur 2011-11-15 harmony 2011-12-15 jakarta 2012-04-15 xml 2013-07-15 esme 2013-07-15 stdcxx 2013-07-15 xmlbeans # keep 2014-05-15 click # keep 2015-03-15 whirr # keep 2015-04-15 lenya # keep 2015-07-15 deltacloud # keep 2015-07-15 directmemory # keep 2015-11-15 shindig # keep 2016-01-15 onami # keep 2016-01-15 rave # keep 2016-04-15 mrunit # keep 2016-04-15 wookie # keep 2016-05-15 continuum # keep 2016-05-15 tuscany # keep 2016-06-15 etch # keep 2016-12-15 devicemap # keep 2017-01-15 stratos # keep 2017-03-15 abdera # keep 2017-04-15 wink # keep 2017-12-15 ace If there are no objections, I'll ask infra to svn rm https://dist.apache.org/repos/dist/release/XXX for XXX = hivemind shale beehive ibatis excalibur harmony jakarta xml esme stdcxx xmlbeans Thanks, regards, HPP ---- _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: project ACE.
On Mon, 12 Feb 2018, jan iversen wrote:
Date: Mon, 12 Feb 2018 12:59:17 +0100
From: jan iversen <jancasacon...@gmail.com>
To: general@attic.apache.org
Subject: Re: project ACE.
I am unhappy about yet another manual step to the retirement process. the
process alreday contain quite a number of steps that could/should be
automated
, like e.x:
- update authorization files
- find maillists, wiki etc in order to tell infra what to close down
Agree ; but ..., automating that stuff could/should be based
on authorative, machine-readable info provided by attic.a.o/ ...
PMC Attic is the only body that can say /when/ the move
is/was actually started and when it was 'done'.
I don't see how stuff can be automated reliably without
such info.
I just looked at the list again and it is enormous.
A project should [IMHO] have a state {podling, tlp, attic}
and graduation/attic-ing should be as easy as
changing the state. Nevermind.
people wanting to know when a retirement happened can e.g. look at svn log
for the auth files.
Hm ;
I will "roll my own" if there is no wider interest ; that's ok.
jan i
Thanks ; regards,
Henk Penning
-------- _
Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: project ACE.
On Tue, 6 Feb 2018, jan iversen wrote:
On Tue, 6 Feb 2018 at 12:40, Henk P. Penning <penn...@uu.nl> wrote:
Hi,
PS To get the "attic'ed" project list, I parse
svn ls https://svn.apache.org/repos/asf/attic/site/docs/projects
stripping '.html', and ignoring entries with a '-' ;
is there a better way ?
I normally use the xdocs directory that is xml and easier to parse.
I don't see a 'date' field in the xdocs files ;
I really would like to have a list like
[ { dist_path : "beehive"
, to_attic : "2010-01-15"
}
, ...
]
Because "moving stuff into the attic", is what PMC Attic does,
it is fine to provide this info (authoratively) on attic.a.o/,
rather than somewhere else.
Other (automated) processes can fetch it from "attic.a.o/".
It means (yet) another item in the "process" list ... ;
is that a problem ? I will provide an initial file, of course.
Ideas ?
Thanks ; regards,
Henk Penning
------------ _
Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: project ACE.
On Tue, 6 Feb 2018, jan iversen wrote:
Date: Tue, 6 Feb 2018 12:50:09 +0100
From: jan iversen <jancasacon...@gmail.com>
To: general@attic.apache.org
Subject: Re: project ACE.
On Tue, 6 Feb 2018 at 12:40, Henk P. Penning <penn...@uu.nl> wrote:
On Tue, 6 Feb 2018, jan iversen wrote:
Date: Tue, 6 Feb 2018 12:01:10 +0100
From: jan iversen <jancasacon...@gmail.com>
To: general@attic.apache.org
Subject: project ACE.
[ I think it looks a bit messy ; too much old stuff in /dist/ ;
Shouldn't we remove /dist/atticked_project/ after
some suitable interval ; 1, 2, 3 or 5 years ?
]
I would opt for 5 years, but I would really like to hear other opinions.
I vote for 3 years.
2. under "attic'ed projects" : a RedStar flags a project
with more than 1 file.
I do not understand what more than 1 file means,
An attic'ed project should have 1 file :
dist/PROJ/.htaccess
PS To get the "attic'ed" project list, I parse
svn ls https://svn.apache.org/repos/asf/attic/site/docs/projects
I normally use the xdocs directory that is xml and easier to parse.
Thanks ; I'll take a look ; I was hoping for a json :
[ { path : $path
, date : ...
, time : ...
, ...
}
, ...
]
... if it can be automated.
jan i
Regards,
HPP
------------ _
Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: Rethinking TLP creation/migration
On Mon, 23 May 2016, Sam Ruby wrote: Date: Mon, 23 May 2016 03:00:51 +0200 From: Sam Ruby <ru...@intertwingly.net> To: general@attic.apache.org Cc: d...@whimsical.apache.org Subject: Re: Rethinking TLP creation/migration Sender: sa3r...@gmail.com As I am working my way through this code, it occurs to me that much of what I am finding could apply to termination of projects. For example, if the secretary adds the PMC to LDAP for 'Establish' resolutions at the end of the board meeting it might make equal sense for the secretary to remove the PMC (and committers) for 'Terminate' resolutions. Thoughts? My thoughts ; looking at the ASF bylaws ... -- the ASF has many PMCs -- each PMC has 0, 1 or more projects ; PMC Attic is like PMC Incubator ; both have many projects -- graduation : -- a new PMC is established ; -- the projects moves from PMC Incubator to the new PMC -- project retirement : -- the project moves to PMC Attic -- PMC retirement : -- the PMC's projects are retired (moved to PMC Attic) -- the PMC is terminated IMHO, PMCs and projects must be treated as distict entities ; where each project has a parent (PMC) pointer. The board (secretary) can -- create and terminate PMCs -- create projects and move projects between PMCs - Sam Ruby Regards, Henk Penning On Tue, May 17, 2016 at 6:51 PM, Sam Ruby <ru...@intertwingly.net> wrote: Statement of the problem (by Chris Lambertus): Our process for tlp creation is to run the script, figure out why half the steps failed, re-run it a few times until it works, then go do all the manual mailing list creations and jira and conflience etc. etc. General outline of the solution being explored (by Sam Ruby): The goal is to make it so that asf-secretary and pmc-chair people can do most of the work themselves. The first step will be to have me do the the tlp requests manually this month (I'm in both groups) with the infrastructure contractors (primarily @fluxo and @pono) providing guidance and adjusting the authorizations as required. As soon as it becomes possible for the secretary and pmc chairs to execute these tasks, focus will turn to automation and providing a web interface. Current code base: https://svn.apache.org/repos/infra/infrastructure/trunk/tlpreq Secretarial tasks will likely be merged into the board agenda tool, pmc chair tasks will like be merged into the roster tool. - Sam Ruby ---- _ Henk P. Penning, ICT-beta R Uithof HFG-406 _/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Budapestlaan 6, 3584CD Utrecht, NLF +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: Dropping the HEADER change
On Sat, 24 May 2014, Henri Yandell wrote:
Date: Sat, 24 May 2014 06:50:15 +0200
From: Henri Yandell bay...@apache.org
To: general@attic.apache.org
Subject: Dropping the HEADER change
Sender: hyand...@gmail.com
Currently the Attic process suggests modifying the
dist.apache.orgHEADER.html for a project. Then later, the directory is
deleted.
I'd like to flatten that and go straight to deleting the directory. I don't
think there is any value in maintaining the directory for a period of time
and it simplifies the process for moving something into the Attic.
Any -1s?
Hi Hen,
+1 ; but I hope you want to keep process[3].2 :
strip dist/project and add a .htaccess containing :
RedirectMatch permanent .* http://attic.apache.org/projects/${project}.html
that is, move process[3].2 to process[2].
I can take care of it ; are attic commit rights sufficient?
Re: process[3].1 delete the user list (unless still active) ;
I wonder if that can also move to process[2].
Hen
Groeten,
HPP
_
Henk P. Penning, ICT-beta R Uithof BBL-761 _/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Princetonplein 5, 3584CC Utrecht, NL F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: Proposed board report, May 2014
On Tue, 13 May 2014, Henri Yandell wrote: Date: Tue, 13 May 2014 07:42:56 +0200 From: Henri Yandell bay...@apache.org To: general@attic.apache.org Subject: Re: Proposed board report, May 2014 Sender: hyand...@gmail.com On Mon, May 12, 2014 at 11:10 AM, Henk P. Penning penn...@uu.nl wrote: Ok ; but please mark 'xml' (like 'esme' and 'ws-muse') as 'needs completing'. Can do. What's left with xml? There was nothing in JIRA for it. Hi Hen, A long time ago I fixed dist/xml : http://www.apache.org/dist/xml/ What;s missing is an attic page : http://attic.apache.org/projects/xml.html If/when that page is in place, http://www.apache.org/dist/xml/ should redirect to it. In the past, I could (as root) fix stuff in www.apache.org/dist, but since everything is now 'svnpubsub'ed, I can't anymore. I would gladly fix stuff in dist/ (dist/esme for instance) but I don't know how I can get the permission to do so. I think it would be nice that, if/when PMC XXX retires, project XXX moves immediately to PMC attic (a PMC can have more than one project), with all the proper changes of ownership, permissions etc. Along the lines of incubator. Ideas? Hen Regards, HPP _ Henk P. Penning, ICT-beta R Uithof BBL-761 _/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Princetonplein 5, 3584CC Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: Moving projects to the Attic
On Thu, 16 Jan 2014, sebb wrote:
Date: Thu, 16 Jan 2014 00:39:23 +0100
From: sebb seb...@gmail.com
To: Henk P. Penning penn...@uu.nl
Cc: general@attic.apache.org,
Apache Infrastructure infrastruct...@apache.org
Subject: Re: Moving projects to the Attic
On 15 January 2014 09:01, Henk P. Penning penn...@uu.nl wrote:
On Wed, 15 Jan 2014, Henri Yandell wrote:
Date: Wed, 15 Jan 2014 04:30:02 +0100
From: Henri Yandell he...@yandell.org
To: general@attic.apache.org
Cc: Apache Infrastructure infrastruct...@apache.org
Subject: Re: Moving projects to the Attic
Sender: hyand...@gmail.com
So updating with Sebb's response:
Hi,
Can be done by Attic:
- Create page on Attic site
- Inform users
- Delete from committee-info.txt (members)
- Remove from www.apache.org navigation
- Announce on announce at apache.org
Needs permissions from Infra for Attic:
Shouldn't the (svn) permissions for 'site' and 'dist' be
transfered from project committers to attic committers ?
to freeze the web-site and dist-area, and let 'attic' do
its thing?
If Infra are happy with the idea, then updating the authn files can be
done by the following groups:
[/infrastructure/trunk/subversion/authorization]
@member = rw
@pmc-chairs = rw
@svnadmins = rw
@board = rw
@exec-officers = rw
Which should be enough for Attic to assign themselves the necessary
karma for the site, as has already been done here:
[/websites/production/esme]
@attic-pmc = rw
@esme = rw
Not sure where the dist/release permissions are defined, so I don't
know if this can be done by Attic personnel
That file is generated by 'infra' with :
https://svn.apache.org/repos/infra/infrastructure/trunk/subversion/authorization/generate-dist-authorization
As you can see, at the moment, 'esme' is a special case :
@attic-pmc = rw is added to [/dev/esme], [/release/esme].
Also, for the record, infra wants to remove the dist/dev/esme
and dist/release/esme areas (six months after 'attic' day).
IHMO, it would be a lot simpler if 'project' esme could simply
move from (defunct) pmc-esme to pmc-attic ; A PMC can run more
than one project.
Regards,
HPP
for dist : [eg esme] https://dist.apache.org/repos/dist/release/esme
eg : svn ls -v https://dist.apache.org/repos/dist/release/esme
[ there may also be a https://dist.apache.org/repos/dist/dev/esme ]
for site : don't know how this would work for a CMS site.
- Update website with Attic notice
- Update HEADER.html in downloads
- Update the project DOAP file
- 6 months+: strip dist/project and add a .htaccess redirect
Needs to be done by Infra:
- Point SVN mails to general at attic
- Make SVN + JIRA/Bugzilla read-only
- Turn off automated builds
- Close down infrastructure resources
- 6 months+: Consider deleting the user list
With sites on the CMS, updating the website with an Attic notice is likely
to be a challenge. Typically I did a search and replace on every .html
page
and inserted a div at the top of the page. Any thoughts from anyone
CMS-knowledgable about whether it's best to try and do that in the CMS
somehow, or perhaps to have a more programmatic notion that marks a site
as
retired and inserts a header?
... or add to the site's style-sheet
body:before
{ content:This project retired ...;
background-color:yellow;
float : top ;
color:red;
font-weight:bold;
}
Hen
_
Henk P. Penning, ICT-beta R Uithof BBL-761 _/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Princetonplein 5, 3584CC Utrecht, NL F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
_
Henk P. Penning, ICT-beta R Uithof BBL-761 _/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Princetonplein 5, 3584CC Utrecht, NL F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: Board report for February
On Tue, 5 Feb 2013, Gianugo Rabellino wrote: Date: Tue, 5 Feb 2013 01:28:36 +0100 From: Gianugo Rabellino gian...@rabellino.it To: general@attic.apache.org general@attic.apache.org Subject: Board report for February Sender: gian...@outlook.com All, I was swamped and failed to post the January report on time, so we are in for a February deadline and I'd like to work well in advance. I'm planning to send a short report stating that we are on track (at least according to jira) and there are no projects in the pipeline/no mailing list traffic. I'm assuming someone is still listening here, and the reason why things are quiet is because, well, there is nothing to do. If however you have concerns that you would like to voice, I'm all ears. Thanks, -- Gianugo Hi, the XML project was retired last april : http://www.apache.org/foundation/records/minutes/2012/board_minutes_2012_04_18.txt I cleaned the dist/ area in september 2012 : http://www.apache.org/dist/xml/ 1. the XML project page has to be attic'ed and 2. a redirect setup in in dist/xml/.htaccess ; I can do 2) when 1) is done. Regards, Henk Penning _ Henk P. Penning, ICT-beta R Uithof WISK-412 _/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Budapestlaan 6, 3584CD Utrecht, NLF +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: cleanup dist
On Sat, 11 Aug 2012, Henri Yandell wrote: Date: Sat, 11 Aug 2012 04:31:49 +0200 From: Henri Yandell he...@yandell.org To: general@attic.apache.org Subject: Re: cleanup dist Sender: hyand...@gmail.com Suggested changes done. Hi, thanks Henri. -- I have stripped dist/harmony to a .htaccess pointing to http://attic.apache.org/projects/harmony.html -- same for 'jakarta' -- thanks for adding this to the attic 'process page'. Regards, HPP On Thu, Jul 5, 2012 at 12:38 PM, Henk P. Penning penn...@uu.nl wrote: On Thu, 28 Jun 2012 19:23:54 GMT, Henri Yandell bay...@apache.org wrote : Not that I know of. That would mean updating the websites to point to the archives and not the mirrors, and we're not in the business of editing the websites without strong cause. Hen Hi, The attic'ed projects can't be on the mirrors forever, imho. A cleanup after, say, 6 months seems reasonable. Cleanup was done for (for instance) 'beehive' like this : the 'dist/beehive/' directory is stripped, containing only a .htaccess file with : RedirectMatch permanent .* http://attic.apache.org/projects/beehive.html The same can be done for other projects. At the moment, candidates are : harmony and jakarta, since the were attic'ed at least half a year ago. Of course, these pages: http://attic.apache.org/projects/harmony.html http://attic.apache.org/projects/jakarta.html should contain a reference to relevant archive.apache.org page, as for instance the beehive attic page does. Please make it the rule to cleanup attic'ed projects after six months. I'll be happy to do the cleanup and set the proper .htaccess files. Please let me know. Regards, Henk Penning -- apache.org infrastructure On Fri, May 25, 2012 at 11:52 PM, Henk P. Penning penn...@uu.nl wrote: Hi, I remember having read that after six months, the dist/ tree of attic'ed projects is to be cleaned up ; that is, stripped to a .htaccess file. -- is this correct ? -- if so, can it be added to the 'process page' ? http://attic.apache.org/process.html Thanks, regards, Henk Penning -- apache.org infrastructure - _ Henk P. Penning, ICT-beta R Uithof WISK-412 _/ \_ Faculty of Science, Utrecht University T +31 30 253 4106 / \_/ \ Budapestlaan 6, 3584CD Utrecht, NL F +31 30 253 4553 \_/ \_/ http://people.cs.uu.nl/henkp/ M penn...@uu.nl \_/ - _ Henk P. Penning, ICT-beta R Uithof WISK-412 _/ \_ Faculty of Science, Utrecht University T +31 30 253 4106 / \_/ \ Budapestlaan 6, 3584CD Utrecht, NL F +31 30 253 4553 \_/ \_/ http://people.cs.uu.nl/henkp/ M penn...@uu.nl \_/ - _ Henk P. Penning, ICT-beta R Uithof WISK-412 _/ \_ Faculty of Science, Utrecht University T +31 30 253 4106 / \_/ \ Budapestlaan 6, 3584CD Utrecht, NL F +31 30 253 4553 \_/ \_/ http://people.cs.uu.nl/henkp/ M penn...@uu.nl \_/
