Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] Jakarta EE platform web site

Because it is always a good thing that a web site of a project indicates the latest status of the project's outcome. Otherwise there would be a risk that the web site is outdated or distinct from the actual outcome of the project. People come to a web site to learn about the project's outcome, and what they don't like is outdated content.

 

Von: jakartaee-platform-dev-bounces@xxxxxxxxxxx [mailto:jakartaee-platform-dev-bounces@xxxxxxxxxxx] Im Auftrag von Guillermo González de Agüero
Gesendet: Sonntag, 23. Juni 2019 10:22
An: jakartaee-platform developer discussions
Betreff: Re: [jakartaee-platform-dev] Jakarta EE platform web site

 

Why do we need to keep it in sync? The website content would be only on gh-branches.

 

El dom., 23 jun. 2019 9:35, Markus KARG <markus@xxxxxxxxxxxxxxx> escribió:

So manually keeping two distinct branches in sync is in any way better? That's simply a misuse of git branches.

 

Von: jakartaee-platform-dev-bounces@xxxxxxxxxxx [mailto:jakartaee-platform-dev-bounces@xxxxxxxxxxx] Im Auftrag von Guillermo González de Agüero
Gesendet: Samstag, 22. Juni 2019 19:35
An: jakartaee-platform developer discussions
Betreff: Re: [jakartaee-platform-dev] Jakarta EE platform web site

 

I know, but the master branch is already in use, so using the root for the website means moving the already existing content to another place.

 

El sáb., 22 jun. 2019 19:12, Markus KARG <markus@xxxxxxxxxxxxxxx> escribió:

Wrong. Read that page again. You can publish from master OR master/docs.

-Markus

 

 

Von: jakartaee-platform-dev-bounces@xxxxxxxxxxx [mailto:jakartaee-platform-dev-bounces@xxxxxxxxxxx] Im Auftrag von Guillermo González de Agüero
Gesendet: Samstag, 22. Juni 2019 17:58
An: jakartaee-platform developer discussions
Betreff: Re: [jakartaee-platform-dev] Jakarta EE platform web site

 

But it forces you to put content under a "docs" folder which I don't think makes much sense on this specific repo.

 

El sáb., 22 jun. 2019 17:44, Markus KARG <markus@xxxxxxxxxxxxxxx> escribió:

That very same page cleary mentions "master" as the very first option also…: "You can configure GitHub Pages to publish your site's source files from master".

 

Von: jakartaee-platform-dev-bounces@xxxxxxxxxxx [mailto:jakartaee-platform-dev-bounces@xxxxxxxxxxx] Im Auftrag von Guillermo González de Agüero
Gesendet: Samstag, 22. Juni 2019 16:30
An: jakartaee-platform developer discussions
Betreff: Re: [jakartaee-platform-dev] Jakarta EE platform web site

 

 

On Sat, Jun 22, 2019 at 3:29 PM Markus KARG <markus@xxxxxxxxxxxxxxx> wrote:

Is that branch some Github best practice?

 

Von: jakartaee-platform-dev-bounces@xxxxxxxxxxx [mailto:jakartaee-platform-dev-bounces@xxxxxxxxxxx] Im Auftrag von Guillermo González de Agüero
Gesendet: Samstag, 22. Juni 2019 12:20
An: jakartaee-platform developer discussions
Betreff: Re: [jakartaee-platform-dev] Jakarta EE platform web site

 

I think he just means to put the content on the branch GH will lookup for website content. Putting it on master won't make it available at https://eclipse-ee4j,github.io/jakartaee-platform

 

On Sat, Jun 22, 2019 at 10:19 AM Markus KARG <markus@xxxxxxxxxxxxxxx> wrote:

Why including the content in a separate branch? Wouldn't it make sense to
simply have it in a separate folder of the same branch, so the content of
both stays in sync always?
-Markus

-----Ursprüngliche Nachricht-----
Von: jakartaee-platform-dev-bounces@xxxxxxxxxxx
[mailto:jakartaee-platform-dev-bounces@xxxxxxxxxxx] Im Auftrag von Bill
Shannon
Gesendet: Freitag, 21. Juni 2019 23:16
An: jakartaee-platform developer discussions
Betreff: [jakartaee-platform-dev] Jakarta EE platform web site

Once we have an official Jakarta EE platform specification project,
I propose to contribute the existing content from the Java EE platform
web site [1] to the gh-pages branch of the Jakarta EE platform
repository [2].  I will make only minimal changes to the content
and wait for Pull Requests to update the content for Jakarta EE.
Clearly many parts of the web site will need to be rewritten.
I won't include the platform javadocs until we have draft javadocs
for Jakarta EE 8.

Any objections?


[1] https://javaee.github.io/javaee-spec/
[2] https://github.com/eclipse-ee4j/jakartaee-platform
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev

_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev

_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev

_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev

_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev

_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev

Back to the top