ݺߣ

ݺߣShare a Scribd company logo

Liferay 2012 Community Survey summary

•
•
James Falkner
James Falkner

The document summarizes the results of a 2012 community survey conducted by Liferay. Some key findings include: - 142 people responded to the survey - Most respondents were between 26-35 years old, male, from North America, and had a college degree or higher. - Respondents had known about Liferay for 1-3 years on average and most discovered it online or from a colleague. - The majority of respondents use Liferay for their jobs and spend over 25% of their professional time working with it.

1 of 19
Download to read offline
  Liferay  Community  Survey  2012  Results   Basic   TOTAL  NUMBER  OF  RESPONDENTS:  142     Age         Sex            
Location          
Education         Are  you  working  for  partner?              
Discovery   How  long  known  about  liferay?     How  did  you  discover  Liferay?     How  many  years  have  you  used  Liferay?        
What  percentage  of  professional  time  spent  on  liferay?         Info  Sources     What  Liferay  information  sources  do  you  use  the  most?          
Project  details   How  many  LR  implementations  worked?       What  versions  in  those  projects?              
What  percentage  of  projects  use  EE?     Why  do/would  you  use  CE?        
Why  do/would  you  use  EE?          
Liferay  Direction     What  should  Liferay  fund  on  for  2013  and  beyond?     What  should  Liferay’s  #1  priority/focus  be?         Motivations   Do  you  contribute  to  the  community?          
How  many  hours  spent  on  other  open  source  projects?       Does  your  company  reward  open  source  contributions  by  employees        
If  so,  how     How  many  days/month  do  you  participate  in  other  FOSS?          
(IF  YOU  DO  CONTRIBUTE)   What  is  your  motivation?       How  do  you  value  your  contributions  relative  to  others’?        
How  do  you  value  others’  relative  to  your  contributions?         Do  you  think  contributing  does  enhance  your  job  opportunities?         How  many  years  have  you  contributed  to  Liferay?              
When  would  you  contribute  more?       how  many  days/month  do  you  contribute  to  LR?        
how  do  you  contribute?            
(IF  NOT  CONTRIBUTE)   Why  do  you  not  contribute?        
When  would  you  start  to  contribute?        
Closing     Survey  Feedback     “Got  to  know  lots  of  Liferay  Facts.Was  surprised  to  see  that  Liferay  even  has  its  University”     “We  use  the  community  edition  because  the  policy  of  our  enterprise  is  to  use  open  source  software  (that  option   wasn't  among  the  answers).”     “I  don't  see  any  reason  to  use  EE,  but  that  was  not  an  option.”     "Hello,  I  really  like  this  initiative  taken  by  Liferay.  Its  really  very  good  to  know  that  Liferay  took  things  to  individual   member  level  and  provided  them  a  chance  to  share  their  experience  with  Liferay."     “I  was  expecting  another  type  of  survey.  Something  more  related  to  the  problems  we  encounter  when  developing.  For   instance  interporlet  comunication,  speed  in  development.”     "Hi,  it  is  a  great  idea  to  do  this,  I  will  participate  even  next  time."     “This  survery,  it's  a  great  idea.  Manage  a  so  huge  community  it's  not  so  simple.  IMHU  James  Falkner  contribution  has   been  a  good  decision  for  a  product  like  Liferay.”       “I  hope  this  survey  will  help  to  improve  the  Liferay  Portal  quality”     “More  open  questions  would  be  interesting.  This  is  only  superficial  information  not  in  depth.”     Other  areas  to  focus  on     “Got  to  know  lots  of  Liferay  Facts.  Was  surprised  to  see  that  Liferay  even  has  its  University”     modularity     An  upgrade  process  that  works  without  trashing  my  data  in  Oracle.     Don't  delay  the  release.     Integration  with  Maven       "Usability  &  Consistency  -­‐  It's  getting  better  and  better,  but....     It  is  difficult  to  design  new  intranet  for  our  customer  -­‐  in  every  project  we  have  to  fix  lot  of  bugs  or  change  lot  of   behaviors...     Some  examples:     1)  WebContent  can  work  with  Scope  (Global/Site/PAGE)  but  TAGs  and  Categories  only  with  Site/Global  scope.  So   ""page  scope""  is  unusable!     2)  We  made  WebContent  structures  (advertisement,  ...).  We  have  to  permit  all  users  publish  any  web  content  -­‐  portal   don't  allow  permit  only  one  structure.  So,  structures  are  useful  olny  for  editors....  
  3)  AssetPublisher  is  very  powerful  portlet.  It's  too  complex  and  it  can't  do  lot  of  things...  Let's  make  more  similar   portlets  for  more  use  cases.     Our  typical  requirement  is:  ""Asset  publisher  will  aggregate  all  contents  from  all  portal  sites.  When  I  click  on  title  I   will  be  redirected  on  page  with  this  article"".     4)  I  have  2  Wikis,  2  pages  (for  every  wiki).  I  have  WebContent  with  related  assets  (wiki1_page1,  wiki2_page1)  -­‐  all   wiki  pages  are  shown  in  wiki1  (ignoring  allowed  wiki  in  configuration)     There  are  lot  of  work  done,  I  know.  But  work  on  details  ;)     Needs  more  quality  in  features,  More  stability  required.       "I  would  prefer  Liferay  making  its  Core  lighter  ...  There  are  too  many  portlets  that  are  not  being  used  by  us,  but  still   all  these  portlets  remain  unused.     If  the  Core  is  light,  then  the  number  of  DB  tables  will  be  less  and  more  over  all  the  Core  Portlets  if  provided  as   separate  portlets  just  like  the  Knowledge  Base  portlet  ...  It  would  be  better.  So  that  We  could  choose  on  what  we  want   to  use,  rather  than  dumping  everything  and  not  using  them.     I  do  not  know  the  ramifications  of  making  the  core  lighter,  but  Liferay  needs  to  think  about  it."     More  OOTB  portlets  with  integration  with  various  frameworks  and  technologies  like  spring,solar,  scheduler,jasper   reports,SAP,SSO  etc.     "Stability  was  VERY  poor  with  6.1  EE  SP1  -­‐-­‐  Henry  N.,  Matt,  and  the  rest  of  the  VERY  talented  Support  Team   heroically  saved  the  day  and  a  potentially  HUGE  (reference)  customer  in  HigherEd.     Please  focus  on  QA  going-­‐forward.      

More Related Content

Liferay 2012 Community Survey summary

  • 1.   Liferay  Community  Survey  2012  Results   Basic   TOTAL  NUMBER  OF  RESPONDENTS:  142     Age         Sex            
  • 2. Location          
  • 3. Education         Are  you  working  for  partner?              
  • 4. Discovery   How  long  known  about  liferay?     How  did  you  discover  Liferay?     How  many  years  have  you  used  Liferay?        
  • 5. What  percentage  of  professional  time  spent  on  liferay?         Info  Sources     What  Liferay  information  sources  do  you  use  the  most?          
  • 6. Project  details   How  many  LR  implementations  worked?       What  versions  in  those  projects?              
  • 7. What  percentage  of  projects  use  EE?     Why  do/would  you  use  CE?        
  • 8. Why  do/would  you  use  EE?          
  • 9. Liferay  Direction     What  should  Liferay  fund  on  for  2013  and  beyond?     What  should  Liferay’s  #1  priority/focus  be?         Motivations   Do  you  contribute  to  the  community?          
  • 10. How  many  hours  spent  on  other  open  source  projects?       Does  your  company  reward  open  source  contributions  by  employees        
  • 11. If  so,  how     How  many  days/month  do  you  participate  in  other  FOSS?          
  • 12. (IF  YOU  DO  CONTRIBUTE)   What  is  your  motivation?       How  do  you  value  your  contributions  relative  to  others’?        
  • 13. How  do  you  value  others’  relative  to  your  contributions?         Do  you  think  contributing  does  enhance  your  job  opportunities?         How  many  years  have  you  contributed  to  Liferay?              
  • 14. When  would  you  contribute  more?       how  many  days/month  do  you  contribute  to  LR?        
  • 15. how  do  you  contribute?            
  • 16. (IF  NOT  CONTRIBUTE)   Why  do  you  not  contribute?        
  • 17. When  would  you  start  to  contribute?        
  • 18. Closing     Survey  Feedback     “Got  to  know  lots  of  Liferay  Facts.Was  surprised  to  see  that  Liferay  even  has  its  University”     “We  use  the  community  edition  because  the  policy  of  our  enterprise  is  to  use  open  source  software  (that  option   wasn't  among  the  answers).”     “I  don't  see  any  reason  to  use  EE,  but  that  was  not  an  option.”     "Hello,  I  really  like  this  initiative  taken  by  Liferay.  Its  really  very  good  to  know  that  Liferay  took  things  to  individual   member  level  and  provided  them  a  chance  to  share  their  experience  with  Liferay."     “I  was  expecting  another  type  of  survey.  Something  more  related  to  the  problems  we  encounter  when  developing.  For   instance  interporlet  comunication,  speed  in  development.”     "Hi,  it  is  a  great  idea  to  do  this,  I  will  participate  even  next  time."     “This  survery,  it's  a  great  idea.  Manage  a  so  huge  community  it's  not  so  simple.  IMHU  James  Falkner  contribution  has   been  a  good  decision  for  a  product  like  Liferay.”       “I  hope  this  survey  will  help  to  improve  the  Liferay  Portal  quality”     “More  open  questions  would  be  interesting.  This  is  only  superficial  information  not  in  depth.”     Other  areas  to  focus  on     “Got  to  know  lots  of  Liferay  Facts.  Was  surprised  to  see  that  Liferay  even  has  its  University”     modularity     An  upgrade  process  that  works  without  trashing  my  data  in  Oracle.     Don't  delay  the  release.     Integration  with  Maven       "Usability  &  Consistency  -­‐  It's  getting  better  and  better,  but....     It  is  difficult  to  design  new  intranet  for  our  customer  -­‐  in  every  project  we  have  to  fix  lot  of  bugs  or  change  lot  of   behaviors...     Some  examples:     1)  WebContent  can  work  with  Scope  (Global/Site/PAGE)  but  TAGs  and  Categories  only  with  Site/Global  scope.  So   ""page  scope""  is  unusable!     2)  We  made  WebContent  structures  (advertisement,  ...).  We  have  to  permit  all  users  publish  any  web  content  -­‐  portal   don't  allow  permit  only  one  structure.  So,  structures  are  useful  olny  for  editors....  
  • 19.   3)  AssetPublisher  is  very  powerful  portlet.  It's  too  complex  and  it  can't  do  lot  of  things...  Let's  make  more  similar   portlets  for  more  use  cases.     Our  typical  requirement  is:  ""Asset  publisher  will  aggregate  all  contents  from  all  portal  sites.  When  I  click  on  title  I   will  be  redirected  on  page  with  this  article"".     4)  I  have  2  Wikis,  2  pages  (for  every  wiki).  I  have  WebContent  with  related  assets  (wiki1_page1,  wiki2_page1)  -­‐  all   wiki  pages  are  shown  in  wiki1  (ignoring  allowed  wiki  in  configuration)     There  are  lot  of  work  done,  I  know.  But  work  on  details  ;)     Needs  more  quality  in  features,  More  stability  required.       "I  would  prefer  Liferay  making  its  Core  lighter  ...  There  are  too  many  portlets  that  are  not  being  used  by  us,  but  still   all  these  portlets  remain  unused.     If  the  Core  is  light,  then  the  number  of  DB  tables  will  be  less  and  more  over  all  the  Core  Portlets  if  provided  as   separate  portlets  just  like  the  Knowledge  Base  portlet  ...  It  would  be  better.  So  that  We  could  choose  on  what  we  want   to  use,  rather  than  dumping  everything  and  not  using  them.     I  do  not  know  the  ramifications  of  making  the  core  lighter,  but  Liferay  needs  to  think  about  it."     More  OOTB  portlets  with  integration  with  various  frameworks  and  technologies  like  spring,solar,  scheduler,jasper   reports,SAP,SSO  etc.     "Stability  was  VERY  poor  with  6.1  EE  SP1  -­‐-­‐  Henry  N.,  Matt,  and  the  rest  of  the  VERY  talented  Support  Team   heroically  saved  the  day  and  a  potentially  HUGE  (reference)  customer  in  HigherEd.     Please  focus  on  QA  going-­‐forward.