AW: archiving EasyAnt
Retire: Issue Tracker - If the subproject/component has its own issue tracker we have to close that. It is enough to make it read-only, so these information are longer available. --> open; use Jira EASYANT --> asked infra per https://issues.apache.org/jira/browse/INFRA-13225 --> done Retire: Free Further Resources -- Maybe a subproject locks further resources (update-site, ...). So we have to unblock them. --> open: There is a domain "easyant.org": www.easyant.org: redirects to ea@ant homepage blogs.easyant.org: blog system (last entry 2013) repo.easyant.org: an Artifactory instance Who owns that domain? Registrant Name: Jean-Louis Boudart --> done: This resource is not under Apache control. Jean-Louis has valid reasons to keep them alive. So retiring EasyAnt is complete. Jan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
AW: archiving EasyAnt
> Even if i understand the purpose of archiving project without too much > activity i don't get the point of shutting down home page and all > related stuff (including old blog or even the domain name). > > For good or bad reason easyant build still rely on repo.easyant.org > (see https://github.com/apache/ant-easyant- > core/blob/master/ivysettings.xml and related discussion > http://ant.1045680.n5.nabble.com/Evaluating-Bintray-as-a-distribution- > platform-for-easyant-plugins-td5714096.html). > Note that with the sources on apache side we should still be able to > rebuild everything. > > I always thought apache projects needs to be "buildable" during long > (that's why we have dist.apache.org and archive.apache.org) available, > but what is the point of having them available if we even don"t have > the available ressources to use it like the website/doc and so on ?? I > mean all this contribute to the history of the project and turning off > all those components/resource will clearly definitively kill the > project. > > I may be nostalgic on that topic but do we really want to do that ? > > If you all believe we should stop thoses resources/components down, > then fine i'll turn off everything, otherwise i will try to keep them > up (domain included) as much as i can. > > WDYT ? I wasn't aware that the *.easyant.org resources were required for building EA. Being able to build even an archived project is valuable as you said - even if _I_ think, that we don't get new committers ... But when these resources are required for building EA, why aren't they hosted on Apache infrastructure? ATM we rely on external resources... Jan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
AW: archiving EasyAnt
Current status: Jan Retire: Version Control --- Most of our source code is in git, only "site" and "sandbox" use subversion. --> only git for sources. Homepage in svn. --> update EA-homepage --> Should we only place a note on the hp or completely remove them. I prefer removing the complete homepage. --> done https://git-wip-us.apache.org/repos/asf ant-easyant-buildtypes.gitApache EasyAnt build types ant-easyant-core.gitApache EasyAnt core ant-easyant-easyant4e.git Apache EasyAnt for Eclipse ant-easyant-plugins.git Apache EasyAnt plugins ant-easyant-skeletons.git Apache EasyAnt skeletons ant-easyant-tasks.git Apache EasyAnt tasks Ask infra to make the repository read-only. --> asked infra per https://issues.apache.org/jira/browse/INFRA-13230 --> done Retire: Issue Tracker - If the subproject/component has its own issue tracker we have to close that. It is enough to make it read-only, so these information are longer available. --> open; use Jira EASYANT --> asked infra per https://issues.apache.org/jira/browse/INFRA-13225 Retire: Announcement We have to announce the retirement of the subproject at dev@ant, announce@apache and the Ant main page. text proposal: " The Ant PMC voted [1] to archive the EasyAnt subproject and all its modules. This means that all its resources are removed or made read only and no further development will be done. It also means that, if a community grows, the subproject could reactivated [2]. [1] http://mail-archives.apache.org/mod_mbox/ant-dev/201612.mbox/ajax/%3C000301d25510%2433d37720%249b7a6560%24%40de%3E [2] http://ant.apache.org/processes.html#Reactivate%20a%20subproject%20or%20component " --> done --> open: announcement on a...@apache.org (requires sending from Apache account) Retire: Releases The last released artifacts, if any, should be removed from the Apache distribution server. To do so, remove any artifact related to the retired subproject in https://dist.apache.org/repos/dist/release/ant/ (it is managed with subversion: https://dist.apache.org/repos/dist/release/incubator/easyant/). --> open, doesnt have write privilege. --> could someone else remove that directory? Retire: Free Further Resources -- Maybe a subproject locks further resources (update-site, ...). So we have to unblock them. --> open: There is a domain "easyant.org": www.easyant.org: redirects to ea@ant homepage blogs.easyant.org: blog system (last entry 2013) repo.easyant.org: an Artifactory instance Who owns that domain? Registrant Name: Jean-Louis Boudart Jean-Louis: could you remove the services and the domain? - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
AW: archiving EasyAnt
Back from holiday I want to do more about archiving EasyAnt. My todo-list now is... there are some questions open I couldnt answer ... Jan Retire: Version Control --- Most of our source code is in git, only "site" and "sandbox" use subversion. --> only git for sources. Homepage in svn. --> update EA-homepage --> Should we only place a note on the hp or completely remove them. I prefer removing the complete homepage. Ask infra to make the repository read-only. --> open (after updating the homepage) Retire: Issue Tracker - If the subproject/component has its own issue tracker we have to close that. It is enough to make it read-only, so these information are longer available. --> open; use Jira EASYANT --> asked infra per https://issues.apache.org/jira/browse/INFRA-13225 Retire: Announcement We have to announce the retirement of the subproject at dev@ant, announce@apache and the Ant main page. --> open text proposal: " The Ant PMC voted [1] to archive the EasyAnt subproject and all its modules. This means that all its resources are removed or made read only and no further development will be done. It also means that, if a community grows, the subproject could reactivated. [1] http://mail-archives.apache.org/mod_mbox/ant-dev/201612.mbox/ajax/%3C000301d25510%2433d37720%249b7a6560%24%40de%3E " Retire: Releases The last released artifacts, if any, should be removed from the Apache distribution server. To do so, remove any artifact related to the retired subproject in https://dist.apache.org/repos/dist/release/ant/ (it is managed with subversion). --> open, where is the repo? Retire: Free Further Resources -- Maybe a subproject locks further resources (update-site, ...). So we have to unblock them. --> open: There is a domain "easyant.org": www.easyant.org: redirects to ea@ant homepage blogs.easyant.org: blog system (last entry 2013) repo.easyant.org: an Artifactory instance Who owns that domain? What to do with these services? (shutdown ;) - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
