librelist archives

« back to archive

Roadmap information

Roadmap information

From:
Loic d'Anterroches
Date:
2011-02-26 @ 21:49
Hello,

just a short information roadmap. Nothing big, just to let you know what
I am doing at the moment.

- I need a minimal port of Cheméo on top of Photon for the end of the
  month and February has only 28 days.

- port of the Pluf form handling to Photon. This is needed for Cheméo.
  At the same time, I have seen that the Django form validation stuff
  improved during the past 3 years, so, I am updating the validation
  code I have to reuse their good work. What is neat is that I do not
  need to carry over all the backward compatibility hacks they have.

- tutorial. I need to get a tutorial, from a bare Debian/Ubuntu
  installation until a working chat server with multiple handler
  processes.

These are the three main points for the coming week. This is not a lot
because I have a large body of consulting work to do and want to get a
code freeze of Indefero.

You can expect a series of releases during the next few days. So, the
best way to keep running with the latest version is to run on a regular
basis:

$ sudo pear update-channels
$ sudo pear upgrade photon/photon-alpha

As usual, full documentation is written at the same time and pushed on
the website. I do not have yet written the fabric receipes to update the
website in one command, so I need to improve.

For the feedback from the soft launch, this was a soft launch, but
somebody decided to post it on HackerNews, then Reddit, the website
received nearly 4000 visitors in about 36h.

For the weeks after, the first points will be authentication and ACLs. A
bit of design will be needed there. The Django way is to have a given
User class. This makes a lot of problem the day you want your user to
have 5 email addresses and an old ICQ account. You have the profile
concept, but it is clumsy and inefficient. So, the idea is to have a
"duck typing" interface to respect for your "user object" and go. I do
not have anything really fixed in my mind, I will need to experiment.

Oh, by the way, from another server on the same switch, 3 childs and
everything in 40MB RAM (small OpenVZ VE with 512MB RAM, 2 cores):

siege -c10 -t15S  http://www.photon-project.com/hello
** SIEGE 2.68
** Preparing 10 concurrent users for battle.
The server is now under siege...
Lifting the server siege..      done.
Transactions:		       89660 hits
Availability:		      100.00 %
Elapsed time:		       14.13 secs
Data transferred:	        1.03 MB
Response time:		        0.00 secs
Transaction rate:	     6345.36 trans/sec
Throughput:		        0.07 MB/sec
Concurrency:		        9.86
Successful transactions:       89660
Failed transactions:	           0
Longest transaction:	        0.01
Shortest transaction:	        0.00

From the same server, I extracted 9000 trans/sec on a similar text file
served directly by Mongrel2: http://dist.photon-project.com/config.xml

Enjoy,
loïc

Current release: 0.0.5

--
Indefero - Project management and code hosting - http://www.indefero.net
Photon - High Performance PHP Framework - http://photon-project.com
Céondo Ltd - Web + Science = Fun - http://www.ceondo.com

Community Involvement for Photon

From:
Devon Weller
Date:
2011-02-27 @ 17:20
Hi Loic.


Thanks for the roadmap post.  That is great to see.


How do you feel about community contributions to Photon?  Is it something 
you want to encourage?  

What do you recommend to someone who wants to get involved in the 
development of photon?  Is there a better way to contribute besides 
emailing patches to this list?


- Devon

Re: [photon.users] Community Involvement for Photon

From:
Loic d'Anterroches
Date:
2011-02-27 @ 17:47
Hi Devon,

> Thanks for the roadmap post. That is great to see.
> 
> 
> How do you feel about community contributions to Photon? Is it
> something you want to encourage?

Definitely.

> What do you recommend to someone who wants to get involved in the
> development of photon? Is there a better way to contribute besides
> emailing patches to this list?

Simple, you first propose patches on the list, we discuss, if your patch
matches the requirements (unit tests, formatting, etc.) and get applied
without the need for me to change a space/tab whatever, you
automatically win commit rights on the develop branch. We then trust you
that you will discuss ideas etc. before doing a commit with big
implications.

I have no problems having 20 people pushing/hacking directly in the code
in the develop branch. I will keep control of the master once we reach
beta as I will use it for some important deployments.

You can also fork somewhere and propose a pull when you have something a
bit complex you want to work on on the side.

The main website will also be but in a git repository, we will need to
ensure the doc is correctly in sync with the code. Top documentation is
critical, with screencasts to showcase the nice stuff, etc. I want
people to have the direct "yes, this is a pain point with my standard
framework under Apache/fastcgi, I can keep doing it with PHP but without
the pain." effect. For a lot of things, we do not need Photon, but for
quite some, it really improves life.

A lot of "I want, I will, I think", but you will see that normally, it
becomes very fast a "we".

So, right now, you know the roadmap, what is really missing and what
would have a real impact, is updating the $ hnu init myproject to create
automatically:

- a very simple hello world app with 2 views, one output hello, the
  other one hello foo! if the url is /hello/foo /hello/(.*).
- the chat application (you can find it in the photon-web.zip) file.
- one application with a task.
- an application with a bit of form handling (I need to finish the
  form stuff before).

All that with the corresponding tests, so that if they do:

$ hnu init myproject
$ cd myproject
$ hnu runtests

we get 100% test coverage.

$ hnu server start
it works.

$ m2sh load -config myproject-mongrel2.conf
$ m2sh start -host localhost

$ curl http://localhost:6767/photon/hello/foo
Hello foo!

Basically, the goal is to be very very fast to "it works, it is great,
it will make my life as a developer better". If we want to grow the
community fast and have a lot of fun, this is really important.

I hope it helps, questions and feedback welcome,
loïc

Dump of the website: http://dist.photon-project.com/photon-web.zip

--
Indefero - Project management and code hosting - http://www.indefero.net
Photon - High Performance PHP Framework - http://photon-project.com
Céondo Ltd - Web + Science = Fun - http://www.ceondo.com

Re: [photon.users] Community Involvement for Photon

From:
Devon Weller
Date:
2011-02-27 @ 21:34
Loic,

I'd like to help out by rewriting the makeDirs and generateFiles methods 
in photon\manager\Init.  Along with that, I'll restructure the photon/data
directory to exactly mirror the setup of a new app.  The new structure 
would look something like this:

data/config.php
data/config.test.php
data/urls.php
data/templates
data/www
data/apps
data/apps/__APPNAME__
data/__APPNAME__/urls.php
data/__APPNAME__/views.php
data/__APPNAME__/tests.php
data/__APPNAME__/templates/__APPNAME__
data/__APPNAME__/www/media/__APPNAME__
data/__APPNAME__/data
data/__APPNAME__/models.php
data/__APPNAME__/task.php



Then the init routine will just recursively copy all files and folders 
over to set up a new project and application, substituting __APPNAME__ 
with "helloworld".


I've checked out the development branch using these instructions: 
http://projects.ceondo.com/p/photon/issues/606.


That should give us a good start toward the out-of-the box working example
we need.

What do you think?

- Devon



On Feb 27, 2011, at 11:47 AM, Loic d'Anterroches wrote:

> Hi Devon,
> 
>> Thanks for the roadmap post. That is great to see.
>> 
>> 
>> How do you feel about community contributions to Photon? Is it
>> something you want to encourage?
> 
> Definitely.
> 
>> What do you recommend to someone who wants to get involved in the
>> development of photon? Is there a better way to contribute besides
>> emailing patches to this list?
> 
> Simple, you first propose patches on the list, we discuss, if your patch
> matches the requirements (unit tests, formatting, etc.) and get applied
> without the need for me to change a space/tab whatever, you
> automatically win commit rights on the develop branch. We then trust you
> that you will discuss ideas etc. before doing a commit with big
> implications.
> 
> I have no problems having 20 people pushing/hacking directly in the code
> in the develop branch. I will keep control of the master once we reach
> beta as I will use it for some important deployments.
> 
> You can also fork somewhere and propose a pull when you have something a
> bit complex you want to work on on the side.
> 
> The main website will also be but in a git repository, we will need to
> ensure the doc is correctly in sync with the code. Top documentation is
> critical, with screencasts to showcase the nice stuff, etc. I want
> people to have the direct "yes, this is a pain point with my standard
> framework under Apache/fastcgi, I can keep doing it with PHP but without
> the pain." effect. For a lot of things, we do not need Photon, but for
> quite some, it really improves life.
> 
> A lot of "I want, I will, I think", but you will see that normally, it
> becomes very fast a "we".
> 
> So, right now, you know the roadmap, what is really missing and what
> would have a real impact, is updating the $ hnu init myproject to create
> automatically:
> 
> - a very simple hello world app with 2 views, one output hello, the
>  other one hello foo! if the url is /hello/foo /hello/(.*).
> - the chat application (you can find it in the photon-web.zip) file.
> - one application with a task.
> - an application with a bit of form handling (I need to finish the
>  form stuff before).
> 
> All that with the corresponding tests, so that if they do:
> 
> $ hnu init myproject
> $ cd myproject
> $ hnu runtests
> 
> we get 100% test coverage.
> 
> $ hnu server start
> it works.
> 
> $ m2sh load -config myproject-mongrel2.conf
> $ m2sh start -host localhost
> 
> $ curl http://localhost:6767/photon/hello/foo
> Hello foo!
> 
> Basically, the goal is to be very very fast to "it works, it is great,
> it will make my life as a developer better". If we want to grow the
> community fast and have a lot of fun, this is really important.
> 
> I hope it helps, questions and feedback welcome,
> loïc
> 
> Dump of the website: http://dist.photon-project.com/photon-web.zip
> 
> --
> Indefero - Project management and code hosting - http://www.indefero.net
> Photon - High Performance PHP Framework - http://photon-project.com
> Céondo Ltd - Web + Science = Fun - http://www.ceondo.com

Re: [photon.users] Community Involvement for Photon

From:
Loic d'Anterroches
Date:
2011-02-27 @ 21:42
Devon,

great. Go ahead. For the git checkout, if you can, please use gitflow.
If you do not use it, you can do the same without installing it, but
what is important is that when you have completed some work on a topic
branch, do a merge without fast forward: --no-ff this will create a
commit just for the merge and keep your work history. This is really
important to see what is coming from where.

Have fun and the motto is more "do and ask later". You will never be
blamed for doing something.

loïc

On 2011-02-27 22:34, Devon Weller wrote:
> Loic,
> 
> I'd like to help out by rewriting the makeDirs and generateFiles methods
in photon\manager\Init.  Along with that, I'll restructure the photon/data
directory to exactly mirror the setup of a new app.  The new structure 
would look something like this:
> 
> data/config.php
> data/config.test.php
> data/urls.php
> data/templates
> data/www
> data/apps
> data/apps/__APPNAME__
> data/__APPNAME__/urls.php
> data/__APPNAME__/views.php
> data/__APPNAME__/tests.php
> data/__APPNAME__/templates/__APPNAME__
> data/__APPNAME__/www/media/__APPNAME__
> data/__APPNAME__/data
> data/__APPNAME__/models.php
> data/__APPNAME__/task.php
> 
> 
> 
> Then the init routine will just recursively copy all files and folders 
over to set up a new project and application, substituting __APPNAME__ 
with "helloworld".
> 
> 
> I've checked out the development branch using these instructions: 
http://projects.ceondo.com/p/photon/issues/606.
> 
> 
> That should give us a good start toward the out-of-the box working 
example we need.
> 
> What do you think?
> 
> - Devon
> 
> 
> 
> On Feb 27, 2011, at 11:47 AM, Loic d'Anterroches wrote:
> 
>> Hi Devon,
>>
>>> Thanks for the roadmap post. That is great to see.
>>>
>>>
>>> How do you feel about community contributions to Photon? Is it
>>> something you want to encourage?
>>
>> Definitely.
>>
>>> What do you recommend to someone who wants to get involved in the
>>> development of photon? Is there a better way to contribute besides
>>> emailing patches to this list?
>>
>> Simple, you first propose patches on the list, we discuss, if your patch
>> matches the requirements (unit tests, formatting, etc.) and get applied
>> without the need for me to change a space/tab whatever, you
>> automatically win commit rights on the develop branch. We then trust you
>> that you will discuss ideas etc. before doing a commit with big
>> implications.
>>
>> I have no problems having 20 people pushing/hacking directly in the code
>> in the develop branch. I will keep control of the master once we reach
>> beta as I will use it for some important deployments.
>>
>> You can also fork somewhere and propose a pull when you have something a
>> bit complex you want to work on on the side.
>>
>> The main website will also be but in a git repository, we will need to
>> ensure the doc is correctly in sync with the code. Top documentation is
>> critical, with screencasts to showcase the nice stuff, etc. I want
>> people to have the direct "yes, this is a pain point with my standard
>> framework under Apache/fastcgi, I can keep doing it with PHP but without
>> the pain." effect. For a lot of things, we do not need Photon, but for
>> quite some, it really improves life.
>>
>> A lot of "I want, I will, I think", but you will see that normally, it
>> becomes very fast a "we".
>>
>> So, right now, you know the roadmap, what is really missing and what
>> would have a real impact, is updating the $ hnu init myproject to create
>> automatically:
>>
>> - a very simple hello world app with 2 views, one output hello, the
>>  other one hello foo! if the url is /hello/foo /hello/(.*).
>> - the chat application (you can find it in the photon-web.zip) file.
>> - one application with a task.
>> - an application with a bit of form handling (I need to finish the
>>  form stuff before).
>>
>> All that with the corresponding tests, so that if they do:
>>
>> $ hnu init myproject
>> $ cd myproject
>> $ hnu runtests
>>
>> we get 100% test coverage.
>>
>> $ hnu server start
>> it works.
>>
>> $ m2sh load -config myproject-mongrel2.conf
>> $ m2sh start -host localhost
>>
>> $ curl http://localhost:6767/photon/hello/foo
>> Hello foo!
>>
>> Basically, the goal is to be very very fast to "it works, it is great,
>> it will make my life as a developer better". If we want to grow the
>> community fast and have a lot of fun, this is really important.
>>
>> I hope it helps, questions and feedback welcome,
>> loïc
>>
>> Dump of the website: http://dist.photon-project.com/photon-web.zip
>>
>> --
>> Indefero - Project management and code hosting - http://www.indefero.net
>> Photon - High Performance PHP Framework - http://photon-project.com
>> Céondo Ltd - Web + Science = Fun - http://www.ceondo.com
> 

-- 
Dr Loïc d'Anterroches
Founder Céondo Ltd

w: www.ceondo.com       |  e: loic@ceondo.com
t: +44 (0)207 183 0016  |  f: +44 (0)207 183 0124

Céondo Ltd
Dalton House
60 Windsor Avenue
London
SW19 2RR / United Kingdom

Re: [photon.users] Community Involvement for Photon

From:
Devon Weller
Date:
2011-02-28 @ 14:26
Loic,

I modified the app template directories and photon\manager\Init so that 
the following sequence now works:

hnu init testproject
cd testproject
hnu server start

m2sh load -config mongrel2/conf/myproject-mongrel2.conf 
m2sh start -host localhost


Next up would be getting hnu runtests to work as well.

Do you want this code now?  If so, how should I push this code to you?

Right now my changes are in a feature branch using git flow.   This is the
first time I've used git flow - it is very handy!


- Devon



On Feb 27, 2011, at 3:42 PM, Loic d'Anterroches wrote:

> Devon,
> 
> great. Go ahead. For the git checkout, if you can, please use gitflow.
> If you do not use it, you can do the same without installing it, but
> what is important is that when you have completed some work on a topic
> branch, do a merge without fast forward: --no-ff this will create a
> commit just for the merge and keep your work history. This is really
> important to see what is coming from where.
> 
> Have fun and the motto is more "do and ask later". You will never be
> blamed for doing something.
> 
> loïc
> 
> On 2011-02-27 22:34, Devon Weller wrote:
>> Loic,
>> 
>> I'd like to help out by rewriting the makeDirs and generateFiles 
methods in photon\manager\Init.  Along with that, I'll restructure the 
photon/data directory to exactly mirror the setup of a new app.  The new 
structure would look something like this:
>> 
>> data/config.php
>> data/config.test.php
>> data/urls.php
>> data/templates
>> data/www
>> data/apps
>> data/apps/__APPNAME__
>> data/__APPNAME__/urls.php
>> data/__APPNAME__/views.php
>> data/__APPNAME__/tests.php
>> data/__APPNAME__/templates/__APPNAME__
>> data/__APPNAME__/www/media/__APPNAME__
>> data/__APPNAME__/data
>> data/__APPNAME__/models.php
>> data/__APPNAME__/task.php
>> 
>> 
>> 
>> Then the init routine will just recursively copy all files and folders 
over to set up a new project and application, substituting __APPNAME__ 
with "helloworld".
>> 
>> 
>> I've checked out the development branch using these instructions: 
http://projects.ceondo.com/p/photon/issues/606.
>> 
>> 
>> That should give us a good start toward the out-of-the box working 
example we need.
>> 
>> What do you think?
>> 
>> - Devon
>> 
>> 
>> 
>> On Feb 27, 2011, at 11:47 AM, Loic d'Anterroches wrote:
>> 
>>> Hi Devon,
>>> 
>>>> Thanks for the roadmap post. That is great to see.
>>>> 
>>>> 
>>>> How do you feel about community contributions to Photon? Is it
>>>> something you want to encourage?
>>> 
>>> Definitely.
>>> 
>>>> What do you recommend to someone who wants to get involved in the
>>>> development of photon? Is there a better way to contribute besides
>>>> emailing patches to this list?
>>> 
>>> Simple, you first propose patches on the list, we discuss, if your patch
>>> matches the requirements (unit tests, formatting, etc.) and get applied
>>> without the need for me to change a space/tab whatever, you
>>> automatically win commit rights on the develop branch. We then trust you
>>> that you will discuss ideas etc. before doing a commit with big
>>> implications.
>>> 
>>> I have no problems having 20 people pushing/hacking directly in the code
>>> in the develop branch. I will keep control of the master once we reach
>>> beta as I will use it for some important deployments.
>>> 
>>> You can also fork somewhere and propose a pull when you have something a
>>> bit complex you want to work on on the side.
>>> 
>>> The main website will also be but in a git repository, we will need to
>>> ensure the doc is correctly in sync with the code. Top documentation is
>>> critical, with screencasts to showcase the nice stuff, etc. I want
>>> people to have the direct "yes, this is a pain point with my standard
>>> framework under Apache/fastcgi, I can keep doing it with PHP but without
>>> the pain." effect. For a lot of things, we do not need Photon, but for
>>> quite some, it really improves life.
>>> 
>>> A lot of "I want, I will, I think", but you will see that normally, it
>>> becomes very fast a "we".
>>> 
>>> So, right now, you know the roadmap, what is really missing and what
>>> would have a real impact, is updating the $ hnu init myproject to create
>>> automatically:
>>> 
>>> - a very simple hello world app with 2 views, one output hello, the
>>> other one hello foo! if the url is /hello/foo /hello/(.*).
>>> - the chat application (you can find it in the photon-web.zip) file.
>>> - one application with a task.
>>> - an application with a bit of form handling (I need to finish the
>>> form stuff before).
>>> 
>>> All that with the corresponding tests, so that if they do:
>>> 
>>> $ hnu init myproject
>>> $ cd myproject
>>> $ hnu runtests
>>> 
>>> we get 100% test coverage.
>>> 
>>> $ hnu server start
>>> it works.
>>> 
>>> $ m2sh load -config myproject-mongrel2.conf
>>> $ m2sh start -host localhost
>>> 
>>> $ curl http://localhost:6767/photon/hello/foo
>>> Hello foo!
>>> 
>>> Basically, the goal is to be very very fast to "it works, it is great,
>>> it will make my life as a developer better". If we want to grow the
>>> community fast and have a lot of fun, this is really important.
>>> 
>>> I hope it helps, questions and feedback welcome,
>>> loïc
>>> 
>>> Dump of the website: http://dist.photon-project.com/photon-web.zip
>>> 
>>> --
>>> Indefero - Project management and code hosting - http://www.indefero.net
>>> Photon - High Performance PHP Framework - http://photon-project.com
>>> Céondo Ltd - Web + Science = Fun - http://www.ceondo.com
>> 
> 
> -- 
> Dr Loïc d'Anterroches
> Founder Céondo Ltd
> 
> w: www.ceondo.com       |  e: loic@ceondo.com
> t: +44 (0)207 183 0016  |  f: +44 (0)207 183 0124
> 
> Céondo Ltd
> Dalton House
> 60 Windsor Avenue
> London
> SW19 2RR / United Kingdom

Re: [photon.users] Community Involvement for Photon

From:
Loic d'Anterroches
Date:
2011-02-28 @ 15:34
Hi Devon,

this is great. Just do a $ git diff develop
it should provide you with a good diff of your changes. If fine, I will
apply and give you write access to the repository, you will then be able
to directly push into develop.

loïc

On 2011-02-28 15:26, Devon Weller wrote:
> Loic,
> 
> I modified the app template directories and photon\manager\Init so that 
the following sequence now works:
> 
> hnu init testproject
> cd testproject
> hnu server start
> 
> m2sh load -config mongrel2/conf/myproject-mongrel2.conf 
> m2sh start -host localhost
> 
> 
> Next up would be getting hnu runtests to work as well.
> 
> Do you want this code now?  If so, how should I push this code to you?
> 
> Right now my changes are in a feature branch using git flow.   This is 
the first time I've used git flow - it is very handy!
> 
> 
> - Devon
> 
> 
> 
> On Feb 27, 2011, at 3:42 PM, Loic d'Anterroches wrote:
> 
>> Devon,
>>
>> great. Go ahead. For the git checkout, if you can, please use gitflow.
>> If you do not use it, you can do the same without installing it, but
>> what is important is that when you have completed some work on a topic
>> branch, do a merge without fast forward: --no-ff this will create a
>> commit just for the merge and keep your work history. This is really
>> important to see what is coming from where.
>>
>> Have fun and the motto is more "do and ask later". You will never be
>> blamed for doing something.
>>
>> loïc
>>
>> On 2011-02-27 22:34, Devon Weller wrote:
>>> Loic,
>>>
>>> I'd like to help out by rewriting the makeDirs and generateFiles 
methods in photon\manager\Init.  Along with that, I'll restructure the 
photon/data directory to exactly mirror the setup of a new app.  The new 
structure would look something like this:
>>>
>>> data/config.php
>>> data/config.test.php
>>> data/urls.php
>>> data/templates
>>> data/www
>>> data/apps
>>> data/apps/__APPNAME__
>>> data/__APPNAME__/urls.php
>>> data/__APPNAME__/views.php
>>> data/__APPNAME__/tests.php
>>> data/__APPNAME__/templates/__APPNAME__
>>> data/__APPNAME__/www/media/__APPNAME__
>>> data/__APPNAME__/data
>>> data/__APPNAME__/models.php
>>> data/__APPNAME__/task.php
>>>
>>>
>>>
>>> Then the init routine will just recursively copy all files and folders
over to set up a new project and application, substituting __APPNAME__ 
with "helloworld".
>>>
>>>
>>> I've checked out the development branch using these instructions: 
http://projects.ceondo.com/p/photon/issues/606.
>>>
>>>
>>> That should give us a good start toward the out-of-the box working 
example we need.
>>>
>>> What do you think?
>>>
>>> - Devon
>>>
>>>
>>>
>>> On Feb 27, 2011, at 11:47 AM, Loic d'Anterroches wrote:
>>>
>>>> Hi Devon,
>>>>
>>>>> Thanks for the roadmap post. That is great to see.
>>>>>
>>>>>
>>>>> How do you feel about community contributions to Photon? Is it
>>>>> something you want to encourage?
>>>>
>>>> Definitely.
>>>>
>>>>> What do you recommend to someone who wants to get involved in the
>>>>> development of photon? Is there a better way to contribute besides
>>>>> emailing patches to this list?
>>>>
>>>> Simple, you first propose patches on the list, we discuss, if your patch
>>>> matches the requirements (unit tests, formatting, etc.) and get applied
>>>> without the need for me to change a space/tab whatever, you
>>>> automatically win commit rights on the develop branch. We then trust you
>>>> that you will discuss ideas etc. before doing a commit with big
>>>> implications.
>>>>
>>>> I have no problems having 20 people pushing/hacking directly in the code
>>>> in the develop branch. I will keep control of the master once we reach
>>>> beta as I will use it for some important deployments.
>>>>
>>>> You can also fork somewhere and propose a pull when you have something a
>>>> bit complex you want to work on on the side.
>>>>
>>>> The main website will also be but in a git repository, we will need to
>>>> ensure the doc is correctly in sync with the code. Top documentation is
>>>> critical, with screencasts to showcase the nice stuff, etc. I want
>>>> people to have the direct "yes, this is a pain point with my standard
>>>> framework under Apache/fastcgi, I can keep doing it with PHP but without
>>>> the pain." effect. For a lot of things, we do not need Photon, but for
>>>> quite some, it really improves life.
>>>>
>>>> A lot of "I want, I will, I think", but you will see that normally, it
>>>> becomes very fast a "we".
>>>>
>>>> So, right now, you know the roadmap, what is really missing and what
>>>> would have a real impact, is updating the $ hnu init myproject to create
>>>> automatically:
>>>>
>>>> - a very simple hello world app with 2 views, one output hello, the
>>>> other one hello foo! if the url is /hello/foo /hello/(.*).
>>>> - the chat application (you can find it in the photon-web.zip) file.
>>>> - one application with a task.
>>>> - an application with a bit of form handling (I need to finish the
>>>> form stuff before).
>>>>
>>>> All that with the corresponding tests, so that if they do:
>>>>
>>>> $ hnu init myproject
>>>> $ cd myproject
>>>> $ hnu runtests
>>>>
>>>> we get 100% test coverage.
>>>>
>>>> $ hnu server start
>>>> it works.
>>>>
>>>> $ m2sh load -config myproject-mongrel2.conf
>>>> $ m2sh start -host localhost
>>>>
>>>> $ curl http://localhost:6767/photon/hello/foo
>>>> Hello foo!
>>>>
>>>> Basically, the goal is to be very very fast to "it works, it is great,
>>>> it will make my life as a developer better". If we want to grow the
>>>> community fast and have a lot of fun, this is really important.
>>>>
>>>> I hope it helps, questions and feedback welcome,
>>>> loïc
>>>>
>>>> Dump of the website: http://dist.photon-project.com/photon-web.zip
>>>>
>>>> --
>>>> Indefero - Project management and code hosting - http://www.indefero.net
>>>> Photon - High Performance PHP Framework - http://photon-project.com
>>>> Céondo Ltd - Web + Science = Fun - http://www.ceondo.com
>>>
>>
>> -- 
>> Dr Loïc d'Anterroches
>> Founder Céondo Ltd
>>
>> w: www.ceondo.com       |  e: loic@ceondo.com
>> t: +44 (0)207 183 0016  |  f: +44 (0)207 183 0124
>>
>> Céondo Ltd
>> Dalton House
>> 60 Windsor Avenue
>> London
>> SW19 2RR / United Kingdom
> 

-- 
Dr Loïc d'Anterroches
Founder Céondo Ltd

w: www.ceondo.com       |  e: loic@ceondo.com
t: +44 (0)207 183 0016  |  f: +44 (0)207 183 0124

Céondo Ltd
Dalton House
60 Windsor Avenue
London
SW19 2RR / United Kingdom

Re: [photon.users] Community Involvement for Photon

From:
Devon Weller
Date:
2011-02-28 @ 15:45
Will do.  Please find the patch file attached.

- Devon

Re: [photon.users] Community Involvement for Photon

From:
Loic d'Anterroches
Date:
2011-02-28 @ 16:33
Hi Devon,

quick look at the patch. Please ensure to use 4 spaces and not tabs for
the indentation. You should also remove your personal path from the paths.

Maybe you can directly name the application "helloworld" in the project
template, that way we can easily add a "chat" application and a
"tutorial" application reflecting the tutorial I will have to write.

What do you think?

For the rest, perfect!
loïc

On 2011-02-28 16:45, Devon Weller wrote:
> 
> Will do.  Please find the patch file attached.
> 
> - Devon
> 
> 
> 
> 
> 
> 
> On Feb 28, 2011, at 9:34 AM, Loic d'Anterroches wrote:
> 
>> Hi Devon,
>>
>> this is great. Just do a $ git diff develop
>> it should provide you with a good diff of your changes. If fine, I will
>> apply and give you write access to the repository, you will then be able
>> to directly push into develop.
>>
>> loïc
>>
>> On 2011-02-28 15:26, Devon Weller wrote:
>>> Loic,
>>>
>>> I modified the app template directories and photon\manager\Init so 
that the following sequence now works:
>>>
>>> hnu init testproject
>>> cd testproject
>>> hnu server start
>>>
>>> m2sh load -config mongrel2/conf/myproject-mongrel2.conf 
>>> m2sh start -host localhost
>>>
>>>
>>> Next up would be getting hnu runtests to work as well.
>>>
>>> Do you want this code now?  If so, how should I push this code to you?
>>>
>>> Right now my changes are in a feature branch using git flow.   This is
the first time I've used git flow - it is very handy!
>>>
>>>
>>> - Devon
> 

-- 
Dr Loïc d'Anterroches
Founder Céondo Ltd

w: www.ceondo.com       |  e: loic@ceondo.com
t: +44 (0)207 183 0016  |  f: +44 (0)207 183 0124

Céondo Ltd
Dalton House
60 Windsor Avenue
London
SW19 2RR / United Kingdom

Re: [photon.users] Community Involvement for Photon

From:
Devon Weller
Date:
2011-02-28 @ 17:07
These are done.

- Devon


Re: [photon.users] Community Involvement for Photon

From:
Loic d'Anterroches
Date:
2011-03-01 @ 19:07
Sorry for the delay Devon, my youngest son was sick, had to pick him
from the daycare and take care of him. I hope a good night will make him
good.

Regards,
loïc

On 2011-02-28 18:07, Devon Weller wrote:
> 
> These are done.
> 
> - Devon
> 
> 
> 
> 
> 
> 
> 
> On Feb 28, 2011, at 10:33 AM, Loic d'Anterroches wrote:
> 
>> Hi Devon,
>>
>> quick look at the patch. Please ensure to use 4 spaces and not tabs for
>> the indentation.
> 
> Will do.  I'll get used to using spaces and not tabs before too long.
> 
> 
>> You should also remove your personal path from the paths.
> 
> Ha!  Yeah - that would help...
> 
> 
>> Maybe you can directly name the application "helloworld" in the project
>> template, that way we can easily add a "chat" application and a
>> "tutorial" application reflecting the tutorial I will have to write.
> 
> Yep - totally agree.  You should just be able to drop in new apps in the
project_template/apps directory now.
> 
> 
>>
>> What do you think?
>>
>> For the rest, perfect!
>> loïc
>>
>> On 2011-02-28 16:45, Devon Weller wrote:
>>>
>>> Will do.  Please find the patch file attached.
>>>
>>> - Devon
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Feb 28, 2011, at 9:34 AM, Loic d'Anterroches wrote:
>>>
>>>> Hi Devon,
>>>>
>>>> this is great. Just do a $ git diff develop
>>>> it should provide you with a good diff of your changes. If fine, I will
>>>> apply and give you write access to the repository, you will then be able
>>>> to directly push into develop.
>>>>
>>>> loïc
>>>>
>>>> On 2011-02-28 15:26, Devon Weller wrote:
>>>>> Loic,
>>>>>
>>>>> I modified the app template directories and photon\manager\Init so 
that the following sequence now works:
>>>>>
>>>>> hnu init testproject
>>>>> cd testproject
>>>>> hnu server start
>>>>>
>>>>> m2sh load -config mongrel2/conf/myproject-mongrel2.conf 
>>>>> m2sh start -host localhost
>>>>>
>>>>>
>>>>> Next up would be getting hnu runtests to work as well.
>>>>>
>>>>> Do you want this code now?  If so, how should I push this code to you?
>>>>>
>>>>> Right now my changes are in a feature branch using git flow.   This 
is the first time I've used git flow - it is very handy!
>>>>>
>>>>>
>>>>> - Devon
>>>
>>
>> -- 
>> Dr Loïc d'Anterroches
>> Founder Céondo Ltd
>>
>> w: www.ceondo.com       |  e: loic@ceondo.com
>> t: +44 (0)207 183 0016  |  f: +44 (0)207 183 0124
>>
>> Céondo Ltd
>> Dalton House
>> 60 Windsor Avenue
>> London
>> SW19 2RR / United Kingdom
> 

-- 
Dr Loïc d'Anterroches
Founder Céondo Ltd

w: www.ceondo.com       |  e: loic@ceondo.com
t: +44 (0)207 183 0016  |  f: +44 (0)207 183 0124

Céondo Ltd
Dalton House
60 Windsor Avenue
London
SW19 2RR / United Kingdom

Re: [photon.users] Community Involvement for Photon

From:
Loic d'Anterroches
Date:
2011-02-28 @ 20:33
Devon,

very good. I will test/apply it during the day tomorrow. I will also add
the unit tests. This will allow you to see how the test client is
emulating GET/POST requests to test the views. I may adapt it just a
little to split the generateFiles into one part for the "project" and
one for the "app". Nothing fundamentally different.

loïc

On 2011-02-28 18:07, Devon Weller wrote:
> 
> These are done.
> 
> - Devon
> 
> 
> 
> 
> 
> 
> 
> On Feb 28, 2011, at 10:33 AM, Loic d'Anterroches wrote:
> 
>> Hi Devon,
>>
>> quick look at the patch. Please ensure to use 4 spaces and not tabs for
>> the indentation.
> 
> Will do.  I'll get used to using spaces and not tabs before too long.
> 
> 
>> You should also remove your personal path from the paths.
> 
> Ha!  Yeah - that would help...
> 
> 
>> Maybe you can directly name the application "helloworld" in the project
>> template, that way we can easily add a "chat" application and a
>> "tutorial" application reflecting the tutorial I will have to write.
> 
> Yep - totally agree.  You should just be able to drop in new apps in the
project_template/apps directory now.
> 
> 
>>
>> What do you think?
>>
>> For the rest, perfect!
>> loïc
>>
>> On 2011-02-28 16:45, Devon Weller wrote:
>>>
>>> Will do.  Please find the patch file attached.
>>>
>>> - Devon
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Feb 28, 2011, at 9:34 AM, Loic d'Anterroches wrote:
>>>
>>>> Hi Devon,
>>>>
>>>> this is great. Just do a $ git diff develop
>>>> it should provide you with a good diff of your changes. If fine, I will
>>>> apply and give you write access to the repository, you will then be able
>>>> to directly push into develop.
>>>>
>>>> loïc
>>>>
>>>> On 2011-02-28 15:26, Devon Weller wrote:
>>>>> Loic,
>>>>>
>>>>> I modified the app template directories and photon\manager\Init so 
that the following sequence now works:
>>>>>
>>>>> hnu init testproject
>>>>> cd testproject
>>>>> hnu server start
>>>>>
>>>>> m2sh load -config mongrel2/conf/myproject-mongrel2.conf 
>>>>> m2sh start -host localhost
>>>>>
>>>>>
>>>>> Next up would be getting hnu runtests to work as well.
>>>>>
>>>>> Do you want this code now?  If so, how should I push this code to you?
>>>>>
>>>>> Right now my changes are in a feature branch using git flow.   This 
is the first time I've used git flow - it is very handy!
>>>>>
>>>>>
>>>>> - Devon
>>>
>>
>> -- 
>> Dr Loïc d'Anterroches
>> Founder Céondo Ltd
>>
>> w: www.ceondo.com       |  e: loic@ceondo.com
>> t: +44 (0)207 183 0016  |  f: +44 (0)207 183 0124
>>
>> Céondo Ltd
>> Dalton House
>> 60 Windsor Avenue
>> London
>> SW19 2RR / United Kingdom
> 

-- 
Dr Loïc d'Anterroches
Founder Céondo Ltd

w: www.ceondo.com       |  e: loic@ceondo.com
t: +44 (0)207 183 0016  |  f: +44 (0)207 183 0124

Céondo Ltd
Dalton House
60 Windsor Avenue
London
SW19 2RR / United Kingdom