To be able to contribute back (and easily get updates from upstream you need to) 0) login to github (collisiondetection) 1) visit https://github.com/apache/openmeetings <https://github.com/apache/openmeetings/blob/master/pom.xml#L29> 2) click "Fork" button 3) (select your github group/org if you have more than one) wait fork is finished 4) clone forked repo (it should be https://github.com/collisiondetection/openmeetings) check out any branch do change code :)
To get recent updates from upstream repo ( https://github.com/apache/openmeetings <https://github.com/apache/openmeetings/blob/master/pom.xml#L29>) 0) cd folder you have cloned https://github.com/collisiondetection/openmeetings 1) add additional remote: `git remote add apache https://github.com/apache/openmeetings` NOTE this step need to be performed only once 2) fetch recent changes: `git fetch apache` 3) merge recent changes: `git merge apache/master` NOTE you should merge `apache/4.0.x` if you are working with 4.0.x branch 3.1) manually resolve conflicts (if any) 4) push recent changes to your repo: `git push` something like this :) On Mon, 25 Mar 2019 at 14:45, Daniel Baker <[email protected]> wrote: > So I downloaded om 5 binary and unpacked it into /opt , now > what should I do ? > On 3/24/2019 10:45 PM, Maxim Solodovnik wrote: > > Yes :) > github master == 5.0.0 > > You can check it in the main pom.xml file [1] > > [1] https://github.com/apache/openmeetings/blob/master/pom.xml#L29 > > > On Sun, 24 Mar 2019 at 21:02, Daniel Baker <[email protected]> > wrote: > >> Yes I will fork 5 but is it on github ? You are saying 5.0 is >> master ? >> On 3/24/2019 8:41 PM, Maxim Solodovnik wrote: >> >> Hello Daniel, >> >> Actually you are forking whole OM repository >> Then you should decide which branch you would like to use as base (master >> == 5.0.x OR 4.0.x) >> :))) >> >> Please let me know if above steps need to be more detailed >> >> On Sun, 24 Mar 2019 at 17:56, Daniel Baker <[email protected]> >> wrote: >> >>> Wouldn't it be a nice idea to be able to fork 5 ? >>> On 3/21/2019 3:20 PM, Maxim Solodovnik wrote: >>> >>> Hello Daniel, >>> >>> It seems you tarted with "manual import" of OM codebase >>> I would start with fork >>> So it would be possible to easily update your version with all latest >>> fixes >>> And would be possible to contribute back :) >>> >>> On Thu, 21 Mar 2019 at 14:44, Daniel Baker <[email protected]> >>> wrote: >>> >>>> Still working on it. Very flaky at the moment : >>>> https://github.com/collisiondetection/om_tutor >>>> On 3/21/2019 1:01 PM, Stefan Kühl wrote: >>>> >>>> Hey @all! >>>> >>>> Any news regarding this theme? I really appreciate this one and would >>>> like to implement it ;-) >>>> >>>> Greetz >>>> >>>> Stefan >>>> >>>> >>>> >>>> Am 14.03.2019 15:38, schrieb Daniel Baker: >>>> >>>> Taking your theme we have implemented it with a lower third >>>> for webcams. I am testing this and will share this soon. >>>> >>>> >>>> >>>> On 3/14/2019 8:59 PM, Peter Dähn wrote: >>>> >>>> Hello all, >>>> >>>> we would like to announce the new themes page. You can find it under >>>> "ready to use theme" at the "themes and branding" site at the project page >>>> ( >>>> http://openmeetings.apache.org/themes-and-branding.html#_toc_ready_to_use_theme). >>>> <http://openmeetings.apache.org/themes-and-branding.html#_toc_ready_to_use_themes> >>>> >>>> This site should be used to show "your" OpenMeetings, to share your >>>> experiences and theme packages. You could show little changes as well as >>>> complete "redesigns". >>>> >>>> To start we add a first theme. We hope you like it! >>>> >>>> BR >>>> Peter >>>> >>>> >>> >>> -- >>> WBR >>> Maxim aka solomax >>> >>> >> >> -- >> WBR >> Maxim aka solomax >> >> > > -- > WBR > Maxim aka solomax > > -- WBR Maxim aka solomax
