search

pear / pear-svn-git

tool to move pear svn repositories to git
5 stars 8 forks source link

Create github team #4

Closed CloCkWeRX closed 12 years ago

CloCkWeRX commented 12 years ago

When migrating a package; we've been setting up a team just for that package.

If we could do that step via the Team API; that would be handy. http://develop.github.com/p/orgs.html

For a much more sophisticated version of this; identifying the pearweb author against a github user account and adding them to the team would be useful

convissor commented 12 years ago

It seems simpler to just use the one "pear-dev" team. That makes it easy for other developers to help out. Overstepping boundaries is a rare problem in PEAR.

CloCkWeRX commented 12 years ago

At first I thought that too - a lot of red tape actually harming the ability for people to contribute = bad.

But; this is github - anyone can fork + pull request. I'm actually keen to encourage that sort of behaviour more if someone proposes a patch, the package owner should be able to review.

There have been a few cases where an eager contributor has joined pear, been given pear-dev karma and... well not exactly succeeded at getting the quality part right. Having the teams; or at least having the fork + pull request model pushed allows that mentoring to take place.

All of that said we should revisit the concept of collectives (https://wiki.php.net/pear/rfc/pear2_policy); which are trivial to implement via github; or your above idea.

convissor commented 12 years ago

The forking/pulling is great for people who don't have PEAR accounts or aren't maintainers on that package. But it's a bunch of extra steps for strong peple with good PEAR community standing and for the QA Team / github pear organization "owners."

The transgressions are minor and can mainly be dealt with by education. The account welcome email and policy documents should/can cover this.

Plus, having teams for each package seems like it'll get unwieldy.

Most importantly, I assume the migration scripts are meant to be run by the users doing the migration, not the QA Team and/or "owners" of the pear organization on GitHub. If that's the case, the regular users don't have GitHub permissions to create teams.

convissor commented 12 years ago

The scripts now add the new repository in the pear-dev team. As mentioned, there's no way for regular users to create teams, so doing so in this script is a no-go.