Unused OpenOffice source tree in incubator: keep or remove?
OpenOffice has had its own TLP source tree http://svn.apache.org/viewvc/openoffice/ since the end of 2012, and the old source tree http://svn.apache.org/viewvc/incubator/ooo/ is still reachable, read-only. Is this the recommended configuration or shall we "svn remove" the whole old tree, maybe leaving only a README.txt pointing to the new location? Apparently there are many outdated web pages around still pointing to the old tree, and this confuses newcomers. Of course, until the stable version is at 3.4.1 (which was released from the incubator and still contains references to the incubator) we wouldn't make the change. But I'd like to know how to behave when we release 4.0. Thanks, Andrea. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Need some help for releasing S4 0.6.0
The hashes contain additional text: "MD5 (apache-s4-0.6.0-incubating-src.zip) =" for the MD5 and "apache-s4-0.6.0-incubating-src.zip" for the SHA1. Making it harder to just diff the hash for the artifacts. Looks like not a blocker for release but I believe typically the hashes do not contain this additional meta text. - Henry On Mon, May 13, 2013 at 9:04 AM, Matthieu Morel wrote: > Hi all, > > we currently have the following +1 votes: > > 1 IPMC / PPMC vote (phunt) > 2 PPMC votes (kishoreg, mmorel) > 1 non binding committer vote (dferro) > > > So we haven't reached the quorum yet. > > > Can we get some help (votes) to finalize this release? (The vote thread > has the following subject: "[VOTE] S4 0.6.0 Incubating Release Candidate 5") > > > > Thanks! > > Matthieu > > > > > > On Mon, May 6, 2013 at 5:37 AM, Matthieu Morel > wrote: > >> Hello, > >> > >> this is the *fifth* release candidate for Apache S4, version 0.6.0 > >> > >> We fixed 2 blocking issues wrt RC1, related to s4 tools, 1 blocking > issue in RC2, related to metrics logging configuration, issues related to > the package contents and license headers in RC3, and removed included > javadoc files in RC4. > >> > >> > >> > >> This release fixes the following issues: > >> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312322&version=12321702 > >> > >> > >> *** Please download, test and vote by Thursday, May 9th 2013, 13:00:00 > GMT *** > >> > >> > >> Note that we are voting upon the source (tag). > >> > >> > >> Source package in zip format: > >> > >> > http://people.apache.org/~mmorel/s4-0.6.0-incubating-release-candidate-5/ > >> > >> > >> > >> The (git) tag to be voted upon: 0.6.0-RC5: > >> > >> > https://git-wip-us.apache.org/repos/asf?p=incubator-s4.git;a=tree;h=8b43b317104cfc9ebc42f6e8ec9c9557867155aa;hb=2f474503e2da111601bb92ca7186c136ba28e5b0 > >> > >> > >> > >> S4 KEYS file containing PGP keys we use to sign the release: > >> > >> http://svn.apache.org/repos/asf/incubator/s4/dist/KEYS > >> > >> > >> The README.md file contains instructions for installing the gradle > wrapper (which is not shipped with the source release). > >> > >> > >> We include a RAT check task. (Can be used by fetching rat from /lib dir > in the git repo and using the .rat-excludes file at the root of the git > repo) > >> > >> It can be run with : > >> gradlew rat > output > >> > >> > >> Please cast your vote, thanks! > >> > >> > >> [ ] +1 approve > >> [ ] +0 no opinion > >> [ ] -1 disapprove (and reason why) > >> > >> > >> > >> NOTES: > >> > >> - All releases by podlings must be approved by the Incubator PMC. The > conventional process is for the podling to follow the usual Apache process > and then call for a Incubator PMC VOTE on the general incubator list. > >> For RC5 however, following recommendations from our mentors, we are > proceeding to a parallel vote on both general@incubator and s4-dev > >> > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
[Proposal] HotdoG for the Apache Incubator
Dear ASF members, We would like to propose HotdoG for the incubator. Paul Ramirez (me) will be the Champion for this project. The proposal draft is available at: https://wiki.apache.org/incubator/HotdoGProposal Looking forward to integration your suggestions and feedback. = HotdoG Proposal = == Abstract == The HotdoG project is an effort and suite of tools to convert HDF/HDF-EOS format into GeoTIFF format. This is the first of a potential series of incoming projects originating from The HDF Group -- the non-profit organization is interested in evaluating the ASF as a potential home for many of its projects. The HDF Group is an independently funded organization that started many years ago with major investment from NASA as the Hierarchical Data Format (HDF), version 4 and now version 5, is the ''de facto'' remote sensing data format for NASA missions, and an increasing number of other disciplines including bio medicine, radio astronomy, climate science, and other domains. HDF is both a data and metadata format, as well as a model for representing and access information. There are numerous downstream tools that can read and write HDF data, including a growing number of Geospatial data tools (ESRI-based, and also OpenGeo and other community led efforts). In addition, major interoperability efforts are also occurring between the remote sensing community and the climate modeling community (which has traditionally favored NetCDF as opposed to HDF) because of the efforts in HDF5 to leverage a common data format and model. HotdoG is poised to be a first of its kind in the form of bringing one of the major 2 data formats for science to the ASF (the other being the NetCDF format). == Proposal == HotdoG is a software converter that converts Earth Science data in HDF/HDF-EOS format into GeoTIFF format. Doing so easily enables users of remote sensing data to interoperate with common GIS tools (like WebGIS, Web Processing, image analysis, and geo computational tools). We feel that the project is an incremental step, and an appropriate focus with tangible success possibilities by restraining our focus to HDF/HDF-EOS to GeoTIFF conversion. There are numerous interesting paths that we can take the toolkit in -- as conversion from remotely sensed data to GeoTIFF involves ensuring that the HDF-EOS metadata elements can be appropriately represented using GeoTIFF headers, and the associated format. Furthermore, capturing the HDF's appropriate geo datum in GeoTIFF will be another important challenge. == Background == GeoTIFF is a data and metadata standard for Earth science applications. It is based on binary Tagged Image File Format (TIFF). A GeoTIFF file has geographic (or cartographic) data embedded as tags within the TIFF file that are used to geo-locate the image. This is required for correct integration of the image in Geographic Information Systems (GIS) and other popular tools like Google Earth Pro. In the recent years, GeoTIFF has gained popularity as a visualization format among NASA HDF Earth science user communities according to the NASA data user's survey. However, the conversion from HDF to GeoTIFF is not straightforward for end users because NASA HDF data products are diverse and organized in many different ways. For example, go to http://hdfeos.org/zoo and you'll see many scripting language examples because no single script can correctly visualize all NASA HDF data. == Rationale == The HEG tool is limited to some NASA HDF-EOS2 products (no support for HDF-EOS5 products) and it is not an open-source tool. The latest GDAL (version 1.9.2 and above) is an open-source tool but it cannot handle many non-HDF-EOS NASA HDF products such as TRMM (pure HDF4) and Aquarius (pure HDF5) correctly and automatically. == Initial Goals == We'll improve GDAL to support NASA HDF products better by handling geo-location information and physical meaning of data correctly and automatically. We'll handle NASA products intelligently so novice users don't have to supply many options or figure out the details about the data products. For advanced users, we'll give a full control of accessing HDF products in many different ways so that the converted GeoTIFF file is scientifically valid and meaningful. We aim to provide command line tools first and evolve them into a GUI tool. == Current Status == We're looking for developers and sponsors. === Meritocracy === We will discuss the milestone and the future plan in an open forum. We plan to encourage an environment that supports a meritocracy. The contributors will have different privileges according to their contributions. === Community === GIS and Earth Science === Core developers === * H. Joe Lee * Denis Nadeau * Pedro Vicente === Alignment === HotdoG employs H4CF Conversion Toolkit for reading data and GDAL for writing GeoTIFF. In addition, we plan to integrate HotdoG with other products from new missions su
RE: [VOTE] S4 0.6.0 Incubating Release Candidate 5
+1. Given that we had enough PPMC votes, I took my time to evaluate the release candidate a bit more carefully. There is a small bug in the scripts that affects paths with spaces. It is not a blocker, though. I also went over the documentation and realized that the discussion about adapters is far from ideal. In fact, there are a number of questions on the list about it and I think we would be able to make it easier for new developers to start working with S4 if we had a better discussion about that. I'm happy to contribute my findings for the next release. Could some IPMC member please vote on this release candidate? There is one vote missing. -Flavio -Original Message- From: Patrick Hunt [mailto:ph...@apache.org] Sent: 10 May 2013 17:23 To: general@incubator.apache.org Cc: s4-...@incubator.apache.org Subject: Re: [VOTE] S4 0.6.0 Incubating Release Candidate 5 +1 (binding) sig/xsum verify. rat runs clean. I've run through the release checklist and everything seems fine to me. Patrick On Mon, May 6, 2013 at 5:37 AM, Matthieu Morel wrote: > Hello, > > this is the *fifth* release candidate for Apache S4, version 0.6.0 > > We fixed 2 blocking issues wrt RC1, related to s4 tools, 1 blocking issue in RC2, related to metrics logging configuration, issues related to the package contents and license headers in RC3, and removed included javadoc files in RC4. > > > > This release fixes the following issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312322&ve rsion=12321702 > > > *** Please download, test and vote by Thursday, May 9th 2013, 13:00:00 GMT *** > > > Note that we are voting upon the source (tag). > > > Source package in zip format: > > http://people.apache.org/~mmorel/s4-0.6.0-incubating-release-candidate-5/ > > > > The (git) tag to be voted upon: 0.6.0-RC5: > > https://git-wip-us.apache.org/repos/asf?p=incubator-s4.git;a=tree;h=8b43b317 104cfc9ebc42f6e8ec9c9557867155aa;hb=2f474503e2da111601bb92ca7186c136ba28e5b0 > > > > S4 KEYS file containing PGP keys we use to sign the release: > > http://svn.apache.org/repos/asf/incubator/s4/dist/KEYS > > > The README.md file contains instructions for installing the gradle wrapper (which is not shipped with the source release). > > > We include a RAT check task. (Can be used by fetching rat from /lib dir in the git repo and using the .rat-excludes file at the root of the git repo) > > It can be run with : > gradlew rat > output > > > Please cast your vote, thanks! > > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > > > NOTES: > > - All releases by podlings must be approved by the Incubator PMC. The conventional process is for the podling to follow the usual Apache process and then call for a Incubator PMC VOTE on the general incubator list. > For RC5 however, following recommendations from our mentors, we are proceeding to a parallel vote on both general@incubator and s4-dev > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
