Re: [Kolab-devel] Submitting changes to pykolab

"Jeroen van Meeuwen (Kolab Systems)" <[email protected]>
Newsgroups gmane.comp.kde.devel.kolab
Message-ID <5b62b778c776bf11366cc09538015a0a__46347.0171358951$1384781081$gmane$org@kolabsys.com>
On 2013-11-18 14:28, Paul Boddie wrote:
> Hello,
> 
> I was looking around to see if there was any kind of guide to 
> submitting
> changes to the actual Kolab software, as opposed to the packaging, but 
> I
> didn't find anything immediately.
> 
> I decided to clone pykolab from git.kolab.org and to make some 
> initially
> trivial changes, with the idea that I might then continue on this path, 
> but
> what is the workflow involved in submitting them back to the project? 
> Should I
> mail my patches somewhere, publish them somewhere (for pulling by the 
> core
> developers), request push privileges, or something else?
> 
> I hope I didn't miss an obvious document describing such matters!
> 
> Paul
> 
> P.S. My initial trivial commit would be to change the old licence 
> boilerplate
> to the FSF-recommended text, but having looked at setup-kolab recently, 
> there
> are probably some other trivial to not-so-trivial changes that would
> eventually be made, too.

You would typically create a ticket, if one does not already exist, and 
attach the git-format-patch version of your patch.

Kind regards,

Jeroen van Meeuwen

-- 
Systems Architect, Kolab Systems AG

e: vanmeeuwen at kolabsys.com
m: +44 74 2516 3817
w: http://www.kolabsys.com

pgp: 9342 BF08
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.