[Lazarus] Lazarus and FPC teams need direction for marketing/promotion

Andrew Brunner andrew.t.brunner at gmail.com
Sat Feb 25 18:07:48 CET 2012


I honestly think this conversation would be better served asking questions like

How can Lazarus get noticed more?
How can Lazarus get more exposure/adoption?
How can Lazarus get industry sponsorship?
How can Lazarus get educational institutions to explore development
using Lazarus/FPC?

IMO, a larger percentage of the development space is something that
can be attained.  Support for alternative operating systems like linux
and offer a break from Microsoft (namely via Ubuntu) should be a
marketing sweet spot.

Library support for hot topic Information Technologies.  FPC/Lazarus
must follow trends and include components.  A broad range of component
support is essential.

Example: Social is trendy so FPC/Lazarus should come with components
to interface with Craigslist / Facebook / Twitter / Google .  Access
requires http or https requests so openssl would need to be more fully
developed.

IMO, the bottom line is - the more components supported the easier
Lazarus makes it for a developer to download and develop what they
need.  MORE IS MORE.

I often find myself needing a library ported to FPC.  Recently I came
across the Lucene project.  With Lucene developers can create full
text search / document searches.  I need a lucene component or
something like it.  Enterprise search is BIG.  It would be ideal.
Then you get in the search engines for Lucene keyword and voila - a
developer is going to evaluate Lazarus/FPC for adoption.  But the more
developed these components are the better chance will be for the
developer to recommend Lazarus.  And for the firm/institution will
approve it.

Having used FPC/Lazarus for 3 years now I have to say I'm impressed on
how long and far these two projects have come.  More components, and
since development team is limited - chose wisely when tapping into
trendy development networks.

Exposure by way of component ports.  Components need to be native to
FPC and when a component in implemented a concerted effort needs to be
made to make sure Links back to FPC/Lazarus must be placed, and the
Lazarus Wiki should be updated with a dedicated page for that
component and an HTTP link BACK to the targeted components' page.




More information about the Lazarus mailing list