Getting started with Lucee core code development (was Wait. Do we want community involvement or not?)

[Andrew Dixon]

Hi All,

I know that personally I would like to have some idea of how to get started with Lucee core code development, along with a couple of others at mso, so do you think it would be a good idea for someone, e.g. Micha, Igal, Gert, etc... to do a introduction webinar, or maybe a couple, say an hour each, of how to get started with it, best tools to use, overview of the code structure, etc... These could also be records and published on Youtube for future reference so when others come along they can also get involved. 

I have some recollection that maybe Mark Drew did something like this before for Railo, maybe at a meetup or something, but I can't seem to find that and I'm not sure it would still be relevant anyway as I think Micha was saying that the Lucee build process was re-done to make it far easier.

Kind regards,

Andrew

about.me
mso - Lucee - Member

[Igal @ Lucee.org]

funny.  as I was reading Jared's email earlier I was thinking of maybe hosting such a webinar, or at least doing a screencast.


Igal

--
You received this message because you are subscribed to the Google Groups "Lucee" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+un...@googlegroups.com.
To post to this group, send email to lu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/CAG1WijUxyqB-SaWZNG9PBdhrV4DQjG%2BL57nGRf3z1aBVQ7fC8g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Jesse Shaffer]

I would definitely be interested.   I've poked around some, but it would be nice to find out what the "best practices" are.

[Chip Pinkston]

I think this is a great idea.

Here's the Mark Drew meetup video you mentioned - London Railo Meetup: Debugging Railo. Even if things have changed, it's at least a place to start from.

[Dominic Watson]

+1. Record it, and shove it up on the website / wiki / somewhere easy to find.

--

You received this message because you are subscribed to the Google Groups "Lucee" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+un...@googlegroups.com.
To post to this group, send email to lu...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/05c823b3-b98a-409d-8c46-db47822d47a7%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Pixl8 Interactive, 3 Tun Yard, Peardon Street, London SW8 3HT, United Kingdom T: +44 [0] 845 260 0726• W: www.pixl8.co.uk• E: in...@pixl8.co.uk

Follow us on: Facebook Twitter LinkedIn

CONFIDENTIAL AND PRIVILEGED - This e-mail and any attachment is intended solely for the addressee, is strictly confidential and may also be subject to legal, professional or other privilege or may be protected by work product immunity or other legal rules. If you are not the addressee please do not read, print, re-transmit, store or act in reliance on it or any attachments. Instead, please email it back to the sender and then immediately permanently delete it. Pixl8 Interactive Ltd Registered in England. Registered number: 04336501. Registered office: 8 Spur Road, Cosham, Portsmouth, Hampshire, PO6 3EB

[Dominic Watson]

Perhaps this is relevant too http://blog.devspark.com/developers-dont-blow-handoff/ (just saw this on twittersphere yesterday). This isn't a case of project hand-off, rather project on-boarding but sounds like a perfect opportunity to "get it right".

The post boils down to two "principles" (quoted below):

The First Principle of the Handoff - Treat the handoff as a critical and mandatory phase of a development project’s lifecycle.

The Second Principle of the Handoff - Hands-on training is necessary for the new dev team.