As a result of a slack thread where @AdamCameron asks about log paths etc - a reply was to use a link in our documentation to place the WEB-INF folder somewhere else. It was also mentioned in the thread that the {approot} should probably never have been used as the location for the WEB-INF folder, obvious security issues etc…
Additionally in the Sys-Admin section of the documentation has information for manually configuring Lucee to use port 80 and other useful “stuff” - that most people now do as “manual” install tasks themselves.
- Could/should - these things be part of the installer?
- Is it a manpower / available hours in the day / priorities “thing” that stops them from being there?
And if so…
Especially with a major release, with possible breaking changes, now being actively worked on - is there an opportunity for;
Tell us the “little” things that really piss you off about Lucee - that you have a work-around for - that you think should be implemented into the product (with the details of the workaround/etc).
And more “pro-actively”;
Give us your changes, now, for active consideration;
and (hopefully) inclusion
Then of course the extra questions that come to my mind, thinking of these things, aloud is;
- How do we make that happen?
I know I can “just” create a pull-request (PR). But is that it? Is the only thing stopping a bug-fix / feature inclusion a PR?
- Do we need more committers / Do we need to trust some more people with “committer” rights?
In a previous thread I asked about submitting documentation changes and adding examples to the docs - (which I am doing some work on at the moment)…
But I also mentioned that I used to be the Patch manager for the Apache SVN project (for quite a few years) - and if it is helpful, at all - I’d happily do it again for the Lucee Project.
Where the Patch Manager is responsible for weekly emails (to a public forum) of the new patches that were submitted by non-committers in the past XXX (period) along with a list of all “unresolved” patches - so that nothing gets “lost” and people can comment on them, “+1 / -1” them: to show their view on the submission.
(Yes I know we have the issue tracker - but things sometimes do just go into the issue tracker to never, ever be seen again! - and that’s why, at least in Apache projects, they have this role)
The installer one, I mentioned earlier, “I” see as something almost anyone could help with - as it doesn’t need Java skills or an in-depth understanding of “Lucee” internals.
- Edit the install scripts to also configure Tomcat’s XMLs for port 80
- Install any required dependencies - which we have to do ourselves (following the current docs)
If you’re like me - you HATE having to repeat the same steps, manually, all the time. So you might create a script that does “that” for you, automatically - with a couple of tweaks - you’ve just implemented your change, permanently into the installer(s) for everyone’s benefit!
I suppose the BIG question is,
- What does the project need help with?
Do you have a list - where someone can say;
- “I” can (ongoing) create / test / etc the .RPM install.
- “I” can do xxxx - but will need a hand with yyyy
- Do you actually want help with it?
- Does it require some sort of “Lucee Association” input?
“I” can’t help with any “serious” Java programming - I only know enough to be dangerous…
But I sure can help with documentation / CFML coding / Creating installers / Lucee as a project, tasks…
And I sure bet I’m not the only one - who could volunteer to help with “a” part.
Thanks as always!
Gavin.