Very well, let me focus on some initial prerequisites needed to make an rpm package for the server:
1) licensing; any bit distributed within the package must be under one of the licenses listed here, in section "Good Licenses"
2) building from sources; any fedora package must be built from sources within the fedora build system.
sources can be downloaded in a release archive from the canonical project website, or from a vcs tag.
we both support ant and maven so i see no problem here.
3) no re-distributed libraries. Any package must NOT distribute libraries; if a required library
is already available in fedora, that must be used; if not, a separate package must be assembled
4) running on openjdk; requiring specific sun/oracle jdk is very rare nowadays, so i think
i can take care of this.
5) system-wise install; packages should use common unix filesystem directories
for configuration, run state, logging etc. This can actually be done in the fedora build,
not in multiverse, if there turns out to be no incompatibilities. the start scripts must be
converted to systemd script to be coherent with other system services.
After these requirements are met, I can start building the package, and submit it to
other contributors for being peer-reviewed. Two interest groups could be interested
in this package, namely the java group and the games group (even if actually we cannot
ship the client or any of the tools as they are windows only atm).
After peer-review, the package is included in rawhide which is fedora devel repository,
and immediately available to developers. Every six months rawhide is branched to a
release candidate: Fedora 17 is coming out soon, so I think we could reasonably target
Fedora 18 which will ship around november.