[Website] Standarise the way to publish releases

[Emily-Jiang]

@Emily-Jiang commented on Tue Aug 13 2019

Since spec html and pdf are not in maven central. In the past, the pdfs and htmls are attached to the releases. However, it is not convenient as they have to be downloaded for viewing.

In the recent release architecture changes, all of the docs and javadocs are uploaded to here. When releasing MicroProfile reactive messaging, I used the following format, which is much more user friendly.

I updated MicroProfile config to use this format. All other specs should adopt this format for improvement.

We also need to update microprofile.io to list all spec/pdf. I've filed this issue on microprofile-site repo.

---

@OndroMih commented on Tue Aug 13 2019

Ideally, the Jenkins release job would use GitHub API to generate the description for the release, including links to Javadocs and spec documents and info about the maven artifact.

[Emily-Jiang]

@rstjames can we meet up to discuss the layout?

[rstjames]

@Emily-Jiang When would you all like to meet?

[rstjames]

@Emily-Jiang Emily and I met,
She is looking for a page that would be on MP site that would list all specs with content bellow. (big spec overview)
Example: (content filler)

We will continue this conversation on the next marketing call and community call. Then we can get others thoughts on this topic and decide what the next steps could be.

[Emily-Jiang]

I am thinking to have two layers:
First layer contains all MP Spec, basically the building blocks(Config, Fault Tolerance, Rest Client, etc). On clicking each individual spec, it lists all versions with the links to javadocs, html, pdf.

[Emily-Jiang]

I will like to make some progress with this. @rstjames what is the next step?

[Emily-Jiang]

@rstjames what's the next stage?

[rstjames]

@Emily-Jiang that is a good question. I am not sure... I can not give away resources (if we have any to spare) without discussing things with @aeiras . This may take a couple weeks because of holidays.

[aeiras]

Hey you two @Emily-Jiang and @rstjames ,

I recommend a deep discussion on next MP Marketing hangout to see exactly what it will take to proceed on this task. Without knowing specifics, we cannot provide Ryan's time to work on a blind task.

Recommendation is always to write up the plan via drive website document, take on priorities and drop anything shiny or "not vital". Once that document is ready, bring it to the Community call for consumption and that will trigger action.

Cheers,

[aeiras]

I added Cesar and myself to this ticket :) for reference!

[aeiras]

new ticket takes into account this feedback with reference to 3.3 written retrospective! #251

The project page under the website needs to be 100% automatic and link to all the active repos.
https://microprofile.io/projects/

Can someone in this ticket find out whats needed? :)

[aeiras]

@rstjames,

Can you please make a call to action bottom on the Project's page that brings the viwer to the MP main Repo: https://github.com/eclipse?utf8=✓&q=microprofile

Thanks

[rstjames]

@aeiras button added to the https://microprofile.io/projects/.

[aeiras]

thanks Ryan. Small improvement for the time being.

[aeiras]

We tackled this today during Mktg hangout. Tackled with new ticket.
The mktg side has its wiki & the technical side is being updated to know how to communicate with branding! #277

[Emily-Jiang]

@rstjames can you create a draft for this web page? Please let me know what info you need from me. Can we set up a deadline? How long do you think this will take @rstjames ?

[aeiras]

Hey @Emily-Jiang,

We have made improvements on this area. Do you believe we still need this ticket or can we close it and iterate via new issues to tackle improvements on the work done?

[aeiras]

@Emily-Jiang,

Now that your formally took a part of the pushing on release MP. 4.0 which includes marketing templates, do we still need this ticket or can we focus the work on a new ticket and go by layers?

I recommend we choose layers and allow for smaller releases to become the norm as well.

[aeiras]

Emily,

we have evolved this and the latest work deals with this ticket under the MPWG.
I will close it.