| Re: [jstl-dev] [jsp-dev] Proposal: merging the Jakarta Tags and Jakarta Pages projects |
_______________________________________________Hello Paul,I would be happy to help you in managing project.Let me know what should I do, please.Dmitri.On Friday, September 17, 2021, 10:03:47 PM GMT+2, Paul Nicolucci <pnicolucci@xxxxxxxxx> wrote:Mark and Arjan thanks for your responses.
I totally understand the time crunch with Jakarta EE10. Mark, you had a good suggestion of just opening up the Jakarta Tags project to Jakarta Pages committers. This suggestion does address the current needs of the project.
So I'd like to propose that if anyone here on this project is willing to help out on Jakarta Tags please contact me and we can work to make that happen!
Arjan, you asked about other projects that use Jakarta Tags. I'm not aware of any outside of Jakarta Pages and Jakarta Faces (you can use Jakarta Tags within a Facelet as well as a Jakarta Server Page to the best of my knowledge.
Does anyone have any input from a project management perspective for my questions here: https://www.eclipse.org/lists/jstl-dev/msg00075.html ?
I'm not very familiar with the release process and how it all exactly works in the Eclipse projects so just looking for some input on how to move forward.
I appreciate the feedback and help!
Regards,
Paul NicolucciOn Thu, Sep 16, 2021 at 6:59 AM arjan tijms <arjan.tijms@xxxxxxxxx> wrote:Hi,I do see merit in merging. The situation feels a little like Faces and the standard tags like h:outputText etc.Is any other project using Tags separate from Pages? Is there any Pages implementation out there which needs to exclude a Tags implementation?There are sometimes good reasons for a split, eg _expression_ Language shared by Security, Pages and Faces. I’m not sure there’s such a reason for the Pages/Tags split. Isn’t it just historical with Tags being an addon initially?That said, there’s higher priority admin tasks that need to be done, like creating a separate project for the _expression_ language API, etc+1 for removing the review requirement. Imho this is only useful for projects such as REST where deleting a whitespace in a javadoc is already controversial._______________________________________________
On Thursday, September 16, 2021, Mark Thomas <markt@xxxxxxxxxx> wrote:Paul,
In the Jakarta EE 10 time frame, I think absolutely not. Time is short and the associated admin overhead of a merge would not be helpful.
A merge after Jakarta EE 10 is worth a discussion. My initial thoughts are:
- The specs would need to remain independent as we don't want to make
Pages implementers have to provide a Tags implementation
- The means we'd need to keep separate repos, CI, releases etc
- So really, the only thing that would be merged is a couple of mailing
lists and two websites.
I'm not at all convinced that such a merger would be a net gain.
What this really boils down to is are there more people here at Pages that would be willing to help move Tags along. If there are, then a simpler solution may be to issue an open invitation for any Pages committer to join Tags. That would give almost the same result with a lot less admin overhead.
In terms of things to help projects with low participation make progress, something that has worked very well for EL is removing (actually it was never applied as far as I recall) the requirement for a PR to be approved by a separate committer. I have been able to make good progress on EL in the last few weeks and the other folks that are involved are able to provide feedback when they need to but things aren't help up waiting for approval for PRs that are trivial / administrative / uncontroversial.
Depending on how things go in the next week or so, I may look to remove the mandatory reviewer requirement from Pages as well.
Mark
On 15/09/2021 20:47, Paul Nicolucci wrote:
Hi, As I'm sure everyone here is aware we have a Jakarta Standard Tag Library (Jakarta Tags) project: https://projects.eclipse.org/projects/ee4j.jstl <https://projects.eclipse.org/projects/ee4j.jstl> The Jakarta Tags project is closely related to the Jakarta Pages project. I'd like to propose we merge the two projects to increase participation in the Jakarta Tags Project. Basically expanding the scope of the Jakarta Pages project to include Jakarta Tags.
I've been trying to make progress for Jakarta EE 10 (Tags 3.0 release) but I've had a really hard time getting participation on the mailing lists and issues/pr reviews..
For example the current thread I'm seeking feedback on: https://www.eclipse.org/lists/jstl-dev/msg00075.html <https://www.eclipse.org/lists/jstl-dev/msg00075.html> .
I have a list of issues I'd like to complete for Jakarta EE 10 here: https://github.com/eclipse-ee4j/jstl-api/issues?q=is%3Aopen+is%3Aissue+label%3AJakartaEE10 <https://github.com/eclipse-ee4j/jstl-api/issues?q=is%3Aopen+is%3Aissue+label%3AJakartaEE10> There is some precedence for project merging such as when the Managed Beans Project was merged into the Platform project. I look forward to hearing from everyone with their thoughts on merging the projects. Regards, Paul Nicolucci
_______________________________________________
jsp-dev mailing list
jsp-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jsp-dev
_______________________________________________
jsp-dev mailing list
jsp-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jsp-dev
jsp-dev mailing list
jsp-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jsp-dev
_______________________________________________
jsp-dev mailing list
jsp-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jsp-dev
jsp-dev mailing list
jsp-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jsp-dev