[RFC] RFC process/management

These requests for comments/change have lead to an implemented feature that has been successfully merged into the 3.1/Ascraeus branch. Everything listed in this forum will be available in phpBB 3.1.
User avatar
nickvergessen
Former Team Member
Posts: 733
Joined: Sun Oct 07, 2007 11:54 am
Location: Stuttgart, Germany
Contact:

Re: [RFC] RFC process/management

Post by nickvergessen » Sun Feb 08, 2015 4:46 pm

I think we should narrow it down to: Idea -> Ticket -> Pull Request
  • Ideas: idea pops up, users rate it, bikesheeding can be down by the main-audiance
  • Ticket: ideas discussion is summed up, details about implementations are discussed
  • PR: final discussion of implementation
Area51 would still be used for discussion of the development process, the unstable releases, etc.
But you would not need to read it anymore to get involved into development.
Member of the Development-TeamNo Support via PM

Nicofuma
3.2 Release Manager
3.2 Release Manager
Posts: 297
Joined: Sun Apr 13, 2014 1:40 am
Location: Paris

Re: [RFC] RFC process/management

Post by Nicofuma » Sun Feb 08, 2015 6:43 pm

So:

Ideas -> JIRA -> Github
the discussion on the RFC take place on JIRA but if it's too long (so if there is a real concern) we to area51 (we create a discussion topic)

I really like this idea, it make more sense than the actual process (Ideas -> Area51 -> JIRA -> Github) and it's also simpler and more dynamic.
Member of the phpBB Development-Team
No Support via PM

Nicofuma
3.2 Release Manager
3.2 Release Manager
Posts: 297
Joined: Sun Apr 13, 2014 1:40 am
Location: Paris

Re: [RFC] RFC process/management

Post by Nicofuma » Mon Feb 09, 2015 9:55 am

Does someone have something else to propose or any concerns about the latest proposal?
naderman wrote:poke
Marc wrote:poke
dhruv.goel92 wrote:poke
bantu wrote:poke
prototech wrote:poke
Member of the phpBB Development-Team
No Support via PM

User avatar
M.Gaetan89
Registered User
Posts: 64
Joined: Tue Jan 28, 2014 7:17 pm
Location: Divonne-les-Bains, France
Contact:

Re: [RFC] RFC process/management

Post by M.Gaetan89 » Mon Feb 09, 2015 7:08 pm

What are all those "Poke" quotes in various posts?

User avatar
JoshyPHP
Registered User
Posts: 348
Joined: Fri Jul 08, 2011 9:43 pm

Re: [RFC] RFC process/management

Post by JoshyPHP » Mon Feb 09, 2015 7:14 pm

A way to alert people via the notification system.

User avatar
M.Gaetan89
Registered User
Posts: 64
Joined: Tue Jan 28, 2014 7:17 pm
Location: Divonne-les-Bains, France
Contact:

Re: [RFC] RFC process/management

Post by M.Gaetan89 » Mon Feb 09, 2015 8:59 pm

Seems obvious now.
Still not used to this new notifications system.
Thanks :)

User avatar
Marc
Development Team Leader
Development Team Leader
Posts: 123
Joined: Thu Sep 09, 2010 11:36 am
Location: Munich, Germany

Re: [RFC] RFC process/management

Post by Marc » Wed Feb 11, 2015 8:23 am

Nicofuma wrote:So:

Ideas -> JIRA -> Github
the discussion on the RFC take place on JIRA but if it's too long (so if there is a real concern) we to area51 (we create a discussion topic)

I really like this idea, it make more sense than the actual process (Ideas -> Area51 -> JIRA -> Github) and it's also simpler and more dynamic.
I'd say that's definitely a nicer approach, especially for people that want to get involved.

Bigger changes can still be discussed here while smaller ones will generally just find their way into the core via a ticket + PR.

To be honest, this is IMHO closer to what we have been practising in the last few months anyway. :?

User avatar
brunoais
Registered User
Posts: 958
Joined: Fri Dec 18, 2009 3:55 pm

Re: [RFC] RFC process/management

Post by brunoais » Tue Feb 17, 2015 12:44 pm

Nicofuma wrote: I really like this idea, it make more sense than the actual process (Ideas -> Area51 -> JIRA -> Github) and it's also simpler and more dynamic.
I prefer that one.
  1. Someone has the idea and posts it in the ideas, while getting some feedback on what it should actually be.
  2. A probable implementor does an RFC to get a code discussion on how to get it done.
  3. A ticket in the tracker to track the change.
  4. A PR in the repository with the actual change in hand.
That looks like the best sequence to make sure it has a new feature has a smooth entering process.
I believe there can be exceptions. E.g.
A popular extension may go directly to RFC.
A bugfix can go directly towards JIRA and github, if no discussion is required, otherwise, directly to the forum.

Comments?
Extra: How much would define a popular extension :D?

Nicofuma
3.2 Release Manager
3.2 Release Manager
Posts: 297
Joined: Sun Apr 13, 2014 1:40 am
Location: Paris

Re: [RFC] RFC process/management

Post by Nicofuma » Tue Feb 17, 2015 2:35 pm

It looks similar to the current official process, which doesn't work.

I don't think that every RFC needs a big discussion (and actually most of them doesn't need any discussion). That's why I prefer to create the ticket directly and a topic only if necessary.
Member of the phpBB Development-Team
No Support via PM

User avatar
RMcGirr83
Registered User
Posts: 357
Joined: Fri Mar 09, 2007 1:51 am
Contact:

Re: [RFC] RFC process/management

Post by RMcGirr83 » Tue Feb 17, 2015 8:50 pm

Nicofuma wrote:I don't think that every RFC needs a big discussion (and actually most of them doesn't need any discussion). That's why I prefer to create the ticket directly and a topic only if necessary.
^ this +1
Do not hire Christian Bullock he won't finish the job and will keep your money

Post Reply