Task #27065
Improve the CLA process
| Status: | Closed | Start date: | 2011-05-26 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | Extbase | |||
| Target version: | - | |||
| Has patch: | No | Tags: | ETM, ETM1 | |
| Votes: | 1 (View) |
Description
From the ExtbaseTeamMeeting 2011-05-26:
- We need a CLA, as we sometimes forward-port fixes/features to FLOW3
- currently a big hurdle (takes very long), we will work on that.
- It's on Karstens todo list
History
Updated by Markus Günther 10 months ago
- Category set to Extbase
- Status changed from New to Needs Feedback
Is it still relevant?
Updated by Stefan Neufeind 10 months ago
How about looking for the 50 most-active current people on review.typo3.org or so, seeing which haven't yet signed a CLA and asking them to do a real-life test of jumping through the CLA-hoops? We'll then know if the CLA-process works in real life.
Updated by Markus Günther 9 months ago
- Status changed from Needs Feedback to On Hold
We actually have the CLA in the extbase team. Is this still relevant? The issue is on hold at the moment.
Updated by Bastian Waidelich 9 months ago
- Status changed from On Hold to Closed
Markus Günther wrote:
We actually have the CLA in the extbase team. Is this still relevant?
This issue was about the bad workflow when new contributors sign the CLA (which is a requirement for all contributions to FLOW3/Phoenix, thus most of contributions for Extbase).
So, yes, this is still relevant. But it's not really a problem of the Extbase team (we had this in here, cause we discussed it in the first Extbase Team Meeting).
I'll close the issue for now. Hopefully the approval process is better in the meantime.