Re: [jakarta.ee-community] [jakarta.ee-spec] Alignment with Code of Cond

["Kevin Sutter" <sutter@xxxxxxxxxx>]

Theodor,
I'm curious how
this question relates to the Code of Conduct?  Are you seeing issues
with how people are responding to the pleas for help?

To answer your
specific question...  I agree that the Change Log (or Revision History)
should be specific to current release effort.  That's how we are doing
it with the Platform, Web Profile, and Managed Beans specs.  Although
it might be nice for consistency, I don't think this has to be enforced
across all of the component specifications.  If an individual spec
wishes to have a running Change Log since the spec was initiated, I would
say that's up to them.  (These are my opinions, not speaking from
a PMC or Spec Committee perspective.)

---------------------------------------------------
Kevin Sutter 
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter



From:
       Theodor
Augustin Dumitrescu <th.theodor.th@xxxxxxxxx>
To:
       Jakarta
specification discussions <jakarta.ee-spec@xxxxxxxxxxx>
Cc:
       Jakarta
EE Ambassadors <jakartaee-ambassadors@xxxxxxxxxxxxxxxx>, Jakarta
EE community discussions <jakarta.ee-community@xxxxxxxxxxx>
Date:
       06/04/2020
07:19
Subject:
       [EXTERNAL]
[jakarta.ee-spec] Alignment with Code of Conduct for specifications  
     migration
Sent
by:        jakarta.ee-spec-bounces@xxxxxxxxxxx

---

Hi folks,
earlier I did a check for understanding
the status of the specifications. Happily to announce that there are new
people willing to participate and help.

During my overview I saw that every project
had been managing the transaction in its own way. In particular, the thing
that I'd like to address is what are your opinions regarding the Change
Log section? I've seen projects that decided to keep it (e.g. [3]) while
in others it has been removed [1][2]. Therefore, I'm starting this conversation
because I strongly believe that all the specification should follow the
same decision regarding this issue. 

In my opinion, the changelog should be
erased for two reasons. First, it forces us to maintain references to old
Oracle documentation. Secondly, in the long run there will be more and
more confusion for new folks going through references regarding discussion
outside the Jakarta/Eclipse ecosystem and also because of the namespaces
javax.


[1] https://www.eclipse.org/lists/servlet-dev/msg00183.html
[2] https://github.com/eclipse-ee4j/servlet-api/pull/319#discussion_r433093802
[3] https://github.com/eclipse-ee4j/jaxrs-api/tree/master/jaxrs-spec/src/main/asciidoc/chapters


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