Hey Hannes,
(we cannot hand out GithHub admin accounts to these repos to everyone).
What do you need to be giving everyone full administrative access for? Not sure
how familiar you are with GitHub however for an organization account, you can
create teams and assign permissions[1] to those teams. Example: people with
karma can be added to the "write access" team so they can merge changes.
Does anyone have the time to give it some love, or create a new one?
As much as I would love a new tool, it sounds like using GitHub for what it was
built for is a better solution here. Sure, you could build a PHP.net version of
GitHub however that is then something custom that needs to be maintained. All
the feature requests you want to build into the new QA site are available within
GitHub by default.
Using GitHub will also lower the barrier for people wanting to propose changes
as many people are now familiar with the GitHub flow style of proposing changes
to open source projects.
I'd be happy to help you out if you are unsure of how to implement any of this
within GitHub so that we can take full advantage of a managed and existing tool
instead of maintaining a custom solution for this.
Thanks,
Jacob.
[1]:
https://help.github.com/articles/permission-levels-for-an-organization-repository
On Sat, 28 Feb 2015, Stelian Mocanita wrote:
I call shotgun on this.
Stelian
On Feb 28, 2015 8:17 PM, "Hannes Magnusson" <[email protected]>
wrote:
Hi all
https://qa.php.net/pulls has been the only way for most people to deal
with GitHub Pull Requests - but lets be honest.. it sucks.
Some projects would like to use GitHub labels for example, but have no
way of adding/removing labels as the qa interface doesn't support it
(we cannot hand out GithHub admin accounts to these repos to
everyone).
Does anyone have the time to give it some love, or create a new one?
We also need better integration in general with GitHub.
Some ideas:
- Consistent mail to the appropriate mailinglists about new PRs
- Mail about new comments
- Mail about status changes (closed/merged)
- Mail about commits added/removed from PR
- List all Repos with oustanding PR
- "My favorite repos"
- Adding/removing labels
- Smarter lookups (we currently seem to hit rate-limiting easily)
It doesn't need to be hosted on qa.php.net, we can just as well create
https://github.php.net or whatever.
I'd prefer if they layout was consistent with the rest of PHP
websites, using http://git.php.net/?p=web/shared.git;a=summary like
the others.
Any takers?
-Hannes
--
PHP Webmaster List Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP Webmaster List Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php