totally agree,
in our company the owner trusted me, but a case history would have helped
me.
-> how to commit a new case History?
Pull Request 'd be very useful but not using symfony2 could be
counterproductive.
On Fri, Apr 19, 2013 at 3:39 PM, Lukas Kahwe Smith <sm...@pooteeweet.org>wrote:
>
> On Apr 17, 2013, at 12:47 , Emanuele Gaspari <inmarelib...@gmail.com>
> wrote:
>
> > @Lukas loving the idea.
> >
> > A showcase would be a great way to achieve multiple goals, it can have
> so many implications! I try to express the pros I see.
> >
> > From the point of view of a company working with Symfony:
> > - I would show which are the skills I can actually put on the ground in
> this very moment; also showing the evolution of my works based on Symfony
> > - I would have a look to the different levels of the other competitors,
> including the tools used (apache, nginx, node.js, capifony, oauth, etc...),
> bundles, and everything of some interest involved in building and deploying
> > - I would highlight the use cases I managed to implement, together with
> the practical explanations about how I did this (eg: I used OAuth2 combined
> with FOSUserBundle, giving the possibility to login through facebook,
> twitter, etc...)
> >
> > As a developer, I'd like:
> > - to have a list of companies/web applications using that bundle/that
> tool (eg. nginx), to have an idea about the complexity and to know if that
> company wrote some advice about using that tool
> > - to know how many companies/websites are using Symfony, how it's
> growing, etc..
> >
> >
> > This showcase would be something very curated and organized, either in
> the graphics and the way to publish something.
> >
> > But, before talking about the "how", I say that I think it should be
> built on Symfony2, and would be a big big plus if the entire platform was
> open source. In this way a developer could find in the website how much
> Symfony is used, and see its power for building something by having a look
> at the code used to build the platform.
> >
> > For this reason I invite you to have a look at https://symfonybricks.com;
> this is exactly the philosophy: offering a useful web application built by
> the community, in which visitors can benefit from the available stuff, and
> developers both from the available one and from the "behind" stuff. Also,
> in my view it will be also a sort of community for Symfony developers. Much
> work is to be done on it, but in this moment is working well and the
> interest is growing; as announced in
> http://blog.symfonybricks.com/2013/04/05/time-for-a-renovated-user-interface,
> the graphics too will be renovated soon ;)
> >
> > The domain is registered to me, and I'm the main developer and
> maintainer; hosting this in a subdomain would be awesome.
>
> What you are suggesting here is more for people that are already within
> the Symfony2 eco-system and here I can see your suggestion as quite useful
> as well.
>
> My vision for this was a bit different. For one I did not want it to be a
> show case of the company that did the project (although I am fine with the
> company being mentioned) but more a show case of what kind of projects have
> been done with Symfony2. The target audience should be exclusively manager
> types, ie. non developers. As such it would expect minimal technical
> expertise and the show cases should position Symfony2 against other PHP
> alternatives, but even more importantly entirely different stacks (Spring,
> Rails etc). The show cases should be very high profile, ie. names people
> recognize or have a considerable "wow-factor" for manager types.
> Furthermore due to the target audience we will likely need
> marketing/managers to write or at least review each show case. In general
> it would be quality over quantity.
>
> regards,
> Lukas Kahwe Smith
> sm...@pooteeweet.org
>
>
>
> --
> --
> If you want to report a vulnerability issue on Symfony, please read the
> procedure on http://symfony.com/security
>
> You received this message because you are subscribed to the Google
> Groups "symfony developers" group.
> To post to this group, send email to symfony-devs@googlegroups.com
> To unsubscribe from this group, send email to
> symfony-devs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/symfony-devs?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Symfony developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to symfony-devs+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
--
__________________liuggio_________________________________
__/|_ We reject kings, presidents and voting.
/o ) \/ We believe in rough consensus
)__ v _/\ and running code (I.E.T.F. credo)
______________________________________________________________
--
--
If you want to report a vulnerability issue on Symfony, please read the
procedure on http://symfony.com/security
You received this message because you are subscribed to the Google
Groups "symfony developers" group.
To post to this group, send email to symfony-devs@googlegroups.com
To unsubscribe from this group, send email to
symfony-devs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en
---
You received this message because you are subscribed to the Google Groups
"Symfony developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to symfony-devs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
