User talk:Argonel: Difference between revisions

From KDE TechBase
mNo edit summary
mNo edit summary
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
=Remaining issues that must be solved before the migration.=
[http://quickgit.kde.org/index.php?p=kdelibs.git&a=commitdiff&h=2b7bb340d71a4c97604adc1952db261be7f2a35a&hp=5d5feb138ae85693a5217b99ec646745825c43ea kdelibs.git&a=commitdiff&h=2b7bb340d7]


== e-mail notifications ==
[http://quickgit.kde.org/index.php?p=kdelibs.git&a=blobdiff&h=01d4050a347a54af3266e85d554b9075cab7616d&hp=0b4a99a0b207b76e6cdfced2e624d6ea4171f62b&hb=2b7bb340d71a4c97604adc1952db261be7f2a35a&f=khtml/CMakeLists.txt khtml/CMakeLists.txt]
{{Progress bar|1.0}}
'''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
http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi


'''Discussion'''
http://techbase.kde.org/Development/CMake/Addons_for_KDE


:See response to ACL support -Mike Arthur 19/10/2009 16:09
; KDE4_ADD_APP_ICON(appsources pattern)
::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
*: Mac OS X and Windows only: Adds application icon to target source list. This macro adds an application icon to the specified target. Mac OS X notes: the application icon is added to a Mac OS X bundle so that Finder and friends show the right thing. You need to provide a 128x128 version of the icon for this to work. Windows notes: the application icon(s) are compiled into the application binary.  
*:Parameters:
*# 'appsources'  - specifies the list of source files
*# 'pattern'    - regular expression for searching application icons


==Method for joining the team==
Examples:
{{Progress bar|0}}
<syntaxhighlight lang="cmake">
'''Owner:''' ''(unknown)''
KDE4_ADD_APP_ICON(myapp_sources "pics/cr*-myapp.png")
</syntaxhighlight>
<syntaxhighlight lang="cmake">
KDE4_ADD_APP_ICON(myapp_sources "${KDE4_INSTALL_DIR}/share/icons/oxygen/*/apps/myapp.png")
</syntaxhighlight>


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.
<pre>
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} ${KDE4_ENABLE_EXCEPTIONS}")
#set_source_files_properties(${khtmldom_STAT_SRCS} PROPERTIES COMPILE_FLAGS ${KDE4_ENABLE_EXCEPTIONS})
</pre>


'''Discussion'''
http://en.wikipedia.org/wiki/Help:List


 
http://en.wikipedia.org/wiki/Help:Wiki_markup#Nowiki
==ACL support==
{{Progress bar|0}}
'''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==
{{Progress bar|0}}
 
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'''<br>
: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==
{{Progress bar|98}}
'''Notes'''<br>
 
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
Ian Monroe
 
:fixed, but how does one subscribe to notices?
 
 
==pre-commit hooks==
{{Progress bar|0}}
'''Notes'''<br>
 
acltest, docbook, EOL/UTF-8
<br>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.
: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'''
{{Progress bar|0}}
'''Owner: '''
 
'''Notes'''
 
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?
 
: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'''
{{Progress bar|0}}
'''Owner: David Faure'''
'''Notes'''
 
not possible with git, broken by design.
:Is there a list of instances of svn::externals anywhere?--[[User:Yokem55|Yokem55]] 19:27, 1 November 2009 (UTC)
 
 
==Snapshot to read-only svn==
{{Progress bar|0}}
'''Owner: Simon'''
 
'''Notes'''
 
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/?
:Could be done with a git-svn gateway presumably? -Mike Arthur 19/10/2009 16:04
 
 
 
 
==[[Development/Tutorials/Git|Techbase Documentation]]==
{{Progress bar|10}}
'''Owner:''' Chani, greeneg, - ''please help out!''
'''Notes'''
 
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.

Latest revision as of 09:45, 20 July 2012

kdelibs.git&a=commitdiff&h=2b7bb340d7

khtml/CMakeLists.txt

http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi

http://techbase.kde.org/Development/CMake/Addons_for_KDE

KDE4_ADD_APP_ICON(appsources pattern)
  • Mac OS X and Windows only: Adds application icon to target source list. This macro adds an application icon to the specified target. Mac OS X notes: the application icon is added to a Mac OS X bundle so that Finder and friends show the right thing. You need to provide a 128x128 version of the icon for this to work. Windows notes: the application icon(s) are compiled into the application binary.
    Parameters:
    1. 'appsources' - specifies the list of source files
    2. 'pattern' - regular expression for searching application icons

Examples:

KDE4_ADD_APP_ICON(myapp_sources "pics/cr*-myapp.png")
KDE4_ADD_APP_ICON(myapp_sources "${KDE4_INSTALL_DIR}/share/icons/oxygen/*/apps/myapp.png")
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} ${KDE4_ENABLE_EXCEPTIONS}")
#set_source_files_properties(${khtmldom_STAT_SRCS} PROPERTIES COMPILE_FLAGS ${KDE4_ENABLE_EXCEPTIONS})

http://en.wikipedia.org/wiki/Help:List

http://en.wikipedia.org/wiki/Help:Wiki_markup#Nowiki