Il 25/10/2015 12:26, Wols Lists ha scritto:
On 25/10/15 10:50, Riccardo Magliocchetti wrote:
Hello,
during the next libreitalia conference we are going to host a 4 hours
development session. The plan is to help more people getting started
hacking on libo.
Given such a short time frame how is this time better spent from your
own experience? What do you think is more important to tackle? helping
people getting setting up their machines, explaining libo tools /
development, going straight to easy hacks or something else?
How long is a piece of string? Can you have multiple streams?
I'm not following you here :)
Personally, I'd focus on the point after doing a "git pull", and how to
set up your machine ready to push to gerrit, then how to use the
bugzilla and easy hacks through to actually pushing your first trivial
fixes.
this sounds like a plan
The thing is, different people are going to hit different roadblocks.
You'll get people who need hand-holding through git, people who struggle
with C++, etc etc. It'd be nice to cater for them, but there are other
avenues open to them. Focus on the LO-specific stuff.
Yeah, hopefully people with different skills can talk to and help each other.
After that, try and explain the background as to how writer, calc, etc
work internally - give people an overview so they can program easier.
I don't think we have enough time for that, but of course we can provide pointers.
thanks
--
Riccardo Magliocchetti
@rmistaken
http://menodizero.it
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.