Hi Sangeeta, best would be to add Jira tickets in our bug tracker: https://issues.apache.org/jira/browse/OPENMEETINGS
We accept contributions via PR requests on Github: Fork https://github.com/apache/openmeetings into your account and then do a PR upstream. You will not have branch permissions on the public repository. Smaller changes are more likely to be accepted quickly to be merged. As for running & development I still would prefer the jetty-embedded commands: https://openmeetings.apache.org/BuildInstructions.html#tips-and-gotchas As it allows you to change the Javascript + recompile JS/CSS code without restarting the entire OpenMeetings Server. So it takes 3 seconds instead of 3 minutes (plus your PC/laptop fan going to 100%). If you do changes to Java/HTML code you would need to run some of the other MVN commands and restart though. Thanks, Seb Sebastian Wagner Director Arrakeen Solutions http://arrakeen-solutions.co.nz/ <https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url> <https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url> On Tue, 29 Sep 2020 at 17:42, Sangeeta Verma <soadevelop...@yahoo.com> wrote: > We are about to decide which one to use. For this customization is the > key. We have lot of customization that needs to be done. > So my question would be how do we incorporate new releases? If we go ahead > with a different branch then I guess it will be difficult to incorporate > new versions? > > Second question is - for customization how are each components like Menu, > screens etc laid out? Is there any documentation on development? > > Thank you, > Regards, > Sangeeta >
