User talk:Argonel: Difference between revisions
mNo edit summary |
|||
| Line 1: | Line 1: | ||
=Remaining issues that must be solved before the migration.= | =Remaining issues that must be solved before the migration.= | ||
== e-mail notifications == | ==e-mail notifications== | ||
{{Progress bar|1.0}} | {{Progress bar|1.0}} | ||
'''Owner:''' (Gitorious wants to fix this) | '''Owner:''' (Gitorious wants to fix this) | ||
| Line 10: | Line 10: | ||
:See response to ACL support -Mike Arthur 19/10/2009 16:09 | :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 | ::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== | ==Method for joining the team== | ||
| Line 19: | Line 22: | ||
'''Discussion''' | '''Discussion''' | ||
| Line 25: | Line 29: | ||
'''Owner:''' ''(unknown)'' | '''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''' | '''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 | :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 | ::wait, what? why? iirc we decided everyone would be in the kde-developers group... --Chani | ||
==Account setup on Gitorious== | ==Account setup on Gitorious== | ||
{{Progress bar|0}} | {{Progress bar|0}} | ||
'''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. | ||
| Line 40: | Line 48: | ||
: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 | :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== | ==Commitfilter== | ||
{{Progress bar|98}} | {{Progress bar|98}} | ||
''' | '''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''' | |||
:fixed, but how does one subscribe to notices? | :fixed, but how does one subscribe to notices? | ||
==pre-commit hooks== | ==pre-commit hooks== | ||
{{Progress bar|0}} | {{Progress bar|0}} | ||
''' | '''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. | |||
'''Discussion''' | |||
:gitorious guys said they *might* be willing to allow a few scripts on their server for kde as a special exception, iirc. --chani | :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 | :: 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== | |||
{{Progress bar|0}} | {{Progress bar|0}} | ||
'''Owner: ''' | '''Owner:''' ''(unknown)'' | ||
' | BUG/CCMAIL<br>email/CIA<br>license header checks<br>gitorious is supposed to provide web hooks for this; have they started? who volunteered to write the scripts once that's done? | ||
'''Discussion:''' | |||
:There is a branch of gitorious called web-hooks http://gitorious.org/gitorious/mainline/commits/web-hooks --Panagiotis Papadopoulos 1 November 2009 | :There is a branch of gitorious called web-hooks http://gitorious.org/gitorious/mainline/commits/web-hooks --Panagiotis Papadopoulos 1 November 2009 | ||
| Line 75: | Line 91: | ||
==Get rid of svn:externals== | |||
{{Progress bar|0}} | {{Progress bar|0}} | ||
'''Owner: | '''Owner:''' David Faure | ||
not possible with git, broken by design. | not possible with git, broken by design. | ||
'''Discussion:''' | |||
:Is there a list of instances of svn::externals anywhere?--[[User:Yokem55|Yokem55]] 19:27, 1 November 2009 (UTC) | :Is there a list of instances of svn::externals anywhere?--[[User:Yokem55|Yokem55]] 19:27, 1 November 2009 (UTC) | ||
| Line 86: | Line 104: | ||
==Snapshot to read-only svn== | ==Snapshot to read-only svn== | ||
{{Progress bar|0}} | {{Progress bar|0}} | ||
'''Owner: | '''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/? | ||
'''Discussion:''' | |||
:Could be done with a git-svn gateway presumably? -Mike Arthur 19/10/2009 16:04 | :Could be done with a git-svn gateway presumably? -Mike Arthur 19/10/2009 16:04 | ||
==[[Development/Tutorials/Git|Techbase Documentation]]== | ==[[Development/Tutorials/Git|Techbase Documentation]]== | ||
'''Owner:''' Chani, greeneg, - ''please help out!'' | |||
{{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. | ||
'''Discussion:''' | |||
Revision as of 03:17, 11 November 2009
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?
Discussion:
- There is a branch of gitorious called web-hooks http://gitorious.org/gitorious/mainline/commits/web-hooks --Panagiotis Papadopoulos 1 November 2009
Get rid of svn:externals
0% completed (estimate)
Owner: David Faure
not possible with git, broken by design.
Discussion:
- Is there a list of instances of svn::externals anywhere?--Yokem55 19:27, 1 November 2009 (UTC)
Snapshot to read-only svn
0% completed (estimate)
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/?
Discussion:
- Could be done with a git-svn gateway presumably? -Mike Arthur 19/10/2009 16:04
Techbase Documentation
Owner: Chani, greeneg, - please help out!
10% completed (estimate)
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.
Discussion: