| Re: [ee4j-pmc] Mailing List Continuity? |
|
Kevin, It would be great to hear that confirmed by a webmaster for Eclipse (or whomever is actually going to be doing this work). For example, if one is subscribed to: _expression_ Language -- right now, both the Compatible Implementation (CI) and the API binaries are produced out of a single repository. Messages on e-mail and repository notifications regarding either the CI, the Spec, or the API all go on el-dev@xxxxxxxxxxx or emanate from the github repository at github.com/eclipse-ee4j/el-ri If the immediate goal is -- no reorganization immediately, just a
few name changes here and there, perhaps these are questions for
another day and you can just stop reading right now. If that's not the immediate goal, after the split, do we intend
to have two projects: one for the CI and one for the API?
Regardless, I would presume we will have two repositories (one for
the CI and one for the api). Will the same GitHub "Team" be used
for both? Maybe it would be best to "clone" the team so that they
could eventually diverge? It is entirely plausible a new
repository could be created for the API -- and it might only
contain the Specification document immediately. If that's the case
-- I think these questions would still apply (same or different
project? same or different team? ...) Sorry, there are just lots of details. It would be great if the
plan to implement this were visible so that we could review and
assure ourselves that questions like this are answered. -- Ed On 6/18/2019 1:25 PM, Kevin Sutter
wrote:
When we had to modify some of our mailing list names in the early days of EE4j/Jakarta, the move was transparent to the subscribers. Everything just got moved automatically. But, if I remember right, the history of the previous mailing list didn't transfer. If you wanted to view the history of the previous mailing list, you had to look at that one specifically. I think... Someone from the EF would know for sure. |