librelist archives

« back to archive

Photon roadmap

Photon roadmap

From:
William Martin
Date:
2012-07-31 @ 11:58
Hi,

What do you think to speak about a roadmap for photon ?
We are not here to speak about date or deadline, just new components,
utility scripts that can help you.

I start with 3 points :

1) i18n
Create a tool to generate the PO template from php code and files into
template's folder.
- Basic mode : Generate a Big POT file for all the project
- Advance mode : From a directory map file, generate multiple POT
file. It's allow to reuse your translate PO file between projects for
common part.

2) Docs
No doc is hard for new developers.
I have start to write a book about photon but i really don't have the
time to continue it before next year !
I am ready to share my start of work to create a online doc with
sample. Code sample are a very important part of the doc.

3) The Website
I think we need to publish the doc and code sample on the website.
Maybe we can create a repository/project for the photon website to
allow more developers than "Loic" to update it.

William

Re: [photon.users] Photon roadmap

From:
Loic d'Anterroches
Date:
2012-07-31 @ 12:16
Hello,

On 2012-07-31 13:58, William MARTIN wrote:
> Hi,
> 
> What do you think to speak about a roadmap for photon ?
> We are not here to speak about date or deadline, just new components,
> utility scripts that can help you.
> 
> I start with 3 points :
> 
> 1) i18n
> Create a tool to generate the PO template from php code and files into
> template's folder.
> - Basic mode : Generate a Big POT file for all the project
> - Advance mode : From a directory map file, generate multiple POT
> file. It's allow to reuse your translate PO file between projects for
> common part.

We need to reuse the work done for Pluf, this is working pretty well.

> 2) Docs
> No doc is hard for new developers.
> I have start to write a book about photon but i really don't have the
> time to continue it before next year !
> I am ready to share my start of work to create a online doc with
> sample. Code sample are a very important part of the doc.
> 
> 3) The Website
> I think we need to publish the doc and code sample on the website.
> Maybe we can create a repository/project for the photon website to
> allow more developers than "Loic" to update it.

Yes, we need to update the docs. My problem is that I have the secret
key in my git repository with the website. So, I need to change this.

In fact, I should push the code on baregit.com to allow collaboration. I
will do it asap.

For my "own" roadmap for Photon:

- asset managements to have the crc32 of the file in the url for each
  asset. crc32 coming from the .phar crc32. This would allow easy
  "permanent" caching and the possible use of cloudfront & cie.
- a generic group and permission system, like for Pluf but with
  the ability to select the backend and use your own "references" to
  define the "id" of a user/group.

The design of the website should definitely be updated together with a
wiki to have community documentation and a blog. As I am refocusing some
of my efforts, please keep pinging me about this, as it is now on my
todo list :) As I am not a designer, I may buy a "website theme", if you
find/know a nice one, just let me know.

loïc