Hi Bill,
If most of the specs end-up in GitHub, do you think we could use this
migration to write the specifications in Asciidoc (or MarkDown) ? This way
we could use Pull-Requests when it comes to amending a specification ? ATM
we exchange PDFs and emails about what could be improved in the
specification. Using Asciidoc would ease this process.
WDYT ?
Antonio
On Tue, May 3, 2016 at 8:16 PM, Bill Shannon <bill.shannon_at_oracle.com>
wrote:
> We're in the process of planning this migration. Some subprojects are
> already mirrored at Github, which is most likely where these projects will
> end up. It's not clear that there's anything the community can do to help,
> but if you have ideas let us know. It will likely be several months before
> we work out all the details for the migration.
>
> arjan tijms wrote on 05/03/16 09:12:
>
> Hi,
>
> It was recently announced that java.net and kenai.com will shutdown on 28
> April, 2017. See
> https://community.oracle.com/community/java/javanet-forge-sunset
>
> I wonder if there's already a plan to migrate the various Java EE assets,
> specifically the RI itself (the GlassFish project), and the associated
> mailing lists, JIRA instance, project pages, etc.
>
> Would people from the community be able to help with this migration in any
> way?
>
> Kind regards,
> Arjan Tijms
>
>
>
--
Antonio Goncalves
Software architect, Java Champion and Pluralsight author
Web site <http://www.antoniogoncalves.org> | Twitter
<http://twitter.com/agoncal> | LinkedIn <http://www.linkedin.com/in/agoncal> |
Pluralsight
<http://pluralsight.com/training/Authors/Details/antonio-goncalves> | Paris
JUG <http://www.parisjug.org> | Devoxx France <http://www.devoxx.fr>