Empathy List Archives

pharo-dev@lists.pharo.org

Pharo Development List

ANN: Introducing PhEPs (Pharo Enhancement Proposals)

Esteban Lorenzano

Tue, May 17, 2022 8:25 AM

Hello,

Some of you were present at PharoDays 2022 were we made a presentation explaining this new way of handling the evolution of Pharo.
In that talk we explained that this is an attempt of having the community involved in more deep way, with a clear (and visible) decision process, taking the model the Python community has been using with success (so why not us? :P).

In a nutshell, the idea is that everybody wanting to work on any kind of enhancement for Pharo can now send their proposal and start a discussion process (a discussion arbitrated by the Pharo Board), and if this discussion leads to an accepted enhancement, the work will be integrated as part of the Pharo Environment.
How it works?

There is a repository: https://github.com/pharo-project/pheps
and a detailed description of the process: https://github.com/pharo-project/pheps/blob/main/phep-0001.md

You will have all the information you need there, but here is a summary of the process (you can also find it in the guidelines PhEP):
0. (Optional, but recommended) the proposer discusses the idea in pharo-dev list or discord, with members of the team, and gather ideas.

The proposer will clone the PhEP repository (pharo-project/pheps) and adds a proposal draft following the required stucture:

the file will not have an ID, hence it needs to be called phep-proposal.md
the proposal will have the header and structure explained in the section Submitting a PhEP (header, abstract, motivation and description).
the proposal will also have a "champion" (which by default is the author itself), responsible for the implementation of the proposal in case is been accepted.

The proposal will be submitted as PR to the PhEP repository.
A mail will be send to pharo-dev mailing list, including the link and the abstract of the proposal.
There will be a discussion process and in case of acceptance of the proposal, an ID will be assigned by the reviewer.
As final stage, the author renames the phep-proposal.md file as phep-ID.md and includes the ID in the phep file header (this step can be performed by the reviewer if he decides so).
The reviewer will merge the PR

In the next days I will be sending a couple fo PhEPs to add to those already there, to get the process started.
Do not hesitate to participate!
Cheers,
Esteban

ps: Yes, I am aware "pheps" sounds fun on english :)

Hello, Some of you were present at PharoDays 2022 were we made a presentation explaining this new way of handling the evolution of Pharo. In that talk we explained that this is an attempt of having the community involved in more deep way, with a clear (and visible) decision process, taking the model the Python community has been using with success (so why not us? :P). In a nutshell, the idea is that everybody wanting to work on any kind of enhancement for Pharo can now send their proposal and start a discussion process (a discussion arbitrated by the Pharo Board), and if this discussion leads to an accepted enhancement, the work will be integrated as part of the Pharo Environment. How it works? - There is a repository: https://github.com/pharo-project/pheps - and a detailed description of the process: https://github.com/pharo-project/pheps/blob/main/phep-0001.md You will have all the information you need there, but here is a summary of the process (you can also find it in the guidelines PhEP): 0. (Optional, but recommended) the proposer discusses the idea in pharo-dev list or discord, with members of the team, and gather ideas. 1. The proposer will clone the PhEP repository (pharo-project/pheps) and adds a proposal draft following the required stucture: - the file will not have an ID, hence it needs to be called `phep-proposal.md` - the proposal will have the header and structure explained in the section **Submitting a PhEP** (header, abstract, motivation and description). - the proposal will also have a "champion" (which by default is the author itself), responsible for the implementation of the proposal in case is been accepted. 2. The proposal will be submitted as PR to the PhEP repository. 3. A mail will be send to `pharo-dev` mailing list, including the link and the abstract of the proposal. 4. There will be a discussion process and in case of acceptance of the proposal, an ID will be assigned by the reviewer. 5. As final stage, the author renames the `phep-proposal.md` file as `phep-ID.md` and includes the ID in the phep file header (this step can be performed by the reviewer if he decides so). 6. The reviewer will merge the PR In the next days I will be sending a couple fo PhEPs to add to those already there, to get the process started. Do not hesitate to participate! Cheers, Esteban ps: Yes, I am aware "pheps" sounds fun on english :)