Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-community] Refining the Mailing Lists Page

GOOD (or at least better)
 - mvc-dev : Jakarta MVC. Standardizes the action-based model-view-controller pattern
 - faces-dev: Jakarta Faces. MVC framework for building user interfaces for web apps

Good catch, I think this will need to be reviewed to many of the current issues [1]

When I saw the +40 issues related to the mailing list refining page [1], I initially +1 on the proposal of having one PR for all the changes, but after seeing the interaction that just the change to mail-dev required [2], I now think we can divide, conquer and take this also as an opportunity to embrace more contributions from the community. 

I'm happy to take one of the open issues and perform a short demo on how to tackle it, test locally the website and open the PR with the ECA validation for the upcoming Friends of Jakarta Call  [3]




On Tue, Nov 17, 2020 at 2:47 PM David Blevins <dblevins@xxxxxxxxxxxxx> wrote:
I've changed the subject to reflect the topic.

A couple quick notes that might help here:

 - Each spec has a `summary_sixty_char` description.  See for example: https://raw.githubusercontent.com/jakartaee/specifications/master/messaging/_index.md
 - These summaries intentionally do not contain the project name as it is already visible where this data is used: https://jakarta.ee/specifications/

If we want to use these descriptions on the mailing list page, that's great.  On that page however we need to make sure we're also using the project name.  For example:

BAD
 - mvc-dev : Standardizes the action-based model-view-controller pattern
 - faces-dev: MVC framework for building user interfaces for web apps

GOOD (or at least better)
 - mvc-dev : Jakarta MVC. Standardizes the action-based model-view-controller pattern
 - faces-dev: Jakarta Faces. MVC framework for building user interfaces for web apps

Also if we don't like some of the descriptions we should make sure to update the `summary_sixty_char` description of the appropriate spec.

If someone has some energy, we could probably put the mailing list links in the `_index.md` file as headers and generate the mailing-list page.


--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com

> On Nov 17, 2020, at 11:01 AM, Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> Chris has commented on Issue 993.
>
> TL;DR: create one pull request with the changes that you'd like to see.
>
> I don't understand the value of having an issue for every single line on the page, but if that helps you create that one pull request, then great.
>
> Wayne
>
> On Mon, Nov 16, 2020 at 10:05 PM Amelia Eiras <aeiras@xxxxxxxxxxxxx> wrote:
> Hola Wayne,
>
> Thank you in advance for your feedback. I am pulling into this thread because I wonder who gets to adjust the Jakarta EE mailing lists?
> The community does the review, but who is in charge of executing the changes? Thank you!
>
> Jakartees,
>
> Topic 3 CLEAN-UP:  Jakarta EE Mailing lists inventory & recommended improvements.
> There are 4 sections to each mailing list:
>       • Mailing list name and number of subscribers
>       • About the forum (description)
>       • Usage: email and archives
>       • Subscribe
> As listed below, in the Jakarta EE Connect > Jakarta EE Mailings, issues are as follows:
>       • no description consistency.  The description ought to start always with a VERB when call to action is the point.
>       • Too many abbreviations. The assumption that everyone knows the technology is poor at best. We must step up and be kinder to newcomers.
>       • The mentioning of EE4J is the forum description not necessary. EE4J is the parent technology, the umbrella. Jakarta EE is a member of the technology under EE4J.  We must be clear on the difference, and that starts with the mailing lists. 
>       •  the alphabetization of the mailing lists could be amazing 
> <image.png>
>
> I have submitted issues in the order the emails are presented in the mailing list.
> The https://jakarta.ee/specifications/ page was helpful with focused descriptions.  Yet that landing page still needs to be alphabetized for better user-navigation.  Kevin already submitted a nice issue on that! :)
>
> PLEASE Find your favorite forums below and help review as you see fits.
> Let's think about those who know nothing about Java EE or Jakarta EE but who might arrive at the Jakarta EE website... with curiosity.  Let capture his/her attention to this open-source ecosystem by showing that we don't take their lack of knowledge as a show stopper.  💪💙
>       • [Jakarta EE Mailing List Inventory Adjustments] Jakarta Bean Validation
>       • [Jakarta EE Mailing List Inventory Adjustments] Jakarta Annotations
>       • [Jakarta EE Mailing List Inventory Adjustments] Jakarta Contexts and Dependency Injection
>       • [Jakarta EE Mailing List Inventory Adjustments] Jakarta Concurrency #956
>       • [Jakarta EE Mailing List Inventory Adjustments] EE4J build (REMOVE) #957
>       • [Jakarta EE Mailing List Inventory Adjustments] EE4J Parent project (REMOVE) #958
>       • [Jakarta EE Mailing List Inventory Adjustments] EE4J PMC (REMOVE) #959
>       • [Jakarta EE Mailing List Inventory Adjustments]Jakarta Enterprise Beans #960
>       • [Jakarta EE Mailing List Inventory Adjustments] Jakarta _expression_ Language #961
>       • [Jakarta EE Mailing List Inventory Adjustments] Jakarta Enterprise Security #962
>       • [Jakarta EE Mailing List Inventory Adjustments] Jakarta Server Faces #963
>       • [Jakarta EE Mailing List Inventory Adjustments] Jakarta Interceptors #964
>       • [Jakarta EE Mailing List Inventory Adjustments] Jakarta Authorization #965
>       • [Jakarta EE Mailing List Inventory Adjustments] Jakarta Activation #966
>       • [Jakarta EE Mailing List Inventory Adjustments] Jakarta Community #967
>       • [Jakarta EE Mailing List Inventory Adjustments] Jakarta EE Specification #968
>       • [Jakarta EE Mailing List Inventory Adjustments] Jakarta Working Group #969
>       • [Jakarta EE Mailing List Inventory Adjustments] Jakarta Batch #970
>       • [Jakarta EE Mailing List Inventory Adjustments] Jakarta Examples- (RETIRE) #971
>       • [Jakarta EE Mailing List Inventory Adjustments] Jakarta EE Platform #972
>       • [Jakarta EE Mailing List Inventory Adjustments] Jakarta EE Specification Leads #973
>       • [Jakarta EE Mailing List Inventory Adjustments] Stable Jakarta EE APIs (Deprecate) #974
>       • [Jakarta EE Mailing List Inventory Adjustments] Technology Compatibility Kit (TCK) #975
>       • [Jakarta EE Mailing List Inventory Adjustments] Jakarta Authentication #976
>       • [Jakarta EE Mailing List Inventory Adjustments]Mailing list: javamail-dev (40 subscribers) #977
>       • [Jakarta EE Mailing List Inventory Adjustments] Jakarta JSON Binding #978
>       • [Jakarta EE Mailing List Inventory Adjustments] Jakarta RESTful Web Services #979
>       • [Jakarta EE Mailing List Inventory Adjustments] Jakarta XML Web Services #980
>       • [Jakarta EE Mailing List Inventory Adjustments] Jakarta Connectors #981
>       • [Jakarta EE Mailing List Inventory Adjustments] Jakarta Messaging #982
>       • [Jakarta EE Mailing List Inventory Adjustments] Jakarta Persistence #983
>       • [Jakarta EE Mailing List Inventory Adjustments] Jakarta JSON Binding #984
>       • [Jakarta EE Mailing List Inventory Adjustments] Jakarta JASON Processing #985
>       • [Jakarta EE Mailing List Inventory Adjustments] Jakarta Server Pages #986
>       • [Jakarta EE Mailing List Inventory Adjustments] Jakarta Standard Tag Library #987
>       • [Jakarta EE Mailing List Inventory Adjustments] Jakarta Transactions #988
>       • [Jakarta EE Mailing List Inventory Adjustments] jts-dev@xxxxxxxxxxx (remove) #989
>       • [Jakarta EE Mailing List Inventory Adjustments] Jakarta MVC #990
>       • [Jakarta EE Mailing List Inventory Adjustments] Jakarta NoSQL #991
>       • [Jakarta EE Mailing List Inventory Adjustments] Jakarta Servlet #992
>       • [Jakarta EE Mailing List Inventory Adjustments] Jakarta WebSocket #993
>
>
>
>
> Amelia Eiras
> twitter.com/ameliaeiras
> Tribe: http://tomitribe.com      https://tribestream.io   
> OSS:  http://microprofile.io     https://jakarta.ee
>
>
> On Fri, Nov 13, 2020 at 12:55 PM Amelia Eiras <aeiras@xxxxxxxxxxxxx> wrote:
> Jakartees,
>
> Much work is being done on the creation of the Jakarta EE 9 Release landing page. The technical work on the Jakarta EE 9 release was completed on Nov. 6th, yeayy!
>       • Jakarta 9 release page #920 #929   
>       • Results: https://deploy-preview-923--jakartaee.netlify.app/release/9/ [ current Page]
> The facts listed on the page relevant to the release are currently incorrect and need our attention.
>
> <image.png>
>
> Topic 1: Jakarta EE Repo - WIP
>
> Last June 2019, the Jakarta EE working group discussed and voted to import the Jakarta EE Repo all the Specs relevant to Jakarta EE from the EE4J repository.
>
> What does it take to get the task completed?
> Can we prioritize it as a crucial item for the Jakarta EE 9.1 release?
> Can we double check the 60 Repo's mentioned above and make sure to not include stuff from the EE4J parent umbrella?

>       • https://github.com/jakartaee
> Topic 2: Jakarta EE projects
> Currently counted 31; however, the 9 release contains 35 specifications.
> Do we also include the 10 repos already allocated in the Jakarta EE repo? If yes, then the number increases to 45. 
>       • excel: Jakarta EE 9 Spec Mentor Assignments & Ballot Progress  36 Specifications
> Topic 3: Jakarta EE Mailing lists and its link to EE4J
>       • Jakarta EE Mailing Lists that helped create this landing page: https://jakarta.ee/connect/mailing-lists/ currently contains 40 forums. Naming adjustments are needed.  How do we submit such feedback?
>       • Does a git issue work? Or PRs? How can we help adjust what currently is?
>       • The removal of many EE4J mailing lists from the Jakarta EE mailing lists matters.
>       • EE4J must become its own independent umbrella parent with its own website, etc., to scale and welcome other projects to join the space.   
>       • The repo specifications migrations need to help with a naming convention and update on the mailing lists.
> Topic 3: What items should be a part of the Release 9 page?
>       • https://jakarta.ee/specifications/ lists 41 Specs, yet the release has 35.
> Should the Jakarta EE 9 release page focus solely on the release's work? Or should summarize the entire project?
>
> The current PR we are about to merge about highlighting the Contributors via Contributors Cards focuses only on the contributors' activity from work completed from Oct 1st, 2019 to Dec 8th, 2020. 
>
> As such, I recommend, the 9 page focus only on the release work. Ideally, each release will have its own landing page. To iterate such a focus is recommended to be applied to future releases. 
>
> Happy wknd everyone,
>
> Amelia Eiras
> twitter.com/ameliaeiras
> Tribe: http://tomitribe.com      https://tribestream.io   
> OSS:  http://microprofile.io     https://jakarta.ee
>
>
> --
> Wayne Beaton
> Director of Open Source Projects | Eclipse Foundation, Inc.
> Join us at our virtual event: EclipseCon 2020 - October 20-22
> _______________________________________________
> jakarta.ee-community mailing list
> jakarta.ee-community@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-community

_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-community

Back to the top