Support for access control lists. ''from gcds:'' 1 project for all accounts on gitorious? sub-project membership? how should gitorious account system work?

+

:Support for access control lists. ''from gcds:'' 1 project for all accounts on gitorious? sub-project membership? how should gitorious account system work?

'''Discussion'''

'''Discussion'''

Line 43:

Line 43:

'''Owner:''' ''(unknown)''

'''Owner:''' ''(unknown)''

−

How do the people get accounts on gitorious? Telling them to make one themselves puts up a big hurdle that people don't need.

+

:How do the people get accounts on gitorious? Telling them to make one themselves puts up a big hurdle that people don't need.

'''Discussion'''

'''Discussion'''

Line 55:

Line 55:

'''Owner:''' Ian Monroe

'''Owner:''' Ian Monroe

−

Commit filter is not implemented on gitorious (or something similar) though rss feeds for each module you are interested in can be subscribed to in the meantime

+

:Commit filter is not implemented on gitorious (or something similar) though rss feeds for each module you are interested in can be subscribed to in the meantime.

'''Discussion'''

'''Discussion'''

Line 67:

Line 67:

'''Owner:''' ''(unknown)''

'''Owner:''' ''(unknown)''

−

acltest, docbook, EOL/UTF-8

+

:acltest, docbook, EOL/UTF-8

−

A web hook isn't good enough for these because they have to run and return whether to allow the push, for every single push to every kde repo.

+

:A web hook isn't good enough for these because they have to run and return whether to allow the push, for every single push to every kde repo.

'''Discussion'''

'''Discussion'''

Line 83:

Line 83:

'''Owner:''' ''(unknown)''

'''Owner:''' ''(unknown)''

−

* BUG/CCMAIL

+

:* BUG/CCMAIL

−

* email/CIA

+

:* email/CIA

−

* license header checks

+

:* license header checks

−

Gitorious is supposed to provide web hooks for this; have they started? who volunteered to write the scripts once that's done?

+

:Gitorious is supposed to provide web hooks for this; have they started? who volunteered to write the scripts once that's done?

'''Discussion'''

'''Discussion'''

Line 99:

Line 99:

'''Owner:''' David Faure

'''Owner:''' David Faure

−

not possible with git, broken by design.

+

:not possible with git, broken by design.

'''Discussion'''

'''Discussion'''

Line 110:

Line 110:

'''Owner:''' Simon

'''Owner:''' Simon

−

It's work, but maybe some people would like it. NEEDED for documentation, in order to get it back into SVN for the translators/scripty/?

+

:It's work, but maybe some people would like it. NEEDED for documentation, in order to get it back into SVN for the translators/scripty/?

'''Discussion'''

'''Discussion'''

Line 122:

Line 122:

{{Progress bar|10}}

{{Progress bar|10}}

−

At least minimal documentation about how to checkout, how to get a gitorious account, how to request a merge needed, other git documentation and links to other git information would be very useful also.

+

:At least minimal documentation about how to checkout, how to get a gitorious account, how to request a merge needed, other git documentation and links to other git information would be very useful also.

Remaining issues that must be solved before the migration.

e-mail notifications

1% completed (estimate)

Owner: (Gitorious wants to fix this)

Everyone added to the kde-developers group gets an e-mail when anyone makes a merge request to any of our projects. This is undesirable (as most kde devs are not Amarok devs and many other permutations). A solution for this will have to be developed on gitorious before all of kde goes to gitorious

Discussion

See response to ACL support -Mike Arthur 19/10/2009 16:09

just because someone needs commit rights to a project doesn't mean they want to listen to all merge requests for that project. also what about kwin vs plasma vs konqueror vs whatever-else in kdebase... --Chani

Method for joining the team

0% completed (estimate)

Owner:(unknown)

A button to join the kde-developers team would be very useful instead of needing to poke admins. This would probably use a similar mechanism to current method for granting svn accounts, i.e. two people vouch for a person to let them in the team.

Discussion

ACL support

0% completed (estimate)

Owner:(unknown)

Support for access control lists. from gcds: 1 project for all accounts on gitorious? sub-project membership? how should gitorious account system work?

Discussion

Each project needs owned by one group so the kdebase/kdepim/etc groups might work well here -Mike Arthur 19/10/2009 16:08

wait, what? why? iirc we decided everyone would be in the kde-developers group... --Chani

Account setup on Gitorious

0% completed (estimate)

Owner:(unknown)

How do the people get accounts on gitorious? Telling them to make one themselves puts up a big hurdle that people don't need.

Discussion

Really? It just requires an email/username/password, I'd be amazed if that's a "big hurdle" for people... -Mike Arthur 19/10/2009 16:02

Commitfilter

98% completed (estimate)

Owner: Ian Monroe

Commit filter is not implemented on gitorious (or something similar) though rss feeds for each module you are interested in can be subscribed to in the meantime.

Discussion

fixed, but how does one subscribe to notices?

pre-commit hooks

0% completed (estimate)

Owner:(unknown)

acltest, docbook, EOL/UTF-8

A web hook isn't good enough for these because they have to run and return whether to allow the push, for every single push to every kde repo.

Discussion

gitorious guys said they *might* be willing to allow a few scripts on their server for kde as a special exception, iirc. --chani

Yes, at least for basic things, heavier things like doc building would probably have to be mirrored (goes for pre/post) --johan-s

post-commit hooks

0% completed (estimate)

Owner:(unknown)

BUG/CCMAIL

email/CIA

license header checks

Gitorious is supposed to provide web hooks for this; have they started? who volunteered to write the scripts once that's done?

At least minimal documentation about how to checkout, how to get a gitorious account, how to request a merge needed, other git documentation and links to other git information would be very useful also.